Typeset Print

typeset-print

Apply a DESIGN.md design system onto structured print templates. The templates handle print-safe layout; the DESIGN.md provides the visual identity.

Print templates are bundled with this skill at assets/templates/*-en.html (relative to this SKILL.md). Read the needed template file directly — do not modify it.

Step 0 · Load the design system

Resolve the DESIGN.md using this priority chain — first match wins:

1. Workspace auto-discovery — silently check if a file named DESIGN.md (case-insensitive) exists in the root of the current project. If found, read it and continue. Emit one line: "Using DESIGN.md found in project root."
2. User-provided path — if the user attached a file with @file or typed a path, read that file.
3. Inline paste — if the user pasted DESIGN.md content directly in the message, use it as-is.
4. Ask once — if none of the above apply: "No DESIGN.md found in the project root. Please attach the file or paste its content." Do not proceed until one is provided.

After loading, extract the following mappings to override template CSS variables:

Compatibility check

Before proceeding, evaluate DESIGN.md Section 1 (Visual Theme & Atmosphere):

• If the design system describes a dark background (e.g. #000, #111, #0d0d0d as the page color), warn: "This design system uses a dark background. The bundled templates are optimised for light print output. Consider using typeset-free for better fidelity." Then ask the user whether to continue or switch.
• If the design system is explicitly screen-only (glassmorphism, neon, neumorphism, etc.), issue the same warning.
• If the user confirms to continue, apply the tokens as-is and note that print results may vary.

Step 1 · Language gate

Detect the language of the user's content and request.

Accept: Latin-script languages — English, Italian, Spanish, French, German, Portuguese, Dutch, Polish, Romanian, and others using the Latin alphabet.

Reject: Chinese, Japanese, Korean, Arabic, Hebrew, Thai, and any script that requires non-Latin glyph rendering. If detected, reply:

"This skill supports Latin-script languages only. For Chinese or Japanese documents, use a CJK-capable typesetting tool."

Then stop.

Step 2 · Intent extraction (silent)

Verify these four dimensions before choosing a template. Do not ask unless two or more are genuinely unclear.

If two or more are unclear, ask in a single compact message. Never ask all four as a form.

Step 3 · Document type

Route to a bundled print template:

Read the chosen template from assets/templates/<template-name> (bundled alongside this SKILL.md).

Diagrams (embed inside long-doc or slides)

When the document needs a chart or diagram, extract the <svg> block from the matching file in assets/diagrams/ and embed it inside a <figure> in the document body.

Auto-select from data when content contains numerical data (first match wins): OHLC fields → candlestick; +/- contributions summing to total → waterfall; one series summing to ~100% ≤ 6 items → donut; two+ series across time → line; one series across time → bar; 2×2 positioning → quadrant; hierarchy depth ≥ 2 → tree; process with decision branches → flowchart.

Always wrap the extracted SVG in <figure><figcaption>…</figcaption></figure> with a caption that states the insight, not just the data range.

Step 4 · Build the token override block

Produce a CSS block to prepend inside the template's existing :root {} declaration. Override only tokens extracted in Step 0 — leave everything else intact.

/* DESIGN.md token overrides — injected by typeset-print */
:root {
  --parchment: /* from DESIGN.md */;
  --ivory: /* derived or fallback */;
  --brand: /* from DESIGN.md accent */;
  --near-black: /* from DESIGN.md foreground */;
  --dark-warm: /* from DESIGN.md secondary text */;
  --stone: /* from DESIGN.md muted */;
  --border: /* from DESIGN.md border */;
  --serif: /* from DESIGN.md display font stack */;
  --tag-bg: /* from DESIGN.md badge/tag bg, or derived */;
}

rgba conversion

WeasyPrint does not render rgba() backgrounds correctly on tags and badges (double-rectangle rendering bug). If any DESIGN.md color value uses rgba(), convert it to an equivalent solid hex by blending on the page background before inserting into the override block. Document the conversion as a comment:

--tag-bg: #E0F0FF; /* converted from rgba(0,120,255,0.12) on #ffffff */

Typography mismatch handling

If the DESIGN.md font stack uses web fonts not available as system fonts, add a note to the layout intent (Step 4.5) and fall back to the nearest system serif. Do not add @font-face declarations unless the user provides font files.

Step 4.5 · Layout intent note

Before filling the template, write a short note (under 60 words, prose) stating: template chosen, token overrides applied, any fallbacks or warnings, output format. Continue immediately — do not wait for approval.

Example:

Layout intent: Resume (EN), bundled print template with Stripe design tokens — navy #061b31 as brand, white surface, sohne-var mapped to Charter fallback (web font unavailable). One rgba conversion: tag-bg rgba(83,58,253,0.1) → #EAE9FE. Output: HTML + PDF.

Step 5 · Content distillation

Auto-detect whether the input needs distilling. Do not ask.

When distilling, extract facts, map to template sections, gap-check, and ask once with a gap table.

Step 6 · Fill the template

Apply changes to the template in this order:

1. Prepend the token override block from Step 4 immediately before the closing } of the existing :root {} block
2. Fill all {{PLACEHOLDER}} fields:

3. Fill body content — data over adjectives, no padding, no invented metrics
4. Verify no {{...}} remain — if any do, replace with [DATA NEEDED: field name]

Step 7 · Build and verify

Run the build script from src/design/scripts/build.mjs (relative to this skill's plugin root):

node scripts/build.mjs --html output.html          # placeholder + structure check
node scripts/build.mjs --pdf output.html           # WeasyPrint → output.pdf
node scripts/build.mjs --check output.html         # palette anti-pattern scan

If WeasyPrint is not installed, provide the browser-print fallback instruction (Chrome → File → Print → Save as PDF, background graphics on, margins None).

Report the result. If any check fails, self-correct and re-run before handing off.