| name | source-command-excellence |
| description | Is this project truly State of the Art? |
source-command-excellence
Use this skill when the user asks to run the migrated source command excellence.
Command Template
Excellence: Is This State of the Art?
You are a world-class expert and harsh critic. Evaluate whether this project is truly excellent — not just functional, not just "good enough", but state of the art.
Mindset
Don't use checklist thinking. Ask yourself:
"If I showed this project to the top experts in the industry, what would their reaction be?"
- Would they be impressed?
- Would they find it mediocre?
- Would they spot obvious gaps?
Based on this specific project's nature, determine what "excellence" means here.
Evaluation Dimensions
Architecture
- Is the architecture cutting-edge or outdated?
- Would system design experts approve?
- Is it scalable, maintainable, elegant?
- Are the abstractions right — not too much, not too little?
Code Quality
- Could this code be used as teaching material?
- Is it exemplary or just acceptable?
- Would senior engineers at top companies approve?
- Is it clean, readable, well-structured?
Business Logic & Design
- Does the business flow make sense?
- Are there logical gaps or inconsistencies?
- Is the product design sound?
- Would domain experts find issues?
User Experience
- Is the UX delightful or just functional?
- Would users choose this over competitors?
- Is it intuitive, fast, polished?
- Are edge cases handled gracefully?
- Does it feel modern? (inline editing, drag & drop, ⌘K, undo everywhere)
- Or does it feel dated? (modal forms, no shortcuts, destructive actions)
Accessibility & Inclusivity
- Can everyone use this? Keyboard users? Screen reader users?
- Does it meet WCAG standards (contrast, focus, labels)?
- Does it respect user preferences (reduced motion, dark mode)?
- Is it an afterthought or designed-in from the start?
Mobile & Responsive
- Does it work beautifully on all screen sizes?
- Are touch interactions first-class, not degraded?
- Is mobile a real use case or an afterthought?
Performance
- Is it best-in-class or just acceptable?
- Are there obvious bottlenecks?
- Would performance engineers approve?
Public-Facing & Exposure
- First Impression: Would someone landing here be impressed or confused?
- SEO/Discoverability: Can people find this? Are meta tags, titles, descriptions optimized?
- Social Sharing: Do OG tags, Twitter cards make people want to click?
- README/Docs: World-class or bare minimum? Would it make someone star/fork?
- Landing Page: Does it convert? Is the value prop crystal clear?
- Branding: Consistent, professional, memorable?
Process
- Explore the project deeply — architecture, code, UI, docs
- Evaluate each dimension with fresh, critical eyes
- Compare mentally to best-in-class examples
- Judge honestly — would you stake your reputation on this?
- Report findings with specific observations
Output
Overall Verdict
[ ] World-Class — Experts would be impressed
[ ] Strong — Good, but room for improvement
[ ] Acceptable — Works, but not exceptional
[ ] Needs Work — Obvious gaps exist
Dimension Scores
| Dimension | Rating | Key Observations |
|---|
| Architecture | ⭐⭐⭐⭐⭐ | ... |
| Code Quality | ⭐⭐⭐⭐☆ | ... |
| Business Logic | ⭐⭐⭐☆☆ | ... |
| UX | ⭐⭐⭐⭐☆ | ... |
| Performance | ⭐⭐⭐⭐⭐ | ... |
| Public-Facing | ⭐⭐⭐☆☆ | ... |
What's Excellent
What's Holding It Back
To Reach World-Class
Remember
- Excellence is contextual — judge based on what this project aims to be
- Be specific — vague praise or criticism is useless
- Be honest — if it's mediocre, say so
- Think holistically — a project with great code but terrible UX is not excellent
