THIS IS ACTUAL F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code. The idea: stop configuring Claude Code by hand. One prompt, 44 seconds, and your whole .claude/ folder writes itself. 7 files, 162 lines, 2 cents. you typed one line and wrote zero of them. You just launch Claude Code like this: claude --model opus "set up this repo: ..." here's the split: → 3 Haiku 5.5 agents scan the repo before a single file gets written → one reads the stack, one reads the npm scripts, one hunts for risky paths → Opus 5.5 takes those three summaries and writes the actual config → 7 files land: CLAUDE.md, 3 agents, permissions, a format hook and a /ship skill the part everyone gets wrong: they write CLAUDE.md from memory. a config written without reading the repo is a guess, and you live with that guess for months. here the risk scan came back with 5 dangerous paths and those went straight into the permissions file, so the agent is blocked from them before it ever runs once. the scripts scan found 5 npm scripts, and the agents got wired to the ones that actually exist in this repo instead of generic placeholders. one prompt from you, 7 files from it, 0 lines written by hand. Haiku reads. Opus writes. You commit. JEV engineering is the same move one layer down: 1,867 forks this run - which file, which agent, allow or ask - resolved in code at 0.97 sharpness, and the split ones (0.59 on "allow or ask") come back to you instead of being guessed the full tree ▸ you paste one prompt describing the setup you want ▸ 3 Haiku 5.5 agents scan stack, scripts and risky paths in parallel ▸ every agent returns a summary, never raw files ▸ Opus 5.5 writes CLAUDE.md, the agents, permissions, the hook and the skill ▸ anything touching permissions comes back to you before it is written ▸ JEV resolves micro-forks in code and escalates only the split ones paste the tree and this prompt into Claude Code ↓ "Set up this repo for me: 1. First scan it with 3 Haiku 5.5 agents in parallel: one reads the stack and manifests, one reads the build and npm scripts, one finds paths that are dangerous to touch. 2. Each agent returns a summary only, never raw file contents. 3. Then write CLAUDE.md, 3 subagents, a permissions file, a format hook and a /ship skill, all based on what the scan actually found, not on defaults. 4. Every risky path from the scan goes into the deny list before anything runs. 5. Ask me before writing anything that grants permissions. Show me every file as a diff first. No writes until I say go." ↳ code.claude.com/docs/en/mode… save it, this is the first thing you run in every new repo.