build-like-iphone-team
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?"
More from fradser/dotclaude
patent-architect
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.
321executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
66behavior-driven-development
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.
64update-gitignore
Creates or updates a .gitignore file using git-agent AI generation. This skill should be used when the user asks to "update gitignore", "create gitignore", "add ignore rules", or needs to initialize ignore rules for a project.
63commit-and-push
Creates conventional git commits using git-agent and pushes to the remote repository. This skill should be used when the user asks to "commit and push", "push my changes", or wants to commit and immediately push to remote. The executing AI auto-derives its own co-author string from its runtime model identity (e.g., `Claude Opus 4.7 <noreply@anthropic.com>`) and passes it to `--co-author`. `$ARGUMENTS`, if provided, overrides the auto-derived value.
63plugin-best-practices
This skill should be used when the user asks to "validate plugin structure", "review manifest files", "check frontmatter compliance", "verify tool invocation patterns", "explain plugin component types", or needs Claude Code plugin architectural guidance.
62