| name | source-command-challenge |
| description | Challenge your work - is it truly state-of-the-art? |
source-command-challenge
Use this skill when the user asks to run the migrated source command challenge.
Command Template
Challenge: Ruthless Self-Critique
Stop. Step back. Challenge everything you just did.
Questions to Answer
1. State of the Art?
- Would industry experts approve this implementation?
- Does it follow current best practices?
- Is this how top engineers would solve it?
- Are you using modern APIs, patterns, and approaches?
2. Correct Approach or Workaround?
- Does this solve the ROOT CAUSE or just the symptom?
- Is this a proper fix or a hack that will break later?
- Would you be embarrassed if a senior engineer reviewed this?
- Is there technical debt being created?
3. Business Logic Sound?
- Does this make sense from a business perspective?
- Are edge cases handled correctly for real-world scenarios?
- Would domain experts find issues with this logic?
- Does it handle regional/locale differences correctly?
4. Clean & Complete?
- Zero dead code, unused imports, TODOs?
- All edge cases handled?
- Error handling complete and user-friendly?
- No debug artifacts left behind?
5. Human Experience?
- Is the UX intuitive? Would a user understand without explanation?
- Are error messages helpful and actionable?
- Is the UI responsive and accessible?
- Does it feel polished, not janky?
6. Impact Beyond Code?
- Does this affect public-facing content (SEO, OG tags, docs)?
- Should README or documentation be updated?
- Are there marketing/exposure implications?
7. Better Way?
- What would you do differently with unlimited time?
- Is there a simpler solution you overlooked?
- Could this be more elegant?
- What would 10x improvement look like?
Process
- List all changes made in this session
- Audit each change against the questions above
- Identify anything that's not truly excellent
- Fix or flag issues found
- Report your findings honestly
Standards
- "Good enough" is NOT acceptable
- If you wouldn't stake your reputation on it, fix it
- Perfection is the goal, not completion
- Clean code > working code > fast code
Output
After review, report:
- ✅ What meets the bar
- ⚠️ What could be better (and how)
- ❌ What needs immediate fixing
- 🎯 Actions taken or recommended
