AgentSkillsCN

format-export

本技能提供剧本导出的多种格式，包括 PDF、FDX 与 HTML。涵盖 Better Fountain VS Code 扩展、Afterwriting CLI 工具，以及 Highland 软件，用于将 Fountain 文件转换为业界通用的交付格式。 适用场景：在将剧本导出为 PDF、转换为 Final Draft（FDX）文件，生成 HTML 预览，或为交付做好脚本准备时使用。

SKILL.md
--- frontmatter
name: format-export
description: |
  This skill provides screenplay export procedures for PDF, FDX, and HTML.
  Covers Better Fountain VS Code extension, afterwriting CLI, and Highland
  for converting Fountain files to industry-standard delivery formats.

  Use when: exporting screenplay to PDF, converting to Final Draft (FDX),
  generating HTML preview, or preparing scripts for delivery.

Format Export Skill

Invocation Triggers

Apply this skill when:

  • •Exporting screenplay to PDF
  • •Converting to Final Draft (FDX)
  • •Generating HTML preview
  • •Preparing scripts for delivery

Recommended: Better Fountain Extension

The simplest export method uses the Better Fountain VS Code extension:

FormatCommand Palette Action
PDFFountain: Export to PDF
FDXFountain: Export to FDX
HTMLFountain: Export to HTML

Steps:

  1. •Open .fountain file in VS Code
  2. •Press Ctrl+Shift+P (or Cmd+Shift+P on macOS)
  3. •Type the export command
  4. •Choose output location

Export Formats Overview

FormatExtensionPurposeTools
PDF.pdfIndustry standard deliveryBetter Fountain, afterwriting, Highland
FDX.fdxFinal Draft importBetter Fountain, screenplain, Highland
HTML.htmlWeb preview/sharingBetter Fountain, afterwriting
Plain Text.txtAccessibility, archivaldirect copy

PDF Export

Industry Standard Format

  • •Font: Courier 12pt
  • •Margins: 1.5" left, 1" right, 1" top/bottom
  • •Page Size: US Letter (8.5" x 11")
  • •Page Numbers: Top right, starting page 2

Better Fountain (Recommended)

In VS Code: Ctrl+Shift+P -> "Fountain: Export to PDF"

CLI: afterwriting (for automation)

bash
# Install
npm install -g afterwriting

# Basic PDF export
afterwriting --source screenplay.fountain --pdf

# With configuration
afterwriting --source screenplay.fountain --pdf --config pdf-config.json

# Output to specific file
afterwriting --source screenplay.fountain --pdf --output script.pdf

PDF Configuration (pdf-config.json)

json
{
  "print_title_page": true,
  "print_profile": "default",
  "print_header": "",
  "print_footer": "",
  "print_watermark": "",
  "print_dialogue_numbers": false,
  "print_notes": false,
  "print_sections": false,
  "print_synopses": false,
  "scenes_numbers": "none",
  "each_scene_on_new_page": false
}

FDX Export (Final Draft XML)

Purpose

  • •Import into Final Draft software
  • •Collaboration with Final Draft users
  • •Industry compatibility

Better Fountain (Recommended)

In VS Code: Ctrl+Shift+P -> "Fountain: Export to FDX"

CLI: screenplain (for automation)

bash
# One-time installation (requires Python 3.8+ and pipx)
pipx install screenplain

# Export to FDX
screenplain --format fdx screenplay.fountain output.fdx

HTML Export

Purpose

  • •Web-based reading
  • •Easy sharing via URL
  • •Print from browser

Better Fountain (Recommended)

In VS Code: Ctrl+Shift+P -> "Fountain: Export to HTML"

CLI: afterwriting (for automation)

bash
afterwriting --source screenplay.fountain --html

Export Workflow

Pre-Export Checklist

  • • Script Supervisor approval
  • • Standards Reviewer approval
  • • All [[notes]] resolved or intentional
  • • Title page complete and current
  • • Fountain syntax validated

Export Process

markdown
1. Validate Fountain file
2. Run export command
3. Verify output file created
4. Open and review output
5. Check page count
6. Verify title page
7. Sample check formatting
8. Package for delivery

Post-Export Verification

  • • File opens without errors
  • • Page count as expected
  • • Title page correct
  • • Character names format correctly
  • • Dialogue layout proper
  • • Transitions right-aligned
  • • No orphaned elements

Version Naming

Convention

code
[Title]_v[Major].[Minor]_[YYYYMMDD].[ext]

Examples

code
Seoul_Identity_v1.0_20251227.pdf
Seoul_Identity_v1.1_20251228.pdf
Seoul_Identity_v2.0_20260115.pdf
Seoul_Identity_v2.0_20260115.fdx

Major vs. Minor

  • •Major (1.0 -> 2.0): Significant rewrite
  • •Minor (1.0 -> 1.1): Polish, small changes

Troubleshooting

PDF Issues

ProblemSolution
Wrong fontsCheck PDF config, ensure Courier
Bad marginsVerify config matches standards
Missing title pageEnable in config
Notes appearingDisable print_notes

FDX Issues

ProblemSolution
Elements misformattedReview in Final Draft, adjust
Notes missingExpected - FDX doesn't support all
Dual dialogue brokenMay need manual fix in FD

HTML Issues

ProblemSolution
Print looks wrongUse paper size option
Styling offUse default CSS or customize

Export Checklist

PDF Delivery

  • • Page count within target
  • • Title page per standards
  • • No scene numbers (spec)
  • • No WGA numbers (spec)
  • • Filename follows convention
  • • File under 10MB

FDX Delivery

  • • Opens in Final Draft
  • • Elements formatted correctly
  • • Scene headings intact
  • • Dialogue blocks correct

Competition Submission

  • • Format matches guidelines
  • • Page count within limits
  • • Anonymous if required
  • • Filename as specified