branded-docx

name	branded-docx
description	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.
metadata	{"author":"Daniel Zivkovic","version":"2.7.0"}

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:

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 page: if title contains a document type (e.g., "Market Value Analysis"), split into category (accent) + subject (dark). Otherwise, full title in dark + accent top bar
First > blockquote after #	Cover page subtitle (heading font italic, mid gray)
Any date-like line in first 10 lines	Cover page date (heading font, mid gray)
## heading	H1 section heading (heading font bold, accent color, bottom border)
### heading	H2 sub-heading (heading font bold, dark)
#### heading	H3 sub-heading (heading font bold, dark)
Regular paragraph	Body text (body font 11pt, dark)
> blockquote (body)	Callout block (left accent border, accent tint background, indented)
- or * bullet list	Bulleted list (accent bullet dot, body font)
1. numbered list	Numbered list (body font)
--- horizontal rule	Section divider (light gray bottom border)
`	table
**bold**	Bold TextRun. If text ends with :, use accent color + heading font
*italic*	Italic TextRun
`code`	Heading font, mid gray
Fenced code block	Indented block, heading font 9pt, light gray background

Cover page detection

If the markdown begins with a # title, treat the document as having a cover page. Extract:

• Category: if the title names a document type (e.g., "Market Value Analysis", "Comparative Market Analysis", "Project Brief"), use it as the category line in accent
• Title: the main subject - often a property address, project name, or entity. If a category was extracted, look for the subject in the subtitle or first few lines
• Subtitle: first blockquote or italicised line after the title
• Date: any date pattern (e.g. "March 2026", "2026-03-06") in the first 10 lines

If no cover page signals are found, start with H1 directly.

Tonal adaptation

The brand file provides a design vocabulary - not rigid rules. Adapt the palette to the document's emotional context:

• Use accent tint backgrounds on callout blocks for emphasis or caution
• Use success tint backgrounds (from the brand's tertiary color) for positive findings or benefits
• Use the secondary color for neutral data highlights or informational elements
• For data-heavy documents (financial reports, CMAs, analyses), use the table data size (9.5pt) from the brand's Typography Reference - this gives tables professional density without sacrificing readability

The brand file defines the palette; you decide when each color serves the content best.

Text fidelity

When converting user-provided markdown, preserve the exact wording. Do not paraphrase, summarize, reorder sections, or add/remove content. Styling, color, and layout decisions are yours - the text is the user's.

When no markdown is provided

Generate the document from the user's description. Ask for content if none is given.

Logo usage

Logos are off by default unless the brand file specifies otherwise. Only include a brand logo when the user explicitly asks for it (e.g., "add the logo", "include a signature block", "with branding") - unless the brand file sets logoDefault: "on", in which case include the logo automatically and only omit it if the user explicitly asks (e.g., "no logo", "without logo", "skip the logo"). Brand files may bundle a *-logo.png file alongside their .md - check the brand file's Logo section for the filename, recommended sizes, and placement guidance. If no logo file exists for the active brand, skip silently.

Default contact info

Brand files may include a DEFAULTS object with contact details (name, title, company, phone, email). When generating signature blocks or contact sections, use these defaults if the user hasn't specified their own info. User-provided values always override defaults. If the brand file has no DEFAULTS, ask the user for contact info when needed. Do not add a website line to signature blocks unless the source document explicitly mentions one.

---

Helper Function Templates

These reference BRAND.* keys defined in the brand file. Copy them into generated scripts.

Page Setup

sections: [{
  properties: {
    page: {
      size: { width: 12240, height: 15840 },
      margin: { top: 1440, right: 1440, bottom: 1440, left: 1440 }
    }
  },
  headers: { default: brandHeader("Document Title") },
  footers: { default: brandFooter() },
  children: [ /* content */ ]
}]

Branded Header

function brandHeader(title) {
  return new Header({
    children: [
      new Paragraph({
        border: { bottom: { style: BorderStyle.SINGLE, size: 4, color: BRAND.accent, space: 4 } },
        tabStops: [{ type: TabStopType.RIGHT, position: TabStopPosition.MAX }],
        children: [
          new TextRun({ text: title, font: BRAND.heading, size: 16, color: BRAND.midGray }),
          new TextRun({ children: [new PositionalTab({ alignment: PositionalTabAlignment.RIGHT, relativeTo: PositionalTabRelativeTo.MARGIN, leader: "none" })], font: BRAND.heading, size: 16, color: BRAND.midGray }),
          new TextRun({ children: [PageNumber.CURRENT], font: BRAND.heading, size: 16, color: BRAND.accent }),
        ]
      })
    ]
  });
}

Branded Footer

When the brand file has a DEFAULTS object, use the contact info in the footer. Fall back to "Confidential" if no defaults are available.

function brandFooter() {
  // Build a single-line contact string from DEFAULTS (if available)
  const parts = [DEFAULTS.name, DEFAULTS.title, DEFAULTS.company, DEFAULTS.phone].filter(Boolean);
  const contactLine = parts.length > 0 ? parts.join("  |  ") : "Confidential";

  return new Footer({
    children: [
      new Paragraph({
        border: { top: { style: BorderStyle.SINGLE, size: 4, color: BRAND.lightGray, space: 4 } },
        spacing: { before: 120, after: 0 },
        children: [
          new TextRun({ text: contactLine, font: BRAND.heading, size: 14, color: BRAND.midGray })
        ]
      })
    ]
  });
}

Cover Page

The cover page supports an optional category parameter for a type-first reading order - the document type appears first in accent (e.g., "MARKET VALUE ANALYSIS"), then the subject in large dark text. If no category is provided, the title displays at full size as before.

function coverPage(title, subtitle, date, category) {
  return [
    new Paragraph({
      border: { top: { style: BorderStyle.SINGLE, size: 48, color: COVER.barColor, space: 0 } },
      spacing: { before: 0, after: 3200 },
      children: []
    }),
    category ? new Paragraph({
      children: [new TextRun({ text: category, font: BRAND.heading, size: 44, bold: true, color: COVER.categoryColor, characterSpacing: COVER.categorySpacing, allCaps: COVER.categoryCaps })],
      spacing: { before: 0, after: 200 }
    }) : null,
    subtitle ? new Paragraph({
      children: [new TextRun({ text: subtitle, font: BRAND.heading, size: 28, color: BRAND.midGray, italics: true })],
      spacing: { before: 0, after: 320 }
    }) : null,
    new Paragraph({
      children: [new TextRun({ text: title, font: BRAND.heading, size: category ? 56 : 72, bold: true, color: BRAND.dark, characterSpacing: COVER.titleSpacing })],
      spacing: { before: 0, after: 240 }
    }),
    new Paragraph({
      border: { bottom: { style: BorderStyle.SINGLE, size: 4, color: BRAND.lightGray, space: 8 } },
      spacing: { before: 0, after: 400 }, children: []
    }),
    date ? new Paragraph({
      children: [new TextRun({ text: date, font: BRAND.heading, size: 20, color: BRAND.midGray })],
      spacing: { before: 0, after: 0 }
    }) : null,
  ].filter(Boolean);
}

Section Divider

function sectionDivider() {
  return new Paragraph({
    border: { bottom: { style: BorderStyle.SINGLE, size: 2, color: BRAND.lightGray, space: 1 } },
    spacing: { before: 360, after: 360 },
    children: []
  });
}

Callout Block

Add a faint tinted background to callout blocks for visual weight. Use the accent tint by default; switch to the success tint (or other tonal colors from the brand file) when the content is positive or celebratory. The left border + tint combination makes callouts feel substantial without being heavy.

new Paragraph({
  style: "Callout",
  shading: { fill: "FFF5F5", type: ShadingType.CLEAR }, // accent tint - adapt per tone
  children: [
    new TextRun({ text: "Key insight: ", font: BRAND.heading, size: 22, bold: true, color: BRAND.accent }),
    new TextRun({ text: "Your callout text here.", font: BRAND.body, size: 22, color: BRAND.dark })
  ]
})

Branded Table

Table data uses 9.5pt (size 19) for a tighter, more professional density - smaller than body text but still readable. Header labels use the heading font at 9pt.

function brandTable(headers, rows, contentWidth = 9360) {
  const colWidth = Math.floor(contentWidth / headers.length);
  const border = { style: BorderStyle.SINGLE, size: 1, color: BRAND.lightGray };
  const borders = { top: border, bottom: border, left: border, right: border };

  return new Table({
    width: { size: contentWidth, type: WidthType.DXA },
    columnWidths: headers.map(() => colWidth),
    rows: [
      new TableRow({
        tableHeader: true,
        children: headers.map(h => new TableCell({
          borders,
          width: { size: colWidth, type: WidthType.DXA },
          shading: { fill: BRAND.dark, type: ShadingType.CLEAR },
          margins: { top: 80, bottom: 80, left: 160, right: 160 },
          verticalAlign: VerticalAlign.CENTER,
          children: [new Paragraph({
            spacing: { before: 0, after: 0 },
            children: [new TextRun({ text: h, font: BRAND.heading, size: 18, bold: true, color: "FFFFFF" })]
          })]
        }))
      }),
      ...rows.map((row, i) => new TableRow({
        children: row.map(cell => new TableCell({
          borders,
          width: { size: colWidth, type: WidthType.DXA },
          shading: { fill: i % 2 === 0 ? "FFFFFF" : BRAND.lightGray, type: ShadingType.CLEAR },
          margins: { top: 80, bottom: 80, left: 160, right: 160 },
          verticalAlign: VerticalAlign.TOP,
          children: [new Paragraph({
            spacing: { before: 0, after: 0 },
            children: [new TextRun({ text: String(cell), font: BRAND.body, size: 19, color: BRAND.dark })]
          })]
        }))
      }))
    ]
  });
}

---

Font fidelity (read before generating)

Brand fonts only render true if the machine that generates or opens the file actually has them, as usable static cuts. This is the most common reason a document looks rough. Before generating, run the font preflight (it fails loud rather than letting a render silently substitute):

# Verify the brand's fonts resolve, or instance/install them; see the brand file for exact flags.
python scripts/setup/font_preflight.py --family <BrandFont>

Two rules that catch most defects, both detailed in references/font-fidelity.md:

• On a headless Linux box, a proprietary font like Georgia is absent and substitutes to the wrong typeface. Use the metric-compatible open replacement (Gelasio for Georgia), never a look-alike. The coral and jasminahomes brand files carry the one-command recipe.
• A bare variable font is read as "Thin" by LibreOffice and some Word installs. Install static Regular/Bold cuts; the preflight instances them.

Before the file leaves your machine, embed the fonts (Word: File, Options, Save, "Embed fonts in the file") or export to PDF, so a recipient without the brand fonts still sees the design. Installing fonts on your machine fixes your render, not theirs.

Setup

1. Node.js installed (node --version)
2. npm install -g docx
3. Check your brand file for required fonts, and run the font preflight above (scripts/setup/font_preflight.py)

All base DOCX technical rules apply - read the docx skill for details on lists, images, hyperlinks, page breaks, and XML editing.