fountain-syntax
Skill66 starsChanged 4 months agoMITView on GitHub
This skill provides complete Fountain screenplay format syntax reference. Covers title page, scene headings, action, character names, dialogue, transitions, notes, sections, and all special formatting elements.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- action-descriptionSkill
- arc-checkSkill
- character-arcsSkill
- character-dialogueSkill
- character-interviewSkill
- continuity-trackingSkill
- dialogue-craftSkill
- format-exportSkill
- glossary-referenceSkill
- loglineSkill
- page-estimationSkill
- pitch-worksheetSkill
- power-analysisSkill
- rewriting-methodologySkill
- scene-analysisSkill
- scene-headingsSkill
- story-checkSkill
- story-structureSkill
- synopsisSkill
- theme-discoverySkill
- title-pageSkill
- transitionsSkill
- writers-roomSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Must begin with: INT, EXT, EST, INT./EXT, INT/EXT, or I/E Force any line as scene heading with .
- Distinctive: line 70
All UPPERCASE on own line, blank line before:
- Very specific: line 114
Add ^ after second character:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fountain Syntax Skill
Invocation Triggers
Apply this skill when:
- Writing or editing .fountain files
- Validating screenplay format
- Converting between formats
- Teaching Fountain syntax
Complete Fountain Syntax Reference
Title Page
Key-value pairs at the start of the document:
Title:
**Seoul Identity**
Credit: Written by
Author: Scott Graham
Draft date: December 27, 2025
Contact: scott@wordstofilmby.comStandard keys: Title, Credit, Author, Source, Draft date, Contact, Copyright, Notes
Scene Headings
INT. COFFEE SHOP - DAY
EXT. MOUNTAIN ROAD - NIGHT
INT./EXT. CAR (MOVING) - CONTINUOUSMust begin with: INT, EXT, EST, INT./EXT, INT/EXT, or I/E
Force any line as scene heading with . prefix:
.FLASHBACK - TWENTY YEARS EARLIEROptional scene numbers:
INT. HOUSE - DAY #1#
INT. HOUSE - DAY #1A#Action (Description)
Plain paragraphs are action. Line breaks are preserved.
The room is dark. A FIGURE moves in the shadows.
Sarah enters, hesitant. She looks around.Force uppercase lines as action with !:
!MONTAGE - SARAH'S MORNING ROUTINECharacter Names
All UPPERCASE on own line, blank line before:
SARAH
I don't understand.With extensions:
MOM (V.O.)
When I was your age...
JOHN (O.S.)
I'm in the kitchen!
SARAH (CONT'D)
And another thing...Force mixed-case with @:
@McCLANE
Yippee ki-yay.Dialogue
Text following Character or Parenthetical:
JOHN
This is dialogue. It can span
multiple lines without a problem.Parentheticals
Wrapped in parentheses, after Character or within Dialogue:
SARAH
(looking away)
I never said that.
(beat)
Not exactly.Dual Dialogue (Simultaneous)
Add ^ after second character:
JACK
I love you!
JILL ^
I hate you!Transitions
Uppercase ending in TO:, or forced with >:
CUT TO:
DISSOLVE TO:
>FADE TO BLACK.Centered Text
Bracket with > and <:
>THE END<
>TITLE CARD: "THREE YEARS LATER"<Emphasis (Formatting)
*italics*
**bold**
***bold italics***
_underline_Escape with backslash: \*not italic\*
Lyrics
Prefix with ~:
~Somewhere over the rainbow
~Way up highPage Breaks
Three or more = on own line:
===Notes (Writer Comments)
Double brackets, won't appear in output:
[[This is a note to myself about the scene.]]Boneyard (Archived Content)
Content between /* and */ is ignored:
/*
CUT SCENE - keeping for reference
INT. DINER - NIGHT
...
*/Sections (Structural, Hidden)
Pound signs for outline hierarchy:
# Act One
## Sequence 1
### Scene GroupSynopses (Scene Summaries, Hidden)
Prefix with =:
= Sarah discovers the truth about her father.
INT. SARAH'S APARTMENT - NIGHTValidation Rules
Required Elements
- Title page (for complete scripts)
- Scene headings with location and time
- Proper character/dialogue structure
Common Errors
- Missing blank line before character names
- Scene heading missing time of day
- Parenthetical not on own line
- Unescaped special characters triggering wrong format
Syntax Validation Checklist
- Title page has required fields
- Scene headings start with INT/EXT
- Character names are UPPERCASE
- Parentheticals are in (parentheses)
- Dual dialogue uses ^ correctly
- Notes use [[double brackets]]
- Boneyard uses /* */ correctly
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

