adopt-project

# Adopt agent-starter in an Existing Project <!-- Mirrors ADOPT.md in the agent-starter repo. If ADOPT.md changes, update this skill to match. --> Use on an existing codebase. Never on a green field - that's `/new-project`. An existing project has state to audit, every change is potentially destructive, and adoption must be incremental. So the flow is **audit-first, merge-don't-overwrite, opt-in per component**. ## Safety rails (read first) - Create a branch before any write: `git checkout -b adopt/agent-starter`. Everything below is reversible by dropping the branch. - Read every file before modifying it. Append and merge; never replace a file the developer wrote. - After each merge-tier step, run the project's own test suite (and linter, if present). A red suite means stop and surface it. - If the project has no tests, say so explicitly and default to the non-invasive tier only. - Surface contradictions between starter patterns and existing conventions; never resolve them silently. ## Phase 1: Interview Ask one at a time: 1. **Components** - which are you interested in? (hooks / skills / CLAUDE.md + memory / lint configs / code patterns / "audit first, then decide") 2. **Repo path** - local path to agent-starter, e.g. `~/code/agent-starter` (only needed if files will be copied). ## Phase 2: Audit (read-only) Build a gap report before proposing anything. **Detect the stack:** - `package.json` + `tsconfig.json` → TypeScript/JavaScript - `pyproject....