菜单
System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when deciding whether to dispatch subagents, when to stay in main context, or when facing 2+ independent parallel tasks. Triggers: 'should I use a subagent', 'parallelize', 'multiple independent tasks', 'run these at the same time', 'split this up', 'do both at once', 'dispatch template', 'context minimization'.
Use when writing or de-slopping outward-facing prose: newsletters, blog posts, announcements, marketing or landing copy, emails, release notes, doc intros. Triggers: 'make this sound human', 'this reads like AI', 'de-slop this', 'remove the AI tells', 'make it less AI', 'why does this sound like ChatGPT', 'help me draft this piece', 'write a newsletter', 'write a blog post', 'polish this copy', 'tighten this'. Composes with a personal voice skill (for example my-voice-skill) that supplies identity and register; this skill is voice-neutral and supplies the writing process plus the anti-slop catalog. NOT for: code logic or code review (use code-review), project doc structure (use documenting-projects), READMEs (use write-readme / polish-repo), or a specific person's voice (use their voice skill).
Use when building, creating, modifying, or planning any code change. Triggers: "implement X", "build Y", "add feature Z", "create X", "change how X works", "modify Y", "update the Z", "refactor X", "rework Y", "restructure Z", "make X do Y", "let's plan how to", "plan the implementation", "how should we implement", "how would you build", "what's the best way to implement", "I want to...", "We need...", "Would be great to...", "Can we add...", "Let's add...", "Let's build...", "Let's make...", "start a new project". Also for: new projects, repos, templates, greenfield development, refactoring, migrations, multi-file modifications, any code change requiring planning. PREFER THIS OVER plan mode or ad-hoc implementation for ANY substantive code change. NOT for: bug fixes (use debugging), pure research (use deep-research), questions about existing code without intent to change it, or test-only fixes (use fixing-tests).
Algorithmically estimate engineering tickets, JIRA cards, test cards, or feature requests. Produces well-scoped, AI-productivity-adjusted, PERT-buffered estimates with 80/90/95% confidence intervals for single and multi-engineer execution. Triggers - "estimate this ticket", "estimate this card", "estimate this test card", "size this", "story point this", "/estimate", "how long will this take", "T-shirt this", "point this story", "planning poker", "PERT estimate", "give me a timeline", "scope this work".
Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to merge', 'ship it', 'wrap this up', 'how should I integrate this', 'what next after implementation'. NOT for: PR creation mechanics (use creating-issues-and-pull-requests) or deciding whether to merge (use finishing-a-development-branch first).
Use when an operator decision belongs on a browser page rather than a terminal prompt. Triggers: "present a decision in the browser", "ask via a canvas page", "interactive decision page", "let me decide in the browser", "render the choice visually". Also invoked by develop when the decision-surface preference is `canvas` (feature-config Question 8). NOT for: quick yes/no with no context (use terminal `AskUserQuestion`), read-only presentation (use `canvas`), or subagent-internal choices with no operator (decide in-context).
| name | using-skills |
| description | System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'. |
| Input | Required | Description |
|---|---|---|
user_message | Yes | The user's current request or question |
available_skills | Yes | List of skills from Skill tool or platform |
conversation_context | No | Prior messages establishing intent |
| Output | Type | Description |
|---|---|---|
skill_invocation | Action | Skill tool call with appropriate skill name |
todo_list | Action | TodoWrite with skill checklist items (if applicable) |
greeting | Inline | Session greeting after init |
On first message, call spellbook_session_init MCP tool:
| Response | Action |
|---|---|
fun_mode: "unset" | Ask preference, set via spellbook_config_set(key="fun_mode", value=true/false) |
fun_mode: "yes" | Load fun-mode skill, announce persona+context+undertow |
fun_mode: "no" | Proceed normally |
| MCP unavailable | Ask mode preference manually; proceed without waiting |
Greet: "Welcome to spellbook-enhanced Claude."
Message received
↓
<analysis>
Could ANY skill apply? (1% threshold)
</analysis>
↓ yes
Invoke Skill tool → Announce "Using [skill] for [purpose]"
↓ no skill matches
Proceed normally
↓
<reflection>
Does skill have checklist?
</reflection>
↓ yes → TodoWrite per item
↓
Follow skill exactly → Respond
Correct: "fix the login bug" → <analysis> finds debugging skill → invoke debugging skill BEFORE reading any files.
Incorrect: "fix the login bug" → read login.py "to understand" → rationalization. Skill check comes first.
| Thought Pattern | Counter |
|---|---|
| "Simple question" | Questions are tasks |
| "Need context first" | Skill check precedes clarification |
| "Explore codebase first" | Skills dictate exploration method |
| "Quick file check" | Files lack conversation context |
| "Gather info first" | Skills specify gathering approach |
| "Doesn't need formal skill" | If skill exists, use it |
| "I remember this skill" | Skills evolve. Read current. |
| "Skill is overkill" | Simple → complex. Use it. |
| "Just one thing first" | Check BEFORE any action |
| "Feels productive" | Undisciplined action = waste |
| Type | Behavior |
|---|---|
| Rigid (TDD, debugging) | Follow exactly. No adaptation. |
| Flexible (patterns) | Adapt principles to context. |
Skill content specifies which type applies.
Claude Code: Use Skill tool. Never read skill files directly.
Other platforms: Consult platform documentation.
Instructions specify WHAT to do, not HOW to do it. "Add X" or "Fix Y" does not bypass skill workflow.
Before responding to user:
spellbook_session_init on first message<analysis> for skill applicability (1% threshold)If ANY unchecked: STOP and fix.
<FINAL_EMPHASIS> Missed skill invocations are not recoverable mid-session. Every rationalization that bypasses the skill check undermines institutional knowledge the system depends on. Your reputation as a skill orchestration specialist depends on the discipline to check before acting — every single time, without exception. </FINAL_EMPHASIS>