Document design
This skill should be used when the user asks to "create a proposal", "design a report", "make a one-pager", "build a PDF", "create a newsletter", "design slides", "make event materials", "design a flyer", or needs help with print-ready HTML documents. Provides brand configuration, CSS patterns for print layout, and document design best practices.
What this skill does
# Document design Create professional, print-ready HTML documents that export to PDF with customizable branding. ## Brand configuration Before creating documents, check for brand configuration in `.claude/pdf-playground.local.md`. If found, use those settings. If not, use sensible defaults or ask the user for their brand colors. ### Reading brand config Look for `.claude/pdf-playground.local.md` in the project root. Parse the 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** in `.claude/pdf-playground.local.md` 2. **Load template** from `${CLAUDE_PLUGIN_ROOT}/templates/` 3. **Apply brand settings** to CSS variables and content 4. **Customize content** based on user requirements 5. **Save HTML file** in current working directory 6. **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 `${CLAUDE_PLUGIN_ROOT}/templates/`: - `proposal-template.html` - `report-template.html` - `onepager-template.html` - `newsletter-template.html` - `slides-template.html` - `event-template.html` ### Brand examples Example brand configurations in `${CLAUDE_PLUGIN_ROOT}/brands/`: - `default.yaml` - Default brand settings - `ccm.yaml` - Center for Cooperative Media - `example-newsroom.yaml` - Sample newsroom config ### Reference files For detailed CSS patterns: `references/css-patterns.md`
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".