brand-voicelisted

# Brand Voice <!-- 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 --> Govern `BRAND-VOICE.md` — the canonical writing voice document for a brand. Two layers: YAML frontmatter (machine-readable normative rules consumed by writing skills) plus eleven prose sections (human-readable rationale). Same split as `DESIGN.md` and the same `design-system` skill pattern: a canonical file at the project root, CLI-style subcommands for the lifecycle. Additional context from the user: $ARGUMENTS ## Subcommand routing Parse the first positi