tribunal-kit 5.8.5 → 6.0.0

package/.agent/skills/fabel-protocol/SKILL.md

@@ -1,12 +1,29 @@
 ---
 name: fabel-protocol
 description: Distilled Fabel-5 cognitive intelligence protocol. Injects epistemic reasoning, coding discipline, design evaluation cascades, and orchestration patterns into any AI model. Load this skill to make any model think, reason, code, and design like Fabel-5. Activates for complex builds, code generation, design tasks, and multi-agent orchestration.
-version: 1.0.0
-last-updated: 2026-07-07
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - agentic-patterns
+  - thinking-protocol
+  - knowledge-graph
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/checklist.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Fabel Protocol — Cognitive Intelligence Engine
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before executing reasoning loops, you MUST inspect:
+1. `package.json` / dependency manifests → Verify exact framework version boundaries (React 19 vs 18, Next.js 15 vs 14)
+2. Epistemic Confidence Checklist (Section 1) → Categorize implementation confidence L1 to L5
+3. High-Risk Hallucination Heatmap (Section 7) → Tag uncertain ORM/SDK method calls with `// VERIFY: [reason]` tags
+
 > Distilled from the Fabel-5 system prompt (191KB → 2,000 tokens). Makes any model reason like Fabel-5.
 
 ---

package/.agent/skills/fixing-accessibility/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: fixing-accessibility
 description: Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: UI Craft & Accessibility
-  tier: pro
-  co-requires: [audit-and-fix, web-accessibility-auditor]
-  trigger-signals:
-    strong: [fixing-accessibility, accessibility audit, WCAG 2.2, aria-label, keyboard navigation, focus trap, color contrast]
-    weak: [a11y, focus ring, screen reader]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - audit-and-fix
+  - build-primitive
+  - baseline-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Fixing Accessibility — WCAG 2.2 AA Audit & Remediation
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before remediating HTML accessibility defects, you MUST inspect:
+1. Priority Matrix (Section 22) → Ensure accessible names on icon buttons (P1) and native HTML keyboard controls (P2) before styling
+2. Focus Ring Policy (Section 29) → Ban `outline: none` without providing explicit `:focus-visible` replacement (`2px` ring + offset)
+3. Form Error Association (Section 32) → Attach `aria-invalid="true"` and `aria-describedby` pointing to error text IDs
+
 Guidelines for detecting, prioritizing, and fixing accessibility defects across web interfaces.
 
 ---

package/.agent/skills/fixing-metadata/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: fixing-metadata
 description: Audit and fix page metadata including page titles, meta descriptions, Open Graph, Twitter cards, canonical URLs, and JSON-LD structured data.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Technical SEO & Metadata Optimization
-  tier: pro
-  co-requires: [seo-fundamentals, web-quality-audit]
-  trigger-signals:
-    strong: [fixing-metadata, Open Graph tags, Twitter card metadata, canonical URL, JSON-LD structured data, meta description fix]
-    weak: [fix metadata, SEO tags]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - nextjs-react-expert
+  - baseline-ui
+  - compact-landing
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Fixing Metadata — Technical SEO & Open Graph Tags
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering metadata or Open Graph tags, you MUST inspect:
+1. Title & Meta Description Caps (Section 24) → Restrict title tags to 50–60 chars and meta descriptions to 140–155 chars
+2. Absolute Image URL Rule (Section 74) → Enforce full absolute HTTPS URLs (`https://domain.com/og.jpg`) for `og:image` and `twitter:image`
+3. Twitter Card Type (Section 39) → Always specify `<meta name="twitter:card" content="summary_large_image" />` for prominent social previews
+
 Audit, generate, and fix page metadata for rich social previews, search engine indexing, and structured data.
 
 ---

package/.agent/skills/fixing-motion-performance/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: fixing-motion-performance
 description: Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: UI Motion & Performance
-  tier: pro
-  co-requires: [60fps-animation, gsap-performance]
-  trigger-signals:
-    strong: [fixing-motion-performance, layout thrashing, compositor properties, scroll jank, animation stutter, GPU acceleration, will-change]
-    weak: [jank, slow animation, stutter]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - 60fps-animation
+  - motion-engineering
+  - gsap-performance
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Fixing Motion Performance — 60/120fps Jank-Free Animation
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before auditing or fixing animation performance, you MUST inspect:
+1. Browser Rendering Pipeline (Section 22) → Restrict properties to Composite-only (`transform`, `opacity`) and eliminate Layout/Paint animators
+2. Layout Thrashing (Section 33) → Batch all DOM reads (`offsetHeight`, `getBoundingClientRect`) before executing DOM writes (`style.height = ...`)
+3. `will-change` VRAM management (Section 53) → Remove `will-change` hints upon animation completion
+
 Guidelines for auditing and resolving web animation jank, layout thrashing, and GPU rendering bottlenecks.
 
 ---

package/.agent/skills/framer-motion-expert/SKILL.md

@@ -1,16 +1,29 @@
 ---
 name: framer-motion-expert
 description: Framer Motion 12+ for React. Declarative animations, layout transitions, gestures, scroll-linked motion, AnimatePresence, useAnimate, LazyMotion. Use when building component animations, page transitions, shared layout animations, or gesture-driven UI.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 3.1.0
-last-updated: 2026-04-06
-routing:
-  domain: general
-  tier: basic
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - motion-engineering
+  - 60fps-animation
+  - accessible-animation
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Framer Motion 12+ — Dense Reference
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before writing Framer Motion code in React, you MUST inspect:
+1. `package.json` / Next.js Client Boundaries → Add `"use client"` directive on Next.js App Router files containing `motion.X`
+2. AnimatePresence & layoutId Rules (Section 117) → Enforce `mode="wait"` and ensure every `<AnimatePresence>` child has a unique `key`
+3. Bundle Optimization (Section 182) → Use `<LazyMotion features={domAnimation}>` with `m.div` for lightweight production bundles
+
 ## Hallucination Traps (Read First)
 
 - ❌ `<Motion>` (capital M) → ✅ `motion.div` (lowercase dot notation)

package/.agent/skills/frontend-design/SKILL.md

@@ -1,249 +1,112 @@
 ---
 name: frontend-design
-description: Design thinking for web UI. Micro-interactions, visual hierarchy, typography scaling, HSL color palettes, spacing systems, and CSS-first UI logic. Avoid generic AI aesthetics.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 3.1.0
-last-updated: 2026-04-06
-applies-to-model: gemini-3-1-pro, claude-3-7-sonnet
-routing:
-  domain: general
-  tier: basic
+description: Design engineering principles for React/Next.js. Relative color syntax (OKLCH), spatial grid math, fluid container queries, and contrast validation.
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - baseline-ui
+  - better-colors
+  - better-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
-# Frontend Design — Dense Reference
+# Frontend Design — Technical Spacing & Color Science
 
-## Hallucination Traps (Read First)
+---
 
-- ❌ Purple gradient backgrounds (`from-purple-500 to-blue-500`) → ✅ The worst AI UI cliché. Use high-contrast solid colors, grain, or sophisticated HSL mono-palettes.
-- ❌ Hardcoded pixels (`font-size: 14px`) → ✅ Use `rem` for accessibility and scaling (`1rem = 16px`).
-- ❌ Gray text (`#888`) on white → ✅ Fails WCAG contrast. Text must be `4.5:1` ratio.
-- ❌ Generic sans-serif → ✅ Inter, Geist, Roboto Mono, or system-ui. Typography is 80% of design.
-- ❌ "Bento Box" grids for everything → ✅ Overused pattern. Use directional flow or asymmetric layouts.
-- ❌ Symmetrical layouts out of laziness → ✅ Tension and blank space (negative space) drive premium feel.
-- ❌ Infinite scrolling without context → ✅ Provide clear footers or logical pagination markers.
-- ❌ Over-animating everything (`all elements fade in`) → ✅ Animate state changes (hover, focus, submit), not static entry layout unless scrollytelling.
+## Mandatory Pre-Flight Context Inspection
 
----
+Before implementing front-end designs or CSS layout systems, you MUST inspect:
+1. Relative Color Syntax (Section 16) → Derive hover/active states dynamically with `oklch(from var(--color-primary) calc(l - 0.08) c h)`
+2. Nested Radius Math (Section 54) → Enforce `outer_radius = inner_radius + padding_inner` for nested card containers
+3. APCA Contrast Thresholds (Section 81) → Ensure Lc > 75 for body text, Lc > 60 for headings, and Lc > 45 for borders and labels
 
-## 1. Modern Color Systems (OKLCH & HSL)
+This skill guides the implementation of responsive layout systems, color science, and spatial tokens.
 
-Never use raw flat HEX colors. Use OKLCH (perceptually uniform) or HSL to build scalable, harmonic themes.
+---
 
+## 1. Relative Color Syntax & OKLCH Theme Tokens
+
+Perceptually uniform color science ensures stable contrast. Use CSS **Relative Color Syntax** to derive state colors dynamically:
 ```css
 :root {
-  /* OKLCH perceptual uniformity: lightness (0-100%), chroma (0-0.37), hue (0-360) */
-  --brand-primary: oklch(62% 0.21 275);
-  --brand-hover: oklch(from var(--brand-primary) calc(l - 0.1) c h); /* Relative Color Syntax */
+  /* base color values */
+  --color-primary: oklch(62% 0.21 250);       /* Brand electric blue */
+  
+  /* Deriving hover states dynamically: reduce lightness, preserve chroma and hue */
+  --color-primary-hover: oklch(from var(--color-primary) calc(l - 0.08) c h);
+  --color-primary-active: oklch(from var(--color-primary) calc(l - 0.12) c h);
   
-  --bg-base: oklch(98% 0.005 240);
+  /* Backgrounds */
   --bg-surface: oklch(100% 0 0);
-  --text-main: oklch(20% 0.02 240);
-  --text-muted: oklch(50% 0.02 240);
+  --text-main: oklch(20% 0.02 250);
 }
 
-/* Light/Dark mode via native light-dark() function or OLED media query */
-:root {
-  color-scheme: light dark;
-  --bg-surface: light-dark(oklch(100% 0 0), oklch(15% 0.01 240));
-  --text-main: light-dark(oklch(20% 0.02 240), oklch(95% 0.01 240));
+[data-theme="dark"] {
+  --bg-surface: oklch(14% 0.008 250);
+  --text-main: oklch(93% 0.003 250);
 }
 ```
 
 ---
 
-## 2. Spatial Systems & Container Queries
-
-Design relies on structural rhythm and component-level adaptability.
-
-- **Base Spacing Grid (8px)**: Micro `4px`, `8px` | Component `16px`, `24px` | Section `48px`, `64px`, `96px`
-- **Nested Border Radius Formula**: `outer_radius = inner_radius + padding`
-- **Fluid Typography**: Use `clamp()` and `cqi` container units over macro media queries.
+## 2. Spatial Grid Math & Radius Tokens
 
+Enforce an 8px spatial grid calculated mathematically to ensure alignment precision:
 ```css
-/* Container Queries for Portable Components */
-.card-container {
-  container-type: inline-size;
-  container-name: card;
-}
-
-@container card (min-width: 400px) {
-  .card-body {
-    display: grid;
-    grid-template-columns: 1fr 2fr;
-    gap: 1.5cqi;
-  }
-}
-
-/* Typographic Balance */
-h1, h2, h3 {
-  font-size: clamp(2rem, 4vw + 1rem, 4rem);
-  letter-spacing: -0.02em;
-  text-wrap: balance; /* Prevents awkward multiline headline breaks */
-}
-
-p {
-  font-size: 1rem;
-  max-width: 65ch;
-  text-wrap: pretty; /* Eliminates typographical orphans in body text */
+:root {
+  --base-grid: 8px;
+  
+  --space-xs:  calc(var(--base-grid) * 0.5);  /* 4px  - icon gaps */
+  --space-sm:  calc(var(--base-grid) * 1);    /* 8px  - tag paddings */
+  --space-md:  calc(var(--base-grid) * 2);    /* 16px - inputs */
+  --space-lg:  calc(var(--base-grid) * 3);    /* 24px - card padding */
+  --space-xl:  calc(var(--base-grid) * 4);    /* 32px - section gaps */
 }
 ```
 
----
-
-## 3. Interaction & Entry Motion (@starting-style)
-
-A premium UI reacts to user actions instantly and provides smooth DOM mount transitions.
-
-```css
-/* Physical press feedback */
-.btn {
-  transition: transform 0.15s cubic-bezier(0.2, 0.8, 0.4, 1), box-shadow 0.15s ease;
-}
-.btn:active {
-  transform: scale(0.97);
-}
-
-/* Entry/Exit Animations for DOM Elements (@starting-style) */
-.toast {
-  display: none;
-  opacity: 0;
-  transform: translateY(8px);
-  transition: opacity 0.25s ease, transform 0.25s ease, display 0.25s allow-discrete;
-}
-.toast.is-open {
-  display: flex;
-  opacity: 1;
-  transform: translateY(0);
-}
-@starting-style {
-  .toast.is-open {
-    opacity: 0;
-    transform: translateY(8px);
-  }
-}
-```
+### Nested Radius Formula
+Ensure component inner borders track correctly:
+`outer_radius = inner_radius + padding_inner`
+If container padding is `16px` and inner content radius is `8px`, then container outer radius must be exactly `24px` (`8px + 16px`).
 
 ---
 
-## 4. Modern Glassmorphism & Multi-Layer Depth
-
-Avoid flat 1px borders and muddy single shadows. Use multi-layered elevation.
+## 3. Responsive Layouts & Container Queries
 
+Avoid viewport-level media queries for self-contained components. Use container queries to make components portable:
 ```css
-.card {
-  background: light-dark(rgba(255, 255, 255, 0.8), rgba(20, 20, 25, 0.8));
-  backdrop-filter: blur(16px);
-  -webkit-backdrop-filter: blur(16px);
-  border: 1px solid light-dark(rgba(0, 0, 0, 0.08), rgba(255, 255, 255, 0.12));
-  border-radius: 16px;
-  box-shadow: 
-    0 1px 2px oklch(0% 0 0 / 0.05),
-    0 4px 12px oklch(0% 0 0 / 0.08);
+.component-wrapper {
+  container-type: inline-size;
+  container-name: component;
 }
-```
-
----
 
-## 5. Accessibility (WCAG 2.2 AA Standards)
-
-Design is broken if it excludes users.
-- ✅ **SC 2.5.8 Target Size**: Interactive controls must be at least `24x24px` CSS pixels (min `44x44px` for touch targets).
-- ✅ **SC 2.4.11 Focus Not Obscured**: Focused elements must never be completely hidden by sticky headers/footers.
-- ✅ **SC 2.4.13 Focus Appearance**: Visible focus rings must achieve `3:1` contrast ratio with a minimum 2px perimeter offset.
-- ✅ **Color Alone**: Never rely solely on color to convey state (pair error alerts with icons).
-
-```css
-button:focus-visible, a:focus-visible {
-  outline: 2px solid var(--brand-primary);
-  outline-offset: 3px;
+@container component (min-width: 450px) {
+  .inner-layout {
+    display: grid;
+    grid-template-columns: repeat(2, 1fr);
+    gap: var(--space-md);
+  }
 }
 ```
 
 ---
 
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
+## 4. APCA Contrast Guidelines
 
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
+Ensure that typography meets the APCA Lc guidelines:
+*   Lc > 75 for body text elements.
+*   Lc > 60 for large titles and headings.
+*   Lc > 45 for secondary input labels and border guides.
 
 ---
 
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-Review these questions before confirming output:
-
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.
-
 ## Pre-Flight Checklist
-
 - [ ] Have I reviewed the user's specific constraints and requests?
 - [ ] Have I checked the environment for relevant existing implementations?
 
 ## VBC Protocol (Verification-Before-Completion)
-
 You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
-
----
-
-## 🤖 LLM-Specific Traps
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before confirming output:
-
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.

package/.agent/skills/frontend-security-expert/SKILL.md

@@ -1,17 +1,31 @@
 ---
 name: frontend-security-expert
 description: Frontend security auditing for modern meta-frameworks. Focuses on React/Next.js UI paradigms, hydration poisoning, third-party script supply chain, local storage security, and XSS prevention in modern environments.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-05-22
-applies-to-model: gemini-3-1-pro, claude-3-7-sonnet
-routing:
-  domain: general
-  tier: basic
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - backend-security-expert
+  - api-security-auditor
+  - vulnerability-scanner
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Frontend Security Expert — Modern Meta-Frameworks
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before auditing or writing client-side code, you MUST inspect:
+1. XSS Sanitize Rules (Section 28) → Require DOMPurify for any `dangerouslySetInnerHTML` and audit dynamic `javascript:` URIs
+2. HttpOnly Auth Token Storage (Section 34) → Ban storing JWTs or auth tokens in `localStorage` or `sessionStorage`; use `HttpOnly`, `Secure`, `SameSite` cookies
+3. PostMessage Origin Verification (Section 46) → Never use `targetOrigin: '*'` and always validate `event.origin` on receiving handlers
+
+# Frontend Security Expert — Modern Meta-Frameworks
+
 ## Hallucination Traps (Read First)
 
 - ❌ Focusing on generic OWASP top 10 (SQLi, IDOR) → ✅ This is the _frontend_ skill. Focus strictly on client-side boundaries, SSR hydration, and DOM.

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

@@ -1,15 +1,29 @@
 ---
 name: game-design-expert
 description: Game Design, UX, and Flow State mastery. Replaces fragmented legacy skills. Core gameplay loop design, 3Cs (Character, Camera, Controls), input buffering, coyote time, juice (game feel), telemetry tracking, narrative alignment, and audio spatialization integration. Use when crafting player experience, progression arcs, or systemic balance.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-02
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
-routing:
-  domain: general
-  tier: basic
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - game-engineering-expert
+  - 12-principles-of-animation
+  - sounds-on-the-web
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Game Design Expert — Player Experience & Flow Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing gameplay systems or controller feel, you MUST inspect:
+1. 3Cs Foundation (Character, Camera, Controls) (Section 25) → Implement input buffering (~150ms) and coyote time (~100ms) before designing enemy AI or progression
+2. Macro Gameplay Loop Validation (Section 42) → Ensure upgrading systems directly alter action and combat feel to prevent player churn
+3. Juicing & Hitstop Feel (Section 58) → Incorporate screen shake, hitstop (3 freeze frames), particle explosions, and squash-and-stretch for impact feedback
+
 ## Hallucination Traps (Read First)
 
 - ❌ Designing reward systems without testing for compulsion loops -> ✅ Playtesting must verify engagement without addiction patterns

package/.agent/skills/game-engineering-expert/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: game-engineering-expert
 description: Game Engineering and Systems Architecture mastery. Replaces fragmented legacy skills. Entity Component Systems (ECS), Unity (C#) / Godot (GDScript) integration, physics calculations, deterministic engine state, WebGL memory management, multiplayer sync architectures (deterministic lockstep vs traditional authoritative), spatial partitioning, and rendering pipelines.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-02
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
-routing:
-  domain: general
-  tier: basic
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - game-design-expert
+  - csharp-developer
+  - 60fps-animation
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Game Engineering Expert — Performance & State Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering game state loops or physics engines, you MUST inspect:
+1. Clamped DeltaTime Rule (Section 25) → Clamp `deltaTime` (max 0.05s) to prevent physics explosions on frame rate drops
+2. Garbage Collection & Object Pooling (Section 50) → Pre-allocate and pool game objects; ban `Instantiate()` or dynamic memory allocations in frame update loops
+3. FixedUpdate vs Update Separation (Section 43) → Put all physics logic in `FixedUpdate()`; use `Update()` strictly for visual interpolation and input collection
+
 ## Hallucination Traps (Read First)
 
 - ❌ Using deltaTime without clamping -> ✅ Unclamped deltaTime causes physics explosions on frame spikes; clamp to max 0.05s

package/.agent/skills/generative-ui-expert/SKILL.md

@@ -1,13 +1,29 @@
 ---
 name: generative-ui-expert
 description: Generative UI mastery. Vercel AI SDK 3.0+, React Server Components (RSC) + LLMs, streaming UI elements, structured tool calling (Zod schemas), and managing client-side AI state via useChat/useObject.
-routing:
-  domain: general
-  tier: basic
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - nextjs-react-expert
+  - react-specialist
+  - browser-native-ai
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Generative UI Expert (Vercel AI SDK)
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before implementing Generative UI streaming pipelines, you MUST inspect:
+1. Tool Parameter Schemas (Section 87) → Validate all LLM tool parameters with Zod schemas
+2. RSC Server Action Boundaries (Section 33) → Annotate server actions with `"use server"` and yield Server Components directly from `streamUI`
+3. Intermediate Skeleton Yielding (Section 80) → Always `yield <SkeletonLoader />` before awaiting async APIs or external LLM tool calls
+
 You are the definitive expert in Generative UI using the Vercel AI SDK and React Server Components (RSC). Your goal is to move AI from spitting out "markdown walls of text" into rendering interactive, stateful, and dynamic UI components natively inside the chat or application stream.
 
 ## 1. Core Principles