cp-toolkit 2.2.3 → 2.2.4

package/templates/skills/optional/game-development/pc-games/SKILL.md

@@ -1,144 +1,146 @@
----
-name: pc-games
-description: PC and console game development principles. Engine selection, platform features, optimization strategies.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# PC/Console Game Development
-
-> Engine selection and platform-specific principles.
-
----
-
-## 1. Engine Selection
-
-### Decision Tree
-
-```
-What are you building?
-│
-├── 2D Game
-│   ├── Open source important? → Godot
-│   └── Large team/assets? → Unity
-│
-├── 3D Game
-│   ├── AAA visual quality? → Unreal
-│   ├── Cross-platform priority? → Unity
-│   └── Indie/open source? → Godot 4
-│
-└── Specific Needs
-    ├── DOTS performance? → Unity
-    ├── Nanite/Lumen? → Unreal
-    └── Lightweight? → Godot
-```
-
-### Comparison
-
-| Factor | Unity 6 | Godot 4 | Unreal 5 |
-|--------|---------|---------|----------|
-| 2D | Good | Excellent | Limited |
-| 3D | Good | Good | Excellent |
-| Learning | Medium | Easy | Hard |
-| Cost | Revenue share | Free | 5% after $1M |
-| Team | Any | Solo-Medium | Medium-Large |
-
----
-
-## 2. Platform Features
-
-### Steam Integration
-
-| Feature | Purpose |
-|---------|---------|
-| Achievements | Player goals |
-| Cloud Saves | Cross-device progress |
-| Leaderboards | Competition |
-| Workshop | User mods |
-| Rich Presence | Show in-game status |
-
-### Console Requirements
-
-| Platform | Certification |
-|----------|--------------|
-| PlayStation | TRC compliance |
-| Xbox | XR compliance |
-| Nintendo | Lotcheck |
-
----
-
-## 3. Controller Support
-
-### Input Abstraction
-
-```
-Map ACTIONS, not buttons:
-- "confirm" → A (Xbox), Cross (PS), B (Nintendo)
-- "cancel" → B (Xbox), Circle (PS), A (Nintendo)
-```
-
-### Haptic Feedback
-
-| Intensity | Use |
-|-----------|-----|
-| Light | UI feedback |
-| Medium | Impacts |
-| Heavy | Major events |
-
----
-
-## 4. Performance Optimization
-
-### Profiling First
-
-| Engine | Tool |
-|--------|------|
-| Unity | Profiler Window |
-| Godot | Debugger → Profiler |
-| Unreal | Unreal Insights |
-
-### Common Bottlenecks
-
-| Bottleneck | Solution |
-|------------|----------|
-| Draw calls | Batching, atlases |
-| GC spikes | Object pooling |
-| Physics | Simpler colliders |
-| Shaders | LOD shaders |
-
----
-
-## 5. Engine-Specific Principles
-
-### Unity 6
-
-- DOTS for performance-critical systems
-- Burst compiler for hot paths
-- Addressables for asset streaming
-
-### Godot 4
-
-- GDScript for rapid iteration
-- C# for complex logic
-- Signals for decoupling
-
-### Unreal 5
-
-- Blueprint for designers
-- C++ for performance
-- Nanite for high-poly environments
-- Lumen for dynamic lighting
-
----
-
-## 6. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Choose engine by hype | Choose by project needs |
-| Ignore platform guidelines | Study certification requirements |
-| Hardcode input buttons | Abstract to actions |
-| Skip profiling | Profile early and often |
-
----
-
-> **Remember:** Engine is a tool. Master the principles, then adapt to any engine.
+---
+name: pc-games
+description: PC and console game development principles. Engine selection, platform
+  features, optimization strategies.
+allowed-tools: Read, Write, Edit, Glob, Grep
+version: '1.0'
+---
+
+# PC/Console Game Development
+
+> Engine selection and platform-specific principles.
+
+---
+
+## 1. Engine Selection
+
+### Decision Tree
+
+```
+What are you building?
+│
+├── 2D Game
+│   ├── Open source important? → Godot
+│   └── Large team/assets? → Unity
+│
+├── 3D Game
+│   ├── AAA visual quality? → Unreal
+│   ├── Cross-platform priority? → Unity
+│   └── Indie/open source? → Godot 4
+│
+└── Specific Needs
+    ├── DOTS performance? → Unity
+    ├── Nanite/Lumen? → Unreal
+    └── Lightweight? → Godot
+```
+
+### Comparison
+
+| Factor | Unity 6 | Godot 4 | Unreal 5 |
+|--------|---------|---------|----------|
+| 2D | Good | Excellent | Limited |
+| 3D | Good | Good | Excellent |
+| Learning | Medium | Easy | Hard |
+| Cost | Revenue share | Free | 5% after $1M |
+| Team | Any | Solo-Medium | Medium-Large |
+
+---
+
+## 2. Platform Features
+
+### Steam Integration
+
+| Feature | Purpose |
+|---------|---------|
+| Achievements | Player goals |
+| Cloud Saves | Cross-device progress |
+| Leaderboards | Competition |
+| Workshop | User mods |
+| Rich Presence | Show in-game status |
+
+### Console Requirements
+
+| Platform | Certification |
+|----------|--------------|
+| PlayStation | TRC compliance |
+| Xbox | XR compliance |
+| Nintendo | Lotcheck |
+
+---
+
+## 3. Controller Support
+
+### Input Abstraction
+
+```
+Map ACTIONS, not buttons:
+- "confirm" → A (Xbox), Cross (PS), B (Nintendo)
+- "cancel" → B (Xbox), Circle (PS), A (Nintendo)
+```
+
+### Haptic Feedback
+
+| Intensity | Use |
+|-----------|-----|
+| Light | UI feedback |
+| Medium | Impacts |
+| Heavy | Major events |
+
+---
+
+## 4. Performance Optimization
+
+### Profiling First
+
+| Engine | Tool |
+|--------|------|
+| Unity | Profiler Window |
+| Godot | Debugger → Profiler |
+| Unreal | Unreal Insights |
+
+### Common Bottlenecks
+
+| Bottleneck | Solution |
+|------------|----------|
+| Draw calls | Batching, atlases |
+| GC spikes | Object pooling |
+| Physics | Simpler colliders |
+| Shaders | LOD shaders |
+
+---
+
+## 5. Engine-Specific Principles
+
+### Unity 6
+
+- DOTS for performance-critical systems
+- Burst compiler for hot paths
+- Addressables for asset streaming
+
+### Godot 4
+
+- GDScript for rapid iteration
+- C# for complex logic
+- Signals for decoupling
+
+### Unreal 5
+
+- Blueprint for designers
+- C++ for performance
+- Nanite for high-poly environments
+- Lumen for dynamic lighting
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Choose engine by hype | Choose by project needs |
+| Ignore platform guidelines | Study certification requirements |
+| Hardcode input buttons | Abstract to actions |
+| Skip profiling | Profile early and often |
+
+---
+
+> **Remember:** Engine is a tool. Master the principles, then adapt to any engine.

package/templates/skills/optional/game-development/vr-ar/SKILL.md

@@ -1,123 +1,124 @@
----
-name: vr-ar
-description: VR/AR development principles. Comfort, interaction, performance requirements.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# VR/AR Development
-
-> Immersive experience principles.
-
----
-
-## 1. Platform Selection
-
-### VR Platforms
-
-| Platform | Use Case |
-|----------|----------|
-| **Quest** | Standalone, wireless |
-| **PCVR** | High fidelity |
-| **PSVR** | Console market |
-| **WebXR** | Browser-based |
-
-### AR Platforms
-
-| Platform | Use Case |
-|----------|----------|
-| **ARKit** | iOS devices |
-| **ARCore** | Android devices |
-| **WebXR** | Browser AR |
-| **HoloLens** | Enterprise |
-
----
-
-## 2. Comfort Principles
-
-### Motion Sickness Prevention
-
-| Cause | Solution |
-|-------|----------|
-| **Locomotion** | Teleport, snap turn |
-| **Low FPS** | Maintain 90 FPS |
-| **Camera shake** | Avoid or minimize |
-| **Rapid acceleration** | Gradual movement |
-
-### Comfort Settings
-
-- Vignette during movement
-- Snap vs smooth turning
-- Seated vs standing modes
-- Height calibration
-
----
-
-## 3. Performance Requirements
-
-### Target Metrics
-
-| Platform | FPS | Resolution |
-|----------|-----|------------|
-| Quest 2 | 72-90 | 1832x1920 |
-| Quest 3 | 90-120 | 2064x2208 |
-| PCVR | 90 | 2160x2160+ |
-| PSVR2 | 90-120 | 2000x2040 |
-
-### Frame Budget
-
-- VR requires consistent frame times
-- Single dropped frame = visible judder
-- 90 FPS = 11.11ms budget
-
----
-
-## 4. Interaction Principles
-
-### Controller Interaction
-
-| Type | Use |
-|------|-----|
-| **Point + click** | UI, distant objects |
-| **Grab** | Manipulation |
-| **Gesture** | Magic, special actions |
-| **Physical** | Throwing, swinging |
-
-### Hand Tracking
-
-- More immersive but less precise
-- Good for: social, casual
-- Challenging for: action, precision
-
----
-
-## 5. Spatial Design
-
-### World Scale
-
-- 1 unit = 1 meter (critical)
-- Objects must feel right size
-- Test with real measurements
-
-### Depth Cues
-
-| Cue | Importance |
-|-----|------------|
-| Stereo | Primary depth |
-| Motion parallax | Secondary |
-| Shadows | Grounding |
-| Occlusion | Layering |
-
----
-
-## 6. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Move camera without player | Player controls camera |
-| Drop below 90 FPS | Maintain frame rate |
-| Use tiny UI text | Large, readable text |
-| Ignore arm length | Scale to player reach |
-
----
-
-> **Remember:** Comfort is not optional. Sick players don't play.
+---
+name: vr-ar
+description: VR/AR development principles. Comfort, interaction, performance requirements.
+allowed-tools: Read, Write, Edit, Glob, Grep
+version: '1.0'
+---
+
+# VR/AR Development
+
+> Immersive experience principles.
+
+---
+
+## 1. Platform Selection
+
+### VR Platforms
+
+| Platform | Use Case |
+|----------|----------|
+| **Quest** | Standalone, wireless |
+| **PCVR** | High fidelity |
+| **PSVR** | Console market |
+| **WebXR** | Browser-based |
+
+### AR Platforms
+
+| Platform | Use Case |
+|----------|----------|
+| **ARKit** | iOS devices |
+| **ARCore** | Android devices |
+| **WebXR** | Browser AR |
+| **HoloLens** | Enterprise |
+
+---
+
+## 2. Comfort Principles
+
+### Motion Sickness Prevention
+
+| Cause | Solution |
+|-------|----------|
+| **Locomotion** | Teleport, snap turn |
+| **Low FPS** | Maintain 90 FPS |
+| **Camera shake** | Avoid or minimize |
+| **Rapid acceleration** | Gradual movement |
+
+### Comfort Settings
+
+- Vignette during movement
+- Snap vs smooth turning
+- Seated vs standing modes
+- Height calibration
+
+---
+
+## 3. Performance Requirements
+
+### Target Metrics
+
+| Platform | FPS | Resolution |
+|----------|-----|------------|
+| Quest 2 | 72-90 | 1832x1920 |
+| Quest 3 | 90-120 | 2064x2208 |
+| PCVR | 90 | 2160x2160+ |
+| PSVR2 | 90-120 | 2000x2040 |
+
+### Frame Budget
+
+- VR requires consistent frame times
+- Single dropped frame = visible judder
+- 90 FPS = 11.11ms budget
+
+---
+
+## 4. Interaction Principles
+
+### Controller Interaction
+
+| Type | Use |
+|------|-----|
+| **Point + click** | UI, distant objects |
+| **Grab** | Manipulation |
+| **Gesture** | Magic, special actions |
+| **Physical** | Throwing, swinging |
+
+### Hand Tracking
+
+- More immersive but less precise
+- Good for: social, casual
+- Challenging for: action, precision
+
+---
+
+## 5. Spatial Design
+
+### World Scale
+
+- 1 unit = 1 meter (critical)
+- Objects must feel right size
+- Test with real measurements
+
+### Depth Cues
+
+| Cue | Importance |
+|-----|------------|
+| Stereo | Primary depth |
+| Motion parallax | Secondary |
+| Shadows | Grounding |
+| Occlusion | Layering |
+
+---
+
+## 6. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Move camera without player | Player controls camera |
+| Drop below 90 FPS | Maintain frame rate |
+| Use tiny UI text | Large, readable text |
+| Ignore arm length | Scale to player reach |
+
+---
+
+> **Remember:** Comfort is not optional. Sick players don't play.