{
 "schema": "aiblocks-page/1",
 "id": "agency-game-designer",
 "type": "agent",
 "name": "Gameplay designer",
 "summary": "Turn a game idea into a game design plan. Get design pillars, a gameplay loop, mechanic specs, tuning numbers to test and a playtest plan.",
 "headline": "Gameplay designer",
 "subhead": "Tell it your game idea, who it is for and how long a play session lasts. It writes the gameplay loop at three time scales, spec sheets for each mechanic, a tuning table marked as guesses, and a playtest plan with questions to ask.",
 "job": {
  "id": "build-product",
  "name": "Build a product people want"
 },
 "level": "intermediate",
 "thinking": "high",
 "tested": true,
 "updated": "2026-11-03",
 "first_published": "2026-10-26",
 "inputs": [
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  },
  {
   "type": "document",
   "required": false,
   "label": "Document",
   "what": "a finished document, such as a Word file, a PDF or a page of notes"
  }
 ],
 "outputs": [
  {
   "type": "document",
   "required": true,
   "label": "Document",
   "what": "a finished document, such as a Word file, a PDF or a page of notes"
  }
 ],
 "you_give": [
  "Your game idea in a few lines, and the genre",
  "Who plays it and on what device",
  "How long one play session should last",
  "The feeling you want players to have, such as powerful, clever or relaxed",
  "Existing notes, rules or a draft design document (optional)"
 ],
 "you_get": [
  "Three to five design pillars the game must deliver",
  "The gameplay loop in three levels, with action, feedback and reward at each",
  "A spec sheet for each key mechanic, with edge cases and failure states",
  "A tuning table where every number is marked as a guess to playtest",
  "A first-session onboarding checklist",
  "A playtest plan with what to watch for and the questions to ask"
 ],
 "use_when": [
  "You have a game idea in your head and need a written design a team can build from.",
  "Playtesters say \"it felt off\" and you need a loop and clear questions to test.",
  "You are adding a new mechanic and want to know how it touches the rest of the game.",
  "You want a first-session flow that teaches the main action without a long tutorial."
 ],
 "skip_when": [
  "You only need coins, gems, prices and drop rates. Use the Game economy designer.",
  "You are building on Roblox and need pass, product and retention advice. Use the Roblox Experience Designer agent.",
  "You need code for the game. Use the Unity software architect or the Godot gameplay programmer.",
  "You want proof the game is fun. Only playtests with real players can show that."
 ],
 "output_sample": {
  "input": [
   "Your game idea, genre and who it is for",
   "How long one session should last",
   "The feeling you want players to have",
   "Existing notes or a draft design document (optional)"
  ],
  "prerequisites": [
   "An AI you can paste a long brief into, such as Claude, ChatGPT or Gemini"
  ],
  "output": [
   {
    "name": "Design pillars",
    "contains": "Three to five player experiences the game must deliver, plus the one thing that must feel good."
   },
   {
    "name": "Core loop",
    "contains": "What the player does, feels and earns in seconds, in one session and over weeks."
   },
   {
    "name": "Mechanic specs",
    "contains": "For each mechanic, its purpose, input, output, success and failure states and edge cases."
   },
   {
    "name": "Tuning table",
    "contains": "Starting numbers with min and max, each with a reason and marked as a guess to playtest."
   },
   {
    "name": "Onboarding flow",
    "contains": "A first-session path that teaches the main action quickly, with no failure in the first beat."
   },
   {
    "name": "Playtest plan",
    "contains": "What success and broken look like, what to watch and the questions to ask players."
   },
   {
    "name": "Open questions",
    "contains": "Gaps and assumptions to settle before you build."
   }
  ]
 },
 "output_shape": "BRIEF AND ASSUMPTIONS\n  <game idea> | <genre, platform, player, session length> | ASSUMED: <list> | MISSING: <list>\n\nDESIGN PILLARS\n  <3 to 5 pillars> | fun hypothesis: <the one thing that must feel good>\n\nCORE LOOP\n  Moment to moment (0 to 30 seconds): action <x> | feedback <y> | reward <z>\n  Session (5 to 30 minutes): goal <x> | tension <y> | resolution <z>\n  Long term (hours to weeks): progression <x> | reason to return <y>\n\nMECHANIC SPECS (one per mechanic)\n  <name> | purpose <why> | player fantasy <feeling> | input | output | success <what working looks like> | failure <what goes wrong> | edge cases <list> | tuning levers <list> | touches <systems>\n\nTUNING TABLE\n  <variable> | start value | min | max | reason | status <PLACEHOLDER until playtested>\n\nONBOARDING FLOW\n  <step> | time <seconds> | what the player learns | safe from failure <yes or no>\n\nPLAYTEST PLAN\n  <what to test> | success looks like <measure> | broken looks like <measure> | question to ask <list>\n\nOPEN QUESTIONS AND CHECKS STILL NEEDED\n  <item> | <how to settle it>",
 "how_to_use": [
  "Download the pack from this page and add it to your AI as a skill. Or paste SKILL.md into a new chat, then paste references/source-agent.md after it.",
  "Write a short brief. Say the game idea, genre, who plays it, session length and the feeling you want.",
  "Your AI asks once for anything missing. Anything still unknown is marked as an assumption you can change.",
  "Read the pillars and the loop first. Ask yourself if each pillar is something players would feel in the first five minutes. Fix them before you read the mechanics.",
  "Check the numbers in the tuning table are all marked as guesses. Build the loop on paper or in a spreadsheet, then test it with real players.",
  "Bring what players did and said back to the agent, and ask it to revise the design."
 ],
 "checks": [
  "The result addresses your actual task and cites the evidence used.",
  "Examples, role-play experience and targets are kept separate from verified results.",
  "Claims of tests, memory, tool access or completed actions match what actually happened."
 ],
 "next": [
  {
   "name": "Roblox experience designer agent",
   "url": "https://useaiblocks.com/skills/agency-roblox-experience-designer",
   "why": "Shape the product"
  }
 ],
 "source": {
  "by": "Michael Sitarzewski and Agency Agents contributors",
  "repo": "msitarzewski/agency-agents",
  "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/game-development/game-designer.md",
  "licence": "MIT",
  "original_name": "Game Designer",
  "commit": "b37b5bb33b78f2c1d6567d98e25ca818e3259219"
 },
 "credits": [
  {
   "title": "Game Designer",
   "by": "Michael Sitarzewski and Agency Agents contributors",
   "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/game-development/game-designer.md",
   "used": "Original agent profile, preserved in references/source-agent.md; AI Blocks adds setup and review instructions."
  }
 ],
 "files": [
  "LICENSE",
  "references/source-agent.md",
  "SETUP.md",
  "source.json"
 ],
 "links": {
  "page": "https://useaiblocks.com/agents/agency-game-designer",
  "markdown": "https://useaiblocks.com/agents/agency-game-designer.md",
  "json": "https://useaiblocks.com/agents/agency-game-designer.json",
  "instructions": "https://useaiblocks.com/skills/agency-game-designer/SKILL.md",
  "download": "https://useaiblocks.com/skills/agency-game-designer.zip",
  "api_item": "https://useaiblocks.com/api/v1/items/agency-game-designer",
  "api_document": "https://useaiblocks.com/api/v1/documents/agent/agency-game-designer",
  "mcp": "https://useaiblocks.com/mcp"
 }
}
