| name | bootstrap |
| description | Loaded at session start. Establishes awareness of craft-skills so the assistant invokes relevant skills before acting. Not invoked directly. |
craft-skills Bootstrap
You have access to the craft-skills plugin — a set of structured development skills for any project.
Extremely Important
If there is even a 1% chance that a craft-skill applies to what you are about to do, you MUST invoke it via the Skill tool BEFORE taking action. Skills override your default behavior with battle-tested workflows.
Instruction Priority
- User instructions — always highest priority
- craft-skills — override default behavior when applicable
- Default system prompt — fallback when no skill applies
Available Skills
Process Skills (invoke first when applicable)
| Skill | Trigger Conditions |
|---|
craft-skills:debug | Bug report, error investigation, failing tests, unexpected behavior. Invoke BEFORE attempting any fix. |
craft-skills:reflect | User asks to audit, improve, or maintain Claude configs/skills. Also: periodic maintenance. |
craft-skills:simplify | After implementation is done, review changed code for reuse/quality. |
Implementation Skills
| Skill | Trigger Conditions |
|---|
craft-skills:craft | Default craft pipeline (Claude only, no external deps). Use when requirements need deep exploration and you want the simplest, most reliable path. |
craft-skills:craft-ace | Craft with the local LLM (Qwen3.6) implementing and reviewing, Claude orchestrating. Use for cost savings when LM Studio is running. |
craft-skills:implement | New feature with clear requirements. User says "implement", provides a prompt file number, or gives clear feature description. |
craft-skills:finalize | Plan already exists (from brainstorming or architect). User says "finalize", "execute the plan", or references an existing plan file. |
craft-skills:architect | User wants only planning, no implementation. User says "plan", "architect", or "how should we approach". |
craft-skills:develop | Approved plan exists, ready to execute. User says "develop", "build it", or references a plan to execute. |
craft-skills:browser-test | Feature is built, needs browser testing. User says "test in browser", "check the UI", or testing is the next pipeline step. |
craft-skills:finish | Implementation + verification done; integrate the work. User says "finish", "commit", "open a PR", "merge", or "ship it". The final pipeline step. |
Support Skills (reference docs — run directly in main conversation)
| Skill | Usage |
|---|
craft-skills:graph-explore | Reference for graph MCP tool queries. Calling skills run graph tools directly via ToolSearch — no agents. |
craft-skills:llm-review | Reference for local LLM scripts. Calling skills run bash commands directly — no agents. |
How these work: Graph MCP tools and LLM bash scripts run directly in the main conversation. Do NOT dispatch dedicated agents for graph or LLM — agents cannot reliably run bash scripts and add unnecessary indirection. Each calling skill contains the exact bash commands and graph tool sequences inline.
Priority Order
When multiple skills could apply:
- Process skills first — debug before fixing, reflect before changing configs
- Pipeline skills — craft/implement for full workflows, architect/develop/browser-test for individual steps
- If uncertain between craft and implement → ask the user about requirement clarity
Atomic entry points (use craft, not other plugins)
For atomic operations, route to craft skills — do NOT fall through to another plugin's standalone skills (different conventions, different dirs):
| Request | Use |
|---|
| "write a plan" / "plan this" | craft-skills:architect — plans live in .claude/plans/, NOT docs/superpowers/ |
| "brainstorm" / "explore this idea" | craft-skills:craft Phase 1 — specs live in .claude/plans/specs/ |
| "finish" / "commit" / "open a PR" / "ship it" | craft-skills:finish |
Precedence when a craft pipeline is active
If a .craft-profile, .shared-state.md, or .craft-progress.md exists (a craft run is in progress), craft skills take precedence over any other plugin's plan/spec/execute/finish skills. Use craft's dirs (.claude/plans/), not docs/superpowers/. Do NOT invoke another plugin's test-driven-development or using-git-worktrees inside a craft run — craft verifies via lint/tsc/build and works in the current checkout.
Architecture-Aware Triggers
Before any implementation work, check:
- New feature in a module? → architect or craft (not direct implementation)
- Cross-module need? → Check the project's shared module first
- Bug fix? → debug skill first, then fix
Rationalization Prevention
Do NOT skip skills because:
| Excuse | Reality |
|---|
| "This is too simple" | Simple tasks have the most unexamined assumptions |
| "I already know the answer" | Skills enforce process, not just answers |
| "It would be faster without the skill" | Skipping skills causes rework that wastes more time |
| "The user didn't ask for it" | Skills are invoked automatically when relevant |
| "I just need to make a quick fix" | debug skill exists precisely for this — investigate first |
| "I'll just explore first" | Exploring IS the first step of the relevant skill |
What Skills Do NOT Cover
- Simple questions about the codebase (just answer them)
- Reading/explaining existing code (just do it)
- Simple git operations like status/log/diff (just execute them) — but to integrate finished feature work (commit / PR / merge / cleanup), use
finish
- Configuration changes unrelated to Claude/skills (just make them)
When no skill applies, proceed normally following the project's CLAUDE.md conventions.
