game-onboarding
Skill27 starsChanged 2 months agoMITView on GitHub
Getting a player from "start" to competent without a text wall - the first 30 seconds, progressive disclosure, and which of the 5 tutorial types fits. Use when a new player is confused, or you're about to write a tutorial popup.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- craftSkill
- game-architectureSkill
- game-audioSkill
- game-axiomsSkill
- game-feelSkill
- game-mechanicsSkill
- game-narrativeSkill
- game-playbooksSkill
- game-qualitySkill
- gameSkill
- objectSkill
- skillsSkill
- threeSkill
- worldSkill
The file
Files
onboarding/ — the first minute
Nobody reads your instructions. The first 30 seconds either teach the verb or lose the player.
| page | what it fixes |
first-30s.md | the opening doesn't land — use the core verb 5+ times, close one feedback loop, win one micro-victory |
progressive-disclosure.md | everything unlocked at once — one new idea per level, then combine |
tutorial-types.md | mixing implicit / explicit / contextual / optional / mandatory tutorials into mush |
See also game/axioms/play-teaching.md — the axiom these three implement.
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.