📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
@@ -1,6 +1,10 @@
|
||||
---
|
||||
name: game-development
|
||||
description: "Game development orchestrator. Routes to platform-specific skills based on project needs."
|
||||
description: >-
|
||||
Game development orchestrator. Routes by platform, dimension, and engine fit
|
||||
(web 2D/3D, hybrid DOM+canvas, narrative tools). Use when starting or
|
||||
structuring a game project, choosing frameworks, or picking among Phaser,
|
||||
PixiJS, Kaplay, Canvas/WebGL, Three.js, Babylon.js, Godot, Unity, or Ink/Twine.
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
@@ -8,13 +12,13 @@ date_added: "2026-02-27"
|
||||
|
||||
# Game Development
|
||||
|
||||
> **Orchestrator skill** that provides core principles and routes to specialized sub-skills.
|
||||
> **Orchestrator skill** — principles plus routing to specialized sub-skills.
|
||||
|
||||
---
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
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.
|
||||
You are working on a game development project. This skill teaches PRINCIPLES and directs you to the right sub-skill based on context.
|
||||
|
||||
---
|
||||
|
||||
@@ -24,7 +28,7 @@ You are working on a game development project. This skill teaches the PRINCIPLES
|
||||
|
||||
| If the game targets... | Use Sub-Skill |
|
||||
|------------------------|---------------|
|
||||
| Web browsers (HTML5, WebGL) | `game-development/web-games` |
|
||||
| Web browsers (HTML5, WebGL, WebGPU) | `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` |
|
||||
@@ -36,10 +40,11 @@ You are working on a game development project. This skill teaches the PRINCIPLES
|
||||
| 2D (sprites, tilemaps) | `game-development/2d-games` |
|
||||
| 3D (meshes, shaders) | `game-development/3d-games` |
|
||||
|
||||
### Specialty Areas
|
||||
### Architecture / tooling
|
||||
|
||||
| If you need... | Use Sub-Skill |
|
||||
|----------------|---------------|
|
||||
| Engine / framework choice, shell vs guest, fit tiers | `game-development/engine-selection` |
|
||||
| GDD, balancing, player psychology | `game-development/game-design` |
|
||||
| Multiplayer, networking | `game-development/multiplayer` |
|
||||
| Visual style, asset pipeline, animation | `game-development/game-art` |
|
||||
@@ -51,8 +56,6 @@ You are working on a game development project. This skill teaches the PRINCIPLES
|
||||
|
||||
### 1. The Game Loop
|
||||
|
||||
Every game, regardless of platform, follows this pattern:
|
||||
|
||||
```
|
||||
INPUT → Read player actions
|
||||
UPDATE → Process game logic (fixed timestep)
|
||||
@@ -64,7 +67,7 @@ RENDER → Draw the frame (interpolated)
|
||||
- Rendering: As fast as possible
|
||||
- Interpolate between states for smooth visuals
|
||||
|
||||
---
|
||||
**Hybrid / UI-heavy games:** the outer app may be DOM/event-driven; use a classic game loop only in canvas/WebGL viewports (or wherever simulation ticks).
|
||||
|
||||
### 2. Pattern Selection Matrix
|
||||
|
||||
@@ -76,11 +79,10 @@ RENDER → Draw the frame (interpolated)
|
||||
| **ECS** | Thousands of similar entities | RTS units, particles |
|
||||
| **Command** | Undo, replay, networking | Input recording |
|
||||
| **Behavior Tree** | Complex AI decisions | Enemy AI |
|
||||
| **Content-as-data** | Designers ship levels/events without code | JSON/YAML packs |
|
||||
|
||||
**Decision Rule:** Start with State Machine. Add ECS only when performance demands.
|
||||
|
||||
---
|
||||
|
||||
### 3. Input Abstraction
|
||||
|
||||
Abstract input into ACTIONS, not raw keys:
|
||||
@@ -90,10 +92,6 @@ Abstract input into ACTIONS, not raw keys:
|
||||
"move" → WASD, Left stick, Virtual joystick
|
||||
```
|
||||
|
||||
**Why:** Enables multi-platform, rebindable controls.
|
||||
|
||||
---
|
||||
|
||||
### 4. Performance Budget (60 FPS = 16.67ms)
|
||||
|
||||
| System | Budget |
|
||||
@@ -105,14 +103,7 @@ Abstract input into ACTIONS, not raw keys:
|
||||
| Rendering | 5ms |
|
||||
| Buffer | 1.67ms |
|
||||
|
||||
**Optimization Priority:**
|
||||
1. Algorithm (O(n²) → O(n log n))
|
||||
2. Batching (reduce draw calls)
|
||||
3. Pooling (avoid GC spikes)
|
||||
4. LOD (detail by distance)
|
||||
5. Culling (skip invisible)
|
||||
|
||||
---
|
||||
**Optimization Priority:** Algorithm → Batching → Pooling → LOD → Culling.
|
||||
|
||||
### 5. AI Selection by Complexity
|
||||
|
||||
@@ -123,8 +114,6 @@ Abstract input into ACTIONS, not raw keys:
|
||||
| **GOAP** | High | Emergent, planning-based |
|
||||
| **Utility AI** | High | Scoring-based decisions |
|
||||
|
||||
---
|
||||
|
||||
### 6. Collision Strategy
|
||||
|
||||
| Type | Best For |
|
||||
@@ -145,30 +134,33 @@ Abstract input into ACTIONS, not raw keys:
|
||||
| Cache nothing | Cache references |
|
||||
| Optimize without profiling | Profile first |
|
||||
| Mix input with logic | Abstract input layer |
|
||||
| Pick an engine by hype | Match engine to genre + team + delivery target |
|
||||
|
||||
---
|
||||
|
||||
## 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
|
||||
### “Browser 2D platformer”
|
||||
→ `game-development/engine-selection` → `game-development/web-games` → `game-development/2d-games` → `game-development/game-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
|
||||
### “UI-heavy web game with small arcade challenges”
|
||||
→ `game-development/engine-selection` (shell vs guest) → `game-development/web-games` → `game-development/2d-games` for guests only
|
||||
|
||||
### Example 3: "Multiplayer VR shooter"
|
||||
→ `game-development/vr-ar` for comfort and immersion
|
||||
→ `game-development/3d-games` for rendering
|
||||
→ `game-development/multiplayer` for networking
|
||||
### “Mobile puzzle”
|
||||
→ `game-development/mobile-games` → `game-development/game-design`
|
||||
|
||||
### “Multiplayer VR shooter”
|
||||
→ `game-development/vr-ar` → `game-development/3d-games` → `game-development/multiplayer`
|
||||
|
||||
### “Branching narrative with light stats”
|
||||
→ `game-development/engine-selection` (Ink/Twine) → host UI of your choice
|
||||
|
||||
---
|
||||
|
||||
> **Remember:** Great games come from iteration, not perfection. Prototype fast, then polish.
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user