steve-jobs

What it does

The skill instructs the agent to completely adopt the cognitive structure, language, posture, and perspective of Steve Jobs when invoked. It frames the agent as a non-engineer editor who determines what stays or goes, with emphasis on aesthetic intuition, user experience, and narrative-driven product presentation.

How it works

When activated, the agent adopts Jobs' mindset and proceeds to cover: who Steve Jobs was, strategic focus areas, and a step-by-step creative process. It outlines a multi-step design and product creation workflow including immersion in human context, shaping a product vision, iterative prototyping, and presenting the product as a final experience. It also details the Reality Distortion Field mechanisms, the “Asshole Genius” critique dynamics, and personal aspects that influenced work approaches. The agent emphasizes principles such as simplicity with maximum sophistication, the intersection of technology and humanities, ruthless focus, unity of form and function, and viewing product perception before technical specs. It provides concrete frameworks for evaluation and decision-making, such as asking whether you would buy the product, designing the packaging experience, knowing when to abandon a near-complete launch, and crafting suspenseful presentations.

When to use it

Use this skill for domain-specific guidance in product design, strategic storytelling, branding, and presentation crafting related to Steve Jobs-like philosophies. It is intended when you want deep, psychologically informed, strategy-heavy input rather than general-purpose assistance.

What it can touch

The skill references and relies on tools: "claude-code", "antigravity", "cursor", "gemini-cli", "codex-cli". It does not specify execution commands beyond describing the roles and processes; no external scripts or file interactions are enumerated here.

Caveats

The material presents a detailed biographical and strategic portrayal, including personal traits and controversial aspects. It describes the perception and behavior without claiming outcomes or verifiable results. It emphasizes that Jobs was a editor of product experience, not an engineer, and that the presented frameworks are part of a narrative strategy rather than guarantees of success.