/onepager

description: Create a single-page fact sheet or program overview
argument-hint: [topic]
allowed-tools: Read, Write, Edit, Glob, mcp__plugin_playwright_playwright__*

Create a print-ready single-page HTML fact sheet.

Version check

Read the plugin version from `${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json` and note it. If the file doesn't exist or the read fails, warn the user that the plugin may not be properly installed.

Setup

1. Check for brand configuration at `.claude/pdf-playground.local.md` 2. If found, parse the YAML frontmatter for brand settings 3. If not found, ask the user for their organization name and primary brand color 4. Load the one-pager template from `${CLAUDE_PLUGIN_ROOT}/templates/onepager-template.html`

Brand application

Apply brand settings throughout:

• Organization name in header
• CSS variables for colors
• Font families from config

Document structure

Create a single 8.5" × 11" page with:

**Header:**

• Organization name/logo
• Document title
• Category eyebrow

**Content area:**

• Key points (3-5 bullet points)
• Brief description (2-3 paragraphs max)
• Sidebar with quick facts or stats
• Call to action

**Footer:**

• Organization website
• Contact information

Layout options

• Two-column (main + sidebar)
• Full-width with callout boxes
• Grid for multiple equal sections

Topic

The topic is: $ARGUMENTS

If no topic provided, ask for:

• Main topic or program name
• 3-5 key points
• Any statistics
• Call to action

Footer clearance (critical)

Content MUST NOT touch or overlap the footer. This is a common issue.

• The page MUST use `display: grid; grid-template-rows: auto 1fr auto` so the footer takes its natural height and content fills the rest — no magic-number `calc()` for heights
• The `.content` area MUST have `overflow: hidden` to prevent text bleeding past its bounds
• Use `padding-bottom: 0.3in` (minimum) on the content area to create a buffer
• After generating, always take a screenshot and visually verify the bottom of the page
• If content is too long, **remove content** rather than shrinking the clearance — the footer gap is non-negotiable
• Tighten the header padding first if you need more room for content

Output

Save HTML file in current working directory. All content MUST fit on one page — no overflow, no text touching the footer.