tribunal-kit 2.4.6 → 3.1.0

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

@@ -1,129 +0,0 @@
----
-name: game-design
-description: Game design principles. GDD structure, balancing, player psychology, progression.
-allowed-tools: Read, Glob, Grep
----
-
-# 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.

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

@@ -1,108 +0,0 @@
----
-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 +0,0 @@
----
-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.

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

@@ -1,144 +0,0 @@
----
-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.

package/.agent/skills/game-development/vr-ar/SKILL.md

@@ -1,123 +0,0 @@
----
-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.