菜单
Manage the project's recipes and how-to sheets. List them as a table, or create and update one from the canonical template. Use when the user wants to list, create, update, or cook a recipe.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | 12-cook |
| description | Manage project recipes/how-to sheets by listing, creating, updating, researching, or applying a recipe. Use for recipe, cook, /cook, list, new, update, research, apply. |
| argument-hint | list | upsert | research | apply |
Maintains recipe how-to sheets. Project recipes live in aidd_docs/recipes/; bundled recipes ship inside this skill under assets/recipes/.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | list | List every recipe as a table | none |
| 02 | upsert | Create or update one recipe from the template | recipe topic + fields |
| 03 | research | Survey modern alternatives, gaps, and counter-intuitive wins | recipe or topic |
| 04 | apply | Execute a recipe on the project as a confirmed todo list | recipe |
Run list to survey project and bundled recipes, research to gather insights, upsert to author one, apply to run an existing one against the project. Always run research before authoring or substantially updating a recipe — never draft from memory alone. Run list first when the user names no recipe.
Before running an action, read its file in actions/, not only the table or assets.
references/recipe-locations.md: where project and bundled recipes live, how resolution works, and when writes target each home.references/recipe-contract.md: the rules every recipe file follows; upsert writes to it.assets/recipe-template.md: the canonical recipe scaffold upsert renders from, and the shape list parses.assets/recipes/: bundled recipes shipped with this skill.Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.