Design project structure and record technical decisions. Use when the user says "architect", after product exploration is complete, or when revisiting architecture after a pivot. Does NOT generate source code — that is build's job.
Generate code from the architecture plan. Use when the user says "build", after architect has recorded a plan, or when re-generating after an architecture change. This is the only command that writes source code.
Design the solution interface (UX/UI, API contract, or agent system). Use when transitioning from the product brief to the engineering phase to determine how the product behaves and looks.
Interactive product discovery — what are we building, who is it for, and what does v1 look like. Use when starting product exploration, adding a new feature, revisiting scope or requirements, or when the user says "discover".
Context-aware command menu showing all available maker commands with recommendations based on current project state. Use when the user says "help", asks how to use maker, asks where to start, asks what maker does, or seems unsure what to do next.
Initialize project context and preferences. Use when starting a new project, when the user says "kickoff", or when there is no .maker/project_state.md and the user wants to get started.
Investigate a specific technology, API, library, framework, competitor, or market. Use when the user says "research [topic]", before making a stack decision, when comparing alternatives, or when validating assumptions about users or market. Accepts a topic as argument.
Show project state, progress, and recommended next steps. Use when the user says "status", when returning to a project after time away, or when unsure what to do next. Read-only.