ce-house-style

# CE House Style Shared Collision Engineers house style and a self-contained branded-document generator. Load this skill whenever document layout, written tone, or producing a branded DOCX/PDF is needed. ## Modes | Mode | Use when | Load | | --- | --- | --- | | `document-builder` | Producing a branded CE document — letter, report, fee note, certificate — as DOCX and/or PDF. | `references/document-spec.md`, `scripts/ce_document.py`, `assets/examples/` | | `visual-layout` | Checking or describing brand layout (logo, typography, headers/footers, brand red, templates). | `references/visual-layout.md` and `assets/` | | `writing-tone` | Drafting or revising client, court, insurer, invoice, rebuttal, valuation, or status wording. | `references/writing-tone.md` and `references/query-responses.md` | ## Building a branded document The builder is self-contained (pure-Python ReportLab + python-docx, no system libraries), so it runs anywhere including Claude Desktop. One-time setup: ```powershell python -m pip install -r src/skills/ce-house-style/requirements.txt ``` Describe the document as a JSON spec (schema in `references/document-spec.md`; start from `assets/examples/report.json` or `letter.json`), then render: ```powershell python src/skills/ce-house-style/scripts/ce_document.py --spec my-spec.json --format both --out output ``` `--format` is `docx`, `pdf`, or `both`. The brand — logo, reference block, footer, red rules, table styling, fonts, margins — is applied automatically; you supply only the content. For the *wording*, follow `writing-tone.md` and reuse `query-responses.md`. ## Governance Assist/reference class. This skill formats and styles output; it does not approve expert findings or authorise external sends. The calling skill owns sign-off: valuation, roadworthy, rebuttal, salvage, and damage-estimating expert outputs remain AI-assisted drafts until a named human signs off. ## Validation - Drafts: `python src/skills/ce-house-style/scripts/check_house_style.py <draft-or-spec>` flags AI tell-tales and internal workflow terms before anything goes out. - Generated documents: render `assets/examples/report.json` and `letter.json` and compare against the worked examples in `assets/` and `docs/reference/case-corpus/`. - Repository changes: `python tools/verify_scaffold.py`.