This is your reference guide when you need to think through why a game mechanic works or doesn't. It breaks down the MDA framework (mechanics to dynamics to aesthetics), maps the flow channel for challenge balancing, and covers Bartle's player types with specific design implications. The troubleshooting section is genuinely useful, walking through "players are bored" or "dominant strategy emerged" with actual root causes and fixes. Pairs well with the bonded game designer agent for translating theory into implementation. Best used during early design when you're establishing core loops or mid-development when playtests reveal engagement problems you need to diagnose properly.
npx -y skills add pluginagentmarketplace/custom-plugin-game-developer --skill game-design-theory --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
leonxlnx/taste-skill
supercent-io/skills-template
supercent-io/skills-template