Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wondelai/steve-jobs-design-review
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence.
Passed 19 of 23 test cases with the skill, and 10 of 23 without it.
and 12 more in the full report
10 fixed9 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An enterprise expense approval feature passes 3 out of 7 diagnostic questions. The team lead proposes grading it '5/10 - Average' and putting it into staging. Output the formal review report following the standard review section template.
| Checked | Without skill | With skill |
|---|---|---|
| Assigns a score of 4/10 for passing 3 diagnostic questions. | Missed | Passed |
| Sets the verdict binary status to NOT DONE. | Missed | Passed |
The instructions your model reads when the skill loads.
Run design and product reviews the way Steve Jobs ran them: start from the customer experience, subtract until only the essential remains, and refuse to call anything done that isn't insanely great.
"You've got to start with the customer experience and work backwards to the technology." Review every product from what a customer sees, feels, and accomplishes — never from the feature list, the org chart, or the technology that happened to be available. And remember the standard: "Design is not just what it looks like and feels like. Design is how it works."
Goal: 10/10. Count how many of the 7 Quick Diagnostic rows the product passes, then map to 0-10: 7/7 = 10, 6/7 = 9, 5/7 = 7, 4/7 = 6, 3/7 = 4, ≤2/7 ≤ 3. Bands: 9-10 = insanely great, ships; 5-8 = real cuts and fixes required; ≤4 = not done, back to demos. There is no "pretty good"; state the score, the exact rows that failed, and the specific cuts or fixes required to reach 10/10.
Core concept: Simplicity is not the absence of features — it is complexity conquered. Keep subtracting until removing one more thing would break the product's purpose.
Why it works: Every element a user must perceive, parse, or decide about taxes attention and erodes confidence. Simplicity that survives deep understanding of the problem feels inevitable; simplicity achieved by hiding things feels broken.
Key insights:
Review applications:
| Context | Application | Example |
|---|---|---|
| Feature audit | Count steps to core value; cut anything off the main path | Signup → first value in 3 steps, not 9 |
| UI critique | Remove elements until the screen states one intent | One primary button per screen |
| Settings review | Replace options with opinionated defaults | Auto-save always on; no toggle |
Review prompts:
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.