bad-patternDocument something to avoid, with the correct alternative, in patterns/bad/anti-patterns.md. Use when the user says "don't do X" or corrects a recurring mistake.
decideRecord architectural or UX decisions and their rationale. Use when the user states a choice and why, asks to document a decision, or asks to save agreed decisions, requirements, patterns, or progress from the conversation.
good-patternSave code, schema, UI, or a script as an approved example in patterns/good. Use when the user points at code and says it is the way to do it.
helpExplain Blueprint Mode and its workflows. Use when the user asks how Blueprint works, how to get started, or where a kind of document belongs.
list-adrsList Architecture Decision Records grouped by status. Use when the user wants to see, filter, or search the ADRs.
onboard-designOpt in to design intent capture by scaffolding design/ux-decisions, optionally a DESIGN.md stub, and optionally reviewing a few existing UI patterns for stated intent. Use when the user asks to set up or enable design intent capture; UI code alone is not a trigger. Safe to rerun.
onboardCreate the Blueprint code/architecture tree for an existing repository, or upgrade one set up by an earlier Blueprint version. Use when the user asks to add Blueprint to an existing repo or upgrade its documentation. Safe to rerun; later runs fill gaps.
requireAdd a functional or non-functional requirement to docs/specs. Use when the user states what the product must do or a measurable target such as latency, uptime, or a security constraint.
setup-repoScaffold a brand-new project with Blueprint documentation and a test setup. Use when the user asks to create a new project with Blueprint; use onboard for an existing codebase.
statusShow what Blueprint has captured in this repo. Use when the user asks what decisions, specs, or patterns are documented, or whether the repo is set up for Blueprint.
supersedeRewrite or retire an existing ADR or UX decision. Use when the user changes a documented choice, asks for an explicit replacement record, or retires a decision.
validateCheck the codebase and its documentation against recorded decisions, boundaries, patterns, specs, and design intent. Use when the user asks for a consistency audit or whether the code still follows the documented decisions.