dialogue-flags
Skill12 starsChanged 23 days agoMITView on GitHub
Use when dialogue choices, conditional lines, relationship facts, shop/gate reactions, or conversation outcomes need persistent branch state without duplicating the quest graph.
In this repository194 other files it gives its agents.
- llms.txtllms.txt
- hd-sprite-sequenceSkill
- pixel-animationSkill
- skin-weightsSkill
- spine-skeletalSkill
- sprite-atlasSkill
- sprite-catalogSkill
- sprite-skinSkill
- art-bibleSkill
- asset-pack-intakeSkill
- character-rigSkill
- materialsSkill
- model-pipelineSkill
- open-asset-fixtureSkill
- vfx-generateSkill
- a11y-controlsSkill
- ability-gateSkill
- action-feelSkill
- ad-breakSkill
- adventure-toolSkill
- aggro-tableSkill
- aim-assistSkill
- ammo-reloadSkill
- analytics-funnelSkill
- animation-blendSkill
- animation-graphSkill
- asset-runtimeSkill
- attack-tellSkill
- audio-busesSkill
- audio-feelSkill
- avatar-createSkill
- balance-designSkill
- boss-designSkill
- browser-inputSkill
- camera-anti-clipSkill
- camera-modestySkill
- camera-shotsSkill
- cert-handoffSkill
- chemistry-verbsSkill
- climb-vaultSkill
- cloud-saveSkill
- collision-layersSkill
- combo-designSkill
- cover-shooterSkill
- cover-spaceSkill
- crafting-loopSkill
- currency-dualSkill
- cutscene-handoffSkill
- day-nightSkill
- death-carrySkill
- debug-slateSkill
- deck-buildSkill
- dialogue-beatSkill
- difficulty-designSkill
- dodge-iframeSkill
- durability-economySkill
- encounter-designSkill
- enemy-aiSkill
- enemy-fireSkill
- enemy-kit-balanceSkill
- The first 60 shown.
The file
Files
Dialogue Flags
This skill owns namespaced dialogue/conversation facts and branch conditions. quest-graph owns quest structure; save-systems owns persistence format/versioning; game-localization owns localized text.
Modes
| Mode | Effect scope |
| flavor-only | changes later dialogue/presentation only |
| flag-alters-shop | changes shop/reward/availability policy |
| flag-alters-gate | participates in an authored access condition |
Each flag has a stable namespaced ID such as dialogue.vendorA.met or a project equivalent. Do not key save state by localized line text, choice index, or transient UI order. Persist through save-systems with schema/migration rules.
Flags can be read by quest/shop/gate systems when explicitly referenced, but they do not become a second hidden quest graph. Effects are authored and inspectable.
Replay/alternate-choice viewing is a project feature, not a universal requirement. If conversations can be replayed, define whether flags are preview-only, rewound, forked in a lab slot, or permanently committed.
Acceptance
Save/reload after representative choices and verify stable flag IDs and dependent outcomes. Reorder/localize choices and confirm persisted meaning does not change. A branch that affects progression must name the consuming system and migration behavior.
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.