Commands

Create PDF

Publication-grade documents from your work

Create-pdf produces publication-grade PDFs that read like McKinsey deliverables, Apple product briefs, or letters from the Oval Office. A serif body, sans-serif headings, restrained color palette, and a built-in component library (callouts, metric cards, styled tables, dark feature blocks) carry the design system across every page. Print-first thinking; hierarchy survives black-and-white.

How it works

From Space content to designed PDF in
one command.

Point create-pdf at any analysis, report, or memo. It transforms the content into a designed document with cover page, table of contents, sectioned body, and component-rich layout. The result reads as designed, not generated; built page-by-page on a print-first design system.

Typography that commands respect

A serif body face for extended reading, a sans-serif heading face for authority. Intentional sizing across the hierarchy: a single dominant title size, distinct H1 with accent underline, lighter H2 with thin separator, tertiary H3 in mid-gray. Tight leading because this is print, not web. Justified body, vertical rhythm instead of first-line indent.

Each H1 starts a fresh page, anchored by an accent rule across the column

Whitespace as architecture

Generous 0.85-1in margins create a frame of authority. Vertical rhythm between sections makes scanning effortless. Components have intentional insets that create visual depth. When in doubt, more whitespace. Crowded signals amateur; spacious signals confidence.

Cover page floats with #v(2in) top + #v(1fr) bottom

Component library out of the box

Callout boxes, metric cards, styled tables with alternating rows, dark feature blocks for hero moments, two-column comparison cards, conversion ladders, deal lines, pitch blocks. Each component carries the design system so every page lands consistent.

#metric[87%][of enterprises cite privacy as #1 barrier]

Print-first, color second

Every layout passes the Print Test: hierarchy survives black-and-white laser printing. Color is restraint, not prose. One accent color used architecturally (heading underlines, callout borders, metric numbers), never decoratively. Weight, size, and spacing carry the structure.

Squint at any page and see the hierarchy without reading a word

Beyond the markdown export

Not "export to PDF."
A designed deliverable that signals the quality of the work.

Markdown / Word PDF
Default fonts, default margins, default everything
No cover page, no table of contents, no visual hierarchy
Tables are dense, callouts are quoted blockquotes
Looks generated; reader judges the quality before reading
Create PDF
Disciplined typeface pairing, intentional sizing, vertical rhythm
Cover page with brand mark, TOC on its own page
Component-rich: callouts, metric cards, dark feature blocks
Looks designed; reader assumes the work is serious

Any document worth designing

Publication-grade output for every kind of deliverable.

Anywhere a Word doc would land flat, a designed PDF lands serious.

Strategic Memo

Tight, decisive, 4-8 pages. Callouts, one dark block, tables

Analysis Report

Detailed, evidence-rich, 10-20 pages with metric cards and exhibits

Sales Playbook

Practical, actionable, 15-30 pages. Pitch blocks, deal lines, tags

Brainstorm

Progressive, creative, 10-20 pages with idea blocks and pre-mortems

Proposal

Clean, confident, 6-12 pages. Metric cards and a dark CTA

Technical Brief

Precise, structured, 4-10 pages. Code blocks and architecture

Ready to publish?

Open a Space in the Workspace and run /create-pdf from the Conductor.

Get AskQP