agent-skill-kit 3.9.135

package/.agent/workflows/game.md

@@ -0,0 +1,329 @@
+---
+description: Full-lifecycle game development — platform-specific engine routing, core loop architecture, asset pipeline optimization, multiplayer networking, and store-ready builds.
+skills: [game-development, perf-optimizer, idea-storm, problem-checker, smart-router, knowledge-compiler, context-engineering]
+agents: [orchestrator, assessor, recovery, critic, learner, project-planner, game-developer, backend-specialist, test-engineer]
+---
+
+# /game - Game Development
+
+$ARGUMENTS
+
+---
+
+## Purpose
+
+Orchestrate game development from concept to published game — routing to platform-specific engines, implementing core game loops, managing asset pipelines, and handling multiplayer networking. **Differs from `/build` (general web/mobile apps) by focusing on game-specific concerns: frame budgets, physics, ECS architecture, networking models, and store submission.** Uses `game-development` with `game-development` skill, coordinated by `orchestrator` for parallel art + audio + code pipelines.
+
+---
+
+## ?? Meta-Agents Integration
+
+| Phase | Agent | Action |
+| ----- | ----- | ------ |
+| **Pre-Flight** | `assessor` | Evaluate scope, risks, and knowledge-compiler patterns |
+| **Execution** | `orchestrator` | Coordinate parallel tasks (art, audio, code) |
+| **Safety** | `recovery` | Save checkpoint before major game logic changes |
+| **Conflict** | `critic` | Resolve design vs performance trade-offs |
+| **Post-Build** | `learner` | Log game patterns for reuse |
+
+```
+Flow:
+assessor.evaluate(scope, platform) ? recovery.save()
+       ?
+orchestrator.parallel(art, audio, code)
+       ? conflict
+critic.resolve(design_vs_perf)
+       ?
+verify ? learner.log(patterns)
+```
+
+---
+
+## Platform Routing
+
+| Target | Engine | Sub-Skill |
+|--------|--------|-----------|
+| Web | Phaser / PixiJS / Three.js | `game-development` (web) |
+| Mobile | Unity / Godot | `game-development` (mobile) |
+| PC | Unity / Godot / Unreal | `game-development` (PC) |
+| VR/AR | Unity XR / A-Frame | `game-development` (VR/AR) |
+
+| Dimension | Key Concerns |
+|-----------|-------------|
+| 2D | Sprite batching, atlas, tile maps |
+| 3D | LOD, occlusion culling, lighting |
+
+---
+
+## ?? MANDATORY: Game Development Protocol
+
+### Phase 1: Pre-flight & knowledge-compiler Context
+
+> **Rule 0.5-K:** knowledge-compiler pattern check.
+
+1. Read `.agent/skills/knowledge-compiler/patterns/` for past failures before proceeding.
+2. Trigger `recovery` agent to run Checkpoint (`git commit -m "chore(checkpoint): pre-game"`).
+
+### Phase 2: Requirements & Scope
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | $ARGUMENTS (game concept description) |
+| **OUTPUT** | Game design doc: platform, dimension, genre, multiplayer model, target FPS |
+| **AGENTS** | `project-planner`, `assessor` |
+| **SKILLS** | `game-development`, `idea-storm`, `context-engineering` |
+
+1. Ask critical questions:
+
+| Question | Options | Impact |
+|----------|---------|--------|
+| Platform? | Web / Mobile / PC / Console / VR-AR | Engine + build pipeline |
+| Dimension? | 2D / 2.5D / 3D | Rendering pipeline |
+| Genre? | Platformer / Puzzle / Shooter / RPG / Sandbox | Core mechanics |
+| Multiplayer? | Solo / Local co-op / Online PvP / MMO | Networking stack |
+| Target FPS? | 30 / 60 / 120 | Performance budget |
+
+2. `assessor` evaluates scope and platform risks
+3. Select engine and architecture pattern
+
+### Phase 3: Core Game Loop & Architecture
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Game design doc from Phase 2 |
+| **OUTPUT** | Game loop implementation, architecture scaffold |
+| **AGENTS** | `orchestrator`, `game-development` |
+| **SKILLS** | `game-development`, `smart-router` |
+
+1. Implement fixed timestep game loop:
+
+| Target | Budget/Frame | Breakdown |
+|--------|-------------|-----------|
+| **60 FPS** | 16.67ms | Input 1ms � Physics 3ms � AI 2ms � Logic 4ms � Render 5ms |
+| **30 FPS** | 33.33ms | Input 1ms � Physics 5ms � AI 5ms � Logic 10ms � Render 10ms |
+
+2. Select architecture pattern:
+
+| Pattern | Use When |
+|---------|----------|
+| **State Machine** | 3-5 discrete states (Idle?Run?Jump) |
+| **Object Pooling** | Frequent spawn/destroy (bullets, particles) |
+| **ECS** | Thousands of similar entities |
+| **Behavior Tree** | Complex AI decisions |
+
+3. Abstract input layer (keyboard ? gamepad ? touch)
+
+### Phase 4: Asset Pipeline & Audio
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Architecture scaffold from Phase 3 |
+| **OUTPUT** | Optimized assets in `assets/`, audio system |
+| **AGENTS** | `game-development` |
+| **SKILLS** | `game-development` |
+
+1. Set up asset directory structure and optimization targets:
+
+| Asset | Optimization | Target |
+|-------|-------------|--------|
+| Sprites | Texture atlasing | <4096�4096 per atlas |
+| 3D Models | LOD, mesh simplification | <10K tris (mobile) |
+| Audio SFX | Mono, 22kHz, OGG | <100KB per sound |
+| Shaders | GPU-efficient | Platform-appropriate |
+
+2. Audio system: pool sources (max 32), priority UI > Player > Enemies > Ambient
+
+### Phase 5: Multiplayer & Networking (if applicable)
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Multiplayer model from Phase 2 design doc |
+| **OUTPUT** | Networking layer, lobby system, anti-cheat |
+| **AGENTS** | `game-development`, `nodejs-pro` |
+| **SKILLS** | `game-development` |
+
+| Model | Use When | Complexity |
+|-------|----------|------------|
+| **Lock-step** | Turn-based, RTS | Low |
+| **Client-server** | FPS, action, MMO | High |
+| **Client prediction** | Fast-paced PvP | Very high |
+| **Relay (P2P)** | Co-op, casual | Medium |
+
+Networking checklist:
+- [ ] State serialization / delta compression
+- [ ] Client prediction + server reconciliation
+- [ ] Lobby + matchmaking
+- [ ] Anti-cheat (server-authoritative)
+- [ ] Graceful disconnect / reconnection
+
+### Phase 6: Build & Export
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Complete game from Phases 3-5 |
+| **OUTPUT** | Platform-specific builds, optimized bundles |
+| **AGENTS** | `game-development` |
+| **SKILLS** | `game-development`, `perf-optimizer` |
+
+| Platform | Build Tool | Distribution |
+|----------|-----------|-------------|
+| Web | Vite / esbuild | itch.io / Newgrounds |
+| Android | Gradle / Unity | Google Play |
+| iOS | Xcode / Unity | App Store |
+| Windows | Electron / Unity / Godot | Steam |
+
+Optimization: Tree shake ? Minify ? Compress assets ? Code split ? CDN
+
+### Phase 7: Testing & Verification
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Built game from Phase 6 |
+| **OUTPUT** | Test results: FPS, memory, platform compatibility |
+| **AGENTS** | `test-architect`, `learner` |
+| **SKILLS** | `game-development`, `perf-optimizer`, `problem-checker`, `knowledge-compiler` |
+
+Test checklist:
+- [ ] Maintains target FPS on lowest-spec device
+- [ ] No memory leaks after 10+ minutes
+- [ ] Works on all target platforms
+- [ ] Input responsive (<100ms lag)
+- [ ] Save/load works correctly
+- [ ] Multiplayer sync verified (if applicable)
+
+---
+
+## ? MANDATORY: Problem Verification Before Completion
+
+> **CRITICAL:** This check MUST be performed before any `notify_user` or task completion.
+
+### Check @[current_problems]
+
+```
+1. Read @[current_problems] from IDE
+2. If errors/warnings > 0:
+   a. Auto-fix: imports, types, lint errors
+   b. Re-check @[current_problems]
+   c. If still > 0 ? STOP ? Notify user
+3. If count = 0 ? Proceed to completion
+```
+
+### Auto-Fixable
+
+| Type | Fix |
+|------|-----|
+| Missing import | Add import statement |
+| Unused variable | Remove or prefix `_` |
+| Type mismatch | Fix type annotation |
+| Lint errors | Run eslint --fix |
+
+> **Rule:** Never mark complete with errors in `@[current_problems]`.
+
+---
+
+## ?? Rollback & Recovery
+
+If game loop, physics engine, or multiplayer netcode breaks functionality:
+1. Restore to pre-game checkpoint (`git checkout -- .` or `git stash pop`).
+2. Log architecture failure via `learner` meta-agent.
+3. Bring in `critic` to evaluate trade-offs before retrying implementation.
+
+---
+
+## Output Format
+
+```markdown
+## ?? Game Built: [Game Name]
+
+### Configuration
+
+| Setting | Value |
+|---------|-------|
+| Platform | Web (Phaser) |
+| Dimension | 2D |
+| Genre | Platformer |
+| Multiplayer | Solo |
+| Target FPS | 60 |
+
+### Components
+
+| Component | Status |
+|-----------|--------|
+| Game loop | ? |
+| Asset pipeline | ? |
+| Audio system | ? |
+| Input abstraction | ? |
+| Multiplayer | ? N/A |
+| Platform build | ? |
+
+### Performance
+
+| Metric | Target | Actual | Status |
+|--------|--------|--------|--------|
+| FPS | 60 | 62 | ? |
+| Memory | <256MB | 180MB | ? |
+| Load time | <3s | 2.1s | ? |
+
+### Next Steps
+
+- [ ] Playtest on target devices
+- [ ] Run `/optimize` for performance tuning
+- [ ] Run `/launch` to publish to store
+```
+
+---
+
+## Examples
+
+```
+/game 2D platformer for web browser with Phaser
+/game mobile puzzle game with Unity and Google Play submission
+/game 3D RPG with online multiplayer support
+/game retro arcade game with leaderboard
+/game multiplayer shooter with client prediction
+```
+
+---
+
+## Key Principles
+
+- **Profile before optimizing** — measure with profiler, don't guess bottlenecks
+- **Data-driven design** — levels, configs, and balancing in JSON, not hardcoded
+- **Abstract input** — map actions to inputs, support keyboard + gamepad + touch
+- **Object pooling** — never create/destroy in hot loops, pool everything
+- **Fixed timestep** — deterministic physics separate from render framerate
+
+---
+
+## ?? Workflow Chain
+
+**Skills Loaded (7):**
+
+- `game-development` - Core game development patterns and engine routing
+- `perf-optimizer` - Performance profiling and optimization
+- `idea-storm` - Requirements gathering and scope definition
+- `problem-checker` - IDE problem verification
+- `smart-router` - Request classifier and agent routing
+- `context-engineering` - Codebase parsing and context gathering
+- `knowledge-compiler` - Learning and logging game patterns
+
+```mermaid
+graph LR
+    A["/plan"] --> B["/game"]
+    B --> C["/validate"]
+    style B fill:#10b981
+```
+
+| After /game | Run | Purpose |
+|------------|-----|---------|
+| Need testing | `/validate` | Run game test suite |
+| Performance tuning | `/optimize` | Profile and fix bottlenecks |
+| UI polish | `/studio` | Design game UI/HUD |
+| Ready to ship | `/launch` | Publish to store |
+
+**Handoff to /validate:**
+
+```markdown
+?? Game built! Platform: [platform], FPS: [fps], Components: [count].
+Run `/validate` to test or `/optimize` for performance tuning.
+```

package/.agent/workflows/inspect.md

@@ -0,0 +1,276 @@
+---
+description: Defense-in-depth code review — four-layer validation across build, tests, security, and logic to eliminate false completion claims with evidence-based verification.
+chain: security-audit
+skills: [security-scanner, code-review, problem-checker, context-engineering, knowledge-compiler]
+agents: [orchestrator, assessor, recovery, learner, security-auditor]
+---
+
+# /inspect - Defense-in-Depth Review
+
+$ARGUMENTS
+
+---
+
+## Purpose
+
+Systematic code review with multi-layer validation — preventing false completion claims through evidence-based verification across build, tests, security, and logic layers. **Differs from `/validate` (runs tests) and `/diagnose` (finds bugs) by performing comprehensive quality audit across all dimensions before deployment.** Uses `security-scanner` with `security-scanner` for vulnerability scanning and `code-review` for quality validation.
+
+---
+
+## Sub-Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/inspect` | Review current changes |
+| `/inspect [file-path]` | Review specific file |
+| `/inspect --pr` | PR-style review |
+| `/inspect --security` | Security-focused review |
+
+---
+
+## ?? Meta-Agents Integration
+
+| Phase | Agent | Action |
+| ----- | ----- | ------ |
+| **Pre-Flight** | `assessor` | Evaluate review scope, risks and knowledge-compiler patterns |
+| **Execution** | `orchestrator` | Coordinate 4-layer validation sequence |
+| **Safety** | `recovery` | Save workspace checkpoint before validation |
+| **Post-Review** | `learner` | Log review patterns for future reference |
+
+```
+Flow:
+assessor.evaluate(scope) ? 4-layer validation
+       ?
+build ? tests ? security ? logic
+       ?
+report ? learner.log(patterns)
+```
+
+---
+
+## ?? MANDATORY: 4-Layer Validation Protocol
+
+### Phase 1: Pre-flight & knowledge-compiler Context
+
+> **Rule 0.5-K:** knowledge-compiler pattern check.
+
+1. Read `.agent/skills/knowledge-compiler/patterns/` for past failures before proceeding.
+2. Trigger `recovery` agent to run Checkpoint (`git commit -m "chore(checkpoint): pre-inspect"`).
+
+### Phase 2: Build Verification
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | $ARGUMENTS (target files/scope or current changes) |
+| **OUTPUT** | Build result: compilation status, lint errors, warnings |
+| **AGENTS** | `orchestrator`, `assessor` |
+| **SKILLS** | `code-review`, `context-engineering` |
+
+// turbo — telemetry: phase-2-build
+```bash
+npx cross-env OTEL_SERVICE_NAME="workflow:inspect" TRACE_ID="$TRACE_ID" npm run build
+```
+
+| Check | Required |
+|-------|----------|
+| TypeScript compiles | ? |
+| No lint errors | ? |
+| No warnings | ?? |
+
+### Phase 3: Test Verification
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Build result from Phase 2 |
+| **OUTPUT** | Test result: pass/fail count, coverage, skipped tests |
+| **AGENTS** | `orchestrator` |
+| **SKILLS** | `code-review` |
+
+// turbo — telemetry: phase-3-test
+```bash
+npx cross-env OTEL_SERVICE_NAME="workflow:inspect" TRACE_ID="$TRACE_ID" npm test
+```
+
+| Check | Required |
+|-------|----------|
+| All tests pass | ? |
+| No skipped tests | ?? |
+| Coverage maintained | ?? |
+
+### Phase 4: Security Scan
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | Source files in scope |
+| **OUTPUT** | Security report: vulnerabilities found, severity levels |
+| **AGENTS** | `security-scanner` |
+| **SKILLS** | `security-scanner`, `code-review` |
+
+| Check | Required |
+|-------|----------|
+| No hardcoded secrets | ? |
+| Input validation present | ? |
+| SQL injection safe | ? |
+| XSS prevention | ? |
+
+### Phase 5: Logic Review
+
+| Field | Value |
+|-------|-------|
+| **INPUT** | All results from Phases 2-4 + source code |
+| **OUTPUT** | Logic review: issues found with severity, required actions |
+| **AGENTS** | `security-scanner`, `learner` |
+| **SKILLS** | `code-review`, `problem-checker`, `knowledge-compiler` |
+
+| Category | Questions |
+|----------|----------|
+| **Correctness** | Does it solve the stated problem? |
+| **Edge Cases** | Null, empty, max values handled? |
+| **Error Handling** | All failure modes covered? |
+| **Performance** | N+1 queries? Memory leaks? |
+| **Maintainability** | Clear naming? Single responsibility? |
+
+---
+
+## ? MANDATORY: Problem Verification Before Completion
+
+> **CRITICAL:** This check MUST be performed before any `notify_user` or task completion.
+
+### Check @[current_problems]
+
+```
+1. Read @[current_problems] from IDE
+2. If errors/warnings > 0:
+   a. Auto-fix: imports, types, lint errors
+   b. Re-check @[current_problems]
+   c. If still > 0 ? STOP ? Notify user
+3. If count = 0 ? Proceed to completion
+```
+
+### Auto-Fixable
+
+| Type | Fix |
+|------|-----|
+| Missing import | Add import statement |
+| Unused variable | Remove or prefix `_` |
+| Lint errors | Run eslint --fix |
+
+> **Rule:** Never mark complete with errors in `@[current_problems]`.
+
+---
+
+## ?? Rollback & Recovery
+
+If the inspection process (builds, scans) creates ghost artifacts or fails to complete legitimately:
+1. Restore workspace to pre-inspect checkpoint (`git reset --hard HEAD` and `git clean -fd`).
+2. Log failure via `learner` meta-agent.
+3. Automatically escalate to `/diagnose` to understand why the pipeline failed.
+
+---
+
+### Evidence-Based Completion
+
+**NEVER claim completion without proof:**
+
+```
+? CORRECT: "Build passed: `npm run build` completed in 3.2s"
+? CORRECT: "Tests: 42/42 passed (npm test output attached)"
+? WRONG:  "I believe the code should work"
+? WRONG:  "This should fix the issue"
+```
+
+---
+
+## Output Format
+
+```markdown
+## ?? Inspect: [Target]
+
+### Layer Results
+
+| Layer | Status | Details |
+|-------|--------|---------|
+| Build | ? Pass | 0 errors, 2 warnings |
+| Tests | ? Pass | 42/42 passed, 78% coverage |
+| Security | ?? Warning | 1 issue found |
+| Logic | ?? Issues | 3 issues found |
+
+### Issues Found
+
+| File | Issue | Severity |
+|------|-------|----------|
+| `user.ts:45` | Missing null check | High |
+| `api.ts:23` | No rate limiting | Medium |
+| `auth.ts:89` | Unused variable | Low |
+
+### Verdict
+
+?? **NEEDS FIXES** before completion
+
+### Required Actions
+
+1. Add null check in user.ts:45
+2. Add CSRF token to POST endpoints
+3. Consider rate limiting
+
+### Next Steps
+
+- [ ] Fix identified issues with `/fix`
+- [ ] Re-run `/inspect` after fixes
+- [ ] Run `/validate` for full test suite
+```
+
+---
+
+## Examples
+
+```
+/inspect
+/inspect src/services/auth.ts
+/inspect --pr
+/inspect --security
+/inspect src/routes/ --security
+```
+
+---
+
+## Key Principles
+
+- **Evidence over belief** — prove it works with command output, not assumptions
+- **Every layer matters** — don't skip build, tests, security, or logic checks
+- **Security first** — always scan for vulnerabilities before marking complete
+- **Fix before claiming** — no "should work" — verify with evidence
+- **Document issues** — clear action items with file, line, and severity
+
+---
+
+## ?? Workflow Chain
+
+**Skills Loaded (5):**
+
+- `security-scanner` - OWASP 2025 vulnerability analysis
+- `code-review` - Multi-layer code quality validation
+- `context-engineering` - Codebase parsing and context extraction
+- `problem-checker` - IDE problem verification
+- `knowledge-compiler` - Learning and logging review patterns
+
+```mermaid
+graph LR
+    A["/inspect"] --> B["/fix"]
+    B --> C["/validate"]
+    C --> D["/launch"]
+    style A fill:#10b981
+```
+
+| After /inspect | Run | Purpose |
+|---------------|-----|---------|
+| Issues found | `/fix` | Fix identified issues |
+| All clear | `/validate` | Run full test suite |
+| Security issue | `/diagnose` | Deep investigation |
+
+**Handoff to /fix:**
+
+```markdown
+?? Review complete. [X] issues found across 4 layers.
+Verdict: [PASS/NEEDS FIXES]. Run `/fix` to resolve or `/validate` if all clear.
+```