tribunal-kit 5.8.4 → 6.0.0

package/.agent/skills/colorize/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: colorize
 description: Introduce strategic, harmonious, accessible color systems and OKLCH color palettes to visually flat or dull interfaces.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Color Systems & Palette Engineering
-  tier: pro
-  co-requires: [better-colors, frontend-design]
-  trigger-signals:
-    strong: [colorize, color system, OKLCH palette, introduce color, color palette generator, UI color tokens]
-    weak: [add color, theme colors]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - better-colors
+  - baseline-ui
+  - better-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Colorize — Color System & OKLCH Palette Design
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing color systems or applying color palettes, you MUST inspect:
+1. OKLCH Color Space (Section 24) → Use `oklch(L C H)` custom properties for uniform perceptual lightness across light/dark themes
+2. 60-30-10 Budget Rule (Section 39) → 60% Dominant Neutral (surfaces), 30% Structural Secondary (text/borders), 10% Intentional Accent (actions)
+3. Status Token Uniformity (Section 45) → Keep status color lightness consistent ($L \approx 0.60$–$0.72$) across Success, Warning, Destructive, and Info scales
+
 Architect uniform, perceptually balanced color scales using the modern OKLCH color space for light and dark modes.
 
 ---

package/.agent/skills/compact-landing/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: compact-landing
 description: Build compact, premium landing pages with clear CTA hierarchy, quiet typography, restrained visual noise, and high conversion flow.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Compact Landing Page & Minimalist UI
-  tier: pro
-  co-requires: [landing-page, quieter, baseline-ui]
-  trigger-signals:
-    strong: [compact-landing, compact landing page, quiet typography, minimal landing page, restrained UI, high-conversion compact]
-    weak: [simple landing, compact page]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - landing-page
+  - quieter
+  - baseline-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Compact Landing — Premium Minimalist Landing Pages
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before engineering compact landing pages, you MUST inspect:
+1. Viewport Fit (Section 24) → Fit hero, preview, and primary CTA inside a single 1080p desktop viewport without initial scrolling
+2. Section Limit (Section 35) → Limit total page structure to max 4 tight sections (Hero, Social Proof, 3-Benefit Grid, Footer Card)
+3. Typography Restraint (Section 30) → Cap display font sizes at `clamp(1.75rem, 4vw, 2.75rem)` and apply `text-wrap: balance`
+
 Build tight, ultra-focused, high-converting landing pages that deliver value quickly without unnecessary multi-scroll filler.
 
 ---

package/.agent/skills/company-logos/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: company-logos
 description: Social proof rows, logo grids, customer carousels, and trust badges layout rules for balanced visual weight and responsive alignment.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Visual Layout & Social Proof
-  tier: pro
-  co-requires: [baseline-ui, landing-page]
-  trigger-signals:
-    strong: [company-logos, logo grid, social proof row, trust badges, customer logos, logo carousel]
-    weak: [logos layout, client logos]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - baseline-ui
+  - landing-page
+  - marquee-loop
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Company Logos — Social Proof & Trust Grids
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before designing logo grids or trust rows, you MUST inspect:
+1. Optical Weight Normalization rules (Section 24) → Enforce bounding box limits (`max-height: 28px`, `max-width: 120px`) with `object-fit: contain`
+2. Monochromatic Harmonization rules (Section 29) → Render all logos in monochromatic SVG fill (`fill="currentColor"`) matching `--text-muted`
+3. Hover States → Transition opacity to 100% smoothly over `200ms` on hover
+
 Architect balanced, optically aligned logo rows and trust grids that communicate credibility without visual clutter.
 
 ---

package/.agent/skills/config-validator/SKILL.md

@@ -1,15 +1,29 @@
 ---
 name: config-validator
 description: Configuration validation and workspace self-auditing mastery. Verifying .agent directory integrity, checking JSON schemas, resolving broken pointers to missing scripts/skills, validating environment states, and enforcing configuration constraints before execution. Use when loading settings, modifying manifests, or diagnosing system configuration rot.
-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:
+  - lint-and-validate
+  - backend-security-expert
+  - clean-code
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Config Validator — System Integrity Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before parsing or mutating configuration files or environment variables, you MUST inspect:
+1. Fail-Fast Boundary Parsing (Section 25) → Validate configurations at startup boundary via Zod schema (`ConfigSchema.parse()`); fail fast on invalid configs
+2. Referential Integrity Audit (Section 60) → Audit referenced assets (scripts, SKILL.md, workflow paths) for physical existence before execution
+3. Atomic File Writes (Section 111) → Write updated configs to `.tmp` files and perform OS atomic rename to prevent file corruption during crashes
+
 ## Hallucination Traps (Read First)
 
 - ❌ Silently using default values for missing config -> ✅ Fail fast with a clear error message naming the missing field

package/.agent/skills/containerization-pro/SKILL.md

@@ -1,18 +1,29 @@
 ---
 name: containerization-pro
 description: Production-grade containerization mastery. Multi-stage Dockerfiles for Node.js/Python/Rust/Go, image hardening (non-root, distroless, read-only FS), BuildKit layer caching, multi-platform builds (docker buildx), Docker Compose for local dev, container security scanning (Trivy/Grype), and AWS ECR workflows. Use when containerizing applications, optimizing Docker builds, or setting up container registries.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-06-21
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
-routing:
-  domain: devops
-  tier: pro
-  co-requires: [cicd-pro]
-  trigger-signals:
-    strong: [multi-stage build, BuildKit, ECR, Trivy, image hardening, Docker Compose]
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - devops-engineer
+  - cicd-pro
+  - cloud-architect
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
+# Containerization Pro — Production-Grade Docker Mastery
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before writing Dockerfiles or containerizing applications, you MUST inspect:
+1. Dockerignore Prerequisite (Section 29) → Create a strict `.dockerignore` file before writing any Dockerfile to prevent leaking `node_modules`, `.env`, `.git`
+2. Non-Root Security User (Section 81) → Create and switch to a dedicated non-root user (`USER appuser`) in the final runtime stage
+3. Deterministic Dependency Installation (Section 19) → Use `npm ci --omit=dev` (or language lockfile equivalent); ban un-pinned `npm install`
+
 ## Hallucination Traps (Read First)
 
 - ❌ `FROM node:22` → ✅ `FROM node:22-alpine` (1GB+ vs ~150MB). Always use slim/alpine variants.

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

@@ -1,20 +1,29 @@
 ---
 name: create-design-md
 description: Create or update a DESIGN.md from an existing product repository or public website, with evidence-based design tokens and guidance. Use when asked to document an interface's design language, reconstruct its visual system, extract design tokens, or give coding agents persistent UI context.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: UI Craft & Design Engineering
-  tier: pro
-  co-requires: [extract-design-system, frontend-design]
-  trigger-signals:
-    strong: [create-design-md, DESIGN.md, extract design tokens, document design language, visual system documentation]
-    weak: [design tokens, theme docs]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - baseline-ui
+  - better-ui
+  - better-colors
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Create DESIGN.md — Evidence-Based Design System Specification
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before extracting design tokens or authoring `DESIGN.md`, you MUST inspect:
+1. Operating Mode (Section 22) → Choose Repository Mode (scan `globals.css` / `theme.ts` / primitives) or URL Mode (3-proof observation)
+2. Contract Schema (Section 41) → Enforce strict 5-section layout (Identity, Colors, Typography, Spacing/Geometry, Motion)
+3. Read-Only Safety (Section 86) → NEVER mutate product source code while extracting tokens or creating `DESIGN.md`
+
 Generate or update an authoritative `DESIGN.md` file for a product repository or website by extracting verified design tokens, components, and layout guidance.
 
 ---

package/.agent/skills/critique/SKILL.md

@@ -1,20 +1,29 @@
 ---
 name: critique
 description: Evaluate design quality with structured UX scoring, heuristic analysis, and persona-based usability checks. Use when asked to critique, evaluate, grade, or audit a UI design before implementation.
-version: 1.0.0
-last-updated: 2026-07-22
-applies-to-model: gemini-3-6-flash, claude-3-7-sonnet
-routing:
-  domain: Design Evaluation & Usability Scoring
-  tier: pro
-  co-requires: [ui-ux-researcher, web-design-guidelines]
-  trigger-signals:
-    strong: [critique, grade UI, evaluate design, UX scoring, heuristic audit, design feedback]
-    weak: [review UI, UX feedback]
+version: 3.0.0
+last-updated: 2026-07-30
+skills:
+  - ui-ux-researcher
+  - web-design-guidelines
+  - baseline-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/checklist.js
+  - .agent/scripts/verify_all.js
 ---
 
 # Critique — Structured UX & Design Quality Evaluation
 
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before evaluating UI designs or code, you MUST inspect:
+1. Target UI screen / component → Grade across the 6 UX Critique Heuristics (Clarity, IA, Interactions, Visual Craft, Accessibility, Resilience)
+2. Required Scorecard Format (Section 51) → Output overall quality score (0-10) and tabular domain breakdown
+3. Top 3 Actionable Fixes → Group recommendations by priority (High, Medium, Low) with concrete CSS/JSX fixes
+
 Evaluate interfaces against 6 core usability heuristics and produce an objective design scorecard with prioritized recommendations.
 
 ---

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.