tribunal-kit 9.2.4 → 9.2.6

package/.agents/skills/gpt-taste/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: gpt-taste
-description: "Use when High-agency UX/UI skill with strict layout variance, typography, and GSAP motion engineering constraints for superior visual judgment."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when building, styling, optimizing, and auditing gpt taste components, responsive layouts, design systems, and frontend state."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - taste-skill
   - better-ui
@@ -15,36 +15,106 @@ scripts-binding:
 
 # GPT Taste — High-Agency Visual Refinement & Layout Variance
 
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `gpt-taste` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-## 🛠️ Technical Architecture & Reference Recipes
 
----
+## Activation Boundaries
+- **Activate when:** Use when building, styling, optimizing, and auditing gpt taste components, responsive layouts, design systems, and frontend state.
+- **DO NOT activate when:** The task falls outside the `gpt-taste` domain or is managed by a different dedicated specialist agent.
 
----
 
-## 4 High-Agency Visual Constraints
+## 🔁 Multi-Pass Execution Protocol
+
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
+
 
-### 1. Structural Layout Variance
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
-Never use standard symmetrical layouts by default. Vary structural axes across sections:
+---
+
+## 4 High-Agency Visual Constraints
+
+### 1. Structural Layout Variance
+
+Never use standard symmetrical layouts by default. Vary structural axes across sections:
+
+- **Hero**: Asymmetric 60/40 split or left-aligned stacked text with offset app preview frame.
+- **Features**: Alternating 2-column image/text rhythm or horizontal scroll cards.
+- **CTA**: Single full-width card with progressive backdrop blur overlay.
+
+### 2. OKLCH Perceptual Palette Generation
+
+Always generate color schemes in OKLCH:
+
+- Background: `oklch(0.98 0.005 240)`
+- Foreground: `oklch(0.18 0.01 240)`
+- Accent: `oklch(0.62 0.22 250)`
+
+### 3. GSAP / Motion Engineering Integration
+
+When animation is requested, use explicit GSAP timelines with custom easing curves (`power3.out`, `expo.out`), avoiding default linear transitions.
+
+### 4. Zero Output Truncation
+
+Never output placeholder `// TODO: add remaining items` comments in UI code. Generate full, production-ready JSX/CSS markup.
 
-- **Hero**: Asymmetric 60/40 split or left-aligned stacked text with offset app preview frame.
-- **Features**: Alternating 2-column image/text rhythm or horizontal scroll cards.
-- **CTA**: Single full-width card with progressive backdrop blur overlay.
+## 🚨 Edge-Case & Failure Mode Matrix
 
-### 2. OKLCH Perceptual Palette Generation
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-Always generate color schemes in OKLCH:
 
-- Background: `oklch(0.98 0.005 240)`
-- Foreground: `oklch(0.18 0.01 240)`
-- Accent: `oklch(0.62 0.22 250)`
+## 🤖 LLM-Specific Traps Table
 
-### 3. GSAP / Motion Engineering Integration
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **Uncontrolled Re-render Loop** | Mutating state inside render bodies or omitting hook dependencies | Wrap effects with explicit deps and isolate reactive derivations in useMemo |
+| **Accessibility Neglect** | Interactive <div> without role="button", tabIndex, or onKeyDown | Use semantic <button> or provide ARIA role, keyboard handlers, and focus ring |
+| **Layout Shift Flash** | Images/dynamic content without aspect-ratio or explicit dimensions | Enforce aspect-ratio or skeleton placeholders to guarantee zero CLS |
 
-When animation is requested, use explicit GSAP timelines with custom easing curves (`power3.out`, `expo.out`), avoiding default linear transitions.
 
-### 4. Zero Output Truncation
+## 🏛️ Tribunal Verification & Guardrails
 
-Never output placeholder `// TODO: add remaining items` comments in UI code. Generate full, production-ready JSX/CSS markup.
+**Active Reviewers:** `frontend-reviewer` · `type-safety` · `ui-ux-auditor` · `complexity-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
+
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
+
+### ✅ Pre-Flight Self-Audit Checklist
+```
+✅ Are all component props strictly typed with zero implicit "any"?
+✅ Are responsive breakpoints, fluid typography, and optical balance verified?
+✅ Is accessibility (ARIA labels, keyboard navigation, contrast ratio >= 4.5:1) validated?
+✅ Are re-renders minimized and state lifecycles cleanly separated?
+✅ Did I verify all imported UI components and icon sets actually exist?
+```
+
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/graph-engineering/SKILL.md

@@ -1,28 +1,116 @@
 ---
 name: graph-engineering
-description: "Use when orchestration planning requires a strict Directed Acyclic Graph (DAG) for managing complex dependencies between tasks."
-version: 1.0.0
-last-updated: 2026-09-25
+description: "Use when designing, compiling, and executing Directed Acyclic Graphs (DAGs) for multi-agent workflows, data pipelines, build systems, and dependency resolution. Enforces cycle detection, topological sorting, and parallel wave execution."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
-  - subagent-driven-development
+  - agent-organizer
+  - system-design-pro
 tools: Read, Grep, Glob, Bash, Edit, Write
 scripts-binding:
   - .agent/scripts/swarm_dispatcher.js
+  - .agent/scripts/verify_all.js
+  - .agent/scripts/lint_runner.js
 ---
 
-# Graph Engineering (DAG Workflow)
+# Graph Engineering — DAG Orchestration & Topological Execution
 
-## Context
-Standard agent workflows are linear pipelines (Maker -> Reviewer -> Human). But complex tasks (like migrating a database AND updating the frontend) have parallelizable steps with strict choke-points. 
+## Activation Boundaries
+- **Activate when:** Use when designing, compiling, and executing Directed Acyclic Graphs (DAGs) for multi-agent workflows, data pipelines, build systems, and dependency resolution. Enforces cycle detection, topological sorting, and parallel wave execution.
+- **DO NOT activate when:** The task falls outside the `graph-engineering` domain or is managed by a different dedicated specialist agent.
 
-## The DAG Strategy
-The `swarm_dispatcher.js` supports `--mode dag` for processing tasks mapped as a Topological Directed Acyclic Graph.
 
-1. **Node Definition**: Every task is a Node.
-2. **Edges (Dependencies)**: Tasks explicitly declare their dependencies (`dependsOn: ['task_1']`).
-3. **Parallel Execution**: Any nodes with no unresolved dependencies are executed simultaneously (`Promise.allSettled`).
-4. **Cascade Failures**: If `task_1` fails, any task dependent on it is marked `SKIPPED`. The DAG continues executing unrelated branches.
+## 🔁 Multi-Pass Execution Protocol
 
-## Anti-Patterns
-- ❌ **Forcing a DAG**: Do not use DAG orchestration for a simple one-file bug fix. Linear execution is safer and faster.
-- ❌ **Circular Dependencies**: The Planner Agent must ensure that Task A does not depend on Task B while Task B depends on Task A. 
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
+
+
+## Mandatory Pre-Flight Context Inspection
+1. **Cycle Detection**: Verify graph is strictly acyclic; circular dependencies cause permanent deadlocks.
+2. **Topological Order**: Sort tasks so every dependency executes and completes before dependent tasks launch.
+3. **Parallel Wave Grouping**: Group tasks with in-degree 0 into simultaneous execution waves.
+4. **State Transmission**: Ensure edge outputs pass structured payloads conforming to target node input schemas.
+5. **Failure Propagation**: Define node failure behavior: abort entire graph, skip downstream dependents, or fallback.
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+### 1. Topological Sorting & Parallel Wave Partitioning (Kahn's Algorithm)
+```typescript
+export interface TaskNode {
+  id: string;
+  dependencies: string[]; // List of task IDs that must complete first
+  execute: () => Promise<void>;
+}
+
+export function computeExecutionWaves(tasks: TaskNode[]): TaskNode[][] {
+  const inDegree = new Map<string, number>();
+  const graph = new Map<string, string[]>();
+
+  tasks.forEach(t => {
+    inDegree.set(t.id, t.dependencies.length);
+    graph.set(t.id, []);
+  });
+
+  tasks.forEach(t => {
+    t.dependencies.forEach(dep => {
+      graph.get(dep)?.push(t.id);
+    });
+  });
+
+  const waves: TaskNode[][] = [];
+  let remaining = new Set(tasks.map(t => t.id));
+
+  while (remaining.size > 0) {
+    const currentWaveIds = Array.from(remaining).filter(id => inDegree.get(id) === 0);
+    if (currentWaveIds.length === 0) {
+      throw new Error('Cycle detected in task dependency graph! Execution deadlocked.');
+    }
+
+    const currentWave = tasks.filter(t => currentWaveIds.includes(t.id));
+    waves.push(currentWave);
+
+    currentWaveIds.forEach(id => {
+      remaining.delete(id);
+      graph.get(id)?.forEach(dependent => {
+        inDegree.set(dependent, (inDegree.get(dependent) || 1) - 1);
+      });
+    });
+  }
+
+  return waves;
+}
+```
+
+## 🚨 Edge-Case & Failure Mode Matrix
+
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Circular Dependency Deadlock** | Node A depends on B, B depends on A; execution stalls indefinitely | Run Kahn's cycle check at compile time before launching any tasks |
+| **Cascading Pipeline Abort** | A non-critical leaf node failure aborts completely unrelated parallel work | Classify node failures as CRITICAL (aborts wave) or OPTIONAL (logs warning, continues) |
+
+## 🏛️ Tribunal Verification & Guardrails
+
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
+
+- **Active Reviewers:** `orchestrator`, `system-architect`
+- **Evidence Standard:** Mark all node states as `[OBSERVED]` execution outputs or `[INFERRED]` dependencies.
+
+## 🤖 LLM-Specific Traps Table
+
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **Hallucinated Tool Capabilities** | Assuming an external library or CLI command exists without verification | Run a verification check or verify package.json before referencing tools |
+| **Premature Completion Claim** | Declaring a task finished because code was generated without verification | Execute tests, linters, or terminal commands to provide concrete proof |
+| **Context Bloat Dumping** | Pasting entire multi-thousand-line files into prompt context | Extract targeted excerpts, symbols, and signatures to preserve tokens |