Project CLAUDE.md Init

Scaffold this project's agent-instruction files and harness config when they don't yet exist. This is the additive counterpart to audit-project-claude (which is subtractive — it critiques files that already exist). Same bar applies: every line in a CLAUDE.md loads into every session, so only earn-the-line facts go in. Propose before writing; don't create files until approved.

Be efficient: delegate discovery to an Explore subagent and work from its condensed findings + file:line refs. Don't pull whole files into the parent context.

Step 1 — Global baseline

Read ~/.claude/CLAUDE.md once. Treat everything in it (communication style, "read first", code-style defaults, discuss-before-implementing, backpressure/verification, the safety hooks) as ALREADY IN EFFECT. Nothing you scaffold may restate or weaken any of it.

Step 2 — Detect (subagent)

Dispatch Explore to report:

• Which of CLAUDE.md, AGENTS.md, .claude/settings.json already exist (root + nested).
• Monorepo layout (workspaces / packages / apps), if any.
• Build·test·lint·format tooling, package manager, language(s) — from manifests (package.json, pyproject.toml, Makefile, justfile, CI config, etc.) and README.

If the substantive files already exist, stop and point the user at /audit-project-claude instead — this skill is for greenfield scaffolding, not critique.