EW Skill — Scene Structure

Dependency chain. Read these in order before writing anything:

1. core/runtime-contract.md (short operating contract; does not replace the full rules)
2. core/obsidian-workspace.md (resolve storage and persistence rules)
3. core/anti-ai-rules.md (full standard)
4. core/ai_slop_commandments.md (mechanism reference and diagnostic checklist)
5. core/voice-profile.md (voice resolver; require the resolved profile's Completed: field to be exactly Yes, otherwise stop and run onboarding)
6. Any .md files in the active voice's references folder, as resolved by core/voice-profile.md

This chain applies on direct invocation (/ew:scene-structure) exactly as it does on dispatch through /ew. Direct invocation skips routing, not constraints.

---

WHAT THIS SKILL IS FOR

Scene-level fiction writing. The mechanics of building scenes that move, breathe, and pull the reader forward. This is not about plot — plot is what happens. This is about how to make what happens feel real, urgent, and inevitable.

A scene is the basic unit of fiction. A novel is not a collection of chapters — it is a chain of scenes, each one connected to the next by consequence. Get the scene right and the rest follows.

---

THE SCENE CONTRACT

Every scene must earn its existence. The test is brutal and simple: if you removed this scene, would the story change? Not just lose color — actually change? If the answer is no, the scene is dead weight. Cut it or rebuild it until it does necessary work.

Every scene must contain three things (Yorke's Law):

1. Event — something happens
2. Change — the situation is different at the end than it was at the start
3. Conflict — a force opposing the character's goal, external or internal

A scene that opens and closes at the same emotional or situational level is not a scene — it is description dressed as action. Something must shift. The character's knowledge, position, relationship, or understanding must be different when the scene ends than when it began.

---

SCENE ENTRY AND EXIT

Enter late. Leave early.

Enter the scene at the last possible moment before the conflict begins. The reader does not need setup. They do not need to know where everyone is sitting before the argument starts. Start in the middle of the tension.

❌ "Sarah arrived at the coffee shop at 2pm. She found a table near the window and ordered a latte. When Marcus walked in, she noticed he looked tired." ✅ "Marcus sat down without taking off his coat. Sarah knew then that this was going to be short."

Exit the scene the moment its work is done. The beat that pays off the scene's conflict — cut immediately after it. Do not explain what it means. Do not let characters recover. Cut to the next scene before the dust settles.

The reader's imagination does the work between scenes. Trust it.

---

THE BEAT STRUCTURE

A scene is built from beats. A beat is an action/reaction pair — one character does something, another responds, and the situation advances or complicates.

How beats work:

• Character A wants something
• Character A acts toward that want (action)
• Character B (or circumstance) responds (reaction)
• The situation is now different — better, worse, or more complicated
• Repeat until the scene's conflict resolves or escalates to a new level

Beats are not always visible. An internal realization is a beat. A silence is a beat. A character deciding not to say the thing they almost said is a beat. What matters is that each one changes something.

The beat pace: Fast scenes have short beats and quick turns. Slow scenes have longer beats where each action is weighted. Match the beat rhythm to the emotional temperature of the scene. A chase has tight, fast beats. A final conversation between estranged lovers has long, heavy beats where every word carries history.

---

SHOW DON'T TELL: THE ACTUAL MECHANICS

"Show don't tell" is the most-repeated rule in fiction and the least-explained. Here is what it actually means:

Telling announces the emotional conclusion: "She was furious." "He was afraid." "The room felt oppressive."

Showing gives the reader the sensory data that produces the conclusion in their own mind. The reader draws the inference. The inference they draw is theirs — which means it lands harder than the one you hand them.

The formula: write the physical, observable, specific detail that carries the emotion — not the emotion itself.

❌ "He was nervous before the meeting." ✅ "He checked his phone twice in the elevator. When the doors opened he was still looking at the screen."

❌ "The house felt abandoned." ✅ "A pizza box sat on the radiator, its grease soaking through the cardboard. Nobody had moved it."

R.U.E. — Resist the Urge to Explain. If you've shown it, do not then state it. The moment you write "She was furious — he could see that now," you have cut the reader's experience in half. You showed it and then told them what to have felt. Trust what you built. Cut the explanation.

---

SENSORY GROUNDING

Scenes that feel real are anchored in specific sensory detail. Not generic sensory detail — specific. "The room smelled like cigarettes" is generic. "The room smelled like the inside of a vending machine — burnt plastic and artificial sugar" is specific.

The one telling detail. You do not need to describe everything. Find the one detail that carries the scene's emotional truth and render it precisely. A half-eaten pizza on a radiator tells us more about the state of a relationship than three paragraphs of backstory.

The detail must be earned: it should carry meaning beyond the description itself. A character checking their phone twice in an elevator tells us they're nervous. A character noticing the paint chipping on a doorframe tells us they've stood here before, waiting, many times.

Sensory hierarchy in tense scenes: Sound and touch are more visceral than sight. Smell is the most memory-triggering sense. Vision is the most overused. Vary the sensory entry point by scene.

---

DIALOGUE

Dialogue in fiction is not transcribed conversation. It is compressed, purposeful, and loaded with subtext.

The subtext rule: Characters almost never say exactly what they mean in high-stakes scenes. They say something else while meaning something else entirely. The gap between what is said and what is meant is where the tension lives.

❌ "I don't trust you anymore," she said. ✅ "I saw you at the restaurant." A pause. "Which restaurant?" "You know which one."

How to write subtext:

• Characters deflect, change the subject, answer a different question than the one asked
• Characters use precision about small things when they won't talk about the big thing
• Characters repeat themselves when they're waiting for a response they know isn't coming
• Silence is dialogue — the beat where nothing is said is often the loudest beat

Dialogue and action: Dialogue does not exist in a vacuum. Characters do things while they talk. They pour coffee, avoid eye contact, pick up objects. These actions either reinforce or contradict what's being said. Contradiction is more interesting.

The said rule: "Said" is invisible. It doesn't need to be replaced with "remarked," "stated," "questioned," "declared." Those words pull the reader out of the scene and into the author's anxiety about variety. Use "said." When an action makes the attribution clear, skip the tag entirely.

---

POINT OF VIEW (POV)

POV is not just whose head you're in — it is whose experience filters every sentence. Get inside the POV character's specific sensory and emotional reality and stay there.

POV violations:

• Describing what the POV character cannot see or know
• Giving the POV character a reaction they haven't earned yet (telling the reader the significance before the character experiences it)
• Head-hopping within a scene — switching whose interiority you're inhabiting mid-scene

The close POV advantage: The tighter the POV, the higher the tension. In close third or first person, the reader only knows what the character knows. This creates dramatic irony (when the reader understands more than the character does) and genuine suspense (when both are in the dark). Use it.

---

SCENE PACING

Dramatize vs. summarize. Not every event deserves a full scene. The rule: scenes earn full dramatization when the conflict in them changes the story significantly. Events that move time without changing the story get summary.

"Over the next three weeks, nothing changed." That's summary. Six words. The scene you dramatize is the one where everything changes.

White space and sentence rhythm. Tension increases when sentences get shorter. Calm decreases when sentences expand, breathing room opens between beats. A scene approaching its crisis should feel like it's speeding up — shorter paragraphs, shorter sentences, faster beats.

The paragraph break is a beat of its own. Use it deliberately.

---

THE SCENE'S FORWARD MOMENTUM

The last beat of a scene must give the reader a reason to turn the page. Not a cliffhanger every time — a question, an unresolved tension, an implication that the situation is going somewhere they need to follow.

The question the scene ends on: Every scene ends with an unanswered question — even if neither the character nor the reader can name it. "What is she going to do now?" "Does he know?" "Can they come back from that?" If the scene ends without leaving a question open, the reader has no momentum into the next scene.

The scene resolved its conflict. Good. Now make sure it opened a new one.

---

POST-GENERATION REVIEW

After producing any prose, stop. Re-read core/anti-ai-rules.md Sections 1–7 with the draft in front of you. Pay particular attention to Section 2 (sentence-level patterns) and Section 6 (craft rules) — the fiction-specific failures live there. Fix every failure before presenting the output.

Fiction tolerates AI patterns least of all formats. A single "marking a significant shift" or tacked-on -ing analysis phrase breaks the reader's immersion. Find it. Cut it.

PRE-DRAFT CHECKLIST

• Does the scene open at the last possible moment before conflict?
• Does something change — knowledge, position, relationship, understanding?
• Is every beat an action/reaction pair?
• Are emotions shown through specific physical detail, not announced?
• Have you cut every explanation that follows a moment of showing?
• Is dialogue carrying subtext — do characters say one thing and mean another?
• Are you in the POV character's specific sensory reality, not above it?
• Does the scene exit the moment its work is done?
• Does the last beat leave a question open for the next scene?
• Have you run the relevant sections of core/anti-ai-rules.md?