guide-pdflisted

Render an already authored Markdown research report, guide, playbook, handbook, tutorial, decision memo, or scorecard into a print-ready A4 PDF with a configurable house style. Lossless presentation only: preserves source order, headings, claims, citations, quotes, tables, and code; does not research, rewrite, restructure, add callouts, or choose narrative style. Use after `researcher` for a verification-first report or after `research-to-guide` for a reader-facing guide when users ask 'make a PDF', 'export to PDF', 'build the guide PDF', or 'print-ready version'. Detects unsupported Mermaid diagrams and stops with an explicit routing choice instead of rendering them as code.
createusernam/setup_project · ★ 0 · Data & Documents · score 62

Install: claude install-skill createusernam/setup_project

# Guide PDF IRON LAW: RENDER THE SOURCE LOSSLESSLY. NEVER REWRITE MARKDOWN CONTENT OR DROP A BLOCK TO FIT THE HOUSE STYLE. ## Responsibility boundary ```text researcher → evidence and validated research report research-to-guide → reader composition and narrative style guide-pdf → PDF typography, pagination, and visual tokens only ``` `GOAL_ROOT`: Produce a print-ready PDF whose semantic content and reading order match the input Markdown. - **Success:** the first and last source content, heading hierarchy, citations, quotes, tables, and code survive rendering. - **Not success:** a visually polished PDF that omits, rewrites, reorders, or silently degrades source content. ## Usage ```bash python3 scripts/build-guide-pdf.py <input.md> <output.pdf> ["Footer text"] [--design-contract <path>] ``` The bundled `scripts/build-guide-pdf.py` is the only canonical builder. Do not reproduce or rewrite it from this skill. ## Input contract The renderer adapts to authored Markdown; authors do not adapt their content to the renderer. - First `# Title` is required and becomes the document title. - An optional `### Subtitle` is metadata only when it is the first nonblank block immediately after the title. - A later H1 is preserved and rendered as a part heading. - H2/H3 and deeper headings preserve their semantic order. - Blockquotes remain blockquotes and receive visual callout styling; never add one only for appearance. - Fenced code, tables, links, lists, and horizo