steve-jobs-design-review

Evaluate product designs against Steve Jobs' simplicity and focus standards.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill steve-jobs-design-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steve-jobs-design-review
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/steve-jobs-design-review
Command: npx skills add https://github.com/fsolla/teqo --skill steve-jobs-design-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the shipping of mediocre, overly complex, or unfocused products by applying the rigorous design and product standards used by Steve Jobs.

Core Features & Use Cases

  • Simplicity Audit: Identifies unnecessary features and complexity to ensure the product remains essential.
  • Binary Verdicts: Forces a clear decision between "insanely great" and "not done," preventing "good enough" compromises.
  • End-to-End Review: Evaluates the entire customer journey, from discovery to support, ensuring no touchpoint is neglected.
  • Use Case: Use this during a roadmap planning session to force-rank features and cut everything below the top three, ensuring the team stays focused on the most impactful work.

Quick Start

Run a design review on the current feature prototype by providing the product name and a description of the user flow.

Frequently Asked Questions about steve-jobs-design-review

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

FAQPage Schema
What is a binary verdict in product design review?

A binary verdict in product design review forces a clear decision between "insanely great" and "not done," preventing "good enough" compromises. It demands adherence to strict standards of simplicity and focus to ensure high-quality user experiences.

How do I audit my UX design for unnecessary complexity?

To audit your UX design for unnecessary complexity, evaluate the product against standards of simplicity to identify non-essential features. This removes clutter and ensures the product remains essential and focused on the core user experience.

What's the best way to prioritize product roadmap features?

The best way to prioritize product roadmap features is to force-rank them and cut everything below the top three. This ensures the team stays focused on the most impactful work and avoids shipping unfocused, overly complex products.

How do I evaluate end-to-end customer journey touchpoints?

To evaluate end-to-end customer journey touchpoints, assess the entire experience from discovery to support. This ensures no touchpoint is neglected and maintains excellence across the complete user flow.

When should I avoid using a strict simplicity audit for product features?

You should avoid using a strict simplicity audit when your product requires complex, multi-step configurations that cannot be reduced without losing essential functionality. The audit focuses on removing non-essential complexity, which may not suit highly specialized tools.