where-claudelisted

# Where to run /init (nested CLAUDE.md placement scout) Project-agnostic, global skill. It scans the current repo and reports the directories that would most benefit from their own nested `CLAUDE.md`, ranked, each with a one-line reason. It does **not** create the files - it removes the guesswork of deciding where `/init` is worth running. It pairs with `/init`: `/init` *writes* a CLAUDE.md for a directory; this skill decides *which* directories are worth that cost. ## Why nesting matters (the model that drives every decision) Claude Code auto-loads the `CLAUDE.md` in the cwd and its parent directories, and pulls in a **nested** `CLAUDE.md` on demand only when work happens inside that subtree. So a nested file is cheap (loaded only when relevant) but only earns its keep when the subtree has *local* context a parent file does not already supply. Two failure modes to avoid: - **Over-placement:** a CLAUDE.md in every folder = duplicated/contradictory context and maintenance burden. Most directories should NOT get one. - **Redundant placement:** recommending a child when its parent already covers it. Bias to restraint: a few high-value placements beat a long list. ## Scoring heuristic (what makes a directory a candidate) Score each directory on these signals; recommend only those that clearly clear the bar. **Positive signals (raise the score):** - **Module boundary** - has its own manifest: `package.json`, `pyproject.toml`, `setup.py`, `go.mod`, `Cargo.toml`, `*.csproj