tribunal-kit 5.8.5 → 6.0.0

package/.agent/skills/csharp-developer/SKILL.md

@@ -1,19 +1,33 @@
 ---
 name: csharp-developer
 description: Senior C#/.NET developer with mastery of .NET 9+, C# 13, ASP.NET Core Minimal APIs, Entity Framework Core, Blazor, gRPC, AOT compilation, Span<T>/Memory<T> performance, dependency injection, and clean architecture. Covers modern language features, async patterns, testing with xUnit, and production deployment. Use when building .NET applications, APIs, or any C# code.
-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:
+  - clean-code
+  - database-design
+  - api-patterns
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # C# / .NET Pro — .NET 9+ & C# 13 Mastery
 
 ---
 
+## Mandatory Pre-Flight Context Inspection
+
+Before writing C# code or ASP.NET Minimal APIs, you MUST inspect:
+1. CancellationToken Propagation (Section 191) → Always pass `CancellationToken ct` to async methods and EF Core queries
+2. Database-Level Projection (Section 283) → Project queries to DTOs using `.Select(...)` BEFORE `.ToListAsync()` to avoid N+1 and memory overhead
+3. Non-Blocking Async Invocations (Section 355) → Always `await` async tasks; strictly ban `.Result` or `.Wait()` to prevent thread deadlocks
+
+# C# / .NET Pro — .NET 9+ & C# 13 Mastery
+
+---
+
 ## Modern C# Language Features
 
 ### Records & Primary Constructors

package/.agent/skills/data-validation-schemas/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: data-validation-schemas
 description: Data validation and schema design mastery. Zod, Yup, Joi, Valibot, and Pydantic schema design, runtime type checking, API boundary validation, form validation patterns, DTO design, schema composition, error message formatting, schema evolution strategies, and coercion rules. Use when validating user input, API payloads, environment config, or any data crossing a trust boundary.
-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:
+  - api-patterns
+  - backend-security-expert
+  - schema-reviewer
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Data Validation & Schemas — Trust No Input
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing schemas or parsing untrusted data boundaries, you MUST inspect:
+1. Universal Trust Boundary Rule (Section 25) → Enforce explicit Zod/Pydantic schemas on API bodies, query params, env vars, and webhooks
+2. Server-Side Mandatory Validation (Section 16) → Never rely solely on client-side UX validation; execute schema validation on the server
+3. Environment Startup Parse (Section 173) → Parse `process.env` with Zod at app startup to crash immediately on missing keys
+
 ## Hallucination Traps (Read First)
 
 - ❌ Using `z.any()` or `z.unknown()` as a lazy escape hatch -> ✅ Always define the actual shape; `any` defeats the purpose of validation

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

@@ -1,17 +1,31 @@
 ---
 name: database-design
 description: Database design mastery. Schema design with normalization, denormalization strategies, indexing, migration pipelines, ORM selection (Prisma/Drizzle/SQLAlchemy/EF Core), connection pooling, soft deletes, audit trails, multi-tenancy, and serverless database patterns. Use when designing schemas, choosing databases, planning migrations, or architecting data layers.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 3.1.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:
+  - supabase-postgres-best-practices
+  - sql-pro
+  - db-latency-auditor
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Database Design — Schema & Architecture Mastery
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing schemas or writing SQL migrations, you MUST inspect:
+1. Timezone Timestamp Standard (Section 17) → Use `TIMESTAMPTZ` for all timestamp columns; ban bare `TIMESTAMP`
+2. Primary Key Index Performance (Section 18) → Use `BIGINT GENERATED ALWAYS AS IDENTITY` or UUID v7 (time-ordered); ban random UUID v4 as primary key
+3. Foreign Key Indexing (Section 19) → Create explicit indexes on all foreign key columns (`CREATE INDEX idx_... ON table(fk_id)`) to prevent full table scans during cascading deletes
+
+# Database Design — Schema & Architecture Mastery
+
 ## Hallucination Traps (Read First)
 
 - ❌ `TIMESTAMP` → ✅ Always `TIMESTAMPTZ` (with timezone). `TIMESTAMP` is ambiguous across timezones.

package/.agent/skills/delight/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: delight
 description: Inject micro-moments of delight, subtle surprise interactions, personality, and tactile feedback into user interfaces. Use when building success celebrations, copy-to-clipboard feedback, empty states, or playful UI elements.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Micro-Delight & Interactive Polish
-  tier: pro
-  co-requires: [whimsy-injector, micro-interaction, emil-design-eng]
-  trigger-signals:
-    strong: [delight, micro-delight, make it playful, add personality, surprise animation, tactile feedback]
-    weak: [sparkle, fun ui, success feedback]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - whimsy-injector
+  - micro-interaction
+  - accessible-animation
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Delight — Micro-Moments of Tactile UI Polish
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before implementing micro-delight moments, you MUST inspect:
+1. Action frequency context → Keep high-frequency delight (performed 50+ times/day) under 100ms and non-intrusive
+2. `prefers-reduced-motion` CSS media query → Provide fallback states for particle bursts and spring animations
+3. Morphing State Checkmark rules (Section 24) → Hold confirmation icon for 1.5s before smoothly morphing back
+
 Elevate everyday digital interactions with subtle, memorable details that make software a joy to use.
 
 ---

package/.agent/skills/deployment-procedures/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: deployment-procedures
 description: Production application deployment mastery. Zero-downtime deployment strategies (Blue/Green, Rolling updates), Container orchestration (Docker/ECS), CI/CD pipelines, secrets injection, database migration safety, health checks, and rollback contingencies. Use when moving code from development to production 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:
+  - devops-engineer
+  - cicd-pro
+  - server-management
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Deployment Procedures — Production Execution Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before deploying application releases or database migrations, you MUST inspect:
+1. Expand-and-Contract DB Migrations (Section 104) → Migrate schema FIRST (expand/copy data), then deploy code SECOND, contract legacy columns THIRD
+2. Instant Rollback Contingency (Section 116) → Tag every Docker image with Git SHA (`myapp:a1b2c3d`) for split-second image swaps during failure
+3. Zero-Downtime Traffic Switching (Section 29) → Use Blue/Green or Rolling updates with active health check verification before draining old instances
+
 ## Hallucination Traps (Read First)
 
 - ❌ Running database migrations and code deploy in the same step -> ✅ Migrate FIRST, deploy code SECOND (expand-and-contract)

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

@@ -1,20 +1,31 @@
 ---
 name: design-lab
 description: Interactive design exploration workflow: conduct interviews, generate variants, and refine UI designs through user feedback loops.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Design Exploration & UI Variants
-  tier: pro
-  co-requires: [brainstorming, shape, frontend-design]
-  trigger-signals:
-    strong: [design-lab, design exploration, generate variants, interactive design workflow, UI experiment]
-    weak: [explore designs, design options]
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - brainstorming
+  - shape
+  - frontend-design
+scripts-binding:
+  - .agent/scripts/auto_preview.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Design Lab — Interactive Design Exploration & Variants
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before generating design variants or conducting design experiments, you MUST inspect:
+1. Structural Variant Difference Rule (Section 39) → Ensure generated layout variants are structurally distinct; ban micro-variations (differing only by 1px or hex color)
+2. Interactive Refinement Protocol (Section 32) → Ask targeted constraint questions before outputting final component implementations
+3. Visual Hierarchy Mapping (Section 26) → Map visual hierarchy explicitly to project design tokens before presenting options
+
+# Design Lab — Interactive Design Exploration & Variants
+
 Conduct rapid design experiments, explore multiple structural variants, and iteratively refine interfaces with feedback.
 
 ---

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

@@ -1,19 +1,33 @@
 ---
 name: devops-engineer
 description: DevOps engineering mastery. Docker containerization, Docker Compose, CI/CD with GitHub Actions, Kubernetes basics, infrastructure as code (Terraform), monitoring/alerting, deployment strategies (blue/green, canary, rolling), secrets management, and production readiness checklists. Use when building CI/CD pipelines, containerizing apps, or managing infrastructure.
-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:
+  - cicd-pro
+  - containerization-pro
+  - cloud-architect
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # DevOps Engineer — CI/CD & Infrastructure Mastery
 
 ---
 
+## Mandatory Pre-Flight Context Inspection
+
+Before building Dockerfiles, Docker Compose, or GitHub Actions pipelines, you MUST inspect:
+1. Non-Root Docker Container Rule (Section 47) → Explicitly specify a non-root user (`USER appuser`) in production Dockerfiles
+2. Deterministic Package Installation (Section 28) → Use `npm ci` (or yarn/pnpm equivalent with lockfiles) in Docker and CI; ban `npm install`
+3. CI/CD Concurrency Group Cancellation (Section 142) → Configure `concurrency.cancel-in-progress: true` on PR workflows to cancel stale builds
+
+# DevOps Engineer — CI/CD & Infrastructure Mastery
+
+---
+
 ## Docker
 
 ### Dockerfile (Production-Ready)

package/.agent/skills/devops-incident-responder/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: devops-incident-responder
 description: Production incident response mastery. MTTR (Mean Time to Recovery) reduction, blameless post-mortems, rapid triaging, halting systemic cascading failures, isolating problematic deployments, and evidence-based forensic analysis. Use when stabilizing broken systems, fighting active production fires, or conducting root-cause post-mortems.
-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:
+  - devops-engineer
+  - error-resilience
+  - observability
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Incident Responder — Production Stabilization Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before responding to production outages or performing incident triage, you MUST inspect:
+1. Stabilization-First Rule (Section 25) → Immediately rollback/mitigate first (revert commit, flip flag, shed load); perform root cause analysis AFTER system is stable
+2. Circuit Breaker Severance (Section 42) → Sever failing downstream dependencies immediately to prevent cascading overload across the system
+3. Triage Hierarchy (Section 73) → Analyze metrics (what) → traces (where) → logs (why) sequentially to pinpoint root causes
+
 ## Hallucination Traps (Read First)
 
 - ❌ Changing code during an active incident -> ✅ STABILIZE first (rollback, feature flag, traffic shift), investigate AFTER

package/.agent/skills/diagnosing-bugs/SKILL.md

@@ -1,20 +1,31 @@
 ---
 name: diagnosing-bugs
 description: Systematic bug diagnosis methodology for hard bugs: Phase 1 (Build feedback loop), Phase 2 (Reproduce + minimise), Phase 3 (Hypothesise), Phase 4 (Instrument), Phase 5 (Fix + regression test), Phase 6 (Cleanup + post-mortem).
-version: 2.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Systematic Debugging & Root Cause Isolation
-  tier: pro
-  co-requires: [systematic-debugging, test-result-analyzer]
-  trigger-signals:
-    strong: [diagnosing-bugs, systematic bug diagnosis, reproduce bug, root cause isolation, intermittent bug, debug protocol, hard bugs]
-    weak: [fix bug, investigate error]
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - systematic-debugging
+  - test-result-analyzer
+  - tdd-workflow
+scripts-binding:
+  - .agent/scripts/test_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Diagnosing Bugs — A Discipline for Hard Bugs
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before attempting bug diagnostics or proposing code fixes, you MUST inspect:
+1. Red-Capable Feedback Loop Rule (Section 34) → Construct a fast, deterministic, automated feedback loop command that reproduces the bug (goes red) BEFORE making code edits
+2. Falsifiable Hypotheses Formulation (Section 107) → Formulate 3–5 falsifiable hypotheses (`"If X is cause, then Y prediction"`) before testing any single theory
+3. Tagged Debug Logging & Cleanup (Section 123) → Tag debug log instrumentation (`[DEBUG-id]`) and sweep clean before finalizing regression fixes
+
+# Diagnosing Bugs — A Discipline for Hard Bugs
+
 A systematic discipline for hard bugs. Skip phases only when explicitly justified.
 
 When exploring the codebase, read `CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.

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