blueprint-mode

Capture decisions and context from the current conversation into blueprint docs, DESIGN.md, and design trees

Record a decision or cross-cutting design rule with rationale. Triages tech vs UX vs DESIGN.md rules vs requirements into the right document type and tree.

Explain Blueprint Mode plugin and available commands. Use when the user asks about Blueprint features, how to use skills, or needs guidance on the intent-capture workflow.

Opt-in. Add design intent capture to a Blueprint repo. Scaffolds design/ux-decisions/, offers to scaffold a minimal community-format DESIGN.md if absent, and can optionally surface a small number of candidate UX decisions found in existing UI/code for the user, developer, or designer to confirm.

Create Blueprint structure from existing repo. Run multiple times to refine.

Show overview of project's Blueprint structure plus important adjacent DESIGN.md context. Use when the user asks about documented decisions, project status, or wants to see what's been captured.

Set up a new repository with Blueprint intent-capture structure from scratch. Use when creating a new project and the user wants to establish specs, ADRs, and patterns from the beginning.

Check code against documented specs, patterns, anti-patterns, ADRs, DESIGN.md, and UX decisions. Use when the user wants to verify consistency, audit the codebase, check spec compliance, or find violations.

Document an anti-pattern to avoid (any subject — code, schema, UI, infra)

Capture good code as a reusable example (any subject — server code, schema, UI, scripts)

Replace or deprecate a previous decision (ADR or UX decision). Use when the user wants to change a tech or UX choice, retire a decision, or remove functionality without replacement.

Add a requirement (functional or non-functional)

List all Architecture Decision Records with their status and summaries. Use when the user wants to see all decisions, review ADR history, or find a specific decision.