chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene",…
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
$ npx -y skills add danjdewhurst/story-skills --skill worldbuilding --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/worldbuildingContext preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
name: worldbuilding description: This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
Create and manage world elements for a story project. Locations, systems (magic, politics, technology, etc.), factions, and artifacts are stored as markdown files in the `worldbuilding/` directory with YAML frontmatter. All elements cross-reference characters and other story elements.
A story project must already exist (created via the story-init skill). Verify by checking for `story.md` in the project root.
1. Read `story.md` for genre, era, and tone context 2. Read `worldbuilding/_index.md` for existing locations and systems 3. Ask for the location's name and type (city, fortress, wilderness, etc.) 4. Build the location through conversation, covering:
5. Write the file using `references/location-template.md` 6. Save to `worldbuilding/locations/{name-kebab}.md` 7. Update `worldbuilding/_index.md` locations table 8. If notable characters are listed, verify those character files exist and add this location's kebab-case identifier to each character file's `locations` frontmatter list 9. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
1. Read `story.md` for genre and themes context 2. Read `worldbuilding/_index.md` for existing systems 3. Identify the system type and consult `references/world-element-types.md` for the relevant prompts 4. Build the system through conversation, addressing the key questions for that type 5. Write the file using `references/system-template.md` 6. Save to `worldbuilding/systems/{name-kebab}.md` 7. Update `worldbuilding/_index.md` systems table 8. Cross-reference with characters who interact with the system (e.g., magic-users for a magic system) 9. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
Use `story add faction "{Faction Name}" --type "{family|guild|government|military|religion|company|community|criminal|other}"` when the CLI is available. Otherwise create `worldbuilding/factions/{name-kebab}.md` with frontmatter fields `name`, `type`, `status`, `members`, `locations`, and `tags`.
Cover:
Use `story add artifact "{Artifact Name}" --type "{object|weapon|document|technology|relic|symbol|resource|other}"` when the CLI is available. Otherwise create `worldbuilding/artifacts/{name-kebab}.md` with frontmatter fields `name`, `type`, `status`, `owner`, `location`, and `tags`.
Cover:
1. Read the existing file 2. Make the requested changes 3. If cross-references changed, update the linked files 4. Update `worldbuilding/_index.md` if name, type, or status changed 5. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
Use the Story CLI when it is available. If `story` is not installed but the `story-maintenance` skill is present, use `node ../story-maintenance/scripts/story.js` with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry and backlink checks manually.
Agent Skills for planning, tracking, and drafting fiction in markdown. Story Skills gives agents a shared project format for fiction: a story bible, character files, worldbuilding notes, factions, artifacts, plot arcs, scene state, continuity questions,
Repo: danjdewhurst/story-skills
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene",…
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character…
This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing",…
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline…
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to…
This skill should be used when the user asks to validate, reindex, repair registries, check links, check continuity, count words, summarize a story project,…