tribunal-kit 5.8.4 → 6.0.0

package/.agent/skills/motion-engineering/SKILL.md

@@ -1,17 +1,30 @@
 ---
 name: motion-engineering
 description: Motion Engineering mastery for 2026 web UI. Covers all 20 modern animation styles across 4 tiers (Core UX, Immersive, Advanced, Specialized). Use when designing motion strategy, choosing animation libraries (Framer, GSAP, WebGL, CSS), or implementing animated UI patterns.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 4.0.0
-last-updated: 2026-04-07
-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:
+  - 60fps-animation
+  - accessible-animation
+  - framer-motion-expert
+  - gsap-react
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Motion Engineering (2026) — Comprehensive Reference
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering web animations or selecting motion libraries, you MUST inspect:
+1. Master Library Decision Matrix (Section 29) → Select appropriate library (Framer Motion, GSAP, View Transitions API, Lottie) based on interaction category
+2. 120fps GPU Compositing Rule (Section 181) → Restrict animations strictly to `transform` and `opacity` to avoid layout thrashing
+3. Accessibility & `prefers-reduced-motion` (Section 158) → Ensure fallback to instant opacity or no-op motion for reduced-motion preference
+
 You are the Motion Engineering Specialist. Your purpose is to bridge the gap between static UI and fluid, intuitive, and high-performance digital experiences. You understand that motion is not decoration; it is usability, narrative, and state communication.
 
 ## Hallucination Traps & Motion Sins (Read First)
@@ -93,216 +106,118 @@ gsap.ticker.add((time) => lenis.raf(time * 1000));
 gsap.ticker.lagSmoothing(0);
 ```
 
-### 3. Page Transitions (View Transitions API)
+### 3. Page Transitions (Native-First View Transitions API)
 
 ```css
-/* CSS — define shared elements */
+/* CSS — Browser-native page transition (Zero JS runtime cost) */
+@view-transition {
+  navigation: auto;
+}
+
 .card-image {
-  view-transition-name: active-image;
-} /* MUST BE UNIQUE */
+  view-transition-name: active-image; /* MUST BE UNIQUE IN DOM */
+}
 ::view-transition-old(active-image) {
-  animation: fade-out 0.3s ease;
+  animation: fade-out 0.25s cubic-bezier(0.4, 0, 0.2, 1);
 }
 ::view-transition-new(active-image) {
-  animation: scale-in 0.3s ease;
+  animation: scale-in 0.25s cubic-bezier(0, 0, 0.2, 1);
 }
 ```
 
-### 4. Loading & Skeleton Animations
-
-Never block the UI entirely. Use structural loading.
-
-```css
-/* Shimmer structural animation */
-.skeleton {
-  background: linear-gradient(90deg, #f0f0f0 25%, #e0e0e0 50%, #f0f0f0 75%);
-  background-size: 200% 100%;
-  animation: shimmer 1.5s infinite linear;
-}
-@keyframes shimmer {
-  100% {
-    background-position: -200% 0;
+```tsx
+// SPA Route Navigation Trigger with Fallback
+function navigateWithTransition(url: string, navigate: (path: string) => void) {
+  if (!document.startViewTransition) {
+    navigate(url);
+    return;
   }
+  document.startViewTransition(() => {
+    navigate(url);
+  });
 }
 ```
 
----
-
-## TIER 2: Narrative & Immersive (Medium Implementation)
-
-_Used for brand storytelling, heroes, and engagement._
-
-### 5. 3D & Immersive Animations
-
-The leading trend of 2026. Use React Three Fiber.
+### 4. DOM Entry & Exit Animations (@starting-style)
 
-```tsx
-// WebGL Scene basics
-import { Canvas, useFrame } from "@react-three/fiber";
-function RotatingCube() {
-  const meshRef = useRef();
-  useFrame((state, delta) => (meshRef.current.rotation.x += delta));
-  return (
-    <mesh ref={meshRef}>
-      <boxGeometry />
-      <meshStandardMaterial color="hotpink" />
-    </mesh>
-  );
+```css
+/* CSS @starting-style allows animating entry from display: none */
+.modal {
+  display: none;
+  opacity: 0;
+  transform: scale(0.95);
+  transition: 
+    opacity 0.2s ease, 
+    transform 0.2s cubic-bezier(0.2, 0.8, 0.4, 1), 
+    display 0.2s allow-discrete;
 }
-```
 
-### 7. Kinetic Typography
+.modal[open] {
+  display: block;
+  opacity: 1;
+  transform: scale(1);
+}
 
-```tsx
-// Word-by-word spring reveal (Framer Motion)
-const words = "Immersive storytelling".split(" ");
-const wordVariants = { hidden: { opacity: 0, y: 20 }, visible: { opacity: 1, y: 0 } };
-
-<motion.h1 transition={{ staggerChildren: 0.05 }} initial="hidden" whileInView="visible" viewport={{ once: true }}>
-  {words.map((w, i) => (
-    <motion.span key={i} variants={wordVariants}>
-      {w}{" "}
-    </motion.span>
-  ))}
-</motion.h1>;
+@starting-style {
+  .modal[open] {
+    opacity: 0;
+    transform: scale(0.95);
+  }
+}
 ```
 
-### 8. Background Animations & 9. Illustrations
-
-- **Backgrounds:** Use CSS `@keyframes` on pseudo-elements with `filter: blur()` for ambient gradients, avoiding repaints.
-- **Illustrations:** Use Rive for interactive state machines, or Lottie via `lottie-react` for simple timeline playback.
-
----
-
-## TIER 3: Advanced & Emerging (Concepts & Tools)
-
-_Highly interactive components elevating standard UI._
-
-- **6. Motion UI & State Transitions:** Use Framer Motion's `layout` prop. Morphing a list item into a modal requires `<motion.div layoutId="item-1">` on both states. Wrap the app in `<LayoutGroup>`.
-- **10. Physics-based:** Animate like real-world objects. Instead of `duration`, define `mass`, `stiffness`, and `damping` in physics springs to simulate gravity and tension.
-- **11. Morphing & Shape:** GSAP `MorphSVGPlugin`. Requires SVGs with comparable path points or GSAP will interpolate poorly. Alternatively, animate CSS `border-radius` for fluid blobs.
-- **12. Glassmorphism:** Animate `backdrop-filter: blur(10px)` but beware of performance costs on mobile. Render shadows via `filter: drop-shadow()` combined with slight `translateY` on hover.
-- **13. Cursor-based:** Modern standard is CSS variables bound to mouse position. Calculate `clientX` relative to the element bounding box and update `--mouse-x` to drive `radial-gradient` masks.
-- **14. AI-driven Adaptive:** Motion that learns. If a user speeds through a form, UI transitions accelerate. If they linger, ambient motion plays. Controlled by tracking interaction deltas and mapping them to global spring configurations.
-- **15. Gamified:** Progress bars that burst on completion, haptic-synchronized checkmarks. Combine SVGs with explicit, highly exaggerated elastic overshoot scales (`scale: [1, 1.2, 0.9, 1]`) on reward thresholds.
-
----
-
-## TIER 4: Specialized (Rules & Fallbacks)
-
-_Niche requirements where performance or specific constraints dominate._
-
-- **16. Video + Motion Hybrid:** Scrubbing `<video>` tags with scroll. Requires pre-encoding video rapidly with keyframes every 1 frame, drawing frames to a `<canvas>` element via `requestAnimationFrame` linked to scroll progress.
-- **17. Experimental:** Glitch effects via overlapping CSS `clip-path` animations. High processing cost.
-- **18. Navigation:** Mega-menus must use `<AnimatePresence>` to prevent DOM unmount before the exit animation resolves. Include exit delays so users don't trigger flickering by rapidly moving the mouse off the nav.
-- **19. Data Visualization:** D3 handles math, React handles DOM, Framer/Spring handles interpolation between D3 datasets. Never let D3 mutate the DOM directly inside a React app.
-- **20. Performance-first Subtle Motion:** Strictly `opacity`, `transform`, CSS-only. Use `@starting-style` for popovers and dialogs to avoid JS intervention.
-
 ---
 
 ## Accessibility & Performance Invariants (Global Rules)
 
 1. **The WCAG 2.2 AA Motion Rule:**
+   Always respect `prefers-reduced-motion`. Fall back to instant opacity or no-op motion.
 
 ```tsx
-import { useReducedMotion } from "framer-motion";
-const reduce = useReducedMotion();
-// Safe: opacity, color
-// Conditional: translate, scale, rotate
-<motion.div animate={{ x: reduce ? 0 : 100, opacity: 1 }} transition={{ duration: reduce ? 0 : 0.5 }} />;
+import { useReducedMotion } from "motion/react";
+
+function AccessibleComponent() {
+  const shouldReduceMotion = useReducedMotion();
+  
+  return (
+    <motion.div
+      animate={{ 
+        x: shouldReduceMotion ? 0 : 100, 
+        opacity: 1 
+      }}
+      transition={{ duration: shouldReduceMotion ? 0 : 0.3 }}
+    />
+  );
+}
 ```
 
 2. **The 120fps GPU Rule:**
    Never animate `width`, `height`, `left`, `top`, `margin`, or `padding`. This triggers layout recalculation algorithms. Use `transform: scale()` or `transform: translate()` instead.
 
-3. **The Cleanup Rule:**
-   Any GSAP ScrollTrigger timeline must use `ScrollTrigger.killAll()` or React's `useGSAP` cleanup functions to avoid memory leaks on SPA route changes.
-
----
-
-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.
-
----
-
-**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.
+3. **The GSAP Memory Cleanup Rule:**
+   Any GSAP ScrollTrigger timeline must use `@gsap/react` `useGSAP` or explicit `tl.kill()` cleanup to avoid memory leaks on SPA route changes.
 
 ---
 
 ## 🤖 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.
+1. **Over-animating Static UI:** Animating page titles and static text on simple forms.
+2. **Missing `allow-discrete`:** Animating `display` or `popover` without `transition-behavior: allow-discrete`.
+3. **GSAP Memory Leaks:** Forgetting to kill GSAP timelines on component unmount.
 
 ---
 
 ## 🏛️ 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?
+✅ Are all animations constrained to GPU-friendly properties (transform, opacity)?
+✅ Is prefers-reduced-motion handled natively or via hooks?
+✅ Are view-transition-name attributes unique across the entire active DOM?
 ```
 
 ### 🛑 Verification-Before-Completion (VBC) Protocol
 
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+Inspect motion frame performance in DevTools Rendering tab to verify 60/120fps compositor execution without layout thrashing.
 
-- ❌ **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/nextjs-react-expert/SKILL.md

@@ -1,17 +1,29 @@
 ---
 name: nextjs-react-expert
 description: Next.js 15+ App Router mastery. Server Components, Server Actions, PPR, caching, metadata, middleware, parallel/intercepting routes. Use when building Next.js apps or optimizing Next.js performance.
-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
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - react-specialist
+  - react-doctor
+  - baseline-ui
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Next.js 15+ App Router — Dense Reference
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering Next.js 15+ App Router code, you MUST inspect:
+1. Client Boundary rules (`"use client"` vs Server Components) → Use Server Components by default; add `"use client"` only for interactivity/hooks
+2. Server Actions Validation (Section 68) → Always include `"use server"` and validate form inputs with Zod (`Schema.safeParse`)
+3. Next.js 15 Caching & Dynamic APIs (Section 106) → `fetch()` is UNCACHED by default in Next.js 15; `cookies()` and `headers()` are `async`
+
 ## Hallucination Traps (Read First)
 
 - ❌ `pages/api/` or `_app.tsx` → ✅ App Router only: `app/api/route.ts`, `app/layout.tsx`

package/.agent/skills/nodejs-best-practices/SKILL.md

@@ -1,19 +1,33 @@
 ---
 name: nodejs-best-practices
 description: Node.js 22+ production mastery. ES Modules, async patterns, Express/Fastify/Hono, middleware architecture, error handling, streaming, worker threads, environment config, security hardening, process management, and deployment patterns. Use when building Node.js servers, APIs, CLI tools, or any server-side JavaScript.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-01
-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:
+  - backend-security-expert
+  - api-patterns
+  - clean-code
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Node.js Best Practices — Node 22+ Production Mastery
 
 ---
 
+## Mandatory Pre-Flight Context Inspection
+
+Before building Node.js services or middleware, you MUST inspect:
+1. Node Built-in Import Protocol (Section 34) → Use explicit `node:` prefix (`import fs from "node:fs/promises"`); ban legacy CommonJS `require()`
+2. Mandatory Process Exit on Uncaught Exception (Section 170) → Ensure process exits (`process.exit(1)`) after `uncaughtException` to prevent running in corrupted state
+3. Startup Environment Validation (Section 373) → Validate environment variables at app startup with Zod; crash immediately if required secrets are missing
+
+# Node.js Best Practices — Node 22+ Production Mastery
+
+---
+
 ## ES Modules (Mandatory)
 
 ```json

package/.agent/skills/observability/SKILL.md

@@ -1,19 +1,33 @@
 ---
 name: observability
 description: Production observability mastery. Structured logging (Pino/Winston), OpenTelemetry tracing, metrics (Prometheus/Grafana), SLIs/SLOs/error budgets, distributed tracing, alerting design, health checks, and AI observability. Use when setting up monitoring, debugging production issues, or designing observable distributed systems.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-01
-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:
+  - devops-incident-responder
+  - nodejs-best-practices
+  - backend-security-expert
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Observability — Production Monitoring Mastery
 
 ---
 
+## Mandatory Pre-Flight Context Inspection
+
+Before instrumenting applications for observability, you MUST inspect:
+1. Structured JSON Logging Rule (Section 34) → Use Pino/structlog for structured JSON logging with ISO timestamps; ban plain `console.log` in production
+2. Separation of Liveness & Readiness Checks (Section 253) → Isolate `/health/live` (process active) from `/health/ready` (DB connected); ban DB calls in liveness checks to prevent restart loops
+3. Correlation Tracking Context (Section 80) → Inject `x-request-id` via AsyncLocalStorage or middleware so every log line is correlated to a specific request
+
+# Observability — Production Monitoring Mastery
+
+---
+
 ## The Three Pillars
 
 ```

package/.agent/skills/page-transition-animation/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: page-transition-animation
 description: Page and route transition patterns using the native View Transitions API, Framer Motion AnimatePresence, and Next.js App Router exit animations.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Route Transitions & Navigation Motion
-  tier: pro
-  co-requires: [framer-motion-expert, 60fps-animation]
-  trigger-signals:
-    strong: [page-transition-animation, View Transitions API, page transition, route transition, Next.js exit animation, shared element transition]
-    weak: [route animation, page animation]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - framer-motion-expert
+  - 60fps-animation
+  - accessible-animation
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Page Transition Animation — Native & Framework Route Motion
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering route or page transitions, you MUST inspect:
+1. Target Framework & API (View Transitions API vs Framer Motion `AnimatePresence`)
+2. `AnimatePresence` Keying (Section 69) → Enforce `key={pathname}` and `mode="wait"` to prevent double-page DOM stacking
+3. Vertical Displacement Cap → Keep route movement under $12\text{px}$ to prevent visual scroll shifts
+
 Architect smooth, seamless page and route transitions without layout jumps or frozen exit states.
 
 ---

package/.agent/skills/parallel-agents/SKILL.md

@@ -1,13 +1,29 @@
 ---
 name: parallel-agents
 description: Parallel processing coordination for multi-agent swarms. Asynchronous dispatches, merging divergent logic streams, race conditions in autonomous agents, avoiding Git conflicts in concurrent generation, and fan-out/fan-in processing patterns. Use when orchestrating multiple agents simultaneously.
-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:
+  - agent-organizer
+  - fabel-protocol
+  - workflow-optimizer
+scripts-binding:
+  - .agent/scripts/swarm_dispatcher.js
+  - .agent/scripts/verify_all.js
+---
+
+# Parallel Agents — Concurrent Orchestration Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before executing parallel agent dispatches, you MUST inspect:
+1. Target file paths for concurrent workers → Enforce directory isolation; never allow two parallel workers to edit the same file
+2. `Promise.allSettled()` error handling (Section 77) → Handle partial worker failures gracefully without crashing the pipeline
+3. Context Window Budget → Keep total context across all parallel workers under 80,000 tokens
+
 ---
 
 ## Hallucination Traps (Read First)

package/.agent/skills/performance-profiling/SKILL.md

@@ -1,19 +1,33 @@
 ---
 name: performance-profiling
 description: Performance profiling mastery. Core Web Vitals (LCP, CLS, INP), Lighthouse auditing, JavaScript profiling, React rendering optimization, bundle analysis, memory leak detection, database query profiling (EXPLAIN ANALYZE), load testing, and performance budgets. Use when optimizing performance, debugging slow pages, or establishing performance standards.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-01
-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:
+  - 60fps-animation
+  - gsap-performance
+  - web-quality-audit
+scripts-binding:
+  - .agent/scripts/bundle_analyzer.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Performance Profiling — Measurement-Driven Optimization
 
 ---
 
+## Mandatory Pre-Flight Context Inspection
+
+Before optimizing performance or auditing benchmarks, you MUST inspect:
+1. Core Web Vitals Targets (INP replacing FID) (Section 26) → Target INP $\le 200\text{ms}$, LCP $\le 2.5\text{s}$, CLS $\le 0.1$; ban FID (deprecated)
+2. Bundle Size Limits & Import Tree-Shaking (Section 55) → Enforce total gzipped JS $<200\text{KB}$; use deep imports (`lodash/debounce`) instead of full barrel imports
+3. SQL EXPLAIN ANALYZE Requirement (Section 156) → Profile database queries with `EXPLAIN ANALYZE` before making index or query optimization changes
+
+# Performance Profiling — Measurement-Driven Optimization
+
+---
+
 ## Core Web Vitals
 
 ```

package/.agent/skills/plan-writing/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: plan-writing
 description: Technical design and implementation planning mastery. Writing structured execution checklists, dependency mapping, establishing rollback protocols, segmenting monolithic tasks, writing ADRs (Architecture Decision Records), and defining verification criteria. Use when transitioning from ideation to coordinated execution.
-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:
+  - project-planner
+  - brainstorming
+  - harness-protocol
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Plan Writing — Execution Blueprints Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before writing implementation plans or execution blueprints, you MUST inspect:
+1. Verification Criteria Requirement (Section 15) → Include explicit "How to verify" criteria for every wave; ban plan steps without verification
+2. Phased Wave Segmentation (Section 41) → Segment multi-file tasks into testable, independent waves (Wave 1: Data, Wave 2: API, Wave 3: UI)
+3. Non-Destructive Defaults & Rollback Rules (Section 66) → Define fallback feature toggles and database rollback procedures prior to execution
+
 ## Hallucination Traps (Read First)
 
 - ❌ Writing plans without verification criteria -> ✅ Every plan needs a 'How to verify this worked' section

package/.agent/skills/platform-engineer/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: platform-engineer
 description: Platform Engineering and Internal Developer Portal (IDP) mastery. Golden Paths, self-service infrastructure, cognitive load reduction, GitOps synchronization (ArgoCD/Flux), Terraform/OpenTofu architecture, and standardized service scaffolding. Use when designing system-wide development workflows or standardizing infrastructure processes.
-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:
+  - cloud-architect
+  - devops-engineer
+  - cicd-pro
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Platform Engineering — Developer Experience Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing developer platforms or GitOps manifests, you MUST inspect:
+1. Golden Path Self-Service Rule (Section 29) → Build pre-approved automated templates for bootstrapping services (CI, metrics, DB Terraform out-of-the-box)
+2. GitOps Continuous Reconciliation (Section 48) → Enforce declarative GitOps (`selfHeal: true`) via ArgoCD/Flux; ban manual `kubectl apply` or console modifications
+3. Higher-Level Terraform Modules (Section 76) → Encapsulate complex IaC logic into simple interface modules (`capacity`, `needs_replica`) to reduce cognitive load
+
 ## Hallucination Traps (Read First)
 
 - ❌ Building internal platforms without talking to developers -> ✅ Platform engineering exists to reduce developer cognitive load; ask them what hurts