← ClaudeAtlas

brand-docxlisted

Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our brand kit", "generate a branded report from our profile", or when a ./brand-kit exists. For one-off Word edits with NO saved brand profile, use the docx skill instead. NOT for .pptx (brand-pptx), .xlsx (brand-xlsx), or PDFs.
ferdinandobons/brand-docs · ★ 44 · Data & Documents · score 83
Install: claude install-skill ferdinandobons/brand-docs
# brand-docx Use this skill when the user wants a reusable Word brand kit or wants to create a new on-brand `.docx` from a company template and variable content. This is an AI-agent skill for Codex and Claude Code. The user should not need to write JSON or run shell commands. The agent converts the user's content into an IntermediateDocument, invokes the internal engine, verifies the output, and returns the generated `.docx`. ## The four verbs Every brand skill (`brand-docx`, `brand-pptx`, `brand-xlsx`) implements the same contract: **extract / comprehend / verify / generate**. | Verb | Input | Output | |---|---|---| | **extract** | a company `.docx` template | a reusable Brand Profile | | **comprehend** *(optional, model-driven)* | a saved profile + a model-authored `comprehension.json` | the profile with a validated, cached `comprehension` block | | **verify** | a saved Brand Profile | QA findings + a verdict | | **generate** | content (an IntermediateDocument) + a profile | a new on-brand `.docx` | `comprehend` is **optional**: `generate` works on the deterministic profile alone. When a current comprehension is present, `generate` additionally reconciles the template's preserved cover/index structures with the new content. See [reference/comprehension.md](reference/comprehension.md) for the full step. ## Hard Rules - Treat `python scripts/brandkit/cli.py ...` as an internal engine command, not the user-facing workflow. - Run the dependency preflight before starting