pattern-dev

Start with the shared pattern development guidance in:

• docs/common/ai/pattern-development-guide.md

Read that guide first. It is the canonical reference.

Runtime notes:

• Use the ct skill, or read skills/ct/SKILL.md, when you need CLI command details.
• If your runtime supports delegation, pass file paths rather than pasted summaries.

Runtime-Specific Notes

Claude Code

• Use EnterPlanMode before building.
• Scale the plan to the problem:
  • simple pattern: 2-3 sentences
  • medium pattern: short list
  • complex pattern: structured plan with entities, relationships, and actions
• Delegate by role when that helps:

Task({
  prompt: "Implement [feature]. Keep it simple, one file.",
  subagent_type: "pattern-maker"
})

Task({
  prompt: "Deploy and test [pattern].",
  subagent_type: "pattern-user"
})

Task({
  prompt: "Review [file] for violations.",
  subagent_type: "pattern-critic"
})

• Run a critic pass before first deploy unless the change is a tiny, low-risk fix.
• At useful milestones, offer a commit.

Other runtimes

• Preserve the same rhythm even when the invocation syntax differs:
  • plan first
  • keep the first slice runnable
  • separate implementation, runtime testing, and critique when the task is large enough to justify it

Phase skills consult as needed:

• Types: docs/common/concepts/types-and-schemas/
• Actions/handlers: docs/common/concepts/action.md, docs/common/concepts/handler.md
• Testing: docs/common/workflows/pattern-testing.md
• Components: packages/patterns/catalog/catalog.tsx — the authoritative, type-checked component catalog. Story files in packages/patterns/catalog/stories/ show live usage for each component. Also see docs/common/components/COMPONENTS.md for narrative docs.
• Debugging: docs/development/debugging/