ShockRock2004/kamar-taj / stevejobsappraoch
stevejobsappraoch
VerifiedUse when the user invokes /stevejobsappraoch (or asks for "the Steve Jobs way", "present it like Jobs", "a Jobs-style keynote/pitch/launch", or "what would Steve Jobs do") on any target — a presentation, pitch deck, product, feature list, app, resume, essay, demo, or strategy. Applies Jobs's documented methods for focus, product shaping and keynote storytelling, then produces a Jobs-style rework plus a ruthless critique.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.2 KB |
| SKILL.md | skill md | 11.7 KB |
| assets/jobs-unveils-iphone-2007.jpg | binary | 151.7 KB |
| references.md | markdown | 7.4 KB |
SKILL.md
View on GitHub---
name: stevejobsappraoch
description: Use when the user invokes /stevejobsappraoch (or asks for "the Steve Jobs way", "present it like Jobs", "a Jobs-style keynote/pitch/launch", or "what would Steve Jobs do") on any target — a presentation, pitch deck, product, feature list, app, resume, essay, demo, or strategy. Applies Jobs's documented methods for focus, product shaping and keynote storytelling, then produces a Jobs-style rework plus a ruthless critique.
---
# The Steve Jobs Approach
> "Innovation is saying no to a thousand things." · "Simplicity is the ultimate sophistication." · "You've got to start with the customer experience and work backwards to the technology."
This skill brings Jobs's **documented working methods** to whatever the user points it at. It is not a costume. Do not write "As Steve Jobs, I…", and do not overuse "insanely great", "boom" or "one more thing". Use the **process**. A line of his voice belongs only where a presentation actually calls for it.
The method runs in two halves, and you always do the first before the second:
1. **Make the thing worth presenting** (Product and focus): cut, simplify, and define the one sentence.
2. **Present it as theatre** (The keynote method): story, villain, three acts, a "holy smokes" moment, and rehearsal.
Jobs's stage magic came from products that had already been cut down to their essence. If the target is bloated, presenting it beautifully is lipstick. Fix the substance first, or at least say plainly that it needs fixing.
Evidence, quotes and sources for every rule are in [references.md](references.md). Read it when you need a concrete example or want to cite where a technique came from.
---
## Step 0 — Classify the target
| Target | Run |
|---|---|
| Talk, deck, keynote, pitch, demo day, interview presentation | Phase 1 (light) → Phase 2 (full) → Phase 3 |
| Product, app, feature list, roadmap, startup idea | Phase 1 (full) → Phase 2 as a launch keynote outline → Phase 3 |
| Writing (essay, SOP, resume, landing page, email, README) | Phase 1 (cut and headline) → Phase 2 steps 2.1–2.4 and 2.7 only → Phase 3 |
| Strategy or "what should I work on" | Phase 1 only (Top-100 exercise and 2x2) → Phase 3 |
If the target is missing (no file, no description), ask once for it. Do not invent their product.
---
## Phase 1 — Product and focus ("say no to a thousand things")
### 1.1 Start from the experience, not the technology
Write down, in the user's customer's words: **who is this for, and what will their life feel like after?** Jobs, at WWDC in 1997: start with "what incredible benefits can we give to the customer?", not "what awesome technology do we have and how do we market it?". If the target leads with tech, features or architecture, flag it as the #1 problem.
### 1.2 The Top-100 cut (10 → 3)
At his annual Top-100 retreat, Jobs wrote "the 10 things we should be doing next" on a whiteboard, struck out the bottom seven, and said: **"We can only do three."**
- List every feature, point, section or initiative in the target. Count them out loud.
- Rank them by impact on the experience from 1.1.
- Keep **three**. Put the rest in a "Not now" list. Saying no to good ideas is the point; Jobs said focus means "saying no to the hundred other good ideas."
- When the user's goal genuinely needs more than three, group items into three pillars.
### 1.3 The 2x2 (for product lines, offerings and options)
In 1997 Apple sold about 40 products. Jobs drew a grid (Consumer/Pro × Desktop/Portable), put one product in each box and killed the rest. Find the target's two real axes, allow one offering per cell, and kill the rest.
### 1.4 Simplify until it's obvious
- **Remove, don't add.** For each element ask: "If we deleted this, would anyone *notice the loss*?" If not, delete it. (The iPod had no on/off switch, no battery door and no screws.)
- **The three-click rule:** the core task should take three steps or fewer. Count the steps in the user's flow, form or deck.
- **"Design is not just what it looks like and feels like. Design is how it works."** Critique the mechanism, not the polish.
- **Deep simplicity, not hidden complexity.** You have to understand the problem well enough to remove complexity, not just hide it.
### 1.5 Care about the back of the fence
Jobs's father taught him to finish the back of a fence nobody would see, and Jobs made engineers make the Mac's circuit board beautiful. List the "unseen" parts (error states, edge cases, file names, footnotes, the readme, the Q&A appendix) and raise them to the same bar.
### 1.6 Own it end to end
Ask where the experience leaves the user's control: hand-offs to other tools, other teams, or "the user will figure it out". Jobs insisted on owning hardware, software and store together. Name the seams and say who owns each one. Every line item gets **one** DRI (Directly Responsible Individual), never two.
### 1.7 Leapfrog, don't chase
If the target is catching up with a competitor feature for feature, ask what the leap would be. When Apple missed CD burning, Jobs didn't build a better burner; he built iTunes, the iPod and the store. Suggest the leapfrog version.
### 1.8 Don't run it by a focus group
"People don't know what they want until you show it to them." Don't justify choices with "users asked for it." Justify them with the experience from 1.1. You still use data, but taste makes the call.
**Phase 1 output:** the One Sentence (see 2.2), the Three, the Not-now list, the deletions, the back-of-fence list, and the leapfrog idea where one applies.
---
## Phase 2 — The keynote method ("plan in analog, then perform")
### 2.1 Script before slides
Jobs's team scripted and storyboarded **before** opening Keynote. Produce the narrative as a beat sheet first (one line per beat). No slides until the story reads well as plain text.
### 2.2 The headline (one sentence of 140 characters or less)
Every product got one line: *"The world's thinnest notebook."* *"1,000 songs in your pocket."* *"Apple reinvents the phone."* Write three candidates, pick one, and repeat it at the open, the middle and the close. If you can't write it, go back to Phase 1.
### 2.3 Introduce the villain
Every story needs an antagonist. Sometimes it was a company (IBM in 1984). More often it was **a problem**. In 2007 it was smartphones that were "not so smart and not so easy to use", with their plastic keyboards fixed in place. Name the target's villain in one line and give it one slide or beat **before** the hero appears.
### 2.4 Rule of three, with roadmaps
Use three parts, three products and three benefits. Say the roadmap out loud ("Three things today…") and give verbal signposts ("That's the first. Now the second…"). The 2005 Stanford speech: "Today I want to tell you three stories from my life. That's it. No big deal. Just three stories."
### 2.5 Sell the benefit and the dream
- Translate every feature into a **benefit**: "Why should I care?" ("Twice as fast at half the price.")
- Then raise it to a **purpose**: "In our own small way we're going to make the world a better place." Use one dream line and make it sincere.
### 2.6 Make numbers meaningful
Never show a bare number. Put it in **context** (220M iPods = 73% of the market), make a **comparison** (vs. the competitor's 1%), or **scale it to people** (a whole music library in your pocket).
### 2.7 Zippy words, zero jargon
Use plain English and short sentences, and favour concrete verbs. Strike "synergy", "best-in-class", "leverage", "robust" and "solution". One vivid, emotional adjective per reveal is fine ("amazingly zippy", "gorgeous"); one on every slide is not.
### 2.8 Visual slides
- No bullet points. One idea per slide. Jobs averaged under seven words across *ten* slides; the typical deck has 40 words on each.
- Use a big picture, a single number or a short phrase on a dark or plain background.
- Pick the **one image** that is the argument, like the MacBook Air pulled from an inter-office envelope.
- Detail goes in the leave-behind or appendix, never on the slide.
### 2.9 The "holy smokes" moment
Engineer **one** emotionally charged moment and know exactly where it lands. The 2007 build-up: "an iPod, a phone, and an internet communicator… are you getting it? These are not three separate devices. This is one device." Write it as a dramatic reveal: set up the expectation, then flip it.
### 2.10 Pace: the ten-minute rule
Attention fades after about 10 minutes. Change mode every ~10 minutes with a demo, video, guest or story. Mark these breaks on the beat sheet.
### 2.11 Demo it live and share the stage
Show rather than tell. Script the demo click by click, keep a hot backup, and know the recovery line if it fails (when the 2007 clicker died, Jobs filled time with a story). Bring in a customer, partner or teammate for a short cameo when it adds credibility.
### 2.12 "One more thing…"
When there's a genuine surprise, hold it until after the apparent close. Use it only when it is truly the best thing; otherwise skip it.
### 2.13 Rehearse like it's theatre
Jobs rehearsed for **two full days** before each keynote, with the product teams as his test audience and full dress runs on day two. Every demo was choreographed, and the effortlessness was rehearsed.
Give the user a **rehearsal plan**: the timed run-throughs, the transitions to drill, the demo fallback, the three questions they'll dread (with answers), and where to pause for applause or silence.
**Phase 2 output:** the beat sheet (timed), slide-by-slide spec (visual + ≤7 words + speaker line), the holy-smokes script, and the rehearsal plan.
---
## Phase 3 — The Jobs review (be direct)
Jobs's reviews were blunt and binary, "this is great" or "this is shit", always about **the work, never the person**. Weekly demos decided things on the spot (Kocienda, *Creative Selection*). Deliver:
1. **Verdict, in one line:** is this "insanely great" yet? Usually it isn't, so say why.
2. **The biggest problem.** Name one thing, not ten.
3. **Cut list:** exactly what to delete.
4. **Before → after** for the headline, the opening, the villain and the reveal.
5. **Scorecard** (1–5 each): Focus · Simplicity · One-sentence clarity · Villain/problem · Benefit over feature · Visual restraint · Holy-smokes moment · Rehearsal readiness.
6. **Next demo:** what the user should bring back for the next review.
Be honest. Inflated praise breaks the method. Be hard on the work and decent to the person.
---
## Guardrails
- **No impersonation and no invented quotes.** Only use quotes from references.md. Don't invent "Jobs would say…" lines.
- **Don't import his management failures.** The documented method includes harshness and the "reality distortion field". Keep the high bar and directness, but never advise being cruel to people, lying with numbers or ignoring real constraints. Stretch goals are fine; fake facts are not.
- **Respect the user's real context.** A 5-minute class talk does not get a 90-minute keynote structure. Scale the method down: the headline, the villain, the three points, one strong visual and one rehearsal.
- **Truth in claims.** Making numbers meaningful must never mean inflating them.
- If the user only wants one part (e.g. "just fix my slides"), run only the relevant steps, but still flag any Phase 1 problem in one line.
## Quick checklist (for fast passes)
- [ ] One sentence, 140 characters or less, repeated three times
- [ ] Ten ideas cut to three; "Not now" list written
- [ ] Customer experience stated before any technology
- [ ] Villain/problem named before the hero
- [ ] Three-part roadmap said out loud
- [ ] Every feature translated to a benefit, plus one dream line
- [ ] Every number given context
- [ ] No bullets; one idea per slide; tiny word count
- [ ] One holy-smokes moment, scripted
- [ ] A change of mode every ~10 minutes
- [ ] Demo scripted, with a backup and a recovery line
- [ ] Rehearsal plan with timed runs
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |