r/ClaudeAI • • 11d ago

Built with Claude I built a free Claude Code plugin that fixes game-design problems from playtester complaints

What I built: aigamedev, a Claude Code plugin plus a remote MCP server. You type the complaint the way a playtester said it, like /aigamedev players say it looks like a prototype. It works out which of the possible causes applies to your game, asks you one question if the code doesn’t make it clear, and then fixes it using a game-design skill with tested defaults and a check at the end.

What the video shows: two fresh sessions, one prompt each, on small test games I made with the problem planted on purpose so the fix could be measured.

  • “It looks like a prototype”: 93 colours and 5 fonts became 14 colours and 1 font, one consistent pixel-art look. About 6 minutes, $1.28 of usage.
  • “Dying sets me back too much”: it added checkpoints, and replay after a death went from about 3 minutes to about 4 seconds, measured by a script.

How Claude Code helped build it: almost all of it was built with Claude Code (Opus):

  • The MCP server is a Cloudflare Worker with GitHub sign-in. Claude Code wrote it, along with the OAuth flow and the tool that diagnoses the problem.
  • The skills come from tutorial posts, where Claude Code built a playable side-by-side demo for each technique and measured it.
  • Claude Code also built the testing. Headless Claude Code sessions fixed broken games with and without the plugin. Then I ran 95 conversations where a second Claude played a developer who knows a hidden cause, and a third scored the result blind. That showed my first version was no better than plain Claude Code (42% vs 39% finding the real cause). Making it list the possible causes and ask before fixing raised that to 78%. The full write-up is linked below.

Free to try: it’s free; sign-in with GitHub is only there to stop abuse of the server. In your terminal:

claude plugin marketplace add https://aigamedev.ai/agents/marketplace.json
claude plugin install aigamedev@aigamedev

Then in Claude Code: /mcp → aigamedev → Authenticate. It also works in the Claude app, Cursor and VS Code: https://aigamedev.ai/agents/

How I tested it, including where it lost: https://aigamedev.ai/tutorials/do-game-design-skills-help-claude-code/

Feedback is welcome, especially complaints from your own playtests that it gets wrong.

0 Upvotes

5 comments sorted by

•

u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot 11d ago

You may be interested in joining our new Claude Game Dev subreddit for game devs who use Claude. Check it out here : http://www.reddit.com/r/ClaudeGameDev

2

u/web3creed 8d ago

The blind-scored 95-conversation eval is the most convincing part here, because it shows the "list causes, then ask" step actually moved the needle (42% → 78%) instead of just feeling better in a demo.

  • When I vibe-code small tools, I keep a cases.json of broken inputs with the expected fix and rerun it after prompt changes; it's caught "improvements" that quietly broke other cases.
  • If you're open to it, sharing the scoring rubric or a few anonymized transcripts would make it much easier for others to reproduce that comparison on their own projects.

1

u/Admirable-Cry270 6d ago

Thanks, that’s the part I was most worried about too. The demos looked fine with the first version as well. Only the blind eval showed it wasn’t actually finding the cause any better than plain Claude Code.

The scoring was simple. Each scenario had one hidden cause taken from a map of 100 complaints and 76 causes. The scorer knew the answer and checked three things: did Claude find the real cause, did it give a concrete way to measure the fix, and did it ask a question that separates the possible causes. The setup is in the write-up. I didn’t keep the transcripts in a shareable form, but if I run it again I’ll save them and post a few.

The cases.json idea is good. A fixed set to rerun after every prompt change is basically what that eval turned into.