Export

Arguments are combinable. Examples:

• /export report.md --format png --theme dark — full PNG with dark theme
• /export report.md --scope summary --format all — summary in all 3 formats
• /export utils.py --format html --theme dark — syntax-highlighted code export

Defaults

If the invocation is ambiguous or the file path is unrecognizable, ask the user to clarify before proceeding.

User Preferences

Read shared/skill-context.md for the full protocol. In brief:

1. Read .claude/skill-context/preferences.md — if missing, proceed with defaults (don't interrupt the export flow).
2. Read .claude/skill-context/export.md (if it exists) for export-specific preferences.

How preferences shape this skill:

Like commit, export does not invoke /preferences on first contact — exports are straightforward operations. If preferences exist, use them as new defaults (CLI flags still override). If not, use the built-in defaults above.

Process

Step 1 — Validate Input

1. Confirm the input file exists. If not, ask the user for the correct path.
2. Parse all flags from the invocation.
3. If --output is used with --format all, warn the user that --output only works with a single format and ask them to choose.

Step 2 — Content Preparation

Based on --scope:

full (default): No content modification. Pass the file directly to the rendering script.

summary: Read the input file and generate a condensed markdown summary:

• Extract and preserve the document title (first H1 or filename).
• Identify key sections, findings, and conclusions.
• Produce a focused summary — typically 30-50% of the original length.
• Preserve code blocks, tables, and other structured elements that are central to the document's message.
• Write the condensed markdown to a temporary file.

1pager: Read the input file and condense to approximately one A4 page worth of content (~500-600 words):

• Prioritize the most important information: conclusions, key findings, critical code.
• Use tighter prose — bullet points over paragraphs where appropriate.
• Omit secondary details, verbose explanations, and supporting examples.
• Write the condensed markdown to a temporary file.

For code files (.py, .cpp, etc.) with summary or 1pager scope: extract the most important functions/classes, add brief descriptions. Do not attempt to summarize every line.

Step 3 — Render

Invoke the rendering script:

python scripts/md_export.py <input_or_temp_file> \
  --format <format> \
  --theme <theme> \
  --orientation <orientation> \
  --scope <scope> \
  [--output <path>]

Each format uses a different rendering pipeline:

The script also handles input detection (markdown vs code) and wraps code files in fenced blocks with syntax highlighting before passing to Pandoc.

PDF typography: PDF output uses Segoe UI for body text, Cascadia Code for code blocks (scaled to 0.88). These are system fonts — if they are missing, LuaLaTeX will fall back to defaults. Orientation is controlled via LaTeX geometry options.

PNG sizing: The --scope flag affects PNG dimensions — 1pager renders at A4-equivalent resolution (794×1123 portrait, 1123×794 landscape), while full/summary use a narrow 430px-wide viewport with auto-height that gets trimmed to content.

Step 4 — Report Results

After successful rendering, report:

• The output file path(s)
• The file size(s)
• A brief confirmation: "Exported <file> as <format> with <theme> theme."

If --format all was used, list all three output files.

If rendering fails, show the error from the script and suggest troubleshooting:

Step 5 — Cleanup

Remove any temporary files created during content preparation (summary/1pager temp markdown files). The rendering script handles its own temp file cleanup.

Output Naming Convention

Output is placed in the same directory as the input file by default. Use --output to override.

Supported Input Types

Themes

Each theme has both a CSS file (for HTML and PNG) and a LaTeX template (for PDF):

Syntax highlighting style varies by theme: pygments (minimal), tango (modern), breezedark (dark).

Dependencies

The script checks for each dependency at runtime and provides install instructions if missing.