if-design-dialogue
Skill0 starsChanged 7 months agoMITView on GitHub
Design free-order character conversations for an Ink interactive fiction project, including dialogue topics, availability, knowledge gates, relationship state, and revelations.
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-mapSkill
- if-design-progressionSkill
- if-design-structureSkill
- if-draft-inkSkill
- if-init-projectSkill
- if-load-contextSkill
- 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
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 10
Use this skill to design the conversation layer of an exploratory Ink game.
- Very specific: line 57
Write project prose in story.language.
- Distinctive: line 63
Ensure every critical clue has a reliable route and every optional clue has a purpose.
- Distinctive: line 64
Add repeatable dialogue patterns that acknowledge prior visits without bloating state.
- Very specific: line 66
Keep implementation-ready notes without drafting full Ink dialogue unless requested through if-draft-ink.
- Distinctive: line 80
Do not write final Ink dialogue here.
- Distinctive: line 81
Do not make critical knowledge missable without an alternate route.
- Distinctive: line 82
Do not assume a fixed player conversation order.
≈ “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 Design Dialogue
Overview
Use this skill to design the conversation layer of an exploratory Ink game. Conversations should work in player-chosen order, react to discovered knowledge, and avoid breaking continuity when topics are encountered early, late, or repeatedly.
Files To Read
Always read:
story.yaml03_characters/protagonist.md03_characters/supporting_cast.md04_design/story_beats.md04_design/state_model.md
Read when relevant:
03_characters/relationships.md04_design/map.md04_design/locations.yaml04_design/dialogue_matrix.md04_design/progression.yaml07_continuity/*
Files To Write
Write or update:
04_design/dialogue_matrix.md04_design/state_model.mdwhen new conversation state is needed.
Optionally update:
03_characters/relationships.mdwhen interaction design clarifies relationships.
Dialogue Model
For each important character, define:
- stable
id; - where and when they can appear;
- default conversational stance;
- repeatable small talk or inspection loop;
- one-time topic revelations;
- topics gated by knowledge, inventory, skills, location, or prior dialogue;
- relationship or trust changes;
- what the character knows, conceals, misunderstands, or refuses to discuss.
Language Rules
Write project prose in story.language. Keep filenames, IDs, and YAML keys in English.
Procedure
- Identify which characters need interactive dialogue rather than static prose.
- Define topic groups and their dependencies.
- Ensure every critical clue has a reliable route and every optional clue has a purpose.
- Add repeatable dialogue patterns that acknowledge prior visits without bloating state.
- Mark topics that should become unavailable, altered, or newly available after state changes.
- Keep implementation-ready notes without drafting full Ink dialogue unless requested through
if-draft-ink.
Output
Provide:
- dialogue matrix summary;
- key topic gates and revelations;
- character availability rules;
- state additions;
- recommended next step, usually
if-design-progression.
Restrictions
- Do not write final Ink dialogue here.
- Do not make critical knowledge missable without an alternate route.
- Do not assume a fixed player conversation order.
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.

