Steve Jobs Design Review
Jobs-style reviews: ruthless simplicity, focus, binary verdicts
Review designs, products, and roadmaps the way Steve Jobs ran reviews: start from the customer experience, subtract until only the essential remains, and deliver a binary verdict — insanely great, or not done. This skill distills Jobs' documented review practices from Walter Isaacson's biography, Ken Segall's "Insanely Simple," and Ken Kocienda's "Creative Selection" into a protocol your AI agent can run on any product.
npx skills add wondelai/skills/steve-jobs-design-review --global 
Steve Jobs Walter Isaacson View on Amazon
02 What it is
What is the Steve Jobs Design Review skill?
Steve Jobs Design Review turns your agent into an unusually harsh reviewer, drawing on Walter Isaacson’s biography and the documented accounts of how Jobs ran product reviews. It judges the experience end to end, demands a kill for every addition, and returns a binary verdict — insanely great, or not done — with a cut list attached.
03 Key concepts
Five principles your agent applies.
Drawn from Steve Jobs — not advice it repeats back to you, but decisions it makes while it works.
04 Fit
When to use it, and
when not to.
four symptoms it fixes, and four it doesn't.
Reach for it when
You are a week from launch and everything is fine, which is a dangerous state to ship in.
Your roadmap has fourteen priorities and nobody will say out loud which three matter.
Features keep being added and nothing has been removed from the product in a year.
You want a review that ends in a decision rather than a list of considerations.
Reach for something else when
You need severity-rated findings your team can triage. UX Heuristics gives that; this gives a verdict.
The team needs buy-in. this review style is deliberately blunt; Lean UX reaches the same cuts collaboratively.
You are working out what customers want. The Mom Test and Jobs to Be Done ask them; this asks taste.
The strategy is the vague part, not the product. Good Strategy Bad Strategy separates diagnosis from wish list.
05 Prompts
Say it like this.
Name the skill at the end of a prompt and the agent applies the framework rather than a vibe. Or say nothing — it loads on its own when a task matches.
Review this landing page like Steve Jobs would — verdict, cut list, fix list using steve-jobs-design-review skill
Cut my Q3 roadmap to the essential three bets and justify every kill using steve-jobs-design-review skill
Audit my onboarding end-to-end, from signup to first value, as one experience using steve-jobs-design-review skill
Find the back-of-the-fence surfaces in my app that fail the quality bar using steve-jobs-design-review skill
06 About the author
07 Same stack
The stack it sits in.
Nine Design & UX skills. Most people run two: this one, and whichever fits the next problem.
All Design & UX skills08 Questions
Before you install.
How do I install the Steve Jobs Design Review skill?
Run npx skills add wondelai/skills/steve-jobs-design-review --global. It takes about 30 seconds and needs no account. The Steve Jobs Design Review skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.
Which book is the Steve Jobs Design Review skill based on?
It packages Steve Jobs by Walter Isaacson — bestselling biographer of Steve Jobs, former CEO of CNN & editor of Time. The skill distils the book's method into instructions your agent follows while it works, covering simplicity is the ultimate sophistication, focus means saying no and design is how it works. It sits in the Design & UX part of the library.
Is this an AI doing a Steve Jobs impression?
It is a protocol, not a personality. The material is the documented practice — review working artifacts on the real device rather than slides, run competing versions against each other, keep one decider, subtract until removing anything else would break the thing, treat every touchpoint as part of the product. You get a repeatable review method. You do not get his taste, and no skill can hand you that.
Will it just tell me to delete everything?
It biases hard toward subtraction, deliberately, because almost every product errs the other way. But it has to justify each cut and it enforces a kill for every add rather than an unbounded purge. Treat it as a reviewer arguing from a fixed extreme: valuable precisely because it will not soften, and something you are expected to push back on when you know a constraint it does not.
When in the process should I run it?
Once something is demoable, and never on a document. Jobs reviewed working artifacts on real hardware, and the skill inherits that — pointed at a staging build or a clickable prototype it evaluates latency, failure states, and the first-run path, which is where products actually disappoint. Pointed at a spec it can only critique the writing. Run it before launch, not after, while cutting is still cheap.
How does it differ from the Top Design skill?
Top Design builds; this one judges. Top Design gives your agent the moves for a striking page — type scale, composition, choreography. This skill will happily conclude that the striking page should not exist, that three of its sections are noise, and that the signup flow it leads into is where the real failure is. One is a craft skill aimed at the surface; the other is an editorial pass over the whole experience.
09 Guides that use it
Put it to work.
Long-form playbooks where this skill does part of the job.
One skill, one command.
Install Steve Jobs Design Review, or the whole stack.
npx skills add wondelai/skills/steve-jobs-design-review --global MIT licensed · Claude, Claude Code, Codex, Cursor, OpenClaw, Hermes · No account