Claude is a strong partner for the written half of game design: stating the core loop, laying out currencies with their sources and drains, writing a progression curve as a formula, and turning a level idea into a brief a team can build. It is a poor judge of fun, and it cannot playtest. It also does not know your players, so any retention or conversion figure it offers is invention. Work in passes (loop, economy, curve, level, one-page GDD), ask for spreadsheet formulas instead of mental arithmetic, and treat every number as a hypothesis for a playtest to confirm or kill. This guide covers systems and level design; story, dialogue and engine code are separate jobs.
Nesta página
- What do you give it before it designs a loop?
- How do you build an economy that does not collapse?
- How do you balance numbers when Claude cannot playtest?
- What goes in a level brief and a one-page GDD?
- If your game is played at a table
- Where does Claude fail at this?
- Which game design skill fits which job?
- How do you install a game design skill in Claude?
- Related guides
- Frequently asked questions
Our running example is invented: a four-minute-session mobile game about tending plants on a space station, free to play. Every number below is an illustration, not a benchmark.
Game Designer (Systems & Level Design) AI Skill - Isembard
Get Game Designer (Systems & Level Design) AI Skill - Isembard →What do you give it before it designs a loop?
"Design a core loop for a cozy farming game" returns the genre average: plant, wait, harvest, sell, upgrade. Not wrong, but not yours. Five inputs make it specific:
The player fantasy. One sentence on who the player is pretending to be and why that is pleasant.
Session shape. Four minutes on a commute, or two hours on a sofa? The loop must close inside the session.
Platform and business model. Free-to-play, premium, ads or none. These decide what an economy is allowed to do.
The feeling you want to produce. Use the MDA framework (mechanics, dynamics, aesthetics) from the other end: start with the emotion, then ask which mechanics could cause it.
What you already know. Your own playtest notes, if any. Claude should say what is missing rather than fill the gap.
The last rule saves you from fiction; without it Claude will write "target day-1 retention of 40%" as if it were a fact about your game. The assumptions list is the most useful output: it is your playtest plan in draft.
How do you build an economy that does not collapse?
An economy is a set of currencies with faucets (where they enter) and sinks (where they leave). Collapse comes from imbalance: too many faucets and everything becomes worthless; too many sinks and players stall. The Isembard skill is built around exactly this table form, with faucets, sinks and currency types.
Asking for formulas is the point. Language models do long chains of arithmetic less reliably than a spreadsheet, and a table of confident balances may hide a slip on day five. Paste the formulas into a sheet and change an input to see what breaks.
How do you balance numbers when Claude cannot playtest?
Claude cannot feel whether level 8 drags. It can set up the structure so your playtest answers a clear question. The most common balancing tool is a progression curve: the amount of work needed to move from one level to the next, as a formula you can change in one cell.
A typical output is a power curve such as =ROUND(100*A2^1.5,0) for XP needed at level A2, which gives 100, 283, 520, 800 and 1,118 for levels 1 to 5. Treat it as a starting shape, not an answer. The sensitivity table is where Claude earns its keep: it shows how fragile your targets are. Then you play, with real people, and replace the guess for XP per session with the number you measure.
What the output looks like (illustration only)
An invented excerpt for the station botanist game. Nothing here is a recommendation for any real game.
What goes in a level brief and a one-page GDD?
A level brief is a document someone else can build from. It names the purpose of the level, the one thing it teaches, the critical path, the gates, where the intensity rises and falls, and the landmarks that help a player find their way. A one-page game design document (GDD) is the opposite compression: the whole game on a page so a new person can disagree with it.
Then compress: ask for a one-page GDD from the documents you have approved, with sections for pitch, loop, mechanics, economy, progression, risks and open questions. Make "open questions" mandatory; a GDD with no unknowns means Claude filled the gaps for you.
If your game is played at a table
For tabletop RPGs and game-master prep
Game Master Bundle · $39
Five files for running a table: a dungeon generator whose layout follows from who built it, an adventure arc generator, an NPC generator built around a want, a need and a secret, a riddle and puzzle generator that ships the answer with a hint ladder, and a name generator for people, taverns and factions. It is built for prep before a session, not for designing a digital game.
Where does Claude fail at this?
It cannot tell whether the game is fun. Fun comes from feel, tension and what players do when you are not looking. A loop that is sound on paper can be tedious in the hand, so playtest early with the roughest prototype you have, paper if need be.
It invents data. Retention curves, conversion rates and "industry standard" drop-off points are not figures you can trust for your game. If a number is not yours, it is a guess.
It makes arithmetic slips in long simulations. A week of balances produced as plain text can drift. Always ask for formulas and check them in a spreadsheet.
It designs by genre average. Ask for three structurally different loops before you pick one, and say what you refuse to copy.
It under-weights friction, producing economies where nothing is scarce and levels with no failure. Ask explicitly for scarcity, failure states and the cost of choices.
It misses dark patterns unless you ask. Random rewards, artificial timers and pressure to spend can creep in. Ask for an ethics pass and check loot box law per country, as the Isembard page advises.
It balances in isolation. A fix to one value breaks the next system along, so ask which other numbers each change affects.
It adds features. Give it your team size and deadline, and ask it to cut.
Which game design skill fits which job?
| Skill | Best for | Price |
|---|---|---|
| Isembard - Game Designer (Systems & Level Design) | Loops, economy, progression curves, level briefs, GDD, playtest plan, ethics pass for a digital game | $19 |
| Game Master Bundle | Tabletop RPG prep: dungeons, NPCs, plots, riddles, names | $39 |
How do you install a game design skill in Claude?
With an All-in-one subscription there is nothing to download. Add KissMySkills to Claude once as a connector: open Customize → Connectors, click +, then Add custom connector, and paste https://mcp.kissmyskills.com/mcp. Sign in with your email, then ask for the skill by name, for example "load Isembard". The same connector works in ChatGPT, Claude Code, Codex and Cursor; the step-by-step setup for each is on the connector page. Signing in is free, and your first skill call starts a 7-day free trial with every skill.
Bought the single file? You download one .skill file, which is a ZIP archive with SKILL.md inside. In Claude, turn on code execution under Settings → Capabilities, then open Customize → Skills, click +, choose Upload a skill, pick the file as it is and toggle the skill on. In ChatGPT, Gemini or another chat, open the file as a ZIP and paste SKILL.md into custom instructions. The Game Master Bundle arrives as several .skill files plus a README; upload them one at a time.
Need more than one specialist?
Buying Game Designer (Systems & Level Design) AI Skill - Isembard gets you one file. The All-in-one subscription loads every skill in the catalog through one connector, in Claude, ChatGPT Business, Enterprise or Edu, Claude Code, Codex or Cursor, and keeps each skill updated when we improve it. $12 a month or $69 a year, with 7 days free and every skill included.
Start the free trial → Why a subscription beats buying filesRelated guides
- How to Use Claude as a QA Engineer
- How to Use Claude as a Story Generator
- How to Use Claude as a Business Analyst
- How to Use Claude for Coding
Frequently asked questions
Is there a Claude skill for game design?
Yes. Isembard - Game Designer (Systems & Level Design) AI Skill ($19) defines the core loop and meta loop, builds economy models with faucets, sinks and spreadsheet formulas, writes level briefs with a critical path and intensity graph, and produces a one-page or full GDD, a playtest plan and an ethics review. It is engine-agnostic and does not write engine code.
Can Claude design a game economy?
It can set up the structure: currencies, faucets, sinks, a week of simulated balances and a progression curve, all as spreadsheet formulas. It cannot know your real player behaviour, so every amount is a placeholder to tune in playtests, and you should check its arithmetic in a sheet rather than trusting a table of numbers.
Can Claude write a game design document?
Yes, as a one-page summary or full sections: pitch, core loop, mechanics, economy, progression, risks and open questions. Feed it your approved decisions and insist on an open-questions list, since a GDD with no unknowns means gaps were filled with guesses.
What is Claude bad at in game design?
Judging whether a game is fun, using real retention or revenue data, long arithmetic, avoiding genre clichés and keeping scope under control. It also tends to remove friction and may suggest manipulative monetisation, so ask for failure states, scarcity and an ethics pass.
Is there a Claude skill for tabletop game masters?
Yes. The Game Master Bundle ($39) covers dungeon, plot, NPC, riddle and name generation for running a tabletop RPG session. It is for table prep, not for designing a digital game's systems.
Game Designer (Systems & Level Design) AI Skill - Isembard
Or get it with every other skill in All-in-one: $12/month, 7 days free, every skill.