Game Knowledge

Use when a game question needs field knowledge rather than a process: "screen shake", "hit-stop", "juice", floaty or flat feel, camera complaints, pricing, wishlist numbers, Next Fest, store page and demo scope, finding playtesters, burnout, IP assignment and contractor agreements, localization, publishers, or the design theory behind a mechanic. Also use on first contact with a game project — project.godot, Assets/, *.uproject, or a package.json with three/phaser/babylon — and when a project is months old with no marketing, no playtesters, or no backups. NOT for defining direction (use game-direction), planning or implementing milestones (use game-production), or judging a build or a readiness claim (use game-review).

gigio1023 Updated 2 repo stars
Four agent skills for building a game with AI coding. game-direction turns taste into a creative brief and the first prototype to build; game-production builds

File contents

gigio1023/game-studio commit e44b4f2f18

Frequently asked questions

npx get-skill add gigio1023/game-knowledge