
By Jabali Team · Published on Sep 13, 2026
Quick answer: Professional game designers use AI most for brainstorming and research (81% of AI users), code assistance (47%), daily writing tasks (47%), and prototyping (35%) (GDC 2026) — general LLMs like ChatGPT (74%), Gemini (37%), Copilot (22%) being the main tools. The workflow pattern: AI at the edges of production (thinking, drafting, fixing) with humans owning design decisions. The emerging frontier is AI-native production (Jabali Studio's category): the AI builds and iterates the game itself under the designer's direction. This guide maps both, stage by stage.
| Production stage | How designers use AI today | What stays human |
|---|---|---|
| Ideation | LLM brainstorms: "20 twists on gravity mechanics"; market scans; theme variations | Selecting the idea; taste |
| Concept validation | Drafting the one-page GDD; interrogating risks ("what kills this concept?") | The go/no-go call |
| Prototyping (35%) | LLM-assisted graybox code; AI-native prototypes (describe → playable in minutes) | Judging if it's fun |
| Production | Code assist (47%): snippets, debugging, boilerplate; asset drafts | Systems design; balance; coherence |
| Content | Placeholder text, barks, item descriptions; localization drafts | Voice, lore, final writing |
| Playtesting | Synthesizing feedback patterns; generating test checklists | Watching real players; deciding |
| Marketing | Store copy drafts, tag research, devlog editing | The hook; the community itself |
Percentages: share of AI-using professionals, GDC 2026 State of the Game Industry.
Notice the pattern: AI touches nearly every stage but owns none. Designers report the same division of labor everywhere — AI proposes, drafts, and repairs; humans select, tune, and certify. The 52%-negative sentiment in the same survey comes largely from workflows that violate that division (unreviewed AI output shipped as finished work).
Designers treat the LLM as a tireless junior designer: generate variations, attack the concept ("steel-man the boring version of this game"), draft the GDD skeleton, list comparable games. The designer's job: bring constraints, kill 90% of suggestions, and keep the spine. Rule of thumb: if you can't say why you kept an AI suggestion, you didn't use it — it used you.
Programmers and tech-designers use AI for the mechanical middle: boilerplate systems, regex-of-the-day, "why does this coroutine leak." Reported gains concentrate in unblocking — the work that used to eat evenings. The craft rule that emerged: AI writes code you could review like a colleague's PR, and you review every line like it's a stranger's.
Instead of assisting tasks, an AI producer builds the game: describe the concept, play it in minutes, iterate by conversation — with project-coherent changes, generated assets, and self-healing builds (Jabali Studio's model). The designer's role shifts fully to direction: intent in, judgment out. This is the workflow GDC's "prototyping 35%" category is growing into, and the one that changes who gets to make games at all.
Design insight: Every designer interviewed about AI lands on the same sentence, give or take: "it does the work, I make the decisions." That's not a compromise — it's a job description upgrade. The parts of game design people fell in love with (finding the fun, tuning feel, watching players light up) are precisely the parts AI can't do; the parts that burned people out (boilerplate, rework, asset chores) are precisely what it absorbs. The designers winning with AI are the ones who were honest about which part of their job was which.
A: Brainstorming/research (81% of AI-using professionals), daily writing tasks (47%), code assistance (47%), and prototyping (35%) — GDC 2026. Main tools: ChatGPT, Gemini, Copilot, plus AI-native production platforms emerging for full-game work.
A: The skill studios value is direction under AI acceleration: prompt craft, verification discipline, and fast iteration judgment. Job postings increasingly name AI-tool fluency, but the durable résumé line remains shipped games — AI just lets you ship more of them.
A: Start at the edges: brainstorming variations, drafting documents, unblocking code. Keep two rules — AI proposes, you dispose; and everything shipped gets human review. Graduate to AI-native production (full prototypes from a description) once the discipline feels natural.
A: On Steam, yes — AI-generated content requires a store-page disclosure. In jams, per event rules (GMTK currently discourages AI content). Professionally, transparency is becoming the norm rather than the exception.
A: The industry's honest answer, per its own surveys: 52% of companies use these tools while the ethics are debated. The position that holds up: AI does work, humans make decisions, players get a better or at least honest product. Tools don't have integrity; workflows do.