ZajLibrary

One organized home for every Zaj handbook, playbook, topic, template, kit, and directory entry. Structured, searchable, and easy to grow.

Browse topics Tech Stack Laravel CodeCanyon playbook

Browse the library

You are here: ZajLibrary home

Topic-first (default): pick a category → subcategory → topic, then open Learn, Build, or Resources inside that topic.

Shelf browse: use Learn / Build / Resources when you already know reader intent, not which subject folder owns the page.

Full taxonomy: Content architecture.

Shelves

Use shelves when you know what the reader is trying to do (learn, build, reuse) rather than which topic folder owns the page.

Learn & Understand Handbooks, guides, concepts, research, and case studies — the durable knowledge layer.

Build & Create Playbooks, blueprints, SOPs, runbooks, and checklists — design and execute.

Resources Templates, kits, cheat sheets, and reference — reusable assets plus site authoring docs.

Topics Folder view — category → subcategory → topic, with Learn, Build, and Resources inside each topic.

Directories Tools, people, vendors, links, prompts, skills, and products — filterable catalogs.

System Platform architecture, deploy status, Library MCP, roadmap, and plugin inventory.

The decision tree

Use this when you add a new thing to the library: first decide what the reader is trying to do, then choose the shelf and content type.

Content decision tree

Start with the topic home, then route the item to the shelf and content type that matches what someone will do with it.

Built to grow

How this hub works

Every document lives on a topic-first path first; shelf and kind describe reader intent inside that topic.

graph TD
  Root["ZajLibrary"] --> Cat["Category"]
  Cat --> Sub["Subcategory"]
  Sub --> Topic["Topic"]
  Topic --> Learn["Learn & Understand"]
  Topic --> Build["Build & Create"]
  Topic --> Res["Resources"]
  Learn --> L1["Handbooks · Guides · Concepts · Research · Case studies"]
  Build --> B1["Playbooks · Blueprints · SOPs · Runbooks · Checklists"]
  Res --> R1["Templates · Kits · Cheatsheets · Reference"]

Add a page Place it under category/subcategory/topic first, then shelf/kind.

Add a topic Use the taxonomy registry, then add Learn, Build, or Resources pages inside that topic.

Search everything Full-text search in the header on production and preview builds. During local dev, use /browse/ or Library MCP search instead.

Library MCP Connect agents to search and read the corpus — production and local dev endpoints.

# ZajLibrary — documentation context

You are helping the user work with material from ZajLibrary — playbooks, guides, templates, and AI-system docs.

**Mission:** Use the document below as the primary source and help the user apply it.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

## Metadata
- title: ZajLibrary
- url: https://library.zajapps.com/
- status: current
- kind: collection
- description: Topic-first Learn, Build, Resources, Directories, and system docs — one organized, searchable hub.

## Assistant instructions
- Use the document body below as the primary source for this topic and help the user apply it.
- Cite section headings (`##`, `###`) when quoting specific parts.

---

# ZajLibrary

<p class="eyebrow">Browse the library</p>

:::start
**You are here:** **ZajLibrary home**

**Topic-first (default):** pick a **category** → subcategory → topic, then open **Learn**, **Build**, or **Resources** inside that topic.

**Shelf browse:** use **Learn / Build / Resources** when you already know reader intent, not which subject folder owns the page.

Full taxonomy: [Content architecture](/zajlibrary/authoring/content-system/resources/reference/content-architecture/).
:::

## Categories

Start here when you know the subject area. Each category hub lists subcategories only; open one to reach topics and documents.

<CardGrid>
  <LinkCard
    title="Tech Stack"
    description="Frameworks and app stacks — Laravel/CodeCanyon playbooks, templates, and operational guides."
    href="/tech-stack/"
  />
  <LinkCard
    title="Infrastructure"
    description="Hosting, servers, and environment setup that application playbooks depend on."
    href="/infrastructure/"
  />
  <LinkCard
    title="AI Systems"
    description="Agent frameworks, MCP, chat surfaces, and assistant integration patterns."
    href="/ai-systems/"
  />
  <LinkCard
    title="ZajLibrary"
    description="Authoring rules, platform behavior, navigation model, directory catalogs, and system docs."
    href="/zajlibrary/"
  />
</CardGrid>

## Shelves

Use shelves when you know what the reader is trying to do (learn, build, reuse) rather than which topic folder owns the page.

<CardGrid>
  <LinkCard
    title="Learn & Understand"
    description="Handbooks, guides, concepts, research, and case studies — the durable knowledge layer."
    href="/zajlibrary/navigation/library-shelves/resources/reference/learn/"
  />
  <LinkCard
    title="Build & Create"
    description="Playbooks, blueprints, SOPs, runbooks, and checklists — design and execute."
    href="/zajlibrary/navigation/library-shelves/resources/reference/build/"
  />
  <LinkCard
    title="Resources"
    description="Templates, kits, cheat sheets, and reference — reusable assets plus site authoring docs."
    href="/zajlibrary/navigation/library-shelves/resources/reference/resources/"
  />
  <LinkCard
    title="Topics"
    description="Folder view — category → subcategory → topic, with Learn, Build, and Resources inside each topic."
    href="/browse/"
  />
  <LinkCard
    title="Directories"
    description="Tools, people, vendors, links, prompts, skills, and products — filterable catalogs."
    href="/zajlibrary/directory/catalog/"
  />
  <LinkCard
    title="System"
    description="Platform architecture, deploy status, Library MCP, roadmap, and plugin inventory."
    href="/zajlibrary/system/"
  />
</CardGrid>

---

## The decision tree

Use this when you add a new thing to the library: first decide what the reader is trying to do, then choose the shelf and content type.

<ContentDecisionTree />

<p class="eyebrow">Built to grow</p>

## How this hub works

Every document lives on a **topic-first path** first; shelf and kind describe reader intent inside that topic.

```mermaid
graph TD
  Root["ZajLibrary"] --> Cat["Category"]
  Cat --> Sub["Subcategory"]
  Sub --> Topic["Topic"]
  Topic --> Learn["Learn & Understand"]
  Topic --> Build["Build & Create"]
  Topic --> Res["Resources"]
  Learn --> L1["Handbooks · Guides · Concepts · Research · Case studies"]
  Build --> B1["Playbooks · Blueprints · SOPs · Runbooks · Checklists"]
  Res --> R1["Templates · Kits · Cheatsheets · Reference"]
```

<CardGrid stagger>
  <LinkCard
    title="Add a page"
    description="Place it under category/subcategory/topic first, then shelf/kind."
    href="/zajlibrary/authoring/content-system/resources/reference/content-architecture/"
  />
  <LinkCard
    title="Add a topic"
    description="Use the taxonomy registry, then add Learn, Build, or Resources pages inside that topic."
    href="/zajlibrary/authoring/content-system/resources/reference/content-architecture/collections-categories-tags/"
  />
  <LinkCard
    title="Search everything"
    description="Full-text search in the header on production and preview builds. During local dev, use /browse/ or Library MCP search instead."
    href="/browse/"
  />
  <LinkCard
    title="Library MCP"
    description="Connect agents to search and read the corpus — production and local dev endpoints."
    href="/zajlibrary/system/mcp/"
  />
</CardGrid>

# ZajLibrary

> Source: https://library.zajapps.com/

<p class="eyebrow">Browse the library</p>

:::start
**You are here:** **ZajLibrary home**

**Topic-first (default):** pick a **category** → subcategory → topic, then open **Learn**, **Build**, or **Resources** inside that topic.

**Shelf browse:** use **Learn / Build / Resources** when you already know reader intent, not which subject folder owns the page.

Full taxonomy: [Content architecture](/zajlibrary/authoring/content-system/resources/reference/content-architecture/).
:::

## Categories

Start here when you know the subject area. Each category hub lists subcategories only; open one to reach topics and documents.

<CardGrid>
  <LinkCard
    title="Tech Stack"
    description="Frameworks and app stacks — Laravel/CodeCanyon playbooks, templates, and operational guides."
    href="/tech-stack/"
  />
  <LinkCard
    title="Infrastructure"
    description="Hosting, servers, and environment setup that application playbooks depend on."
    href="/infrastructure/"
  />
  <LinkCard
    title="AI Systems"
    description="Agent frameworks, MCP, chat surfaces, and assistant integration patterns."
    href="/ai-systems/"
  />
  <LinkCard
    title="ZajLibrary"
    description="Authoring rules, platform behavior, navigation model, directory catalogs, and system docs."
    href="/zajlibrary/"
  />
</CardGrid>

## Shelves

Use shelves when you know what the reader is trying to do (learn, build, reuse) rather than which topic folder owns the page.

<CardGrid>
  <LinkCard
    title="Learn & Understand"
    description="Handbooks, guides, concepts, research, and case studies — the durable knowledge layer."
    href="/zajlibrary/navigation/library-shelves/resources/reference/learn/"
  />
  <LinkCard
    title="Build & Create"
    description="Playbooks, blueprints, SOPs, runbooks, and checklists — design and execute."
    href="/zajlibrary/navigation/library-shelves/resources/reference/build/"
  />
  <LinkCard
    title="Resources"
    description="Templates, kits, cheat sheets, and reference — reusable assets plus site authoring docs."
    href="/zajlibrary/navigation/library-shelves/resources/reference/resources/"
  />
  <LinkCard
    title="Topics"
    description="Folder view — category → subcategory → topic, with Learn, Build, and Resources inside each topic."
    href="/browse/"
  />
  <LinkCard
    title="Directories"
    description="Tools, people, vendors, links, prompts, skills, and products — filterable catalogs."
    href="/zajlibrary/directory/catalog/"
  />
  <LinkCard
    title="System"
    description="Platform architecture, deploy status, Library MCP, roadmap, and plugin inventory."
    href="/zajlibrary/system/"
  />
</CardGrid>

---

## The decision tree

Use this when you add a new thing to the library: first decide what the reader is trying to do, then choose the shelf and content type.

<ContentDecisionTree />

<p class="eyebrow">Built to grow</p>

## How this hub works

Every document lives on a **topic-first path** first; shelf and kind describe reader intent inside that topic.

```mermaid
graph TD
  Root["ZajLibrary"] --> Cat["Category"]
  Cat --> Sub["Subcategory"]
  Sub --> Topic["Topic"]
  Topic --> Learn["Learn & Understand"]
  Topic --> Build["Build & Create"]
  Topic --> Res["Resources"]
  Learn --> L1["Handbooks · Guides · Concepts · Research · Case studies"]
  Build --> B1["Playbooks · Blueprints · SOPs · Runbooks · Checklists"]
  Res --> R1["Templates · Kits · Cheatsheets · Reference"]
```

<CardGrid stagger>
  <LinkCard
    title="Add a page"
    description="Place it under category/subcategory/topic first, then shelf/kind."
    href="/zajlibrary/authoring/content-system/resources/reference/content-architecture/"
  />
  <LinkCard
    title="Add a topic"
    description="Use the taxonomy registry, then add Learn, Build, or Resources pages inside that topic."
    href="/zajlibrary/authoring/content-system/resources/reference/content-architecture/collections-categories-tags/"
  />
  <LinkCard
    title="Search everything"
    description="Full-text search in the header on production and preview builds. During local dev, use /browse/ or Library MCP search instead."
    href="/browse/"
  />
  <LinkCard
    title="Library MCP"
    description="Connect agents to search and read the corpus — production and local dev endpoints."
    href="/zajlibrary/system/mcp/"
  />
</CardGrid>