branded-docxlisted

Creates Word (.docx) documents styled with a brand identity from pluggable theme files (coral, remax, jasminahomes, accessible, magma). Use whenever the user wants a branded, professional Word document - reports, briefs, memos, playbooks, CMAs, listing presentations, market reports, or any .docx where visual quality matters. Triggers: 'branded report', 'coral docx', 'remax report', 'jasminahomes style', 'Jasmina Homes', 'magma docx', 'magma report', 'my brand', 'in my style', 'Anthropic style', 'styled document', 'polished report', 'make it look professional', 'convert this markdown', 'with logo', 'add signature block', 'accessible', 'large print', 'big font', 'easier to read', 'for my father', 'for someone older', 'reading glasses', 'elder reader', 'presbyopia'. Also triggers when the user names a brand or asks for 'my usual theme'/'my usual brand'. Reads brands/ to apply the theme. Logos and signature blocks are optional, off by default. All base DOCX rules apply - see the docx skill.
dzivkovi/claude-skills · ★ 0 · Data & Documents · score 65

Install: claude install-skill dzivkovi/claude-skills

# Branded DOCX - Pluggable Brand Themes This skill extends the base `docx` skill with pluggable brand themes. Follow all technical rules from the base DOCX skill (fonts, lists, tables, page size, etc.). This file adds the brand layer on top. ## Brand Selection 1. List files in `brands/` to see available brands. 2. If the user names a brand matching a filename (e.g., "coral report" matches `brands/coral.md`), read that file. 3. If only one brand file exists, use it without asking. 4. If multiple brands exist and the request is ambiguous, list available brands and ask. 5. Read the selected brand file. Use its `BRAND` tokens, `COVER` tokens, `brandStyles`, and design principles for all document generation. 6. If the brand file does not define a `COVER` object, use defaults: `barColor: BRAND.accent`, `categoryColor: BRAND.accent`, `categorySpacing: 0`, `categoryCaps: false`, `titleSpacing: 0`. --- ## NODE_PATH Preamble Every generated script must start with this so globally-installed npm packages resolve regardless of working directory: ```javascript const { execSync } = require('child_process'); if (!process.env.NODE_PATH) { process.env.NODE_PATH = execSync('npm root -g').toString().trim(); require('module').Module._initPaths(); } ``` --- ## Markdown-to-DOCX Conversion Rules When the user provides markdown, apply these mappings automatically: | Markdown element | Branded DOCX equivalent | |-----------------|------------------------| | First `#` heading | Cover pag