pdf-generation
Professional PDF documentation generation. Convert Markdown to PDF with custom templates, styling, table of contents, cross-references, and optimized output for print and archival.
What this skill does
# PDF Generation Skill
Professional PDF documentation generation.
## Capabilities
- Markdown to PDF conversion
- Custom PDF templates and styling
- Table of contents generation
- Cross-reference and link handling
- Image optimization for print
- PDF/A compliance for archival
- Multi-chapter document assembly
- Cover page and headers/footers
## Usage
Invoke this skill when you need to:
- Generate PDF documentation from Markdown
- Create printable user guides
- Archive documentation as PDF
- Produce branded PDF output
- Build multi-chapter manuals
## Inputs
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| inputPath | string | Yes | Path to Markdown source(s) |
| outputPath | string | Yes | Output PDF file path |
| template | string | No | Path to PDF template |
| config | object | No | PDF generation options |
| metadata | object | No | Document metadata |
| toc | boolean | No | Generate table of contents |
### Input Example
```json
{
"inputPath": "./docs",
"outputPath": "./output/documentation.pdf",
"template": "./templates/manual.html",
"toc": true,
"metadata": {
"title": "Product Documentation",
"author": "Documentation Team",
"version": "1.0.0"
}
}
```
## Output Structure
### Single PDF Output
```
output/
└── documentation.pdf
├── Cover page
├── Table of Contents
├── Chapter 1: Getting Started
│ ├── Installation
│ └── Quick Start
├── Chapter 2: User Guide
│ ├── Configuration
│ └── Features
├── Chapter 3: API Reference
└── Appendix
```
### Multi-PDF Output
```
output/
├── getting-started.pdf
├── user-guide.pdf
├── api-reference.pdf
└── complete-manual.pdf
```
## Pandoc Configuration
### pandoc-defaults.yaml
```yaml
from: markdown+smart+yaml_metadata_block+implicit_figures+table_captions
to: pdf
pdf-engine: xelatex
variables:
documentclass: report
papersize: letter
fontsize: 11pt
geometry:
- margin=1in
- top=1.25in
- bottom=1.25in
mainfont: "Source Serif Pro"
sansfont: "Source Sans Pro"
monofont: "Source Code Pro"
linkcolor: blue
urlcolor: blue
toccolor: black
toc-depth: 3
include-before-body:
- cover.tex
include-in-header:
- preamble.tex
metadata:
title: "Documentation"
author: "Documentation Team"
date: "2026-01-24"
lang: en-US
toc: true
toc-title: "Table of Contents"
number-sections: true
colorlinks: true
highlight-style: pygments
```
### LaTeX Preamble (preamble.tex)
```latex
% Custom styling
\usepackage{fancyhdr}
\usepackage{titlesec}
\usepackage{xcolor}
\usepackage{listings}
\usepackage{graphicx}
% Header/Footer
\pagestyle{fancy}
\fancyhf{}
\fancyhead[L]{\leftmark}
\fancyhead[R]{\thepage}
\fancyfoot[C]{\small Documentation v1.0}
% Code block styling
\lstset{
basicstyle=\ttfamily\small,
breaklines=true,
frame=single,
backgroundcolor=\color{gray!10}
}
% Heading styles
\titleformat{\chapter}[display]
{\normalfont\huge\bfseries}
{\chaptertitlename\ \thechapter}{20pt}{\Huge}
% Link colors
\definecolor{linkblue}{RGB}{0,102,204}
```
## WeasyPrint Configuration
### weasyprint-config.css
```css
@page {
size: letter;
margin: 1in;
margin-top: 1.25in;
margin-bottom: 1.25in;
@top-center {
content: string(chapter-title);
font-size: 10pt;
color: #666;
}
@bottom-center {
content: "Page " counter(page) " of " counter(pages);
font-size: 9pt;
}
}
@page :first {
@top-center { content: none; }
@bottom-center { content: none; }
}
/* Cover page */
.cover {
page: cover;
text-align: center;
padding-top: 3in;
}
.cover h1 {
font-size: 36pt;
color: #333;
}
.cover .version {
font-size: 14pt;
color: #666;
margin-top: 1in;
}
/* Table of contents */
#toc {
page-break-after: always;
}
#toc h2 {
font-size: 24pt;
margin-bottom: 0.5in;
}
#toc a {
text-decoration: none;
color: inherit;
}
#toc a::after {
content: leader('.') target-counter(attr(href), page);
}
/* Chapters */
h1 {
string-set: chapter-title content();
page-break-before: always;
font-size: 28pt;
border-bottom: 2px solid #333;
padding-bottom: 0.25in;
}
h2 { font-size: 20pt; margin-top: 0.5in; }
h3 { font-size: 16pt; margin-top: 0.3in; }
/* Code blocks */
pre {
background-color: #f5f5f5;
padding: 0.5em;
border-radius: 4px;
font-size: 9pt;
overflow-x: auto;
page-break-inside: avoid;
}
code {
font-family: "Source Code Pro", monospace;
background-color: #f0f0f0;
padding: 0.1em 0.3em;
border-radius: 3px;
}
/* Tables */
table {
width: 100%;
border-collapse: collapse;
margin: 1em 0;
page-break-inside: avoid;
}
th, td {
border: 1px solid #ddd;
padding: 0.5em;
text-align: left;
}
th {
background-color: #f5f5f5;
font-weight: bold;
}
/* Images */
img {
max-width: 100%;
height: auto;
}
figure {
text-align: center;
page-break-inside: avoid;
}
figcaption {
font-style: italic;
color: #666;
margin-top: 0.5em;
}
/* Links */
a {
color: #0066cc;
text-decoration: none;
}
/* Print optimizations */
@media print {
a[href^="http"]::after {
content: " (" attr(href) ")";
font-size: 0.8em;
color: #666;
}
}
```
## Cover Page Template
### cover.html
```html
<!DOCTYPE html>
<html>
<head>
<style>
body {
font-family: "Source Sans Pro", sans-serif;
text-align: center;
padding-top: 200px;
}
.logo {
max-width: 200px;
margin-bottom: 50px;
}
h1 {
font-size: 48px;
color: #333;
margin-bottom: 20px;
}
.subtitle {
font-size: 24px;
color: #666;
margin-bottom: 100px;
}
.version {
font-size: 18px;
color: #999;
}
.date {
font-size: 14px;
color: #999;
margin-top: 10px;
}
.footer {
position: absolute;
bottom: 50px;
width: 100%;
text-align: center;
color: #666;
}
</style>
</head>
<body>
<img src="logo.png" alt="Company Logo" class="logo">
<h1>{{title}}</h1>
<p class="subtitle">{{subtitle}}</p>
<p class="version">Version {{version}}</p>
<p class="date">{{date}}</p>
<div class="footer">
<p>{{company}}</p>
<p>Confidential</p>
</div>
</body>
</html>
```
## Multi-Chapter Assembly
### build-manual.js
```javascript
const pandoc = require('pandoc');
const fs = require('fs');
const path = require('path');
async function buildManual(config) {
const chapters = [
{ title: 'Getting Started', files: ['intro.md', 'installation.md', 'quickstart.md'] },
{ title: 'User Guide', files: ['configuration.md', 'features.md', 'advanced.md'] },
{ title: 'API Reference', files: ['api/*.md'] },
{ title: 'Appendix', files: ['glossary.md', 'changelog.md'] }
];
// Combine all Markdown files
let combined = '';
for (const chapter of chapters) {
combined += `# ${chapter.title}\n\n`;
for (const filePattern of chapter.files) {
const files = glob.sync(filePattern, { cwd: config.docsDir });
for (const file of files) {
const content = fs.readFileSync(path.join(config.docsDir, file), 'utf8');
// Adjust heading levels
const adjusted = adjustHeadings(content, 1);
combined += adjusted + '\n\n';
}
}
}
// Write combined file
const tempFile = '/tmp/combined.md';
fs.writeFileSync(tempFile, combined);
// Run Pandoc
await pandoc({
input: tempFile,
output: config.outputPath,
args: [
'--defaults', config.pandocDefaults,
'--metadata-file', config.metadataFile
]
});
return { output: config.outputPath };
}
```
## PDF/A Compliance
### GeneRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.