apple-ouyang

把一本书拆解成 Claude Code 可执行的 Skill。当用户说"拆书"、"把这本书变成 Skill"、"book to skill"、"extract skill from book" 时触发。

Use when committing resources to a project, investment, or relationship. When feeling the pull of sunk cost. When a plan has no defined exit criteria. When you catch yourself thinking "let's wait and see what happens."

Use when facing a significant decision, evaluating options, or feeling stuck between choices. Especially when the decision is high-stakes, irreversible, or involves uncertainty about outcomes. Triggers on phrases like "should I", "I don't know whether to", "I'm torn between", or "help me decide".

Use when tempted to predict, analyze, or debate whether something will work instead of testing it. When facing uncertainty about a decision, product, hire, or opportunity and relying on gut feeling or expert opinions.

Use when a decision feels obvious or everyone agrees, when evaluating omeone's proposal or pitch, when in a team debate that's going nowhere, or when you suspect confirmation bias in your own thinking.

This skill should be used when the user asks to "create a team", "create agent team", "蜂群", "swarm", "团队协作", "parallel agents", "spawn teammates", "多 agent 协作", "组建团队", or executes "/swarm". Analyzes user tasks, designs optimal team structure (roles, count, prompts), presents plan for confirmation, then orchestrates team execution.

Use when you need to treat `docs/**/*.md` as a routed docs system for kernel and low-level repos: list doc entrypoints, choose what to read from `summary` and `read_when`, lint metadata quality, initialize empty front matter for legacy docs, or decide the correct `version/domain` landing path before writing. Do not use for archive and knowledge-lift work, or when the main job is reading code and turning that code reading into a durable doc.

Use when reading kernel, OS, or low-level system code and turning that code reading into a durable doc under `docs/`: choose the correct `version/domain`, decide whether to update or create a doc, extract the stable conclusions, and write the result as a reusable design note rather than a plan or TODO list. Do not use for docs-only entrypoint maintenance, metadata lint or front matter init tasks, or archive and knowledge-lift work.

Apply Elon Musk's five-step engineering method ("The Algorithm") to workflows, products, processes, roadmaps, operations, hiring loops, software delivery, manufacturing, or engineering decisions. Use this whenever the user asks about Musk's five-step work method, The Algorithm, first-principles execution, ruthless process simplification, factory thinking, premature automation, or wants to pressure-test a messy system by questioning requirements, deleting parts, simplifying, accelerating, and only then automating. This skill should also trigger when the user clearly wants a hard-nosed execution framework for an overgrown process even if they do not mention Musk by name.