MCPInstall

build-like-iphone-team

Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.

Installs
87
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads build-like-iphone-team automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Build Like the Original iPhone Team

Knowledge reference for applying Apple's Project Purple design philosophy. Based on the original iPhone (2004-2007) development that created the revolutionary device.

Project Purple Context

Timeline: 2003-2007, $150 million investment, 2.5 years in complete isolation Team: 200 of Apple's top engineers, sworn to secrecy Code names: Project Purple (overall), P1 (iPod phone), P2 (multi-touch tablet), Purple Dorm (isolation building) Origin: Started as tablet project (Model 035), pivoted to phone after multi-touch breakthrough

The pivot: In 2003, Jony's team experimented with multi-touch to get rid of mouse and keyboard. Duncan Kerr demonstrated multi-touch in a brainstorming meeting - first time the team had seen it. Within a week, Input Engineering built a working prototype with a 12-inch MacBook display. When Jobs saw this - zoom in/out on Apple campus with finger gestures - he said "My God, we can build a phone with this." Tablet aside, phone began.

The Five iPhone Principles

1. First-Principles Thinking: Slash All Redundancy

Strip away all assumptions. Ask "What is the absolute minimum needed to deliver core value?"

iPhone example:

  • When industry said "phones need physical keyboards," Apple asked "If the screen can become anything, why do we need fixed buttons?"
  • Jony Ive's first iPhone sketch showed the entire front face as one big, unbroken expanse of glass
  • The screen wasn't a display - it was the interface. Hardware and software designed together

Application: Identify fundamental truth, question every industry assumption, rebuild from basics.

See ./references/first-principles.md for detailed patterns and templates.

2. Force "Impossible" Technology into Reality

Never accept "no" as an answer. Find or create breakthrough technology.

iPhone examples:

  • Multi-touch: Only existed in labs. Apple's Input Engineering team built a ping-pong-table-sized capacitive display for testing. Within a week, they had a working prototype.
  • Gorilla Glass: Jobs called Corning CEO 6 months before launch. Gorilla Glass existed as lab curiosity. Jobs said "You're afraid." Corning transformed their facility.
  • Capacitive display: Scaling laboratory technology to mobile required inventing new manufacturing processes.

Application: Identify barriers, research breakthroughs, find partners, confront fear.

See ./references/breakthrough-research.md for breakthrough stories and research methodology.

3. Experience-Driven Specifications

Define in human moments, not technical metrics.

iPhone example: "A device Steve can use in the bathroom to check email" translated to 60fps scrolling with fluid inertia. Greg Christie's team got a two-week ultimatum from Jobs in 2005: bigger ideas or project goes elsewhere. Under pressure, they developed features like swipe to unlock - designed to feel intuitive and natural.

Application: Describe the moment, extract the feeling, derive technical constraints.

See ./references/experience-specs.md for writing experience-driven specifications.

4. Internal Competition: Survival of the Fittest

Let best ideas win through fierce competition. No compromise hybrids.

iPhone example: Apple hedged its bets by developing two phones in parallel. P1 (iPod nano with phone features, led by Tony Fadell) vs P2 (multi-touch device based on Model 035 tablet, led by Jony). After six months, Fadell's team produced a working prototype, but the multi-touch approach won. P1 team's insights enhanced P2, but final product was pure P2 vision.

Application: Spawn competing teams, compare head-to-head, winner takes all.

See ./references/internal-competition.md for competition patterns and selection criteria.

5. Purple Dorm Isolation

Build in secret. Eliminate all outside noise.

iPhone example: Scott Forstall couldn't tell recruits what they'd work on. Team locked down a building with badge readers, cameras, Fight Club poster. Jobs spread teams across campus. Presentations to Jobs happened in windowless rooms to avoid leaks. Employees had to sign NDAs for their NDAs. Only 30 people saw complete iPhone before announcement. The "soup of misery" - pressure cooker with impossible deadline, impossible mission, company's future resting on it.

Application: Isolate teams from trends, competitors, conventions. Focus on perfect.

See ./references/purple-dorm.md for isolation principles and team setup.

The iPhone Formula: Key Lessons

  1. Tablet before phone - The multi-touch display was invented for a tablet, then pivoted to phone. Technology readiness meets opportunity.
  2. Pressure creates breakthroughs - Jobs' two-week ultimatum to Greg Christie's team forced creative solutions like swipe to unlock.
  3. Hardware-software together - The screen wasn't just a display. It was the interface. Capacitive touchscreen and software designed in tandem.
  4. Rapid prototyping - Within a week of seeing multi-touch demo, engineers had working 12-inch display prototype.
  5. Ultimatum-driven innovation - When Christie ran out of time, Jobs gave him two weeks for bigger ideas or project moves to another group.
  6. No compromise on interface - The entire front was one big, unbroken expanse of glass. No buttons, no distractions.
  7. Swipe to unlock - Designed to feel intuitive and natural with the new touch input paradigm.
  8. Full web, not "baby web" - Competitors used WAP giving dumbed-down web. iPhone delivered full internet experience.
  9. Windowless secrecy - Presentations to Jobs in windowless rooms to avoid leaks.
  10. Pressure cooker culture - Round-the-clock work through weekends, holidays, vacations, honeymoons. The future of the company was at stake.

When to Apply iPhone Philosophy

Use this knowledge when:

  • Creating new product categories, not improving existing ones
  • Industry conventions are blocking innovation
  • Need to challenge fundamental assumptions
  • "Everyone does it this way" is the primary obstacle
  • Willing to invest in radical innovation
  • Facing pressure that could drive breakthrough solutions

Don't apply when:

  • Making incremental improvements
  • Problem is straightforward and well-understood
  • Quick delivery matters more than breakthrough
  • Stakeholders demand proven, conservative approaches

Quick Reference

SituationApply Which Principle
Industry says "can't"First-Principles + Breakthrough
Technology doesn't existBreakthrough + Rapid Prototyping
Need to define requirementsExperience-Driven Specs
Facing deadline pressureUltimatum-Driven Innovation
Multiple viable approachesInternal Competition
Outside influencePurple Dorm Isolation
Hardware-software mismatchIntegration: Design Together
Need commitment to visionAll principles together

Reference Files

Detailed guidance for each principle:

  • ./references/first-principles.md - Questioning assumptions, zero-based approach
  • ./references/breakthrough-research.md - Multi-touch, Gorilla Glass, iOS, Capacitive Display
  • ./references/experience-specs.md - Writing specs in human moments
  • ./references/internal-competition.md - P1 vs P2, winner-takes-all selection
  • ./references/purple-dorm.md - Extreme isolation, Fight Club poster, pressure cooker culture

Remember: iPhone wasn't better because of more features. It was better because it rejected all assumptions and built something from first principles. The multi-touch display was invented for a tablet, then pivoted to phone when Jobs realized "My God, we can build a phone with this."

FAQ

What does the build-like-iphone-team skill do?

Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.

How do I install build-like-iphone-team?

Run npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/build-like-iphone-team/ (personal) or .claude/skills/build-like-iphone-team/ (project).

Which AI agents can use build-like-iphone-team?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is build-like-iphone-team safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains build-like-iphone-team?

It is published by fradser in fradser/dotclaude. It has 87 recorded installs.

More from fradser/dotclaude

View all →

patent-architect

fradser/dotclaude

Automatically searches prior art via SerpAPI and generates Chinese patent application forms. This skill should be used when the user wants to generate Chinese patent application forms, or mentions "patents", "inventions", or wants to protect technical innovations.

Media & Creative618 installs

agent-browser

fradser/dotclaude

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.

Testing & QA148 installs

commit-and-push

fradser/dotclaude

Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.

executing-plans

fradser/dotclaude

Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.

brainstorming

fradser/dotclaude

Designs new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).

Popular mobile skills

View category →

design-mobile-apps

designed-by-ai/skills

Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.

Mobile1.1M installs

ios-design

uizze.sh

Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.

Mobile416.5K installs

vercel-react-native-skills

vercel-labs/agent-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

OfficialMobile256.7K installs

animate-expo

emilkowalski/skills

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.

Mobile140.1K installs

xcode-project-setup

firebase/agent-skills

Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).

OfficialMobile131.2K installs

firebase-remote-config-basics

firebase/agent-skills

Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.

OfficialMobile121.7K installs