菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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".
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.
| name | maker:help |
| description | 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. |
Shows available commands with context-aware recommendations. Adapts based on current project state.
maker:help.maker:kickoff and after first maker:build.Read .maker/project_state.md if it exists to determine context.
## Maker Commands
| Command | What it does |
|---|---|
| `/maker:kickoff` | Initialize project context and preferences |
| `/maker:discover` | Interactive product discovery — flesh out what you're building |
| `/maker:research [topic]` | Investigate technology, APIs, competitors, or market |
| `/maker:architect` | Design project structure and record technical decisions |
| `/maker:build` | Generate code from the architecture plan |
| `/maker:status` | See project state, progress, and next steps |
| `/maker:help` | This menu |
Based on project state, add a recommendation section:
No .maker/project_state.md:
### Where to Start
You don't have a project set up yet.
→ `/maker:kickoff` — Let's get started.
Has profile but no product context:
### Recommended Next
→ `/maker:discover` — Let's figure out what you're building.
Has product context but no architecture:
### Recommended Next
→ `/maker:architect` — Product context is ready. Let's plan the technical structure.
→ `/maker:research [topic]` — If you want to investigate a technology or the competitive landscape first.
Has architecture but not built:
### Recommended Next
→ `/maker:build` — Architecture is planned. Ready to generate code.
Fully built:
### Recommended Next
→ Run quality gates (detect commands from `package.json` scripts).
→ `/maker:discover` — Add a new feature or change requirements.
→ `/maker:status` — See the full project state.
None. Help is informational only.