Using Templates

The knowledge vault ships with templates for client folders, proposals, reports, and more. Here is how to use them.

Onboarding a New Client

Copy the client template to create a new client folder:

cd ~/agency-workspace/knowledge
cp -r clients/_template clients/acme-corp

Edit context.yaml

The key file is context.yaml — it contains machine-readable fields that pipelines use:

contact_name: "Jane Smith"
contact_email: "jane@acme.com"
contact_phone: "(555) 123-4567"
business_name: "Acme Corp"
website: "https://acme.com"
notion_page_id: "abc123-def456"
launch_date: "2026-04-15"

research_notes: "Local bakery, 3 locations, no online ordering"
last_research_date: "2026-03-20"

Fill In Other Template Files

Commit

cd ~/agency-workspace/knowledge
git add clients/acme-corp/
git commit -m "Add client folder: acme-corp"
git push

How Pipelines Use Client Files

Pipelines reference client files via relative paths from $KNOWLEDGE_DIR. For example, the propose pipeline reads:

• clients/[business-name]/brief.md — for scope and requirements
• clients/[business-name]/brand.md — for visual identity
• clients/[business-name]/context.yaml — for contact details and project metadata

The pipeline system prompt construction chain reads system/CLAUDE.md as the base prompt, appends the pipeline definition, and provides instructions to read the relevant client files.

Document Compiler

After a pipeline generates raw output, use the compile command to produce a branded version:

compile [doc-type] [client-name]

The compiler reads system/rules/compile-guidelines.md for formatting rules and applies the client's brand tokens from their brand.md and voice.md files. Output is saved to .output/compiled/.

Tiered Brief Templates

Proposals use tiered briefs based on the client's service tier:

Copy the appropriate template, fill it in, and save as clients/[business-name]/brief.md.