tribunal-kit 5.8.4 → 6.0.0

package/.agent/skills/distill/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: distill
 description: Simplify noisy interfaces by removing non-essential visual and operational complexity. Use when a UI has too many options, crowded toolbars, redundant text, or unnecessary visual containers.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: UX Simplification & Reduction
-  tier: pro
-  co-requires: [quieter, clarify, baseline-ui]
-  trigger-signals:
-    strong: [distill, simplify ui, declutter, remove complexity, streamline interface, too crowded]
-    weak: [clean up, simplify options]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - quieter
+  - clarify
+  - baseline-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Distill — UX Simplification & Decluttering
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before decluttering UI layouts, you MUST inspect:
+1. Active screen components → Identify core primary user task and secondary/tertiary options
+2. Container Reduction rules (Section 25) → Replace nested card containers and redundant borders with whitespace grid gaps
+3. Progressive Disclosure patterns (Section 30) → Move advanced parameters into collapsible accordions or popovers
+
 Systematically strip away visual clutter, redundant controls, and cognitive friction to reveal the core user task.
 
 ---

package/.agent/skills/documentation-templates/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: documentation-templates
 description: Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-03-12
-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:
+  - readme-builder
+  - geo-fundamentals
+  - clean-code
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Documentation Standards
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before creating or editing documentation, API references, or comments, you MUST inspect:
+1. Target Audience Identification (Section 27) → Match template strictly to audience (README for 10-min quickstart, API docs for payload contracts, Runbook for on-call triage)
+2. Explain "Why", Not "What" in Code Comments (Section 147) → Document non-obvious business rules or bug workarounds; ban restating obvious code syntax
+3. AI-Friendly Documentation Mapping (Section 171) → Maintain `ARCHITECTURE.md` and `@purpose:` annotations for codebase mental models and automated ingestion
+
 ## Hallucination Traps (Read First)
 
 - ❌ Writing documentation that only AI-generated code can understand -> ✅ Docs are for HUMANS; use clear language and real examples

package/.agent/skills/domain-modeling/SKILL.md

@@ -1,20 +1,31 @@
 ---
 name: domain-modeling
 description: Builds and sharpens project domain models, ubiquitous language, entity relationships, and bounded contexts before writing code.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Domain Driven Design & Business Modeling
-  tier: pro
-  co-requires: [architecture, codebase-design]
-  trigger-signals:
-    strong: [domain-modeling, ubiquitous language, bounded context, aggregate root, domain entity, business logic model]
-    weak: [model data, data entities]
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - architecture
+  - codebase-design
+  - database-design
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Domain Modeling — Ubiquitous Language & Bounded Contexts
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing domain entities or business modeling, you MUST inspect:
+1. Ubiquitous Language Uniformity (Section 25) → Standardize 1 explicit term across UI, code, and DB (e.g. Customer vs User); ban interchangeable synonyms
+2. Bounded Context Separation (Section 30) → Isolate models per context (e.g. Inventory Product vs Catalog Product); ban 60-column monolithic entities
+3. Aggregate Root Invariants (Section 34) → Mutate child entities strictly through Aggregate Root methods (`order.addItem(...)`); ban direct child mutations
+
+# Domain Modeling — Ubiquitous Language & Bounded Contexts
+
 Model business domain concepts cleanly before committing to database schemas or API signatures.
 
 ---

package/.agent/skills/edge-computing/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: edge-computing
 description: Edge computing mastery. Cloudflare Workers, Vercel Edge Functions, Durable Objects, edge-compatible data patterns, cold start elimination, caching policies (Stale-While-Revalidate), and global data locality. Use when designing globally distributed, extreme low-latency applications architectures.
-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:
+  - nextjs-react-expert
+  - local-first-architecture
+  - backend-security-expert
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Edge Computing — Global Latency Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering edge computing handlers or Cloudflare Workers, you MUST inspect:
+1. Edge Runtime Restrictions (Section 25) → Strictly ban Node.js native core modules (`fs`, `child_process`, native `bcrypt`); use Web APIs (`fetch`, `crypto.subtle`)
+2. Stale-While-Revalidate Caching (Section 47) → Use `Cache-Control: s-maxage=60, stale-while-revalidate=86400` and asynchronous `ctx.waitUntil()` cache puts
+3. Edge Database Access (Section 81) → Never open direct raw TCP connections to DBs; use HTTP connection poolers (Prisma Accelerate, LibSQL, Supabase Pooler)
+
 ## Hallucination Traps (Read First)
 
 - ❌ Importing Node.js-only APIs (fs, net, child_process) in edge functions -> ✅ Edge runtime has NO Node.js APIs; use Web APIs only

package/.agent/skills/emil-design-eng/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: emil-design-eng
 description: Encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great. Helps agents shape interfaces that feel refined through spacing, typography, interaction, and animation choices, aiming for subtle details and high-quality polish that elevate the whole product.
-version: 1.0.0
-last-updated: 2026-06-26
-applies-to-model: gemini-3-1-pro, claude-3-7-sonnet
-routing:
-  domain: frontend
-  tier: pro
-  co-requires: [frontend-design, motion-engineering]
-  trigger-signals:
-    strong: [emil, kowalski, design engineering, interface craft, ui polish, micro-interactions, animations.dev, craft sensibility]
-    weak: [animations, feel right, ui polish, subtle details]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - apple-design
+  - motion-engineering
+  - 60fps-animation
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Design Engineering
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing or reviewing UI micro-animations, you MUST inspect:
+1. Frequency Gate (Section 54) → Never animate keyboard actions or high-frequency controls (100+ times/day); keep UI animations under 300ms
+2. Easing Rule (Section 75) → Use strong `ease-out` (`cubic-bezier(0.23, 1, 0.32, 1)`) for entering UI elements; ban `ease-in`
+3. Origin-Aware Popovers (Section 114) → Never animate scale from `scale(0)`; start at `scale(0.95)` with origin bound to trigger coordinates
+
 ## Initial Response
 
 When this skill is first invoked without a specific question, respond only with:

package/.agent/skills/error-resilience/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: error-resilience
 description: Error resilience and fault tolerance mastery. Retry strategies (exponential backoff with jitter), circuit breakers, bulkheads, graceful degradation, React error boundaries, dead letter queues, timeout patterns, fallback chains, and idempotent error recovery. Use when building fault-tolerant systems, handling flaky external services, or preventing cascading failures.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-04-17
-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
+  - backend-security-expert
+  - observability
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Error Resilience — Fault-Tolerant Systems
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before writing retry logic, circuit breakers, or error handling routines, you MUST inspect:
+1. Idempotency Key Rule for Retries (Section 123) → Require explicit idempotency keys when retrying non-safe operations (POST/PUT); ban un-keyed retries
+2. Exponential Backoff with Jitter (Section 106) → Implement randomized full jitter with capped exponential delays; ban fixed-delay retry loops
+3. Operational vs Programmer Error Split (Section 28) → Catch and recover strictly from `OperationalError` instances; allow programmer bugs (`TypeError`) to crash fast
+
 ## Hallucination Traps (Read First)
 
 - ❌ Retrying non-idempotent operations (POST payments) without idempotency keys -> ✅ Always require idempotency keys for non-safe HTTP methods before retrying

package/.agent/skills/extract-design-system/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: extract-design-system
 description: Design system extraction and tokenization mastery. Identifying repeated HTML/CSS patterns, extracting CSS variables, generating design tokens (colors, spacing, typography), building reusable component schemas, and standardizing ad-hoc styles into cohesive global systems. Use when refactoring messy CSS into a unified design system.
-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:
+  - create-design-md
+  - tailwind-patterns
+  - baseline-ui
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Extract Design System — Tokenization Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before extracting design systems or tokenizing CSS variables, you MUST inspect:
+1. 3+ Repetition Frequency Rule (Section 15) → Only tokenize values that recur 3+ times across components to prevent variable bloat
+2. Semantic Naming Convention (Section 17) → Use functional/semantic names (`--color-primary`) rather than literal colors (`--red-500`)
+3. Accessibility Token Contract (Section 110) → Ensure extracted text and surface tokens satisfy a min 4.5:1 WCAG AA contrast ratio
+
 ## Hallucination Traps (Read First)
 
 - ❌ Creating CSS variables for every possible value -> ✅ Only tokenize values that appear 3+ times across components

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,33 +1,44 @@
 ---
 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.
 
 ---
 
-## 1. Priority Priority Matrix
+## 1. Priority Priority Matrix (WCAG 2.2 AA)
 
 | Priority | Category | Critical Requirements |
 | --- | --- | --- |
 | **P1** | **Accessible Names** | Every icon button MUST have `aria-label` or `aria-labelledby`. Decorative icons MUST have `aria-hidden="true"`. |
 | **P2** | **Keyboard Access** | All interactive controls MUST be reachable and operable via `Tab` / `Shift+Tab`, `Space`, `Enter`. NEVER use `<div>` or `<span>` as clickable elements without `role="button"`, `tabIndex={0}`, and key handlers. |
-| **P3** | **Focus & Dialogs** | Modals/Dialogs MUST trap focus within the dialog container while open, return focus to trigger on close, and dismiss on `Escape`. |
-| **P4** | **Color Contrast** | Text MUST satisfy WCAG AA 4.5:1 ratio (3.0:1 for large text). Focus rings MUST have at least 3.0:1 contrast against adjacent background. |
-| **P5** | **Form Validation** | Inputs MUST have explicit `<label>` or `aria-labelledby`. Errors MUST use `aria-invalid="true"` and `aria-describedby` pointing to error text. |
+| **P3** | **Focus & Dialogs (SC 2.4.11)** | Modals/Dialogs MUST trap focus within the dialog container while open, return focus on close, dismiss on `Escape`, and ensure focused items are **never fully obscured by sticky headers/footers**. |
+| **P4** | **Focus Appearance (SC 2.4.13)** | Focus indicators MUST be clearly visible (`:focus-visible`), achieve at least **3:1 contrast** against adjacent background, and have a min **2px thickness**. |
+| **P5** | **Target Size (SC 2.5.8)** | Interactive controls MUST measure at least **24x24 CSS pixels** (min **44x44px** recommended for mobile touch targets) or have sufficient non-intersecting spacing. |
+| **P6** | **Color & Contrast** | Text MUST satisfy WCAG AA 4.5:1 ratio (3.0:1 for large text). Color alone MUST NOT be the only indicator of state or error. |
+| **P7** | **Form Validation** | Inputs MUST have explicit `<label>` or `aria-labelledby`. Errors MUST use `aria-invalid="true"` and `aria-describedby` pointing to error text. |
 
 ---
 

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)