AI Game Studio in One Skill: Lead, 22 Roles, 9 Guides

    1

    You bring the game idea and make the design decisions.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI Game Studio in One Skill: Lead, 22 Roles, 9 Guides

    Example session with this skill installed

    I have a game idea: a single-player 2D deckbuilder for PC where you play a lighthouse keeper holding back a storm. Go.

    • Read your context and instructions
    • Compiled the ai game studio

    Summary

    Acting as Studio Lead. Nothing gets built until the design for milestone 1 is decided by you, so I start with the pitch.

    I need these in one message:

    1. Who plays it (age, taste, how long a session is)?
    2. PC only, or other platforms later?
    3. An engine, if you have one in mind. Full guides here cover Unity, Roblox and Unreal; for Godot or a web stack I ticket an engine note first.
    4. Any reference images for the look?

    What happens next

    StepWhat I doWhat you decide
    Design sessionShort interview rounds until milestone 1's sections of the design doc are DECIDEDEvery design answer
    SetupGit repository if missing, then the records: STATE, GDD, DECISIONS, vision, MILESTONESNothing
    Tooling ticketEngineer: project skeleton and a test commandNothing
    Milestone 1 planGoal, exit criteria and tickets, each with an owner role, owned files and a done lineApprove the plan
    The loopDispatch, independent review, playtest, integrate, reportDesign questions only

    What a ticket looks like

    0003-draw-and-play-a-card
    Owner: engineer    Type: feature    Priority: P1    Depends on: 0001
    Owns: src/cards/*, tests/cards/*
    Acceptance:
    - A hand of 5 is drawn at the start of a turn
    - Playing a card spends energy and moves it to the discard pile
    Done when: the project's test command passes with the new CardTurnTests
    Checks: reviewer (code), playtester (player-visible, PASS or FAIL per criterion)
    

    Next steps

    • Answer the four questions above.
    • I run the design session, then bring you the milestone 1 plan to approve.
    • Installs, spending, pushing and publishing always come back to you first.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Turns one coding agent into a whole game studio. You bring the game idea and make the design decisions. A Studio Lead plans it into milestones and tickets, hands each ticket to the right specialist, has a different role review it, playtests it from the player's side, and keeps the project's memory in plain files so work resumes cleanly after any break.

    New in v1.1: the delegating pipeline

    Every code or content ticket now runs nine steps on tiered models. A fast model scouts the files and the current check numbers. A mid model reads the source and cites every claim to a file and line. The Lead writes the brief with your decisions quoted word for word. The right role builds in its own tree. A separate prover runs the gates and the mutants: undo each part of the change, and the check must fail. A different model reviews in a fresh context. Fixes are proved again. The Lead accepts and ships, and only the Lead commits. Hosts that cannot choose models or run sub-agents are covered too: the steps stay, and the limit is recorded.

    What you get

    • The Studio Lead method: intake, planning, tickets with an owner, owned files and a provable done line, dispatch, review, playtest, risk gates and memory. One start-here path for a new game and one for adopting an existing project.
    • 22 role playbooks: engineer, principal, coder, ui, reviewer, designer, loremaster, economist, muse, asset-builder, animator, primary-asset-creator, art-director, playtester, game-security, optimizer, researcher, legal, monetization, overseer, second-brain and consultant. Each one says what the role owns, its steps, its checks, its hand-offs and its hard rules.
    • 9 engine and audit guides, the full text of our nine separate skills: Unity, Roblox, Unreal Engine 5 C++, Roblox VFX and Models, Moderation Console, Game Economy Inflation Audit, First-Session Friction Audit, Game Design Session and Feel From Footage, with their 28 template files (Luau modules and tests, Unity build and test scripts, an Unreal test, audit sheets).
    • Studio templates: ticket, review checklist, playtest report, vision with an art master prompt, milestones, policy, approvals, license policy, UI theme, and a short spec for the minimum tooling a project needs.

    How it works

    • Uses sub-agents where your agent supports them (one per ticket), or takes one role at a time where it does not.
    • No builder approves its own work: code goes to the reviewer, the look to the art-director, anything a player can touch to the playtester.
    • Design stays yours. The lead asks you about design, taste, scope and money, and decides the rest itself.
    • Risky actions are gated: installs need an approval; secrets, spending, pushing and publishing stay with you.

    Good to know

    • It is a method in text files. There is nothing to install.
    • Bot playtests need a small test bridge that the engineer role builds into your game. On Roblox and Unreal the playtest is written steps for you to run in the editor.
    • Full engine guides cover Unity, Roblox and Unreal. For other engines (Godot, a web stack) the researcher role writes an engine note first.
    • Already own our single skills? This includes all nine.

    For: solo developers and small teams building a game with any SKILL.md agent.

    Example prompts:

    • "I have a game idea, go."
    • "Adopt this Unity project and plan the next milestone."
    • "Act as the reviewer for ticket 0042."
    • "Run the economy inflation audit on my drop tables."

    A method in text files: it adds no engine, tools or assets of its own. Bot playtests need a small test bridge that the engineer role builds into your game; on Roblox and Unreal, playtests are written steps you run in the editor. Full engine guides cover Unity, Roblox and Unreal only; other engines start with a researcher-written engine note. Payments, credentials, pushing and publishing stay with the developer. Legal content is a checklist and drafts, not legal advice.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Requires

    Git

    Permissions

    Read Files
    Write Files
    Terminal / Shell
    Listed6 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    One SKILL.md with the Studio Lead method, 22 role playbooks, 9 engine and audit guides (Unity, Roblox, Unreal Engine 5 C++, Roblox VFX and Models, Moderation Console, Game Economy Inflation Audit, First-Session Friction Audit, Game Design Session, Feel From Footage), 28 engine template files, and studio templates for tickets, reviews, playtest reports, vision, milestones, policy, approvals, license policy and UI theme. Text files only.

    Every ticket names the files it owns and a done line that a command can prove. The role that builds never approves its own work: code goes to a separate reviewer role, and anything a player can see or touch goes to the playtester, who reports bugs instead of fixing them.

    Yes. There is an adoption path: a read-only scan, records created around your existing layout, the test and build commands run once for a baseline, and each current failure filed as a ticket. Nothing is restructured without your say.

    Any agent that reads SKILL.md skills. Where the agent supports sub-agents, the lead runs one per ticket; where it does not, the lead takes one role at a time and switches role before reviewing.

    Partly. Playtests are written from each acceptance criterion. Bots can run them once the engineer role has built a small test bridge into your game. On Roblox and Unreal, and before a bridge exists, the playtest is written steps for you to run in the editor, and those criteria stay open until you report back.

    Decide your game design, spend money, handle passwords or keys, push code to a remote, publish or upload to a store. Installs and new dependencies need an approval first. Legal notes are drafts for you or a lawyer, not legal advice.

    New in Game Development