-
Clone the repository:
git clone https://github.com/yourusername/claude-cook.git cd claude-cook -
Install to your local Claude Code config for testing:
cp -r .claude/commands ~/.claude/ cp -r .claude/skills ~/.claude/ cp -r .claude/templates ~/.claude/ cp -r .claude/agents ~/.claude/
-
Test the command:
/cook Test feature --well-done
-
Create a new file in
.claude/agents/:.claude/agents/your_chef.md -
Follow the structure:
# Role <what this chef does> # Questions to Ask - <question 1> - <question 2> # Blockers <what causes this chef to block progress> # Output <what this chef contributes to the artifact>
-
Update
.claude/agents/README.mdto document the new chef. -
Submit a PR with:
- The new agent file
- Updated README
- Example showing the chef in action (optional)
Rules live in two places:
- Microwave blockers:
.claude/skills/feature-development/SKILL.md(section: Microwave Blockers) - Phase definitions:
.claude/skills/feature-development/SKILL.md(section: Cooking Steps) - Output formats:
.claude/skills/feature-development/SKILL.md(section: Output Format)
To propose changes:
-
Open an issue describing:
- Current behavior
- Proposed change
- Rationale
-
If approved, submit a PR with:
- Updated SKILL.md
- Updated documentation if needed
- Example artifact showing the change
- Keep PRs focused on a single change
- Update documentation for user-facing changes
- Test with both
--well-doneand--microwavemodes - Include example output when adding features
Be respectful. Focus on the work, not the person. Assume good intent.