tool-bootstrappinglisted

# Tool Bootstrapping — project-aware MCP/skill proposal discipline > **Authoritative for:** §13.25 tool-bootstrapping discipline (6 rules) for consumer projects that install this skill via `install.sh`. Consumer-facing shipped version; project-internal cross-links omitted. > **NOT authoritative for:** authoring-repo goal — see authoring repo `README.md#why-this-exists`. Project-internal version with repo-specific cross-links — see `.claude/skills/tool-bootstrapping/SKILL.md` after install. ## When this skill is relevant In your project, after running `install.sh`, this skill auto-triggers when: - Starting work on a new project for the first time (onboarding moment) - User asks which MCPs or skills to install - `package.json` dependencies change since last tool-bootstrap - `.ai-factory/tool-decisions.md` is missing or stale - A consumer who separately runs AIF invokes `/aif` and wants the decisions persisted (AIF is optional — see §2) ## The 6 rules ### Rule 1 — Analyse stack Read `package.json`, `.mcp.json`, and framework config files to enumerate explicit deps, external services, and existing MCP config — those files always exist, so this rule always runs. Reuse the project's stack detector **when one is available** (AIF `/aif` maps language/framework/database to matching skills and MCP servers via its `skills.sh` registry); with no detector present, derive the stack from the same config files you just read. ### Rule 2 — Propose tool set Based on detected stack, sur