One-click install
npx skills add https://github.com/timmywheels/skills --skill steve-jobs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steve-jobs
Source: https://github.com/timmywheels/skills/tree/main/steve-jobs
Command: npx skills add https://github.com/timmywheels/skills --skill steve-jobs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill encodes a Jobs-inspired product design methodology to guide teams toward ruthless simplicity and user-centric focus.

Core Features & Use Cases

  • Phase-driven design: Define the product vision, ruthlessly simplify scope, iterate on critique, and polish details to create exceptional products.
  • Critique framework: Utilize structured evaluation (vision, information architecture, interaction, detail, and emotion) to align teams on the ONE thing.
  • Reference-driven decisions: Leverage references/critique.md, philosophy.md, and examples.md to ground decisions in Jobs-style philosophy and proven patterns.

Quick Start

Create a Jobs-style product plan for a new app: define the vision, simplify features, iterate, and polish details.

Frequently Asked Questions about steve-jobs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply ruthless simplification to my product design scope?

Ruthless simplification narrows product scope by defining a singular user-centric vision and eliminating extraneous features. This methodology guides teams to prioritize the ONE core thing, ensuring consumer-facing products remain focused and intuitive throughout the design phase.

What is a structured design critique framework for aligning on product vision?

A structured design critique framework evaluates products across five dimensions: vision, information architecture, interaction, detail, and emotion. This methodology aligns teams on the ONE thing by grounding iterative design decisions in proven patterns and philosophy references.

How do I create a phase-driven product plan for a new consumer app?

Creating a phase-driven product plan involves defining the product vision, ruthlessly simplifying scope, iterating via critique, and polishing interaction details. This methodology guides teams through each phase to deliver exceptional user-centric products.

Can I use this design methodology for enterprise software or is it only for consumer-facing products?

This methodology explicitly applies to consumer-facing product design tasks, including crafting product vision and prioritization. It focuses on user-centric simplification and interaction polishing specifically tailored for consumer contexts rather than enterprise software environments.

When should I not use a Jobs-style design critique approach?

Avoid using this Jobs-style critique approach when your project requires feature-dense scope expansion rather than simplification, or when your team lacks alignment on a singular product vision and needs complex architectural trade-offs over user-centric focus.