agentleFS
ThomasHoussinThomasHoussin/Claude-Book/.claude/skills/story-ideator/SKILL.md

story-ideator

Skill112 starsChanged 10 months agoMITView on GitHub

Generate original storylines from any universe bible without plagiarizing source material. Use when creating new adventures using established characters, locations, and style. Triggers on "invent a story", "create a new adventure", "generate synopsis", "brainstorm plot".

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use only ELEMENTS (characters, locations, tone) from bible

    line 19
  2. Distinctive:

    Verify originality against known source plots

    line 21
  3. Distinctive:

    Create NEW mysteries, conflicts, and resolutions

    line 22
  4. Distinctive:

    Before ideation, verify these files exist:

    line 26
  5. Very specific:

    If analysis/output/*/structure.md files exist, load them for anti-plagiarism checks.

    line 32
  6. Distinctive:

    Read and extract from bible:

    line 38
  7. Distinctive:

    Create conflict BETWEEN protagonists:

    line 83
  8. Distinctive:

    Add ecological/environmental stakes

    line 90
  9. Distinctive:

    Add moral dilemma without clear villain

    line 91
  10. Distinctive:

    Add rescue mission to mystery

    line 92
  11. Distinctive:

    Add discovery that changes understanding of universe

    line 93
  12. Very specific:

    Use patterns from bible/structure.md:

    line 111
  13. Very specific:

    If analysis/output/*/structure.md files exist, compare generated plot:

    line 123
  14. Distinctive:

    Write synopsis following structure:

    line 150
  15. Very specific:

    Create detailed chapter plan matching structure from bible/structure.md:

    line 180
  16. Distinctive:

    After each phase, ask for validation before proceeding

    line 208
  17. Distinctive:

    If user has specific ideas, integrate them as constraints

    line 209

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Story Ideator Skill

Generate original storylines using an established universe bible. The goal is authentic stories that feel like they belong in the universe while being completely new.

Core Principle: Originality Over Imitation

NEVER:

  • Reuse plot structures from analyzed source books
  • Copy specific scenes, events, or mysteries
  • Recreate villain archetypes with minor changes
  • Mirror chapter-by-chapter progression patterns

ALWAYS:

  • Use only ELEMENTS (characters, locations, tone) from bible
  • Generate plots through COMBINATORIAL techniques
  • Verify originality against known source plots
  • Create NEW mysteries, conflicts, and resolutions

Input Requirements

Before ideation, verify these files exist:

  • bible/style.md - Writing constraints
  • bible/structure.md - Narrative arc patterns
  • bible/characters/*.md - Character profiles
  • bible/universe/*.md - Location files

If analysis/output/*/structure.md files exist, load them for anti-plagiarism checks.

Ideation Workflow

Phase 1: Load Universe Context

Read and extract from bible:

  1. Characters: List all from bible/characters/, extract:
    • Name, core traits, usual role in stories
    • Relationships between characters
    • Capabilities and limitations
  2. Locations: List all from bible/universe/, extract:
    • Name, atmosphere, typical story function
    • Connections between locations
  3. Structure constraints: From bible/structure.md:
    • Expected chapter count/length
    • Arc patterns, pacing expectations
    • Genre-specific mechanics (mystery, adventure, etc.)
  4. Style constraints: From bible/style.md:
    • Tone, vocabulary, forbidden elements
    • POV, tense, target audience

Output: Brief synthesis in .work/universe-context.md

Phase 2: Brainstorm via Collision Techniques

Generate 10-15 story seeds using these methods. Apply them to the SPECIFIC characters and locations found in Phase 1:

A. What-If Inversion Take a character's usual role and invert it:

  • "What if [leader character] had to follow instead of lead?"
  • "What if [protector character] needed protection?"
  • "What if [cautious character] had to take the biggest risk?"

B. Location Collision Combine two locations in unexpected ways:

  • "[Safe location] becomes dangerous"
  • "[Adventure location] becomes refuge"
  • "Mystery connects [location A] to [location B] unexpectedly"

C. External Pressure Introduce constraints the series hasn't explored:

  • Time pressure (deadline creates urgency)
  • Resource constraint (usual support unavailable)
  • Information asymmetry (one character knows what others don't)

D. Relationship Stress Test Create conflict BETWEEN protagonists:

  • Disagreement on moral choice
  • Competing loyalties
  • Temporary separation forcing independent action

E. Genre Blend Mix the series formula with adjacent elements:

  • Add ecological/environmental stakes
  • Add moral dilemma without clear villain
  • Add rescue mission to mystery
  • Add discovery that changes understanding of universe

Output: Numbered list of seeds in .work/story-seeds.md

Phase 3: Seed Selection & Development

Present seeds to user. For selected seed:

  1. Expand to Logline (1-2 sentences)
    • WHO wants WHAT but OBSTACLE leads to STAKES
  2. Define MICE Type (Orson Scott Card)
    • Milieu: Story about exploring a place (ends when they leave/return)
    • Idea: Story about answering a question (ends when answered)
    • Character: Story about transformation (ends when character changes)
    • Event: Story about restoring order (ends when resolved)
  3. Map to Structure Template Use patterns from bible/structure.md:
    • Opening hook
    • Discovery/catalyst
    • Investigation/adventure
    • False victory/setback
    • Climax
    • Resolution

Output: Expanded seed in .work/selected-seed.md

Phase 4: Anti-Plagiarism Check

If analysis/output/*/structure.md files exist, compare generated plot:

Extract from each source structure.md:

  • Mystery/conflict type
  • Antagonist archetype
  • Discovery method (how protagonists learn about problem)
  • Resolution pattern (how it's solved)
  • Key location usage

Compare to generated plot:

ElementGeneratedSource 1Source 2...
Conflict type
Antagonist
Discovery
Resolution
Location role

Scoring:

  • 0-1 matches with any single source: ✅ Proceed
  • 2-3 matches with any single source: ⚠️ Modify overlapping elements
  • 4+ matches with any single source: ❌ Return to Phase 2, select different seed

Output: Comparison table in .work/plagiarism-check.md

Phase 5: Synopsis Generation

Write synopsis following structure:

# [Title]

## Logline
[1-2 sentences]

## Setup
[Initial situation, what triggers the adventure]

## Conflict
[Main obstacle, antagonist forces, stakes]

## Complications
[2-3 escalating problems]

## Climax
[Confrontation, how protagonists solve it]

## Resolution
[New equilibrium, character growth]

## Themes
[What the story explores beyond plot]

Output: story/synopsis.md

Phase 6: Chapter Plan

Create detailed chapter plan matching structure from bible/structure.md:

# Chapter Plan

## Chapter 1: [Title]
**Function**: [Setup/Catalyst/Development/Climax/Resolution]
**Location**: [From bible/universe/]
**POV focus**: [Which character(s)]
**Events**:
- [Beat 1]
- [Beat 2]
- [Beat 3]
**Ends with**: [Hook for next chapter]

[Repeat for all chapters per bible/structure.md chapter count]

Output: story/plan.md

Output Language

Match language of bible/style.md. Internal thinking/checks can be in English.

Interaction Style

  • Present options, don't decide alone
  • After each phase, ask for validation before proceeding
  • If user has specific ideas, integrate them as constraints
  • Explain reasoning for anti-plagiarism flags

Quick Commands

User can trigger abbreviated flow:

  • Ideate: [constraint] → Skip to Phase 2 with constraint
  • Develop seed N → Take seed N directly to Phase 3
  • Check plot: [description] → Run only Phase 4 on description

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.