game-design — Claude Code skill: core gameplay loop prototyping
game-design guides coding assistants on game development fundamentals using project reference files.
Apache-2.0 247 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill game-design -a claude-codeWhat game-design does
This skill frames the AI as a game developer across Claude Code, Codex, Cursor, and other tools. It focuses on shipping lean prototypes, prioritizing framerate, and refining core mechanics before expanding architecture.
Operational logic relies on local documentation. The assistant checks references/patterns.md when building gameplay systems, uses references/sharp_edges.md for diagnosing failures, and validates constraints against references/validations.md.
Without these three reference files present in your workspace, the agent cannot execute the specific checks and patterns enforced by the skill prompt.
What it helps with
- prototype a tight core gameplay loop early
- audit physics and tick logic against known edge cases
- validate game mechanics against project rule constraints
- structure entity components using predefined patterns
Example prompts for the agent
- Build a tilemap player movement controller following
references/patterns.md - Diagnose collision glitches using
references/sharp_edges.md - Review my core game loop against rules in
references/validations.md
How to install game-design
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill game-design -a claude-code2Manually: put the files in place
~/.claude/skills/game-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/game-design/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill game-design -a codex2Manually: put the files in place
.agents/skills/game-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill game-design -a cursor2Manually: put the files in place
.cursor/skills/game-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/game-design2Manually: put the files in place
.github/skills/game-design/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill game-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/game-designManually: put the files in place
.devin/skills/game-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill game-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about game-design
How to install game-design in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill game-design -a claude-code in your terminal. This writes the skill definition to ~/.claude/skills/game-design/SKILL.md.
What does game-design do?
It applies production principles like core-loop prioritization and points the model directly to workspace reference docs for pattern selection, risk evaluation, and code review.
Which external files does this skill require?
The instructions direct the agent to read references/patterns.md, references/sharp_edges.md, and references/validations.md as domain truth during implementation.
Source text
SKILL.md · Apache-2.0
--- name: game-design description: Building interactive experiences that engage, challenge, and delight playersUse when "game, gamedev, game development, phaser, unity, unreal, godot, gameplay, game loop, sprites, collision, physics, player, level, tilemap, games, gamedev, interactive, gameplay, physics, engines, performance, player-experience" mentioned. --- # Game Design ## Identity You're a game developer who has shipped titles across platforms—from browser games to console releases. You understand that games are systems that create experiences, and you've debugged physics glitches at 2 AM and celebrated when the feel finally clicked. You've built entity-component systems, optimized draw calls, and learned that the simplest mechanics are often the hardest to perfect. You know that technical excellence serves player experience, that scope creep kills more games than technical debt, and that a polished core loop beats a feature-complete mess. You've learned from your over-ambitious projects and your successful launches, and you bring that hard-won wisdom to every game you build. Your core principles: 1. Fun is the first feature 2. Prototype the core loop before building systems 3. Frame rate is a feature—performance is non-negotiable 4. Juice makes the difference between good and memorable 5. Playtest early, playtest often, playtest with fresh eyes 6. Every system exists to serve the player experience 7. Scope kills games—ship smaller, ship sooner ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity