scene-writing
Write individual screenplay scenes with proper industry formatting, visual action, and dramatic structure
What this skill does
# Scene Writing Skill
## Purpose
Write individual screenplay scenes that advance the story, reveal character, and engage the reader. Each scene should be a complete dramatic unit with its own structure, conflict, and resolution.
## Scene Anatomy
### The SCENE Framework
| Element | Description |
|---------|-------------|
| **S**pacing | INT/EXT, Location, Time |
| **C**haracter | Who's in the scene, POV |
| **E**motion | Underlying tension, stakes |
| **N**arrative | Information delivered |
| **E**xit | How we leave, hook to next |
## Screenplay Format (Fountain)
```fountain
INT. POLICE PRECINCT - INTERROGATION ROOM - NIGHT
Harsh fluorescent light. Bare walls. A metal table bolted to the floor.
DETECTIVE SARAH CHEN (40s, tired eyes, sharp mind) sits across from MARCUS WEBB (30s, expensive suit, expensive smile).
A manila folder between them like a dare.
SARAH
You know why you're here.
MARCUS
(leaning back)
Enlighten me.
Sarah opens the folder. Crime scene photos. Blood. Chaos.
SARAH
Your fingerprints. Her blood.
Her dying breath, calling out
your name.
Marcus doesn't flinch. His smile never wavers.
MARCUS
Detective... I have an alibi.
SARAH
So did every guilty man I ever caught.
She slides one photo across the table. Marcus looks at it.
For just a moment—something flickers in his eyes.
MARCUS
I want my lawyer.
Sarah smiles. Finally. A crack.
```
## Formatting Rules
### Slugline (Scene Heading)
```
INT. or EXT.
LOCATION NAME (in caps)
TIME OF DAY (DAY, NIGHT, CONTINUOUS, LATER, SAME)
```
Examples:
- `INT. COFFEE SHOP - DAY`
- `EXT. BROOKLYN BRIDGE - NIGHT`
- `INT./EXT. CAR (MOVING) - CONTINUOUS`
### Action Lines
- Present tense, active voice
- 3-4 lines max per paragraph
- WHITE SPACE for pacing
- CHARACTER NAMES in CAPS on first appearance
- Sounds in CAPS (BANG, CRASH)
- Only describe what we SEE and HEAR
### Dialogue
- Character name centered, ALL CAPS
- Parentheticals (sparingly) for tone/direction
- Dialogue left-aligned under name
- Keep speeches short—film is visual
### Transitions
- Use sparingly: `CUT TO:`, `SMASH CUT TO:`, `DISSOLVE TO:`
- Most scene changes are implied cuts
- `FADE IN:` at start, `FADE OUT.` at end
## Scene Structure
### Mini Three-Act
Every scene has its own structure:
**Beginning (10%)**
- Establish location/time
- Character enters situation
- Scene goal introduced
**Middle (80%)**
- Conflict develops
- Stakes escalate
- Complications arise
- Information delivered
**End (10%)**
- Scene climax
- Value shift
- Hook to next scene
### Value Shift
Every scene should shift a value:
- Hope → Despair
- Trust → Suspicion
- Power → Vulnerability
- Ignorance → Knowledge
## Scene Types
### Dialogue Scene
- Characters talking
- Subtext underneath
- Physical action woven in
- Avoid "talking heads"
### Action Scene
- Visual storytelling
- Minimal dialogue
- Clear geography
- Beat-by-beat choreography
### Montage
- Series of shots
- Passage of time
- Unified by theme or music
- Each shot advances story
### Intercut
- Parallel action
- Multiple locations
- Build tension through comparison
- `> INTERCUT - LOCATION A/LOCATION B`
## Writing Tips
### Pacing
```
Fast pace:
- Short sentences.
- Fragments.
- White space.
- Action verbs.
Slower pace:
The room settles into silence. Dust motes drift through the
shaft of light from the window. Somewhere, a clock ticks.
```
### Visual Writing
**Instead of:** "John is sad about his breakup."
**Write:** "John sits alone at a table for two. An untouched birthday cake. Two candles, unlit."
### Subtext
**On the nose:** "I'm angry at you for lying!"
**Subtext:** "Did you have a nice evening?"
## Scene Checklist
- [ ] Does the scene advance plot?
- [ ] Does it reveal character?
- [ ] Is there conflict?
- [ ] Does a value shift?
- [ ] Could any lines be cut?
- [ ] Is there subtext?
- [ ] Does it end with a hook?
- [ ] Is formatting correct?
## Common Mistakes
1. **Overwriting** - Trust the reader
2. **Camera directions** - Not your job
3. **Internal thoughts** - Can't be filmed
4. **Too much dialogue** - Show, don't tell
5. **No conflict** - Every scene needs tension
6. **Weak endings** - End on strength
## Output Format
```fountain
INT. [LOCATION] - [TIME]
[Opening action/description - 2-3 lines]
[CHARACTER NAME] ([age, brief description]) [action].
[CHARACTER]
[Dialogue]
[Action/response]
[OTHER CHARACTER]
([parenthetical])
[Dialogue]
[Scene climax/turning point]
[Exit action - hook to next scene]
```
Related 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.