claude-mdlisted

# CLAUDE.md <!-- canonical:writing-rules:start --> ## Important — Writing rules These rules govern every prose artifact this skill emits — READMEs, CHANGELOGs, commit messages, PR bodies, release notes, doc paragraphs, non-trivial comments. Apply them at draft time, verify before output. - Match the surrounding style — punctuation, capitalization, backtick conventions, em-dash vs parens, bullet style. - Every sentence changes the reader's understanding. Cut it otherwise. - Front-load the verb — "Creates", not "This helps you create". - Concrete over abstract. Lists for ≥3 enumerable items. - Assert positively. Reserve negation for real constraints (`NEVER commit secrets`). - No marketing words: powerful, robust, seamlessly, leverage, unlock, comprehensive, delightful. - No AI tells: delve, tapestry, intricate, pivotal, testament, underscore, crucial, garner, showcase, additionally, moreover, furthermore, indeed. - After drafting English prose, invoke `/humanize-en` if installed. <!-- canonical:writing-rules:end --> ## Core Principle Memory files consume tokens every session. Keep them minimal — include only what the agent cannot discover on its own or what a tool doesn't already enforce (linter, TypeScript, tests). Three mechanisms carry knowledge across sessions: - **CLAUDE.md** — single-file instructions you write. Always loaded. - **`.claude/rules/`** — modular rule files, optionally path-scoped. Load alongside CLAUDE.md. - **Auto memory** — notes Claude writes itse