refactor-claude-md

# Overview Refactor a CLAUDE.md toward progressive disclosure. Every line it keeps is loaded into every session the file covers, and a frontier model follows only around 150 to 200 standing instructions consistently, so each line competes for that budget. Everything else moves down the ladder or out of the file. ## Instructions 1. **Pick the target.** If the invocation names one, use it. Otherwise ask with `AskUserQuestion`, one option per file that exists, with the resolved path in the label: - The user-level CLAUDE.md at `~/.claude/CLAUDE.md` - The current project's CLAUDE.md 2. **Fetch the yardsticks.** Fetch these pages. They calibrate the delete and rewrite verdicts below: - https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices - https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-fable-5 - https://www.aihero.dev/a-complete-guide-to-agents-md 3. **Audit.** Read the file and give every instruction exactly one verdict, judged against the target's bar below. Done when no instruction lacks one. - **contradiction**: conflicts with another instruction. Record both sides. - **delete**: fails the no-op test, meaning the agent would behave the same without it. Covers instructions the agent already follows by default, instructions too vague to act on, and platitudes like "write clean code". - **demote**: real instruction that only applies to some paths or tasks. Pi...