document-design — Claude Code skill: PDF and install
document-design builds print-ready HTML for PDF export with brand styling. Use it for reports, proposals, one-pagers, newsletters, slides, or flyers.
MIT 255 installs ★ 458 updated 2026-10-24
npx skills add jamditis/claude-skills-journalism --skill document-design -a claude-codeWhat document-design does
This skill creates print-ready HTML documents with configurable branding and PDF export. It targets Letter pages and sets page dimensions, margins, typography, colors, and fixed footers. CSS variables, reusable templates, and print rules shape the output.
Before writing a document, it checks pdf-playground.local.md in the project root, then .claude/pdf-playground.local.md as a legacy fallback. The selected YAML file can define the organization, colors, fonts, heading case, and related style settings. When no configuration is present, the skill uses its listed defaults or asks for brand colors.
The installed resources include templates for proposals, reports, one-pagers, newsletters, slides, and events. The workflow saves HTML in the current working directory and can offer a Playwright browser preview. A screenshot check of the page bottom is required before delivery, since content can run into the footer.
What it helps with
- turn a template and source data into a PDF
- apply brand colors and fonts to a document
- lay out a report with fixed page dimensions
- prepare slides or a flyer for printing
- catch content overflow before export
Example prompts for the agent
- Create a print-ready report from
report-template.htmland save the HTML in the current directory. - Read the brand configuration and build a one-page document for PDF export.
- Use
slides-template.htmlfor a deck, replace local image references with available assets, and inspect the bottom of every page.
How to install document-design
1Skills CLI (Vercel)
npx skills add jamditis/claude-skills-journalism --skill document-design -a claude-code2Manually: put the files in place
~/.claude/skills/document-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/document-design/
1Skills CLI (Vercel)
npx skills add jamditis/claude-skills-journalism --skill document-design -a codex2Manually: put the files in place
.agents/skills/document-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jamditis/claude-skills-journalism --skill document-design -a cursor2Manually: put the files in place
.cursor/skills/document-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jamditis/claude-skills-journalism pdf-playground/skills/document-design2Manually: put the files in place
.github/skills/document-design/SKILL.md1Skills CLI (Vercel)
npx skills add jamditis/claude-skills-journalism --skill document-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/jamditis/claude-skills-journalism --path pdf-playground/skills/document-designManually: put the files in place
.devin/skills/document-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jamditis/claude-skills-journalism --skill document-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about document-design
How do I install document-design in Claude Code?
Run npx skills add jamditis/claude-skills-journalism --skill document-design -a claude-code. The skill file is placed at ~/.claude/skills/document-design/SKILL.md.
What does document-design do?
It produces branded, print-ready HTML for PDF export. The skill covers page layout, typography, footers, print CSS, and document templates.
Which brand configuration files does document-design check?
It checks pdf-playground.local.md in the project root first, then .claude/pdf-playground.local.md. If both are present, the project-root file takes precedence.
Source text
SKILL.md · MIT
--- name: document-design description: Creates print-ready HTML that exports to PDF. Use to make a proposal, report, one-pager, newsletter, slides, or flyer. --- # Document design Create professional, print-ready HTML documents that export to PDF with customizable branding. ## Brand configuration Before creating documents, check for `pdf-playground.local.md` in the project root. If it is absent, check the legacy Claude Code path `.claude/pdf-playground.local.md`. If both exist, use only the project-root file. If neither exists, use sensible defaults or ask the user for their brand colors. ### Reading brand config Parse the selected config file's YAML frontmatter: ```yaml --- brand: name: "Organization Name" tagline: "Tagline" website: "https://example.com" email: "[email protected]" colors: primary: "#CA3553" secondary: "#000000" background: "#FFFFFF" text: "#2d2a28" muted: "#666666" fonts: heading: "Playfair Display" body: "Source Sans 3" style: headingCase: "sentence" useOxfordComma: true --- ``` ### Default brand values If no config exists, use these defaults: - **Primary color**: `#CA3553` (red) - **Secondary color**: `#000000` (black) - **Heading font**: Playfair Display - **Body font**: Source Sans 3 - **Heading case**: sentence case ## Core principles 1. **Print-first design**: All documents target 8.5" × 11" letter size with proper margins 2. **Brand compliance**: Use colors and fonts from brand configuration 3. **Sentence case by default**: Unless brand config specifies "title" case 4. **Clean exports**: Documents must render correctly when printed to PDF ## CSS variables Generate CSS variables from brand config: ```css :root { --primary: [colors.primary]; --secondary: [colors.secondary]; --background: [colors.background]; --text: [colors.text]; --muted: [colors.muted]; /* Derived colors */ --primary-dark: [darken primary by 15%]; --gray-100: #f5f4f2; --gray-200: #e8e6e3; } ``` ## Print CSS fundamentals ### Page setup ```css @page { size: 8.5in 11in; margin: 0; } @media print { body { -webkit-print-color-adjust: exact !important; print-color-adjust: exact !important; } .page { page-break-after: always; page-break-inside: avoid; } } ``` ### Fixed page dimensions ```css .page { width: 8.5in; height: 11in; padding: 0.5in 0.75in; padding-bottom: 1in; /* Space for footer */ position: relative; box-sizing: border-box; overflow: hidden; } ``` ### Fixed footers ```css .page-footer { position: absolute; bottom: 0.4in; left: 0.75in; right: 0.75in; font-size: 9pt; border-top: 1px solid var(--gray-200); padding-top: 0.1in; background: var(--background); } ``` ### Footer clearance (critical) Content overlapping or touching the footer is a recurring issue. **Preferred layout, grid rows `auto 1fr auto`:** ```css .page { display: grid; grid-template-rows: auto 1fr auto; overflow: hidden; } ``` This makes the header and footer take their natural height, and the content fills the remaining space. No magic-number `calc()` needed, the footer clearance is structural. **Required safeguards:** 1. Use `grid-template-rows: auto 1fr auto` on the page so content automatically gets the space between header and footer 2. Set `overflow: hidden` on the content container to prevent text bleeding past its bounds 3. Include `padding-bottom: 0.3in` (minimum) inside the content area as a buffer 4. Never use hardcoded `height: calc(...)` with magic numbers for header/footer heights, they drift when padding or font sizes change 5. After rendering, always screenshot and visually verify the bottom of the page before delivering 6. If content overflows, **reduce content**, never shrink the footer gap. Tighten the header first if you need more room. ## Typography patterns ### Font loading ```css @import url('https://fonts.googleapis.com/css2?family=[heading-font]:wght@400;600;700&family=[body-font]:wght@400;500;600;700&display=swap'); body { font-family: '[body-font]', Arial, sans-serif; font-size: 11pt; line-height: 1.6; color: var(--text); } h1, h2, h3 { font-family: '[heading-font]', Georgia, serif; font-weight: 700; } ``` ### Heading styles ```css .section-title { font-size: 26pt; color: var(--secondary); margin-bottom: 0.25in; } .section-title::after { content: ''; display: block; width: 0.5in; height: 3px; background: var(--primary); margin-top: 0.12in; } ``` ## Common components ### Cover page header ```html <header class="cover-header"> <div class="logo-bar"> <div class="logo-primary">[brand.name]</div> </div> <div class="cover-title-block"> <div class="cover-eyebrow">[Document type] • [Date]</div> <h1 class="cover-title">[Title in configured case]</h1> </div> </header> ``` ### Budget table ```css .budget-table thead { background: var(--secondary); color: white; } .budget-table tbody tr:last-child { background: var(--primary); color: white; font-weight: 700; } ``` ### Highlight box ```css .highlight-box { background: linear-gradient(135deg, var(--primary) 0%, var(--primary-dark) 100%); color: white; padding: 0.3in; } ``` ## Document creation workflow 1. **Check for brand config** at project-root `pdf-playground.local.md`, then the legacy `.claude/pdf-playground.local.md` fallback 2. **Locate this installed `SKILL.md`** and resolve bundled resources from its directory. Do not assume a plugin-root environment variable is available. 3. **Load template** from the skill-relative `templates/` directory 4. **Apply brand settings** to CSS variables and content 5. **Customize content** based on user requirements 6. **Save HTML file** in current working directory 7. **Offer preview** with Playwright browser tools ## PDF export instructions 1. Open the HTML file in Chrome 2. Press Ctrl+P (or Cmd+P on Mac) 3. Set "Destination" to "Save as PDF" 4. Set "Margins" to "None" 5. Enable "Background graphics" 6. Save the file ## Additional resources ### Templates Pre-built templates in the installed skill's `templates/` directory: - `proposal-template.html` - `report-template.html` - `onepager-template.html` - `newsletter-template.html` - `slides-template.html` - `event-template.html` `slides-template.html` contains illustrative local photo and wordmark paths, not bundled image assets. Before delivering a deck based on it, replace every CSS `url(...)` and `<img src>` reference with an available asset. If the user has no suitable images, remove every unresolved reference, use the template's gradient or solid-color slide variants, and replace a missing wordmark image with text. Never deliver a deck with an unresolved local asset path. ### Brand examples Example brand configurations in the installed skill's `brands/` directory: - `default.yaml` - Default brand settings - `ccm.yaml` - Center for Cooperative Media - `example-newsroom.yaml` - Sample newsroom config ### Reference files For detailed CSS patterns, use the installed skill's `references/css-patterns.md`. ### Preview controls Reusable preview assets are in the installed skill's `controls/` directory. These files are resources for document generation; they do not turn the Claude-only preview command or plugin hook into Codex features. ## Related Use **document-delivery** to inspect, share, send, and verify the final PDF or editable document.
© jamditis · MIT · jamditis/claude-skills-journalism