Awesome-omni-skills game-development

Game Development workflow skill. Use this skill when the user needs Game development orchestrator. Routes to platform-specific skills based on project needs and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/game-development" ~/.claude/skills/diegosouzapw-awesome-omni-skills-game-development && rm -rf "$T"

manifest: skills/game-development/SKILL.md

Game Development

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/game-development

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Game Development > Orchestrator skill that provides core principles and routes to specialized sub-skills. ---

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Sub-Skill Routing, Anti-Patterns (Universal), Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

You are working on a game development project.
This skill teaches the PRINCIPLES of game development and directs you to the right sub-skill based on context.
Use when the request clearly matches the imported source intent: Game development orchestrator. Routes to platform-specific skills based on project needs.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`2d-games/SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`3d-games/SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Sub-Skill Routing

Platform Selection

If the game targets...	Use Sub-Skill
Web browsers (HTML5, WebGL)	`game-development/web-games`
Mobile (iOS, Android)	`game-development/mobile-games`
PC (Steam, Desktop)	`game-development/pc-games`
VR/AR headsets	`game-development/vr-ar`

Dimension Selection

If the game is...	Use Sub-Skill
2D (sprites, tilemaps)	`game-development/2d-games`
3D (meshes, shaders)	`game-development/3d-games`

Specialty Areas

If you need...	Use Sub-Skill
GDD, balancing, player psychology	`game-development/game-design`
Multiplayer, networking	`game-development/multiplayer`
Visual style, asset pipeline, animation	`game-development/game-art`
Sound design, music, adaptive audio	`game-development/game-audio`

Examples

Example 1: Ask for the upstream workflow directly

Use @game-development to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @game-development against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @game-development for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @game-development using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Routing Examples

Example 1: "I want to make a browser-based 2D platformer"

→ Start with

game-development/web-games

for framework selection → Then

game-development/2d-games

for sprite/tilemap patterns → Reference

game-development/game-design

for level design

Example 2: "Mobile puzzle game for iOS and Android"

→ Start with

game-development/mobile-games

for touch input and stores → Use

game-development/game-design

for puzzle balancing

Example 3: "Multiplayer VR shooter"

→

game-development/vr-ar

for comfort and immersion →

game-development/3d-games

for rendering →

game-development/multiplayer

for networking

Remember: Great games come from iteration, not perfection. Prototype fast, then polish.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Physics/logic: Fixed rate (e.g., 50Hz)
Rendering: As fast as possible
Interpolate between states for smooth visuals
Pattern - Use When - Example
State Machine - 3-5 discrete states - Player: Idle→Walk→Jump
Object Pooling - Frequent spawn/destroy - Bullets, particles
Observer/Events - Cross-system communication - Health→UI updates

Imported Operating Notes

Imported: Core Principles (All Platforms)

1. The Game Loop

Every game, regardless of platform, follows this pattern:

INPUT  → Read player actions
UPDATE → Process game logic (fixed timestep)
RENDER → Draw the frame (interpolated)

Fixed Timestep Rule:

Physics/logic: Fixed rate (e.g., 50Hz)
Rendering: As fast as possible
Interpolate between states for smooth visuals

2. Pattern Selection Matrix

Pattern	Use When	Example
State Machine	3-5 discrete states	Player: Idle→Walk→Jump
Object Pooling	Frequent spawn/destroy	Bullets, particles
Observer/Events	Cross-system communication	Health→UI updates
ECS	Thousands of similar entities	RTS units, particles
Command	Undo, replay, networking	Input recording
Behavior Tree	Complex AI decisions	Enemy AI

Decision Rule: Start with State Machine. Add ECS only when performance demands.

3. Input Abstraction

Abstract input into ACTIONS, not raw keys:

"jump"  → Space, Gamepad A, Touch tap
"move"  → WASD, Left stick, Virtual joystick

Why: Enables multi-platform, rebindable controls.

4. Performance Budget (60 FPS = 16.67ms)

System	Budget
Input	1ms
Physics	3ms
AI	2ms
Game Logic	4ms
Rendering	5ms
Buffer	1.67ms

Optimization Priority:

Algorithm (O(n²) → O(n log n))
Batching (reduce draw calls)
Pooling (avoid GC spikes)
LOD (detail by distance)
Culling (skip invisible)

5. AI Selection by Complexity

AI Type	Complexity	Use When
FSM	Simple	3-5 states, predictable behavior
Behavior Tree	Medium	Modular, designer-friendly
GOAP	High	Emergent, planning-based
Utility AI	High	Scoring-based decisions

6. Collision Strategy

Type	Best For
AABB	Rectangles, fast checks
Circle	Round objects, cheap
Spatial Hash	Many similar-sized objects
Quadtree	Large worlds, varying sizes

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/game-development

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@2d-games
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@3d-games
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@daily-gift
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@design-taste-frontend
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Anti-Patterns (Universal)

Don't	Do
Update everything every frame	Use events, dirty flags
Create objects in hot loops	Object pooling
Cache nothing	Cache references
Optimize without profiling	Profile first
Mix input with logic	Abstract input layer

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.