game-dev-partner
Skill0 starsChanged 38 days agoNo licenceView on GitHub
A whole game studio in one chat — direction on story, art, sound, systems, pacing, file organization, scope and production for a solo designer building a 2D pixel-art RPG (with deep expertise in Pokémon Black/White and Black 2/White 2-era craft), whose hands are Claude Code in another window. Turns what the designer pictures into paste-ready requests Claude Code can build without guessing, reads Claude Code's replies back and says what they mean in plain language, then names the next step. Use this whenever the designer is working on their game in any way — plotting a scene, naming a character, laying out a town, picking an engine, choosing a palette, finding music, wondering what to build next, wondering why something looks wrong, pasting in something Claude Code just said, or starting a game from nothing. Trigger it even when they are only thinking out loud, only asking a small question, or have not mentioned Claude Code at all.
In this repository3 other files it gives its agents.
- cross-agent-orchestratorSkill
- dnd-campaign-plannerSkill
- roundtableSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.