← ClaudeAtlas

docx-brandkitlisted

Use when the user asks for a Word document, .docx, report, spec, handbook, onboarding doc, proposal, or runbook — or asks to brand/theme generated Word output, set up a document theme, or fix a .docx that Word shows with the wrong page count. Produces themed .docx via the docx-brandkit toolkit rather than hand-written OOXML.
the3ma/docx-brandkit · ★ 0 · Data & Documents · score 65
Install: claude install-skill the3ma/docx-brandkit
# docx-brandkit Build branded Microsoft Word `.docx` files from a JSON theme plus a small Node build script. The theme carries every brand decision (colors, fonts, sizes, spacing, markers, feature toggles); the build script carries only content. **Core principle: never hand-write OOXML, and never hard-code brand values into a build script.** Both are how these documents rot. Put brand in the theme, content in the script. ## When to use - The user wants a `.docx`: report, spec, handbook, onboarding doc, proposal, runbook, meeting pack. - The user wants generated Word output to match a company's brand. - A generated `.docx` opens in Word with a wrong page count (see Bake, below). **When not to use:** plain Markdown or HTML output is enough; the user wants `.pptx` or `.xlsx`; the user wants to edit an existing `.docx` in place — this toolkit generates, it does not round-trip. ## Setup Once per project. The wizard writes `brandkit.config.json` and, next to it, `brandkit.schema.json` for editor autocomplete. ```bash npx brandkit init # interactive wizard npx brandkit presets # see the built-in starting points npx brandkit doctor # check node, docx, unzip, Word COM, config ``` Non-interactive (scripts, CI, or when the user already told you the brand): ```bash npx brandkit init --yes --name "Acme Corp" --primary "#0F5C8C" --accent "#E67E22" --preset corporate-blue ``` `--primary` alone is usually enough: `primaryDark` is derived from it. Only a