agentleFS
bs779517bs779517/story-skills/skills/worldbuilding/SKILL.md

worldbuilding

Skill8 starsChanged 9 months agoMITView on GitHub

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.

7 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 4 are distinctive, and 11 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create and manage world elements for a story project.

    line 10
  2. Very specific:

    Read story.md for genre, era, and tone context

    line 18
  3. Very specific:

    Read worldbuilding/_index.md for existing locations and systems

    line 19
  4. Distinctive:

    Ask for the location's name and type (city, fortress, wilderness, etc.)

    line 20
  5. Very specific:

    Write the file using references/location-template.md

    line 27
  6. Very specific:

    Update worldbuilding/_index.md locations table

    line 29
  7. Distinctive:

    If notable characters are listed, verify those character files exist and add location references to them

    line 30
  8. Very specific:

    Read story.md for genre and themes context

    line 34
  9. Very specific:

    Read worldbuilding/_index.md for existing systems

    line 35
  10. Very specific:

    Update worldbuilding/_index.md systems table

    line 40
  11. Distinctive:

    Read the existing file

    line 45
  12. Distinctive:

    If cross-references changed, update the linked files

    line 47
  13. Very specific:

    Update worldbuilding/_index.md if name, type, or status changed

    line 48
  14. Very specific:

    When a location is used in a chapter, the chapter's frontmatter locations field links back

    line 54
  15. Very specific:

    Keep the worldbuilding/_index.md world overview section current as elements are added

    line 55

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Worldbuilding

Overview

Create and manage world elements for a story project. Locations and systems (magic, politics, technology, etc.) are stored as markdown files in the worldbuilding/ directory with YAML frontmatter. All elements cross-reference characters and other story elements.

Prerequisites

A story project must already exist (created via the story-init skill). Verify by checking for story.md in the project root.

Creating a Location

  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:
    • Physical description and atmosphere
    • History relevant to the story
    • Culture and customs of inhabitants
    • Notable features characters will interact with
    • Current state at story's timeline
  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 location references to them

Creating a System

  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)

Updating World Elements

  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

Cross-Referencing

  • Locations reference characters via notable-characters in frontmatter
  • Systems reference practitioners via character tags
  • When a location is used in a chapter, the chapter's frontmatter locations field links back
  • Keep the worldbuilding/_index.md world overview section current as elements are added

Reference Files

  • references/location-template.md - Template for location files
  • references/system-template.md - Template for system files
  • references/world-element-types.md - Detailed prompts for each system type (magic, political, technology, religion, economic, military, social)

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.