bootstrap-agent-configlisted

# Bootstrap agent config for a repository Produce a `CLAUDE.md` and a symlinked/parallel `AGENTS.md` that are *grounded in the real repo*, not generic boilerplate. A good config is the single highest-ROI thing for agent productivity in a codebase — it pays for itself on the first task. ## Steps 1. **Detect the stack.** Run the helper to get a fast inventory: ``` bash "${CLAUDE_SKILL_DIR}/detect-stack.sh" . ``` It reports languages, package managers, build/test/lint commands, monorepo layout, and whether ADRs/CI exist. 2. **Verify, don't trust.** Confirm the detected build/test commands actually exist (read the Makefile / package.json / justfile). Read 2–3 representative source files to learn the real conventions (error handling, test style, naming). 3. **Find the invariants.** The most valuable part of a `CLAUDE.md` is the *load-bearing rules* — the things that cause incidents if violated. Look for them in: existing ADRs, `ARCHITECTURE.md`, `SECURITY.md`, README "gotchas", and patterns the code enforces (e.g. tenant scoping, a trust boundary, a generated file you must not hand-edit). Ask the user if the architecture isn't legible. 4. **Draft `CLAUDE.md`** using the structure in `${CLAUDE_SKILL_DIR}/../../../templates/CLAUDE.md.tmpl` as a skeleton. Fill every placeholder with real, verified content. Sections that matter most: - One-sentence "what this is" - Languages and *exact* build/test/lint commands (copy-pasteable) - R