tribunal-kit 9.2.3 → 9.2.5

package/skills/colorize/SKILL.md

@@ -1,57 +1,57 @@
----
-name: colorize
-description: "Use when Introduce strategic, harmonious, accessible color systems and OKLCH color palettes to visually flat or dull interfaces."
-version: 5.0.0
-last-updated: 2026-09-13
-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
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
----
-
-## 4 Color System Principles
-
-### 1. Why OKLCH Over HSL/Hex
-
-- Traditional HSL suffers from perceptual lightness jumps (e.g. pure yellow `#FFFF00` at Lightness 50% looks blindingly bright compared to pure blue `#0000FF` at Lightness 50%).
-- OKLCH enforces constant perceptual lightness ($L$), predictable chroma ($C$), and hue angles ($H$).
-
-```css
-:root {
-  /* Primary Brand Scale in OKLCH: L C H */
-  --primary-50: oklch(0.97 0.02 250);
-  --primary-100: oklch(0.92 0.04 250);
-  --primary-500: oklch(0.6 0.18 250); /* Main Brand Color */
-  --primary-700: oklch(0.42 0.16 250);
-  --primary-900: oklch(0.24 0.1 250);
-}
-```
-
-### 2. The 60-30-10 Color Budget Rule
-
-- **60% Dominant Neutral**: Backgrounds, page canvas, card surfaces (`oklch(0.98 0.005 240)`).
-- **30% Structural Secondary**: Typography, borders, icons, navigation chrome (`oklch(0.20 0.01 240)`).
-- **10% Intentional Accent**: Primary actions, key badges, status confirmations (`oklch(0.60 0.18 250)`).
-
-### 3. Functional Status Color Tokens
-
-Never use random red/green/yellow hex codes. Maintain matching chroma and lightness across status semantic scales:
-
-- **Success**: `oklch(0.62 0.17 145)` (Emerald)
-- **Warning**: `oklch(0.72 0.16 75)` (Amber)
-- **Destructive**: `oklch(0.58 0.22 25)` (Coral Red)
-- **Info**: `oklch(0.62 0.16 240)` (Sky Blue)
+---
+name: colorize
+description: "Use when Introduce strategic, harmonious, accessible color systems and OKLCH color palettes to visually flat or dull interfaces."
+version: 5.0.0
+last-updated: 2026-09-13
+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
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+---
+
+## 4 Color System Principles
+
+### 1. Why OKLCH Over HSL/Hex
+
+- Traditional HSL suffers from perceptual lightness jumps (e.g. pure yellow `#FFFF00` at Lightness 50% looks blindingly bright compared to pure blue `#0000FF` at Lightness 50%).
+- OKLCH enforces constant perceptual lightness ($L$), predictable chroma ($C$), and hue angles ($H$).
+
+```css
+:root {
+  /* Primary Brand Scale in OKLCH: L C H */
+  --primary-50: oklch(0.97 0.02 250);
+  --primary-100: oklch(0.92 0.04 250);
+  --primary-500: oklch(0.6 0.18 250); /* Main Brand Color */
+  --primary-700: oklch(0.42 0.16 250);
+  --primary-900: oklch(0.24 0.1 250);
+}
+```
+
+### 2. The 60-30-10 Color Budget Rule
+
+- **60% Dominant Neutral**: Backgrounds, page canvas, card surfaces (`oklch(0.98 0.005 240)`).
+- **30% Structural Secondary**: Typography, borders, icons, navigation chrome (`oklch(0.20 0.01 240)`).
+- **10% Intentional Accent**: Primary actions, key badges, status confirmations (`oklch(0.60 0.18 250)`).
+
+### 3. Functional Status Color Tokens
+
+Never use random red/green/yellow hex codes. Maintain matching chroma and lightness across status semantic scales:
+
+- **Success**: `oklch(0.62 0.17 145)` (Emerald)
+- **Warning**: `oklch(0.72 0.16 75)` (Amber)
+- **Destructive**: `oklch(0.58 0.22 25)` (Coral Red)
+- **Info**: `oklch(0.62 0.16 240)` (Sky Blue)

package/skills/compact-landing/SKILL.md

@@ -1,50 +1,50 @@
----
-name: compact-landing
-description: "Use when Build compact, premium landing pages with clear CTA hierarchy, quiet typography, restrained visual noise, and high conversion flow."
-version: 5.0.0
-last-updated: 2026-09-13
-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
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
----
-
-## 4 Compact Landing Rules
-
-### 1. The Single Viewport Value Pitch
-
-- Above-the-fold content must answer 3 questions instantly within 1 single screen viewport:
-  1. _What is it?_ (Clear, un-hypey headline + subhead)
-  2. _What does it look like?_ (Crisp UI screenshot or interactive preview component)
-  3. _How do I get it?_ (Unambiguous primary CTA input/button)
-
-### 2. Quiet Typographic Hierarchy
-
-- Use subdued monochrome typography (`oklch(0.95 0.005 240)` background with `oklch(0.20 0.01 240)` body copy).
-- Keep display font sizes restrained (`clamp(1.75rem, 4vw, 2.75rem)`) rather than giant 5rem text blocks.
-
-### 3. Tight Spatial Grid
-
-- Limit total page section count to max 4 sections:
-  1. Hero + Primary CTA + Product Preview
-  2. Social Proof / Logo Bar
-  3. Feature Grid (3 core benefits max)
-  4. Conversion Footer Card
-
-### 4. Zero Unnecessary Visual Noise
-
-- Omit decorative background shapes, floating 3D spheres, and rainbow gradients. Let contrast and typography drive visual quality.
+---
+name: compact-landing
+description: "Use when Build compact, premium landing pages with clear CTA hierarchy, quiet typography, restrained visual noise, and high conversion flow."
+version: 5.0.0
+last-updated: 2026-09-13
+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
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+---
+
+## 4 Compact Landing Rules
+
+### 1. The Single Viewport Value Pitch
+
+- Above-the-fold content must answer 3 questions instantly within 1 single screen viewport:
+  1. _What is it?_ (Clear, un-hypey headline + subhead)
+  2. _What does it look like?_ (Crisp UI screenshot or interactive preview component)
+  3. _How do I get it?_ (Unambiguous primary CTA input/button)
+
+### 2. Quiet Typographic Hierarchy
+
+- Use subdued monochrome typography (`oklch(0.95 0.005 240)` background with `oklch(0.20 0.01 240)` body copy).
+- Keep display font sizes restrained (`clamp(1.75rem, 4vw, 2.75rem)`) rather than giant 5rem text blocks.
+
+### 3. Tight Spatial Grid
+
+- Limit total page section count to max 4 sections:
+  1. Hero + Primary CTA + Product Preview
+  2. Social Proof / Logo Bar
+  3. Feature Grid (3 core benefits max)
+  4. Conversion Footer Card
+
+### 4. Zero Unnecessary Visual Noise
+
+- Omit decorative background shapes, floating 3D spheres, and rainbow gradients. Let contrast and typography drive visual quality.

package/skills/company-logos/SKILL.md

@@ -1,54 +1,54 @@
----
-name: company-logos
-description: "Use when Social proof rows, logo grids, customer carousels, and trust badges layout rules for balanced visual weight and responsive alignment."
-version: 5.0.0
-last-updated: 2026-09-13
-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
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
----
-
-## 4 Logo Layout Rules
-
-### 1. Optical Weight Normalization
-
-Logos vary wildly in aspect ratio (e.g. square logos vs wide wordmarks).
-
-- **Rule**: Set a maximum bounding box (`max-height: 28px`, `max-width: 120px`) and use `object-fit: contain` with `filter: grayscale(100%) opacity(0.7)`.
-- On hover, transition `opacity(1)` and remove grayscale smoothly over `200ms`.
-
-### 2. Monochromatic Harmonization
-
-- Never display multi-colored corporate logos together—they create visual chaos.
-- Render all logos in monochromatic SVG fill (`fill="currentColor"`) matching `--text-muted` or `--foreground-muted`.
-
-### 3. Responsive Flex Grid
-
-```css
-.logo-trust-row {
-  display: flex;
-  flex-wrap: wrap;
-  align-items: center;
-  justify-content: center;
-  gap: 2rem 3.5rem; /* Row gap 2rem, Column gap 3.5rem */
-}
-```
-
-### 4. Seamless Ticker Marquee (Optional)
-
-- For 8+ logos, use a hardware-accelerated CSS marquee animation with duplicate items for seamless continuous looping and `animation-play-state: paused` on hover.
+---
+name: company-logos
+description: "Use when Social proof rows, logo grids, customer carousels, and trust badges layout rules for balanced visual weight and responsive alignment."
+version: 5.0.0
+last-updated: 2026-09-13
+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
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+---
+
+## 4 Logo Layout Rules
+
+### 1. Optical Weight Normalization
+
+Logos vary wildly in aspect ratio (e.g. square logos vs wide wordmarks).
+
+- **Rule**: Set a maximum bounding box (`max-height: 28px`, `max-width: 120px`) and use `object-fit: contain` with `filter: grayscale(100%) opacity(0.7)`.
+- On hover, transition `opacity(1)` and remove grayscale smoothly over `200ms`.
+
+### 2. Monochromatic Harmonization
+
+- Never display multi-colored corporate logos together—they create visual chaos.
+- Render all logos in monochromatic SVG fill (`fill="currentColor"`) matching `--text-muted` or `--foreground-muted`.
+
+### 3. Responsive Flex Grid
+
+```css
+.logo-trust-row {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  justify-content: center;
+  gap: 2rem 3.5rem; /* Row gap 2rem, Column gap 3.5rem */
+}
+```
+
+### 4. Seamless Ticker Marquee (Optional)
+
+- For 8+ logos, use a hardware-accelerated CSS marquee animation with duplicate items for seamless continuous looping and `animation-play-state: paused` on hover.

package/skills/config-validator/SKILL.md

@@ -1,125 +1,125 @@
----
-name: config-validator
-description: "Use when 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."
-version: 5.0.0
-last-updated: 2026-09-13
-skills:
-  - lint-and-validate
-  - backend-security-expert
-  - clean-code
-tools: Read, Grep, Glob, Bash, Edit, Write
-scripts-binding:
-  - .agent/scripts/lint_runner.js
-  - .agent/scripts/verify_all.js
----
-
-# Config Validator — System Integrity Mastery
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
-## Hallucination Traps (Read First)
-
-- ❌ Silently using default values for missing config -> ✅ Fail fast with a clear error message naming the missing field
-- ❌ Trusting environment variables without validation -> ✅ Validate ALL env vars at startup with Zod or a schema, not at usage time
-- ❌ Mixing config source precedence without documenting it -> ✅ Document: CLI args > env vars > config file > defaults
-
----
-
----
-
-## 1. Fail Fast, Fail Loudly
-
-Never allow a system to boot, run, or proceed into a workflow if the underlying configuration is invalid. Parse configurations at the absolute boundary.
-
-```typescript
-import { z } from 'zod';
-
-// ❌ VULNERABLE: Implicit Trust
-// Assumes the JSON file is correct. Will crash randomly deep in the execution stack
-// if 'maxRetries' is missing or set to a string.
-const config = JSON.parse(fs.readFileSync('./.agent/config.json', 'utf8'));
-runAgent(config.maxRetries);
-
-// ✅ SAFE: Boundary Validation via Zod
-const ConfigSchema = z.object({
-  version: z.string().regex(/^\d+\.\d+\.\d+$/),
-  maxRetries: z.number().min(0).max(10).default(3),
-  enabledSkills: z.array(z.string()),
-  environment: z.enum(['development', 'production', 'test']),
-  apiEndpoint: z.string().url().optional(),
-});
-
-try {
-  const rawData = JSON.parse(fs.readFileSync('./.agent/config.json', 'utf8'));
-  const config = ConfigSchema.parse(rawData); // Throws heavily detailed error instantly
-} catch (err) {
-  logger.fatal('System boot aborted. Invalid config.json:', err.errors);
-  process.exit(1);
-}
-```
-
----
-
-## 2. Directory & Manifest Self-Auditing
-
-Configuration files often reference physical system assets (scripts, workflows, other config files). The validator must check referential integrity.
-
-If `manifest.json` says `{"workflow": "scripts/deploy.sh"}`, the validator MUST verify that `scripts/deploy.sh` actually exists before the orchestrator tries to run it.
-
-```typescript
-// Validating Referential Integrity
-function auditAgentDirectory(config: Config) {
-  const missingFiles = [];
-
-  for (const skill of config.enabledSkills) {
-    const skillPath = path.join('.agent/skills', skill, 'SKILL.md');
-    if (!fs.existsSync(skillPath)) {
-      missingFiles.push(`Skill manifest definition missing: ${skillPath}`);
-    }
-  }
-
-  if (missingFiles.length > 0) {
-    throw new Error(`Referential Integrity Failure:\n${missingFiles.join('\n')}`);
-  }
-}
-```
-
----
-
-## 3. Environment Variable Validation
-
-Missing or malformed `.env` files are the #1 cause of deployment failure.
-
-Treat environment variables exactly like JSON configs: apply a rigid schema mapping at boot.
-
-```typescript
-// Instead of checking process.env.DATABASE_URL throughout the app,
-// export a strictly validated object once.
-
-// src/env.ts
-import { z } from 'zod';
-
-const EnvSchema = z.object({
-  DATABASE_URL: z.string().url(),
-  PORT: z.coerce.number().default(3000), // Transforms string "3000" to number 3000
-  NODE_ENV: z.enum(['development', 'production']).default('development'),
-  API_KEY: z.string().min(16), // Ensures keys aren't empty or mock data
-});
-
-export const ENV = EnvSchema.parse(process.env);
-```
-
----
-
-## 4. Safe Configuration Mutation
-
-When automating updates to a JSON configuration (e.g., adding a new skill to `config.json`), never serialize over the original file blindly.
-
-1. **Read** original JSON.
-2. **Apply** modifications in memory.
-3. **Validate** the new object against the Zod schema.
-4. **Write** atomically (write to `config.json.tmp`, then standard OS file rename to `config.json` to prevent corruption if power dies mid-write).
+---
+name: config-validator
+description: "Use when 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."
+version: 5.0.0
+last-updated: 2026-09-13
+skills:
+  - lint-and-validate
+  - backend-security-expert
+  - clean-code
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
+---
+
+# Config Validator — System Integrity Mastery
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Silently using default values for missing config -> ✅ Fail fast with a clear error message naming the missing field
+- ❌ Trusting environment variables without validation -> ✅ Validate ALL env vars at startup with Zod or a schema, not at usage time
+- ❌ Mixing config source precedence without documenting it -> ✅ Document: CLI args > env vars > config file > defaults
+
+---
+
+---
+
+## 1. Fail Fast, Fail Loudly
+
+Never allow a system to boot, run, or proceed into a workflow if the underlying configuration is invalid. Parse configurations at the absolute boundary.
+
+```typescript
+import { z } from 'zod';
+
+// ❌ VULNERABLE: Implicit Trust
+// Assumes the JSON file is correct. Will crash randomly deep in the execution stack
+// if 'maxRetries' is missing or set to a string.
+const config = JSON.parse(fs.readFileSync('./.agent/config.json', 'utf8'));
+runAgent(config.maxRetries);
+
+// ✅ SAFE: Boundary Validation via Zod
+const ConfigSchema = z.object({
+  version: z.string().regex(/^\d+\.\d+\.\d+$/),
+  maxRetries: z.number().min(0).max(10).default(3),
+  enabledSkills: z.array(z.string()),
+  environment: z.enum(['development', 'production', 'test']),
+  apiEndpoint: z.string().url().optional(),
+});
+
+try {
+  const rawData = JSON.parse(fs.readFileSync('./.agent/config.json', 'utf8'));
+  const config = ConfigSchema.parse(rawData); // Throws heavily detailed error instantly
+} catch (err) {
+  logger.fatal('System boot aborted. Invalid config.json:', err.errors);
+  process.exit(1);
+}
+```
+
+---
+
+## 2. Directory & Manifest Self-Auditing
+
+Configuration files often reference physical system assets (scripts, workflows, other config files). The validator must check referential integrity.
+
+If `manifest.json` says `{"workflow": "scripts/deploy.sh"}`, the validator MUST verify that `scripts/deploy.sh` actually exists before the orchestrator tries to run it.
+
+```typescript
+// Validating Referential Integrity
+function auditAgentDirectory(config: Config) {
+  const missingFiles = [];
+
+  for (const skill of config.enabledSkills) {
+    const skillPath = path.join('.agent/skills', skill, 'SKILL.md');
+    if (!fs.existsSync(skillPath)) {
+      missingFiles.push(`Skill manifest definition missing: ${skillPath}`);
+    }
+  }
+
+  if (missingFiles.length > 0) {
+    throw new Error(`Referential Integrity Failure:\n${missingFiles.join('\n')}`);
+  }
+}
+```
+
+---
+
+## 3. Environment Variable Validation
+
+Missing or malformed `.env` files are the #1 cause of deployment failure.
+
+Treat environment variables exactly like JSON configs: apply a rigid schema mapping at boot.
+
+```typescript
+// Instead of checking process.env.DATABASE_URL throughout the app,
+// export a strictly validated object once.
+
+// src/env.ts
+import { z } from 'zod';
+
+const EnvSchema = z.object({
+  DATABASE_URL: z.string().url(),
+  PORT: z.coerce.number().default(3000), // Transforms string "3000" to number 3000
+  NODE_ENV: z.enum(['development', 'production']).default('development'),
+  API_KEY: z.string().min(16), // Ensures keys aren't empty or mock data
+});
+
+export const ENV = EnvSchema.parse(process.env);
+```
+
+---
+
+## 4. Safe Configuration Mutation
+
+When automating updates to a JSON configuration (e.g., adding a new skill to `config.json`), never serialize over the original file blindly.
+
+1. **Read** original JSON.
+2. **Apply** modifications in memory.
+3. **Validate** the new object against the Zod schema.
+4. **Write** atomically (write to `config.json.tmp`, then standard OS file rename to `config.json` to prevent corruption if power dies mid-write).