agentleFS
Sign inStart free
bladecoderbladecoder/narrative-skills/skills/if/if-design-map/SKILL.md

if-design-map

Skill0 starsChanged 7 months agoMITView on GitHub

Design the explorable two-dimensional map for an Ink interactive fiction project, including locations, connections, gates, revisits, and spatial unlocks.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to design or refine the spatial layer of a free-exploration Ink game.

    line 10
  2. Very specific:

    Use English keys and filenames.

    line 55
  3. Distinctive:

    Create a navigable topology with clear start location and revisitable hubs when useful.

    line 60
  4. Distinctive:

    Ensure each unlock changes reachable space, available dialogue, or player knowledge.

    line 62
  5. Distinctive:

    Keep optional locations useful but not required for basic completion unless documented as critical path.

    line 63
  6. Very specific:

    Update locations.yaml as structured source of truth.

    line 64
  7. Distinctive:

    Do not draft Ink location files here.

    line 77
  8. Distinctive:

    Do not create decorative locations that have no gameplay or narrative function.

    line 78
  9. Distinctive:

    Do not hide critical path requirements only in prose.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

IF Design Map

Overview

Use this skill to design or refine the spatial layer of a free-exploration Ink game. The map should support meaningful revisits, visible blockers, state-driven unlocks, and clear relationships between locations.

Files To Read

Always read:

  • story.yaml
  • 04_design/story_beats.md
  • 04_design/critical_path.md
  • 04_design/state_model.md

Read when relevant:

  • 00_meta/*
  • 02_story/worldbuilding.md
  • 03_characters/*
  • 04_design/locations.yaml
  • 04_design/progression.yaml
  • 07_continuity/locations.yaml

Files To Write

Write or update:

  • 04_design/map.md
  • 04_design/locations.yaml
  • 07_continuity/locations.yaml when stable canon location facts emerge.

Location Model

For each meaningful location, define:

  • stable id;
  • display name;
  • narrative function;
  • initial availability;
  • connections;
  • visible exits and blocked exits;
  • discoveries available on first visit and revisit;
  • characters who may appear there;
  • obstacles or unlocks connected to the location;
  • state changes the location can grant.

Language Rules

Use English keys and filenames. Write human-readable values in story.language.

Procedure

  1. Identify only locations that create action, discovery, pressure, or choice.
  2. Create a navigable topology with clear start location and revisitable hubs when useful.
  3. Mark gates and locked routes without solving progression details prematurely.
  4. Ensure each unlock changes reachable space, available dialogue, or player knowledge.
  5. Keep optional locations useful but not required for basic completion unless documented as critical path.
  6. Update locations.yaml as structured source of truth.

Output

Provide:

  • map summary;
  • location list and major connections;
  • gated areas and unlock dependencies;
  • recommended next step, usually if-design-dialogue or if-design-progression.

Restrictions

  • Do not draft Ink location files here.
  • Do not create decorative locations that have no gameplay or narrative function.
  • Do not hide critical path requirements only in prose; record them structurally.

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.

Check your setup, free