if-load-context
Skill0 starsChanged 7 months agoMITView on GitHub
Read, validate, and summarize the shared project context for an Ink interactive fiction workspace before map, dialogue, progression, drafting, or playtest skills run.
In this repository27 other files it gives its agents.
- beta-reader-passSkill
- build-distributionSkill
- chapter-reviewSkill
- continuity-checkSkill
- create-character-bibleSkill
- define-style-bibleSkill
- draft-chapterSkill
- generate-high-level-outlineSkill
- if-design-dialogueSkill
- if-design-mapSkill
- if-design-progressionSkill
- if-design-structureSkill
- if-draft-inkSkill
- if-init-projectSkill
- if-plan-ink-sliceSkill
- if-playtest-reviewSkill
- if-sync-stateSkill
- ink-docSkill
- init-story-projectSkill
- load-story-contextSkill
- manuscript-reviewSkill
- plan-chapterSkill
- prepare-exportSkill
- rewrite-chapterSkill
- sync-story-bibleSkill
- update-character-stateSkill
- update-timelineSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Very specific: line 10
Use this skill to load the current workspace as an Ink interactive fiction project.
- Distinctive: line 14
Use this skill when:
- Very specific: line 23
Always read story.yaml and README.md when present.
- Distinctive: line 25
Read these when present and relevant:
- Very specific: line 47
Treat story.yaml as the source of truth.
- Very specific: line 66
If story.language is missing, treat it as blocking for content-writing skills.
- Distinctive: line 88
Do not rewrite creative content just to tidy context.
- Distinctive: line 89
Do not invent missing design facts.
- Distinctive: line 90
Do not treat optional incomplete files as blockers unless a downstream skill needs them.
≈ “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.
Files
IF Load Context
Overview
Use this skill to load the current workspace as an Ink interactive fiction project. It should validate story.yaml, identify the current IF workflow stage, and summarize the reliable design, state, and source files that downstream IF skills should use.
When To Use
Use this skill when:
- the current directory is expected to contain an Ink IF project;
story.yamlor IF design files may be incomplete;- another IF skill needs grounded context before making changes;
- the user asks for project readiness, status, or next step.
Files To Read
Always read story.yaml and README.md when present.
Read these when present and relevant:
00_meta/*01_style/*02_story/*03_characters/*04_design/map.md04_design/locations.yaml04_design/dialogue_matrix.md04_design/progression.yaml04_design/state_model.md04_design/story_beats.md04_design/critical_path.md05_ink/main.ink05_ink/locations/*05_ink/dialogues/*05_ink/systems/*06_playtest/*07_continuity/*
Metadata Contract
Treat story.yaml as the source of truth. For IF projects, preserve or normalize these fields when enough evidence exists:
project:
format: "interactive_fiction_ink"
interactive:
engine: "ink"
entrypoint: "05_ink/main.ink"
navigation_model: "free_2d_map"
conversation_model: "free_order_dialogues"
workflow:
next_skill: ""Language Rules
- Skill instructions and canonical filenames stay in English.
- YAML keys stay in English.
- Human-readable project content must be written in
story.language. - If
story.languageis missing, treat it as blocking for content-writing skills.
Procedure
- Confirm whether the workspace is initialized as an IF Ink project.
- Validate shared metadata, especially
project.format,interactive.engine,story.language, andworkflow.next_skill. - Identify which IF artifacts exist and which are still missing.
- Cross-check obvious consistency between design files and Ink source files.
- Report the reliable context, missing blockers, and recommended next IF skill.
Output
Provide:
- project validity and workflow stage;
- selected story language;
- current map, dialogue, progression, and Ink source status;
- missing or inconsistent files;
- recommended next skill.
Restrictions
- Do not rewrite creative content just to tidy context.
- Do not invent missing design facts.
- Do not treat optional incomplete files as blockers unless a downstream skill needs them.
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
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.

