Pro Report Builder

Pro Report Builder

Polished consulting reports as standalone HTML. Export to PDF via Chrome headless.

Install

git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/pro-report-builder ~/.claude/skills/

Quick Reference

When to Use This Skill vs pro-deck-builder

Before You Start

Step 1: Understand the Brief

Ask the user:

1. What type of document? Audit report, assessment, technical brief, case study?
2. How many pages roughly? Helps plan section flow and page distribution.
3. What data do they have? Raw numbers, API exports, spreadsheets? Pull exact values -- never estimate when actuals exist.
4. Where should the file be saved? Default: ./output/

Step 2: Plan the Document Structure

Every report follows this structure:

Cover Page --> Executive Summary --> Analysis Sections (3-6) --> Prioritized Recommendations --> Quick Wins --> Appendix

Each analysis section should occupy 1-2 pages. Recommendation cards are the most space-intensive component -- budget carefully.

Design System

Customizable Brand Identity

The included design system provides a professional default. All color tokens, typography, and spacing are defined as CSS custom properties in :root. Override these to match your brand.

Color Tokens

:root {
  /* Accent -- change this to your brand color */
  --accent:        #3D7A5C;
  --accent-dim:    rgba(61, 122, 92, 0.08);
  --accent-dark:   #2E6B4A;
  --accent-light:  #6AB88A;

  /* Severity */
  --excellent:     #2e8b57;
  --warning:       #D97706;
  --critical:      #c0392b;

  /* Light-mode backgrounds (warm cream) */
  --bg-page:       #FAF7F2;
  --bg-surface:    #F2EDE6;
  --bg-elevated:   #EBE5DD;

  /* Light-mode text */
  --text-primary:  #0f0e0e;
  --text-body:     #57606a;
  --text-muted:    #8b949e;

  /* Borders */
  --border:        rgba(15, 14, 14, 0.1);
  --border-dim:    rgba(15, 14, 14, 0.06);

  /* Callout tints */
  --tint-blue:     #eaf2ed;
  --tint-green:    #eaf5ef;
  --tint-red:      #fef2f2;
  --tint-amber:    #fffbeb;

  /* Dark mode (cover page only) */
  --dark-bg:       #141414;
  --dark-surface:  #1E1E1E;
  --dark-text:     #f0f3f6;
  --dark-muted:    #6e7681;
  --dark-secondary:#9ca3af;
  --dark-border:   rgba(255, 255, 255, 0.08);
}

Color rules:

• Warm cream (#FAF7F2) backgrounds on ALL content pages -- NOT white. This is a brand differentiator.
• Dark mode (#141414) is reserved for the cover page only.
• Accent color for accent rules, table headers, bullet markers, priority banner accents, rec-card left stripes. Used deliberately, never for decoration.
• Severity colors (green/amber/red) ONLY for performance indicators. Never decorative.
• Callout tints (blue/green/red/amber) for left-bordered callout boxes matching their severity.

Typography

Critical typography rules:

1. Cover title uses Light (300), NOT Bold. Light at large sizes = confident, premium.
2. Monospace font for ALL numeric/data content. KPI values, table headers, rec-card labels, priority banners.
3. Body text at 9.5pt with 1.6 line-height. Reading-optimized document, not a slide.
4. Table headers are ALL CAPS monospace on accent background. Distinctive table style.

Font defaults (swappable):

• Switzer: loaded from Fontshare CDN (free). Fallback: system-ui, sans-serif
• Cartograph CF: commercial, loaded via local(). Fallback: JetBrains Mono, monospace

Page Dimensions

Width:   8.5in
Height:  11in
Orientation: Portrait

Spacing

Component Library

All components are documented with full HTML + CSS in REFERENCE.md. Here is what is available:

Page Structure

Data Display

Content Blocks

Recommendations

Document Compositions

Mandatory Pages

Every report must include:

1. Cover Page (.cover-page) -- Dark background, document title, metadata (date, account, period)
2. Executive Summary -- KPI row + key findings callout + brief narrative
3. Recommendations -- Prioritized rec-cards grouped by priority tier
4. Quick Wins -- Short action table for immediate wins

Content Page Types

Narrative Rules

1. One section per page when possible. If a section spans multiple pages, use "(continued)" on subsequent pages.
2. Lead with the data. Tables and KPI cards BEFORE the narrative explanation.
3. Callout after evidence. Every data table should be followed by a callout summarizing the key insight.
4. Never estimate when actuals exist. If the data has exact values, compute precise totals.
5. Benchmark everything. Always show industry benchmarks alongside metrics.
6. Severity colors = signal. Green/amber/red ONLY for performance indicators.
7. Callout colors match severity. .callout-green for strengths, .callout-red for problems, .callout-amber for warnings, .callout-blue for neutral insights.
8. Accent rules under section titles. Every .section-title is followed by <hr class="accent-rule">.
9. Consistent rec-card fields. Every recommendation card should have at minimum: title bar, ISSUE, ACTION fields.

Page Overflow Prevention

Pages are fixed at 11in tall. Content that exceeds the page container overflows visibly in the PDF. Every page must be budgeted before building.

Height Budget

Component Density Limits

Page Break Strategy

1. Test every page in the browser before exporting to PDF
2. Redistribute content across pages when overflow occurs
3. Each <div class="page"> is one PDF page
4. Use .keep-together on components that should not split across pages
5. Update ALL downstream page numbers when redistributing

Anti-Patterns (Never Do)

1. No white backgrounds. Always #FAF7F2 (warm cream) for content pages.
2. No bold section titles. Use Regular (400) for .section-title.
3. No decorative accent bars beyond the 40px accent rule under section titles.
4. No emoji in reports. Unless the user explicitly requests them.
5. No dark-mode content pages. Dark is only for the cover page.
6. No walls of text. Break long prose into bullet lists. Max 3 sentences per callout.
7. No unformatted numbers. Always use $X,XXX or $XXXK with tabular-nums.
8. No inline styles when a class exists. Use the component library.
9. No monospace fonts in page footers. Use body font for footers.
10. No orphan rec-cards. Priority tier banner + first card must be on same page.
11. No missing accent rules. Every .section-title must be followed by <hr class="accent-rule">.

PDF Export

Automated Export (Preferred)

Use Chrome headless for reliable 8.5x11" portrait PDF generation:

"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
  --headless \
  --disable-gpu \
  --print-to-pdf="/OUTPUT/PATH/report.pdf" \
  --no-pdf-header-footer \
  --print-to-pdf-no-header \
  "file:///PATH/TO/report.html"

Manual Export (Fallback)

1. Open the HTML file in Chrome
2. Cmd+P --> Save as PDF
3. Set margins to "None"
4. Enable "Background graphics"
5. Paper size: Letter (8.5" x 11")

Required Print CSS

Every report MUST include this @page rule and @media print block:

@page { size: 8.5in 11in; margin: 0; }
@media print {
  * { print-color-adjust: exact; -webkit-print-color-adjust: exact; }
  body { background: white; margin: 0; }
  .page {
    margin: 0;
    box-shadow: none;
    page-break-after: always;
    page-break-inside: avoid;
    width: 8.5in;
    min-height: 11in;
  }
  .page:last-child { page-break-after: avoid; }
}

QA Checklist

Before delivering, verify:

Data Accuracy

• All numbers are accurate and internally consistent
• Percentages add up where they should
• Revenue figures match across exec summary KPIs, tables, and rec-card references

Page Overflow (check EVERY page)

• No content overflows page boundaries
• Rec-card pages have max 3 full-field cards
• Data tables with 13+ rows use dense mode

Visual Consistency

• Every content page has a .page-footer with correct page number
• Cover page has NO .page-footer
• Every .section-title is followed by <hr class="accent-rule">
• Multi-page sections use "(continued)"
• Callout colors match their severity
• Priority banners use correct level class

PDF Export

• @page rule present with size: 8.5in 11in
• print-color-adjust: exact applied globally
• All background colors render in PDF