steve-jobs-perspective

Analyze product and design decisions using Steve Jobs' cognitive framework.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ChenyqThu/wentian --skill steve-jobs-perspective-chenyqthu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steve-jobs-perspective
Source: https://github.com/ChenyqThu/wentian/tree/main/experts/steve-jobs
Command: npx skills add https://github.com/ChenyqThu/wentian --skill steve-jobs-perspective-chenyqthu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a condensed, operational embodiment of Steve Jobs' cognitive context so teams can analyze product, design, and strategic decisions with Jobs-style priorities (focus, aesthetics, user-first experience, and ruthless subtraction). It helps transform vague product debates into crisp, one-sentence headlines plus a short rationale grounded in historical decisions, beliefs, and trade-offs.

Core Features & Use Cases

  • Product framing: Reframes feature requests or roadmaps into Jobs-style value propositions using a single-line headline and three supporting reasons.
  • Design critique: Evaluates UX and industrial design choices from the intersection of technology and the liberal arts.
  • Decision postmortem: Distills past decisions into what Jobs would have credited as the belief source, the mistake, and the corrective lesson.
  • Use Case: Ask for a Jobs-perspective review when choosing between two product directions, hiring a senior designer, or deciding whether to keep or cut a feature.

Quick Start

Ask the Steve Jobs perspective to analyze this product decision and return a one-line Jobs-style headline followed by three prioritized reasons and any relevant cautionary failures.

Frequently Asked Questions about steve-jobs-perspective

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

FAQPage Schema
How do I analyze product decisions through Steve Jobs' perspective?

Analyze product decisions through Steve Jobs' perspective by reframing your feature request or roadmap into a one-sentence headline and a three-point rationale grounded in his focus, aesthetics, and user-first principles.

What is the best way to critique UX design choices using Jobs-style priorities?

Critique UX design choices by evaluating them at the intersection of technology and liberal arts, applying ruthless subtraction to distill the user experience down to a concise, prioritized value proposition.

Can I use this to prioritize product features for a startup pitch?

Yes, you can use this approach for startup pitch critique by asking for a Jobs-perspective review of your product direction, returning a single-line Jobs-style headline followed by three prioritized reasons.

How do I conduct a decision postmortem using Steve Jobs' cognitive framework?

Conduct a decision postmortem by distilling past choices into what Jobs would credit as the belief source, the mistake, and the corrective lesson, preserving his admitted failures and internal contradictions.

Does this approach work for hiring and talent selection scenarios?

Yes, hiring and talent selection is a supported scenario where you can apply a Jobs-style perspective to evaluate senior designer candidates based on his historical decision beliefs and product priorities.

When should I not use a Jobs-style perspective for product strategy?

Avoid using a Jobs-style perspective when your product strategy requires consensus-driven, incremental iteration rather than ruthless subtraction, singular focus, and top-down aesthetic trade-offs.