@mclawnet/agent 0.6.19 → 0.6.21

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

@@ -0,0 +1,200 @@
+---
+name: game-audio
+description: "Game audio principles. Sound design, music integration, adaptive audio systems."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Game Audio Principles
+
+> Sound design and music integration for immersive game experiences.
+
+---
+
+## 1. Audio Category System
+
+### Category Definitions
+
+| Category | Behavior | Examples |
+|----------|----------|----------|
+| **Music** | Looping, crossfade, ducking | BGM, combat music |
+| **SFX** | One-shot, 3D positioned | Footsteps, impacts |
+| **Ambient** | Looping, background layer | Wind, crowd, forest |
+| **UI** | Immediate, non-3D | Button clicks, notifications |
+| **Voice** | Priority, ducking trigger | Dialogue, announcer |
+
+### Priority Hierarchy
+
+```
+When sounds compete for channels:
+
+1. Voice (highest - always audible)
+2. Player SFX (feedback critical)
+3. Enemy SFX (gameplay important)
+4. Music (mood, but duckable)
+5. Ambient (lowest - can drop)
+```
+
+---
+
+## 2. Sound Design Decisions
+
+### SFX Creation Approach
+
+| Approach | When to Use | Trade-offs |
+|----------|-------------|------------|
+| **Recording** | Realistic needs | High quality, time intensive |
+| **Synthesis** | Sci-fi, retro, UI | Unique, requires skill |
+| **Library samples** | Fast production | Common sounds, licensing |
+| **Layering** | Complex sounds | Best results, more work |
+
+### Layering Structure
+
+| Layer | Purpose | Example: Gunshot |
+|-------|---------|------------------|
+| **Attack** | Initial transient | Click, snap |
+| **Body** | Main character | Boom, blast |
+| **Tail** | Decay, room | Reverb, echo |
+| **Sweetener** | Special sauce | Shell casing, mechanical |
+
+---
+
+## 3. Music Integration
+
+### Music State System
+
+```
+Game State → Music Response
+│
+├── Menu → Calm, loopable theme
+├── Exploration → Ambient, atmospheric
+├── Combat detected → Transition to tension
+├── Combat engaged → Full battle music
+├── Victory → Stinger + calm transition
+├── Defeat → Somber stinger
+└── Boss → Unique, multi-phase track
+```
+
+### Transition Techniques
+
+| Technique | Use When | Feel |
+|-----------|----------|------|
+| **Crossfade** | Smooth mood shift | Gradual |
+| **Stinger** | Immediate event | Dramatic |
+| **Stem mixing** | Dynamic intensity | Seamless |
+| **Beat-synced** | Rhythmic gameplay | Musical |
+| **Queue point** | Next natural break | Clean |
+
+---
+
+## 4. Adaptive Audio Decisions
+
+### Intensity Parameters
+
+| Parameter | Affects | Example |
+|-----------|---------|---------|
+| **Threat level** | Music intensity | Enemy count |
+| **Health** | Filter, reverb | Low health = muffled |
+| **Speed** | Tempo, energy | Racing speed |
+| **Environment** | Reverb, EQ | Cave vs outdoor |
+| **Time of day** | Mood, volume | Night = quieter |
+
+### Vertical vs Horizontal
+
+| System | What Changes | Best For |
+|--------|--------------|----------|
+| **Vertical (layers)** | Add/remove instrument layers | Intensity scaling |
+| **Horizontal (segments)** | Different music sections | State changes |
+| **Combined** | Both | AAA adaptive scores |
+
+---
+
+## 5. 3D Audio Decisions
+
+### Spatialization
+
+| Element | 3D Positioned? | Reason |
+|---------|----------------|--------|
+| Player footsteps | No (or subtle) | Always audible |
+| Enemy footsteps | Yes | Directional awareness |
+| Gunfire | Yes | Combat awareness |
+| Music | No | Mood, non-diegetic |
+| Ambient zone | Yes (area) | Environmental |
+| UI sounds | No | Interface feedback |
+
+### Distance Behavior
+
+| Distance | Sound Behavior |
+|----------|----------------|
+| **Near** | Full volume, full frequency |
+| **Medium** | Volume falloff, high-freq rolloff |
+| **Far** | Low volume, low-pass filter |
+| **Max** | Silent or ambient hint |
+
+---
+
+## 6. Platform Considerations
+
+### Format Selection
+
+| Platform | Recommended Format | Reason |
+|----------|-------------------|--------|
+| PC | OGG Vorbis, WAV | Quality, no licensing |
+| Console | Platform-specific | Certification |
+| Mobile | MP3, AAC | Size, compatibility |
+| Web | WebM/Opus, MP3 fallback | Browser support |
+
+### Memory Budget
+
+| Game Type | Audio Budget | Strategy |
+|-----------|--------------|----------|
+| Mobile casual | 10-50 MB | Compressed, fewer variants |
+| PC indie | 100-500 MB | Quality focus |
+| AAA | 1+ GB | Full quality, many variants |
+
+---
+
+## 7. Mix Hierarchy
+
+### Volume Balance Reference
+
+| Category | Relative Level | Notes |
+|----------|----------------|-------|
+| **Voice** | 0 dB (reference) | Always clear |
+| **Player SFX** | -3 to -6 dB | Prominent but not harsh |
+| **Music** | -6 to -12 dB | Foundation, ducks for voice |
+| **Enemy SFX** | -6 to -9 dB | Important but not dominant |
+| **Ambient** | -12 to -18 dB | Subtle background |
+
+### Ducking Rules
+
+| When | Duck What | Amount |
+|------|-----------|--------|
+| Voice plays | Music, Ambient | -6 to -9 dB |
+| Explosion | All except explosion | Brief duck |
+| Menu open | Gameplay audio | -3 to -6 dB |
+
+---
+
+## 8. Anti-Patterns
+
+| Don't | Do |
+|-------|-----|
+| Play same sound repeatedly | Use variations (3-5 per sound) |
+| Max volume everything | Use proper mix hierarchy |
+| Ignore silence | Silence creates contrast |
+| One music track loops forever | Provide variety, transitions |
+| Skip audio in prototype | Placeholder audio matters |
+
+---
+
+> **Remember:** 50% of the game experience is audio. A muted game loses half its soul.
+
+## 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/game-design/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: game-design
+description: "Game design principles. GDD structure, balancing, player psychology, progression."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Game Design Principles
+
+> Design thinking for engaging games.
+
+---
+
+## 1. Core Loop Design
+
+### The 30-Second Test
+
+```
+Every game needs a fun 30-second loop:
+1. ACTION → Player does something
+2. FEEDBACK → Game responds
+3. REWARD → Player feels good
+4. REPEAT
+```
+
+### Loop Examples
+
+| Genre | Core Loop |
+|-------|-----------|
+| Platformer | Run → Jump → Land → Collect |
+| Shooter | Aim → Shoot → Kill → Loot |
+| Puzzle | Observe → Think → Solve → Advance |
+| RPG | Explore → Fight → Level → Gear |
+
+---
+
+## 2. Game Design Document (GDD)
+
+### Essential Sections
+
+| Section | Content |
+|---------|---------|
+| **Pitch** | One-sentence description |
+| **Core Loop** | 30-second gameplay |
+| **Mechanics** | How systems work |
+| **Progression** | How player advances |
+| **Art Style** | Visual direction |
+| **Audio** | Sound direction |
+
+### Principles
+
+- Keep it living (update regularly)
+- Visuals help communicate
+- Less is more (start small)
+
+---
+
+## 3. Player Psychology
+
+### Motivation Types
+
+| Type | Driven By |
+|------|-----------|
+| **Achiever** | Goals, completion |
+| **Explorer** | Discovery, secrets |
+| **Socializer** | Interaction, community |
+| **Killer** | Competition, dominance |
+
+### Reward Schedules
+
+| Schedule | Effect | Use |
+|----------|--------|-----|
+| **Fixed** | Predictable | Milestone rewards |
+| **Variable** | Addictive | Loot drops |
+| **Ratio** | Effort-based | Grind games |
+
+---
+
+## 4. Difficulty Balancing
+
+### Flow State
+
+```
+Too Hard → Frustration → Quit
+Too Easy → Boredom → Quit
+Just Right → Flow → Engagement
+```
+
+### Balancing Strategies
+
+| Strategy | How |
+|----------|-----|
+| **Dynamic** | Adjust to player skill |
+| **Selection** | Let player choose |
+| **Accessibility** | Options for all |
+
+---
+
+## 5. Progression Design
+
+### Progression Types
+
+| Type | Example |
+|------|---------|
+| **Skill** | Player gets better |
+| **Power** | Character gets stronger |
+| **Content** | New areas unlock |
+| **Story** | Narrative advances |
+
+### Pacing Principles
+
+- Early wins (hook quickly)
+- Gradually increase challenge
+- Rest beats between intensity
+- Meaningful choices
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Design in isolation | Playtest constantly |
+| Polish before fun | Prototype first |
+| Force one way to play | Allow player expression |
+| Punish excessively | Reward progress |
+
+---
+
+> **Remember:** Fun is discovered through iteration, not designed on paper.
+
+## 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/mobile-games/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: mobile-games
+description: "Mobile game development principles. Touch input, battery, performance, app stores."
+risk: safe
+source: community
+date_added: "2026-02-27"
+---
+
+# Mobile Game Development
+
+> Platform constraints and optimization principles.
+
+---
+
+## 1. Platform Considerations
+
+### Key Constraints
+
+| Constraint | Strategy |
+|------------|----------|
+| **Touch input** | Large hit areas, gestures |
+| **Battery** | Limit CPU/GPU usage |
+| **Thermal** | Throttle when hot |
+| **Screen size** | Responsive UI |
+| **Interruptions** | Pause on background |
+
+---
+
+## 2. Touch Input Principles
+
+### Touch vs Controller
+
+| Touch | Desktop/Console |
+|-------|-----------------|
+| Imprecise | Precise |
+| Occludes screen | No occlusion |
+| Limited buttons | Many buttons |
+| Gestures available | Buttons/sticks |
+
+### Best Practices
+
+- Minimum touch target: 44x44 points
+- Visual feedback on touch
+- Avoid precise timing requirements
+- Support both portrait and landscape
+
+---
+
+## 3. Performance Targets
+
+### Thermal Management
+
+| Action | Trigger |
+|--------|---------|
+| Reduce quality | Device warm |
+| Limit FPS | Device hot |
+| Pause effects | Critical temp |
+
+### Battery Optimization
+
+- 30 FPS often sufficient
+- Sleep when paused
+- Minimize GPS/network
+- Dark mode saves OLED battery
+
+---
+
+## 4. App Store Requirements
+
+### iOS (App Store)
+
+| Requirement | Note |
+|-------------|------|
+| Privacy labels | Required |
+| Account deletion | If account creation exists |
+| Screenshots | For all device sizes |
+
+### Android (Google Play)
+
+| Requirement | Note |
+|-------------|------|
+| Target API | Current year's SDK |
+| 64-bit | Required |
+| App bundles | Recommended |
+
+---
+
+## 5. Monetization Models
+
+| Model | Best For |
+|-------|----------|
+| **Premium** | Quality games, loyal audience |
+| **Free + IAP** | Casual, progression-based |
+| **Ads** | Hyper-casual, high volume |
+| **Subscription** | Content updates, multiplayer |
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Desktop controls on mobile | Design for touch |
+| Ignore battery drain | Monitor thermals |
+| Force landscape | Support player preference |
+| Always-on network | Cache and sync |
+
+---
+
+> **Remember:** Mobile is the most constrained platform. Respect battery and attention.
+
+## 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/multiplayer/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: multiplayer
+description: "Multiplayer game development principles. Architecture, networking, synchronization."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Multiplayer Game Development
+
+> Networking architecture and synchronization principles.
+
+---
+
+## 1. Architecture Selection
+
+### Decision Tree
+
+```
+What type of multiplayer?
+│
+├── Competitive / Real-time
+│   └── Dedicated Server (authoritative)
+│
+├── Cooperative / Casual
+│   └── Host-based (one player is server)
+│
+├── Turn-based
+│   └── Client-server (simple)
+│
+└── Massive (MMO)
+    └── Distributed servers
+```
+
+### Comparison
+
+| Architecture | Latency | Cost | Security |
+|--------------|---------|------|----------|
+| **Dedicated** | Low | High | Strong |
+| **P2P** | Variable | Low | Weak |
+| **Host-based** | Medium | Low | Medium |
+
+---
+
+## 2. Synchronization Principles
+
+### State vs Input
+
+| Approach | Sync What | Best For |
+|----------|-----------|----------|
+| **State Sync** | Game state | Simple, few objects |
+| **Input Sync** | Player inputs | Action games |
+| **Hybrid** | Both | Most games |
+
+### Lag Compensation
+
+| Technique | Purpose |
+|-----------|---------|
+| **Prediction** | Client predicts server |
+| **Interpolation** | Smooth remote players |
+| **Reconciliation** | Fix mispredictions |
+| **Lag compensation** | Rewind for hit detection |
+
+---
+
+## 3. Network Optimization
+
+### Bandwidth Reduction
+
+| Technique | Savings |
+|-----------|---------|
+| **Delta compression** | Send only changes |
+| **Quantization** | Reduce precision |
+| **Priority** | Important data first |
+| **Area of interest** | Only nearby entities |
+
+### Update Rates
+
+| Type | Rate |
+|------|------|
+| Position | 20-60 Hz |
+| Health | On change |
+| Inventory | On change |
+| Chat | On send |
+
+---
+
+## 4. Security Principles
+
+### Server Authority
+
+```
+Client: "I hit the enemy"
+Server: Validate → did projectile actually hit?
+         → was player in valid state?
+         → was timing possible?
+```
+
+### Anti-Cheat
+
+| Cheat | Prevention |
+|-------|------------|
+| Speed hack | Server validates movement |
+| Aimbot | Server validates sight line |
+| Item dupe | Server owns inventory |
+| Wall hack | Don't send hidden data |
+
+---
+
+## 5. Matchmaking
+
+### Considerations
+
+| Factor | Impact |
+|--------|--------|
+| **Skill** | Fair matches |
+| **Latency** | Playable connection |
+| **Wait time** | Player patience |
+| **Party size** | Group play |
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Trust the client | Server is authority |
+| Send everything | Send only necessary |
+| Ignore latency | Design for 100-200ms |
+| Sync exact positions | Interpolate/predict |
+
+---
+
+> **Remember:** Never trust the client. The server is the source of truth.
+
+## 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.