update-rules
Update Rules: CLAUDE.md Maintenance
After every correction, end with: "Update your CLAUDE.md so you don't make that mistake again." — Boris Cherny, creator of Claude Code
Activation
When user invokes /update-rules or says "update rules" or "add to CLAUDE.md":
Process
1. Identify the Lesson
If $ARGUMENTS provided, use that as the lesson context. Otherwise, analyze the recent conversation for:
- Corrections the user made
- Mistakes that were pointed out
- Preferences that were expressed
- Patterns that should be followed
More from potatoman03/runbook
runbook
Claude Code productivity system based on tips from the Claude Code team. Provides commands for parallel worktrees, plan reviews, CLAUDE.md maintenance, tech debt hunting, auto-fixing, code grilling, elegant refactors, visual explanations, and subagent orchestration. Use when wanting to work more effectively with Claude Code.
5explain
Generate visual explanations of code, architecture, or concepts. Creates HTML presentations, ASCII diagrams, and interactive visualizations. Use for learning unfamiliar code or explaining to others.
1techdebt
Find and kill duplicated code and technical debt. Run at the end of every session to clean up. Based on the Claude Code team practice of building a /techdebt slash command.
1grill
Get grilled on your changes before making a PR. Claude acts as a rigorous reviewer, asking probing questions and not approving until you demonstrate understanding. Use to catch issues before they reach code review.
1elegant
Scrap a mediocre solution and implement the elegant one. Use after a fix feels hacky or over-complicated. Claude uses all accumulated context to find the right solution. Based on the prompting pattern from the Claude Code team.
1plan-review
Review a plan as a staff engineer would. Use when you have a plan and want rigorous feedback before implementation. Catches issues, suggests alternatives, and identifies risks. Based on the Claude Code team practice of having a second Claude review plans.
1