Getting started
Adopt the playbook in your project in under an hour.
The playbook is designed to be adopted incrementally — you can pull one pillar at a time, copy the templates that fit, and wire the gate scripts as you go.
60-minute adoption path
- Copy
CLAUDE.md(andAGENTS.mdif you don't already have one) from templates into your repo root. Customise the non-negotiables to your stack. - Add the
MEMORY.mdindex + a.agent-memory/directory. Every lesson learned becomes a one-file memory. - Pick 2-3 gate scripts from scripts — start with
check-file-size,check-no-any,check-named-exports. Wire them as apnpm check:quality-gatesscript. - Stand up
docs/adr/with ADR-0001 (Philosophy) using the ADR template. - Adopt the PR-intent manifest (template) on the next PR.
That's it for day one. Everything else flows from these.
Per-pillar deeper adoption
| Pillar | Most-impactful first move |
|---|---|
| Architecture | Modular boundary table in AGENTS.md |
| Security | Threat model skeleton + vault stub |
| UI / UX | Tokens + 8-10 primitives in packages/ui |
| Quality | Gate orchestrator + per-package coverage targets |
| Governance | PR-intent gate + tombstone convention |
| AI-collaboration | CLAUDE.md + MEMORY pattern |
For agents working in adopting repos
If you're an agent landing in a repo that has adopted this playbook:
- Read
CLAUDE.mdfirst. - Read
AGENTS.mdto find which package to touch. - Pull the relevant doc from this site via raw URL:
https://playbook.agentskit.io/raw/<path>.md. - Follow the per-pillar discipline.
- Update memory when a lesson lands.
Not adopting wholesale?
That's fine. The playbook is modular. Take what fits; leave the rest. Each pattern doc explains the failure mode it prevents — if you don't have that failure mode, you don't need that pattern.