bs779517/story-skills / skills/chapter-writing
chapter-writing
VerifiedThis skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| references/chapter-template.md | markdown | 687 B |
| references/writing-guidelines.md | markdown | 2.6 KB |
references/writing-guidelines.md
View on GitHub# Writing Guidelines
Guidelines for writing chapter prose. Adapt to the story's genre, tone, and POV as defined in `story.md`.
## Show, Don't Tell
- Convey emotion through action, dialogue, and sensory detail rather than stating feelings
- BAD: "She was angry."
- GOOD: "Her fingers whitened around the hilt. She spoke through her teeth."
## POV Consistency
- **First person:** Everything filtered through narrator's voice, knowledge, and bias
- **Third-person limited:** Stay in one character's head per scene. Only describe what they perceive, think, and feel
- **Third-person omniscient:** Can reveal any character's thoughts, but maintain a consistent narrative voice
Do NOT shift POV mid-scene. If a POV shift is needed, use a scene break (marked with `---`).
## Dialogue
- Dialogue should reveal character, advance plot, or both
- Each character should have a distinct voice (reference their Voice & Speech Patterns)
- Use dialogue tags sparingly - "said" is invisible, fancy tags distract
- Break up long speeches with action beats
- Avoid exposition dumps disguised as conversation
## Pacing
- Short sentences and paragraphs = fast pace, tension, action
- Longer sentences and paragraphs = slower pace, reflection, atmosphere
- Vary sentence length for rhythm
- Scene length should match importance - don't over-write minor moments
## Scene Structure
Each scene should have:
- **Goal:** What the POV character wants in this scene
- **Conflict:** What opposes them
- **Outcome:** What happens (often a setback that drives the next scene)
Not every scene needs explosive conflict - quiet character moments matter too. But every scene should change something.
## Sensory Detail
Ground scenes in the physical world:
- Sight, sound, smell, touch, taste
- Choose 2-3 senses per scene, not all five
- Use details specific to the location (reference the location file)
- Sensory details should reflect the POV character's state of mind
## Chapter Openings
- Orient the reader quickly: who, where, when
- Hook with tension, mystery, or voice
- Avoid opening with weather or waking up (unless deliberately subverting the cliche)
## Chapter Endings
- End on a moment of change, revelation, or tension
- Cliffhangers work for action chapters
- Quiet resonance works for character chapters
- The last line should make the reader want to continue
## Continuity
Before writing, check:
- Previous chapter's ending (pick up threads, don't contradict)
- Character states (injuries, emotional state, knowledge)
- Timeline consistency (time of day, travel times, seasons)
- Plot arc progress (what beats need to land)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |