← ClaudeAtlas

docx-builderlisted

Use this skill to create professional, fully-editable Word (.docx) documents — reports, letters, contracts, memos, manuals. Design the document as flowing HTML/CSS (preview it as an Artifact to iterate visually with the user), then run the included Playwright + python-docx pipeline to convert the HTML into native, editable Word content (real headings, paragraphs with per-run formatting, lists, tables, images) — not a screenshot dump. Trigger on "make a Word document", "build a docx", "write a report", "draft a letter/contract", "create documentation".
Julien339/docx-builder-skill · ★ 0 · Data & Documents · score 72
Install: claude install-skill Julien339/docx-builder-skill
# DOCX Builder Two-stage workflow: **design in HTML** (fast to iterate, easy to preview), then **compile to native DOCX** (fully editable in Word — real headings, paragraphs, lists, tables, not an image). **This is a flowing document, not a slide/canvas.** Unlike the sibling `pptx-builder`/`pdf-builder` skills (absolute pixel positions on a fixed canvas), a Word document's content reflows — so this pipeline reads **document order and computed style**, not pixel coordinates. Write the HTML as a normal top-to-bottom page, no `position:absolute`. If what's actually wanted is a pixel-exact one-pager/flyer, use `pdf-builder` instead — that's a different authoring model, not just a different file extension. ## Stage 0 — Pick a style (fonts + accent color) Before writing any HTML, settle on a visual identity so headings, body text and tables stay consistent throughout instead of improvising fonts and colors section by section. 1. Publish `templates/style-gallery.html` as an **Artifact**. It shows 8 named presets (A–H), each pairing a heading/body font choice with one accent color and a rule/table-header treatment. Ask the user to pick a letter, or to describe a tweak (e.g. "F but in blue"). 2. **If the user already has a brand or template to match** — an existing `.docx`, a brand guideline, or explicit fonts/colors — skip the gallery and use that instead. 3. Whichever path was used, write down the resolved heading font, body font, accent color, and heading col