AI party members that build with you — free, local, yours. A QA guard that learns your game — and never asks the same question twice.
Your role stays deliberately small: produce assets and playtest your own game. Everything else, the party does — it drives your engine headlessly and never asks you to click around an editor.
/fullparty:directorParty leader. Runs whole production campaigns, dispatches the party, enforces doctrine distilled from shipped live games — and interrupts you only for the calls that are yours.
/fullparty:artStyle-locked prompts for any image platform, then local post-processing, QA gates, and in-game placement.
/fullparty:uiBuilds your entire game UI in code — safe-area, fonts, panels, toasts — then self-reviews with screenshots.
/fullparty:engineDrives Unity/Godot directly: headless compile gates, batch imports, scene placement, build verification.
/fullparty:soundSweeps the game for every sound it needs, hands you sourcing sheets, wires what you bring back.
/fullparty:bmMonetization designed with you against your economy, then the rails: IAP, receipt validation, ledgers, refunds.
/fullparty:launchRelease builds, store listing, age rating, submission checklists, launch-day rollout and rollback.
/fullparty:legalPrivacy policy, terms, gacha-odds disclosures, licenses — drafted from your game's reality, for your review.
/fullparty:liveopsMonitoring, log triage, incident runbooks, maintenance flow — live pushes always wait for your go.
A QA scan against a 264-pattern failure catalog built from live-game postmortems. Your code never leaves your machine — the server sees summaries, returns the checks relevant to your change, and remembers every judgment you make. Need an API key? Open a GitHub issue — it's free.
/fullparty:initRegister the project — opens your server-side judgment ledger. Once per project.
/fullparty:scanDiff/manifest summary in → the relevant slice of the catalog out → checks run locally → report.
/fullparty:triageJudge findings in plain language. A question answered once is never asked again — the guard knows your game better every scan.
No setup ritual. Paste one line to your AI coding agent — Claude Code, Codex, anything — and it sets itself up:
Set up Fullparty from https://github.com/apiwoo/fullparty and be my party for this game.
Claude Code users can also install it as a plugin:
/plugin marketplace add apiwoo/fullparty
/plugin install fullparty@fullparty --scope user
The guard receives summaries and distilled findings only — never raw source. Ever.
Player-visible choices — art style, UI frame, fonts, tone — are locked per game in your charter. We ship methods, never a house style.
The party verifies facts and does the work; the calls that shape your game are always yours to make.