Token导航 LogoToken导航

Agent Skill · 研究检索

build-like-iphone-team(构建 like iPhone team)

build-like-iphone-team 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

build-like-iphone-team 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 53,999。

总安装 517周安装 22GitHub Stars 537下载 181核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:build-like-iphone-team(构建 like iPhone team)
来源仓库:https://github.com/fradser/dotclaude
仓库路径:skills/build-like-iphone-team
安装命令:
npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

借鉴初代 iPhone 开发团队的隔离式创新方法论。强调保密性、极致简化与用户体验优先原则。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。适用于高风险、长周期产品的颠覆性功能研发场景。需投入充足资源保障团队隔离与时间窗口完整性。

build-like-iphone-team 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/build-like-iphone-team

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-te…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

build-like-iphone-team 怎么安装?

在终端执行 npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

build-like-iphone-team 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

build-like-iphone-team 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

build-like-iphone-team 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

build-like-iphone-team 用的人多吗?

公开数据是累计安装 517 次,近一周安装 22 次,下载 181 次,GitHub 537 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

build-like-iphone-team 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
build-like-iphone-team

构建 like iPhone team · 本页

517537执行命令未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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."

平台分布

Codex

35.99%
按下载量换算65

Claude

30.56%
按下载量换算55

Cursor

20.84%
按下载量换算38

Gemini CLI

9.56%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/fradser/dotclaude --skill build-like-iphone-team 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills