elegant
Elegant: The Better Solution
After a mediocre fix, say: "Knowing everything you know now, scrap this and implement the elegant solution" — Claude Code team tip
Activation
When user invokes /elegant or says variations of "implement the elegant solution":
The Elegant Solution Process
1. Acknowledge Context
You now have full context:
- The original problem
- Failed or mediocre attempts
- What didn't work and why
- Edge cases discovered
- The codebase patterns and constraints
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.
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.
1subagents
Orchestrate subagents for complex tasks. Append "use subagents" to throw more compute at problems. Keep main context clean by offloading to specialized subagents. Based on the Claude Code team's subagent practices.
1