@heyai-rules/pilo-masterkit 1.2.2 → 2.1.0

package/.agent/skills/game-development/mobile-games/SKILL.md

@@ -1,108 +1,108 @@
----
-name: mobile-games
-description: Mobile game development principles. Touch input, battery, performance, app stores.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# 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.
+---
+name: mobile-games
+description: Mobile game development principles. Touch input, battery, performance, app stores.
+allowed-tools: Read, Write, Edit, Glob, Grep
+---
+
+# 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.

package/.agent/skills/game-development/multiplayer/SKILL.md

@@ -1,132 +1,132 @@
----
-name: multiplayer
-description: Multiplayer game development principles. Architecture, networking, synchronization.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# 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.
+---
+name: multiplayer
+description: Multiplayer game development principles. Architecture, networking, synchronization.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+---
+
+# 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.