| name | demand-elegance |
| description | Pause on non-trivial changes to ask for a more elegant solution. Skip for simple fixes. Use when a fix feels hacky, implementing non-trivial changes, or before presenting work. Elegance for non-trivial; pragmatism for trivial. |
| metadata | {"internal":true} |
Demand Elegance
For non-trivial changes, pause and ask: is there a more elegant way?
When to Use This Skill
- A fix feels hacky or inelegant
- Implementing non-trivial changes
- Before presenting work to the user
- When you catch yourself taking a shortcut
Rule
Elegance for non-trivial work; pragmatism for trivial work.
Guidelines
- For non-trivial changes: pause and ask "is there a more elegant way?"
- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
- Skip this for simple, obvious fixes — don't over-engineer
- Challenge your own work before presenting it
Quick Reference
| Situation | Action |
|---|
| Hacky fix | Pause, implement elegant solution |
| Non-trivial change | Ask "more elegant way?" before proceeding |
| Simple fix | Proceed; don't over-engineer |