brand-docs

---

What is BrandDocs?

BrandDocs is an open-source agent-skill bundle that learns a company's existing Office templates and generates new on-brand documents from them. Point it at one branded .docx, .pptx, or .xlsx; it extracts the brand (theme colors and fonts, named styles, the document's structure, layouts, cover anchors, logos and tables) into a portable Brand Profile. From then on, every document it generates is built from the original template shell and uses only the artifacts the template actually defines. Each format stays in its own lane: there is no cross-format conversion.

The core guarantee: off-brand output is impossible by construction. No generator ever writes a literal style name, hex color, or font: those live only in the Brand Profile, and verify refuses a profile that points at anything the template doesn't contain.

At a glance

Question	Answer
Input	Existing company .docx, .pptx, or .xlsx templates
Output	Same-format on-brand Word documents, PowerPoint decks, and Excel workbooks
Works with	Claude Code, Codex, compatible AI agents, or the direct Python CLI
Best for	Repeatable reports, decks, workbooks, proposals, memos, briefs, and internal document workflows
Privacy model	Local-first; no cloud service is required, and real templates are git-ignored
Speed	First run on a new template: up to ~15 min end to end (extract + model comprehension + visual QA); every later document from the saved profile: seconds
Current release	v0.10.0 alpha

---

The three skills

Skill	Format	Generates
brand-docx	Word .docx	reports, letters and memos in the template's structural order
brand-pptx	PowerPoint .pptx	decks from the template's real masters & layouts, with native charts, diagrams & merged tables
brand-xlsx	Excel .xlsx	workbooks: named-region fills with formulas preserved and brand number formats

All three share one engine and expose the same verbs: extract → comprehend (optional, model-driven) → verify → generate, plus the learning verbs learn / propose-overrides / refine that fold QA findings and user feedback back into the profile. Details → documentation/SKILLS.md.

Several templates, one brand? extract --blend folds a second same-format template into a saved profile at the value-fact level: it fills gaps and corroborates agreements, the primary template wins every conflict, and the brand guarantee is untouched because artifact pointers never cross templates. compare-profiles reports brand drift (theme colors, fonts, off-theme usage) between any two saved profiles and exits non-zero on drift, so it can gate brand coherence in CI.

Two-phase by design: the deterministic engine works with no model at all (extract / verify / generate, fully offline); the model-assisted verbs sit ON TOP and can only NAME captured facts - every proposal is validated fail-closed, so the brand guarantee never depends on a model being right.

---

Prerequisites

BrandDocs runs locally and needs a few things installed before first use: