@mclawnet/agent 0.6.20 → 0.6.22

package/skills/game-development/2d-games/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: 2d-games
+description: "2D game development principles. Sprites, tilemaps, physics, camera."
+risk: none
+source: community
+date_added: "2026-02-27"
+---
+
+# 2D Game Development
+
+> Principles for 2D game systems.
+
+---
+
+## 1. Sprite Systems
+
+### Sprite Organization
+
+| Component | Purpose |
+|-----------|---------|
+| **Atlas** | Combine textures, reduce draw calls |
+| **Animation** | Frame sequences |
+| **Pivot** | Rotation/scale origin |
+| **Layering** | Z-order control |
+
+### Animation Principles
+
+- Frame rate: 8-24 FPS typical
+- Squash and stretch for impact
+- Anticipation before action
+- Follow-through after action
+
+---
+
+## 2. Tilemap Design
+
+### Tile Considerations
+
+| Factor | Recommendation |
+|--------|----------------|
+| **Size** | 16x16, 32x32, 64x64 |
+| **Auto-tiling** | Use for terrain |
+| **Collision** | Simplified shapes |
+
+### Layers
+
+| Layer | Content |
+|-------|---------|
+| Background | Non-interactive scenery |
+| Terrain | Walkable ground |
+| Props | Interactive objects |
+| Foreground | Parallax overlay |
+
+---
+
+## 3. 2D Physics
+
+### Collision Shapes
+
+| Shape | Use Case |
+|-------|----------|
+| Box | Rectangular objects |
+| Circle | Balls, rounded |
+| Capsule | Characters |
+| Polygon | Complex shapes |
+
+### Physics Considerations
+
+- Pixel-perfect vs physics-based
+- Fixed timestep for consistency
+- Layers for filtering
+
+---
+
+## 4. Camera Systems
+
+### Camera Types
+
+| Type | Use |
+|------|-----|
+| **Follow** | Track player |
+| **Look-ahead** | Anticipate movement |
+| **Multi-target** | Two-player |
+| **Room-based** | Metroidvania |
+
+### Screen Shake
+
+- Short duration (50-200ms)
+- Diminishing intensity
+- Use sparingly
+
+---
+
+## 5. Genre Patterns
+
+### Platformer
+
+- Coyote time (leniency after edge)
+- Jump buffering
+- Variable jump height
+
+### Top-down
+
+- 8-directional or free movement
+- Aim-based or auto-aim
+- Consider rotation or not
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Separate textures | Use atlases |
+| Complex collision shapes | Simplified collision |
+| Jittery camera | Smooth following |
+| Pixel-perfect on physics | Choose one approach |
+
+---
+
+> **Remember:** 2D is about clarity. Every pixel should communicate.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
+
+## 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.

package/skills/game-development/3d-games/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: 3d-games
+description: "3D game development principles. Rendering, shaders, physics, cameras."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# 3D Game Development
+
+> Principles for 3D game systems.
+
+---
+
+## 1. Rendering Pipeline
+
+### Stages
+
+```
+1. Vertex Processing → Transform geometry
+2. Rasterization → Convert to pixels
+3. Fragment Processing → Color pixels
+4. Output → To screen
+```
+
+### Optimization Principles
+
+| Technique | Purpose |
+|-----------|---------|
+| **Frustum culling** | Don't render off-screen |
+| **Occlusion culling** | Don't render hidden |
+| **LOD** | Less detail at distance |
+| **Batching** | Combine draw calls |
+
+---
+
+## 2. Shader Principles
+
+### Shader Types
+
+| Type | Purpose |
+|------|---------|
+| **Vertex** | Position, normals |
+| **Fragment/Pixel** | Color, lighting |
+| **Compute** | General computation |
+
+### When to Write Custom Shaders
+
+- Special effects (water, fire, portals)
+- Stylized rendering (toon, sketch)
+- Performance optimization
+- Unique visual identity
+
+---
+
+## 3. 3D Physics
+
+### Collision Shapes
+
+| Shape | Use Case |
+|-------|----------|
+| **Box** | Buildings, crates |
+| **Sphere** | Balls, quick checks |
+| **Capsule** | Characters |
+| **Mesh** | Terrain (expensive) |
+
+### Principles
+
+- Simple colliders, complex visuals
+- Layer-based filtering
+- Raycasting for line-of-sight
+
+---
+
+## 4. Camera Systems
+
+### Camera Types
+
+| Type | Use |
+|------|-----|
+| **Third-person** | Action, adventure |
+| **First-person** | Immersive, FPS |
+| **Isometric** | Strategy, RPG |
+| **Orbital** | Inspection, editors |
+
+### Camera Feel
+
+- Smooth following (lerp)
+- Collision avoidance
+- Look-ahead for movement
+- FOV changes for speed
+
+---
+
+## 5. Lighting
+
+### Light Types
+
+| Type | Use |
+|------|-----|
+| **Directional** | Sun, moon |
+| **Point** | Lamps, torches |
+| **Spot** | Flashlight, stage |
+| **Ambient** | Base illumination |
+
+### Performance Consideration
+
+- Real-time shadows are expensive
+- Bake when possible
+- Shadow cascades for large worlds
+
+---
+
+## 6. Level of Detail (LOD)
+
+### LOD Strategy
+
+| Distance | Model |
+|----------|-------|
+| Near | Full detail |
+| Medium | 50% triangles |
+| Far | 25% or billboard |
+
+---
+
+## 7. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Mesh colliders everywhere | Simple shapes |
+| Real-time shadows on mobile | Baked or blob shadows |
+| One LOD for all distances | Distance-based LOD |
+| Unoptimized shaders | Profile and simplify |
+
+---
+
+> **Remember:** 3D is about illusion. Create the impression of detail, not the detail itself.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
+
+## 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.

package/skills/game-development/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: game-development
+description: "Game development orchestrator. Routes to platform-specific skills based on project needs."
+version: 1.0.0
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Game Development
+
+> **Orchestrator skill** that provides core principles and routes 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.
+
+---
+
+## 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` |
+
+---
+
+## 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:**
+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)
+
+---
+
+### 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 |
+
+---
+
+## 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 |
+
+---
+
+## 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.
+
+## 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.

package/skills/game-development/game-art/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: game-art
+description: "Game art principles. Visual style selection, asset pipeline, animation workflow."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Game Art Principles
+
+> Visual design thinking for games - style selection, asset pipelines, and art direction.
+
+---
+
+## 1. Art Style Selection
+
+### Decision Tree
+
+```
+What feeling should the game evoke?
+│
+├── Nostalgic / Retro
+│   ├── Limited palette? → Pixel Art
+│   └── Hand-drawn feel? → Vector / Flash style
+│
+├── Realistic / Immersive
+│   ├── High budget? → PBR 3D
+│   └── Stylized realism? → Hand-painted textures
+│
+├── Approachable / Casual
+│   ├── Clean shapes? → Flat / Minimalist
+│   └── Soft feel? → Gradient / Soft shadows
+│
+└── Unique / Experimental
+    └── Define custom style guide
+```
+
+### Style Comparison Matrix
+
+| Style | Production Speed | Skill Floor | Scalability | Best For |
+|-------|------------------|-------------|-------------|----------|
+| **Pixel Art** | Medium | Medium | Hard to hire | Indie, retro |
+| **Vector/Flat** | Fast | Low | Easy | Mobile, casual |
+| **Hand-painted** | Slow | High | Medium | Fantasy, stylized |
+| **PBR 3D** | Slow | High | AAA pipeline | Realistic games |
+| **Low-poly** | Fast | Medium | Easy | Indie 3D |
+| **Cel-shaded** | Medium | Medium | Medium | Anime, cartoon |
+
+---
+
+## 2. Asset Pipeline Decisions
+
+### 2D Pipeline
+
+| Phase | Tool Options | Output |
+|-------|--------------|--------|
+| **Concept** | Paper, Procreate, Photoshop | Reference sheet |
+| **Creation** | Aseprite, Photoshop, Krita | Individual sprites |
+| **Atlas** | TexturePacker, Aseprite | Spritesheet |
+| **Animation** | Spine, DragonBones, Frame-by-frame | Animation data |
+| **Integration** | Engine import | Game-ready assets |
+
+### 3D Pipeline
+
+| Phase | Tool Options | Output |
+|-------|--------------|--------|
+| **Concept** | 2D art, Blockout | Reference |
+| **Modeling** | Blender, Maya, 3ds Max | High-poly mesh |
+| **Retopology** | Blender, ZBrush | Game-ready mesh |
+| **UV/Texturing** | Substance Painter, Blender | Texture maps |
+| **Rigging** | Blender, Maya | Skeletal rig |
+| **Animation** | Blender, Maya, Mixamo | Animation clips |
+| **Export** | FBX, glTF | Engine-ready |
+
+---
+
+## 3. Color Theory Decisions
+
+### Palette Selection
+
+| Goal | Strategy | Example |
+|------|----------|---------|
+| **Harmony** | Complementary or analogous | Nature games |
+| **Contrast** | High saturation differences | Action games |
+| **Mood** | Warm/cool temperature | Horror, cozy |
+| **Readability** | Value contrast over hue | Gameplay clarity |
+
+### Color Principles
+
+- **Hierarchy:** Important elements should pop
+- **Consistency:** Same object = same color family
+- **Context:** Colors read differently on backgrounds
+- **Accessibility:** Don't rely only on color
+
+---
+
+## 4. Animation Principles
+
+### The 12 Principles (Applied to Games)
+
+| Principle | Game Application |
+|-----------|------------------|
+| **Squash & Stretch** | Jump arcs, impacts |
+| **Anticipation** | Wind-up before attack |
+| **Staging** | Clear silhouettes |
+| **Follow-through** | Hair, capes after movement |
+| **Slow in/out** | Easing on transitions |
+| **Arcs** | Natural movement paths |
+| **Secondary Action** | Breathing, blinking |
+| **Timing** | Frame count = weight/speed |
+| **Exaggeration** | Readable from distance |
+| **Appeal** | Memorable design |
+
+### Frame Count Guidelines
+
+| Action Type | Typical Frames | Feel |
+|-------------|----------------|------|
+| Idle breathing | 4-8 | Subtle |
+| Walk cycle | 6-12 | Smooth |
+| Run cycle | 4-8 | Energetic |
+| Attack | 3-6 | Snappy |
+| Death | 8-16 | Dramatic |
+
+---
+
+## 5. Resolution & Scale Decisions
+
+### 2D Resolution by Platform
+
+| Platform | Base Resolution | Sprite Scale |
+|----------|-----------------|--------------|
+| Mobile | 1080p | 64-128px characters |
+| Desktop | 1080p-4K | 128-256px characters |
+| Pixel art | 320x180 to 640x360 | 16-32px characters |
+
+### Consistency Rule
+
+Choose a base unit and stick to it:
+- Pixel art: Work at 1x, scale up (never down)
+- HD art: Define DPI, maintain ratio
+- 3D: 1 unit = 1 meter (industry standard)
+
+---
+
+## 6. Asset Organization
+
+### Naming Convention
+
+```
+[type]_[object]_[variant]_[state].[ext]
+
+Examples:
+spr_player_idle_01.png
+tex_stone_wall_normal.png
+mesh_tree_oak_lod2.fbx
+```
+
+### Folder Structure Principle
+
+```
+assets/
+├── characters/
+│   ├── player/
+│   └── enemies/
+├── environment/
+│   ├── props/
+│   └── tiles/
+├── ui/
+├── effects/
+└── audio/
+```
+
+---
+
+## 7. Anti-Patterns
+
+| Don't | Do |
+|-------|-----|
+| Mix art styles randomly | Define and follow style guide |
+| Work at final resolution only | Create at source resolution |
+| Ignore silhouette readability | Test at gameplay distance |
+| Over-detail background | Focus detail on player area |
+| Skip color testing | Test on target display |
+
+---
+
+> **Remember:** Art serves gameplay. If it doesn't help the player, it's decoration.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
+
+## 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.