fountain

Validate Fountain screenplay syntax in .fountain files for correct formatting.

26|8|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/bgrundmann/obsidian-fountain --skill fountain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fountain
Source: https://github.com/bgrundmann/obsidian-fountain/tree/main/fountain
Command: npx skills add https://github.com/bgrundmann/obsidian-fountain --skill fountain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you write and maintain screenplays in Fountain format by ensuring your text follows the exact syntax the format expects, especially for scenes, dialogue, and screenplay structure.

Core Features & Use Cases

  • Fountain syntax validation & guidance: Learn and apply the rules that determine whether a line becomes action, scene headings, characters, dialogue, parentheticals, transitions, lyrics, and page breaks.
  • Structure for outlining and revision: Use sections and synopsis lines for planning while keeping those organizational elements non-rendered.
  • Obsidian Fountain-specific enhancements: Support margin markers, todos, note kinds, cross-file vault links, snippets, and boneyard sections for alternative content.

Quick Start

Open or create a .fountain file and write your screenplay using Fountain rules for scene headings (INT./EXT.), character names (ALL CAPS), and dialogue, using optional markers like [[todo: ...]] and [[@marker]] as needed.

Frequently Asked Questions about fountain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format Fountain screenplay syntax correctly in Obsidian?

To format Fountain syntax in Obsidian, use blank-line delimitation between elements and forced prefixes like !, ., @, and > to define scene headings, characters, dialogue, parentheticals, and transitions.

What is the Fountain markup syntax for writing dialogue and scene headings?

Fountain markup syntax uses INT./EXT. prefixes for scene headings, ALL CAPS for character names, and places dialogue immediately after character lines, using blank lines to delimit each screenplay element.

Can I use Obsidian cross-file links and todos inside a .fountain file?

Yes, Obsidian supports cross-file vault links, todos, and margin markers using [[@marker]] syntax inside .fountain files, allowing you to embed structured notes and vault references directly within your screenplay.

Does Fountain format support outlining and keeping alternative scenes while writing?

Fountain format supports outlining through sections and synopsis lines that stay non-rendered, and uses boneyard sections to store alternative content and snippets for screenplay revision planning.

Why does my Fountain text render as action instead of a character or dialogue?

Fountain lines render as action instead of characters or dialogue when blank-line delimitation between elements is missing or forced prefixes like @ and . are not applied to identify the intended element type.

What's the best way to write dual dialogue using Fountain markup?

Writing dual dialogue in Fountain markup requires using forced elements and specific syntax constraints to align two character dialogue blocks side-by-side under the Obsidian plugin's rendering rules.