tribunal-kit 6.0.0 → 7.0.0

package/.agent/skills/shadcn-ui-expert/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before using or customizing shadcn/ui components, you MUST inspect:
+
 1. Component Installation State → Check `@/components/ui/` directory for existing components before running `npx shadcn@latest add`
 2. `cn` Utility Usage (Section 144) → Use `cn(...)` (combining `clsx` + `tailwind-merge`) for all conditional and overridden class names
 3. Client Component Boundaries (Section 166) → Add `"use client"` on interactive Radix primitives (Dialog, Select, Popover) before rendering in App Router
@@ -78,30 +79,35 @@ Do not treat `components/ui/*` as an immutable black box. You are _supposed_ to
 ### Adding Variants via `cva` (Class Variance Authority)
 
 ```typescript
-import { cva, type VariantProps } from "class-variance-authority";
+import { cva, type VariantProps } from 'class-variance-authority';
 
 // Adding a new "ghost-rounded" variant to the Button component
-const buttonVariants = cva("inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium transition-colors...", {
-  variants: {
-    variant: {
-      default: "bg-primary text-primary-foreground shadow hover:bg-primary/90",
-      destructive: "bg-destructive text-destructive-foreground shadow-sm hover:bg-destructive/90",
-      outline: "border border-input bg-background shadow-sm hover:bg-accent hover:text-accent-foreground",
-      // YOUR CUSTOM VARIANT:
-      "ghost-rounded": "bg-transparent hover:bg-accent hover:text-accent-foreground rounded-full px-6",
+const buttonVariants = cva(
+  'inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium transition-colors...',
+  {
+    variants: {
+      variant: {
+        default: 'bg-primary text-primary-foreground shadow hover:bg-primary/90',
+        destructive: 'bg-destructive text-destructive-foreground shadow-sm hover:bg-destructive/90',
+        outline:
+          'border border-input bg-background shadow-sm hover:bg-accent hover:text-accent-foreground',
+        // YOUR CUSTOM VARIANT:
+        'ghost-rounded':
+          'bg-transparent hover:bg-accent hover:text-accent-foreground rounded-full px-6',
+      },
+      size: {
+        default: 'h-9 px-4 py-2',
+        sm: 'h-8 rounded-md px-3 text-xs',
+        lg: 'h-10 rounded-md px-8',
+        icon: 'h-9 w-9',
+      },
     },
-    size: {
-      default: "h-9 px-4 py-2",
-      sm: "h-8 rounded-md px-3 text-xs",
-      lg: "h-10 rounded-md px-8",
-      icon: "h-9 w-9",
+    defaultVariants: {
+      variant: 'default',
+      size: 'default',
     },
   },
-  defaultVariants: {
-    variant: "default",
-    size: "default",
-  },
-});
+);
 ```
 
 ---
@@ -156,8 +162,8 @@ Implementation with Tailwind v4 CSS-first configuration:
 The `cn` utility combines `clsx` (conditional classes) and `tailwind-merge` (fixing class conflicts).
 
 ```typescript
-import { clsx, type ClassValue } from "clsx";
-import { twMerge } from "tailwind-merge";
+import { clsx, type ClassValue } from 'clsx';
+import { twMerge } from 'tailwind-merge';
 
 export function cn(...inputs: ClassValue[]) {
   return twMerge(clsx(inputs));
@@ -168,7 +174,7 @@ export function cn(...inputs: ClassValue[]) {
 const className = `px-4 py-2 bg-blue-500 hover:bg-blue-600 ${props.className}`;
 
 // ✅ GOOD: cn resolves conflicts correctly
-const className = cn("px-4 py-2 bg-blue-500 hover:bg-blue-600", props.className);
+const className = cn('px-4 py-2 bg-blue-500 hover:bg-blue-600', props.className);
 ```
 
 ---

package/.agent/skills/shape/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating UI component code for new features, you MUST inspect:
+
 1. Target feature scope & user goals → Execute the 3-Step Shaping Workflow (Section 22)
 2. State Inventory (Section 29) → Define 5 required component states (Default, Empty, Loading, Error, Success)
 3. Architecture Contract (Section 37) → Draft entry/exit points and primary action contract before coding
@@ -31,12 +32,16 @@ Uncover core requirements, define interaction boundaries, and lock down screen f
 ## The 3-Step Shaping Workflow
 
 ### Step 1: High-Ambiguity Socratic Interview
+
 Before designing components, ask 2 targeted questions about high-ambiguity choices:
-1. **Primary User Goal**: *What is the single most important action the user must accomplish on this screen?*
-2. **Context & Entry Point**: *Where does the user arrive from, and where do they expect to go after completing this step?*
+
+1. **Primary User Goal**: _What is the single most important action the user must accomplish on this screen?_
+2. **Context & Entry Point**: _Where does the user arrive from, and where do they expect to go after completing this step?_
 
 ### Step 2: Screen Boundaries & State Inventory
+
 Define the component states before implementation:
+
 - **Default State**: Primary layout with standard populated data.
 - **Empty State**: Zero-data view with creation prompt.
 - **Loading State**: Skeleton placeholders.
@@ -44,7 +49,9 @@ Define the component states before implementation:
 - **Success State**: Instant feedback toast or confirmation view.
 
 ### Step 3: Architecture Contract
+
 Summarize the screen contract in a concise visual outline before coding:
+
 ```
 [Screen Title]
   ├── Entry Point: (e.g. Dashboard -> "New Project" button)

package/.agent/skills/skill-creator/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before creating a new skill module, you MUST inspect:
+
 1. `.agent/skills/` directory → Check if a skill in the same domain already exists to prevent duplication
 2. Option A+C Hybrid Skill Schema (Section 26) → Enforce frontmatter with `version: 3.0.0`, `scripts-binding`, `Pre-Flight Checklist`, and `VBC Protocol`
 3. Target skill path (`.agent/skills/<skill-name>/SKILL.md`) → Verify destination directory structure before creation

package/.agent/skills/soft-skill/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering luxury or soft-depth UI interfaces, you MUST inspect:
+
 1. Multi-Layer Shadow Recipe (Section 25) → Blend low-opacity multi-layered ambient shadows ($\le 6\%$ opacity per layer) instead of heavy single drop shadows
 2. Spatial Cadence (Section 37) → Increase container padding by $1.5\times$ ($\ge 24\text{px}$) to provide generous negative space
 3. Color Harmonies (Section 40) → Use quiet, low-chroma monochromatic OKLCH palettes for background and typography
@@ -31,7 +32,9 @@ Craft high-end, luxury interfaces featuring soft depth, gentle surface transitio
 ## 4 Soft Design Rules
 
 ### 1. Multi-Layer Soft Ambient Depth
+
 - Avoid harsh drop-shadows. Use low-opacity multi-layered ambient lighting shadows:
+
 ```css
 .soft-depth-card {
   background: var(--surface);
@@ -44,12 +47,15 @@ Craft high-end, luxury interfaces featuring soft depth, gentle surface transitio
 ```
 
 ### 2. Generous Negative Space Cadence
+
 - Increase component padding by 1.5x (e.g. `24px` -> `36px`, `32px` -> `48px`). Generous negative space is the ultimate indicator of luxury software.
 
 ### 3. Subdued Monochrome Color Harmonies
+
 - Use quiet, low-chroma monochromatic palettes (`oklch(0.97 0.005 240)` background with `oklch(0.22 0.01 240)` primary text).
 
 ### 4. Fluid, Low-Velocity Transitions
+
 - Transition speeds should be gentle ($\approx 250\text{ms}$) with strong ease-out curves (`cubic-bezier(0.16, 1, 0.3, 1)`).
 
 ---

package/.agent/skills/sounds-on-the-web/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing web audio feedback, you MUST inspect:
+
 1. Autoplay Policy Rules (Section 78) → Initialize `AudioContext` strictly after/inside user gesture interaction handlers
 2. Gain Volume Caps → Keep gain volume subtle ($\le 0.15$ max gain) to prevent user auditory discomfort
 3. Mute Preference Toggle (Section 66) → Provide a persistent sound mute option in settings or local storage

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

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before writing complex SQL queries or optimizing database performance, you MUST inspect:
+
 1. SARGability Inspection (Section 328) → Ensure WHERE clauses use SARGable predicates; avoid functions or string operations on indexed columns
 2. Keyset Pagination over OFFSET (Section 74) → Use keyset/cursor pagination (`WHERE (created_at, id) < (...)`) instead of `OFFSET` for large tables (>10K rows)
 3. EXPLAIN ANALYZE Verification (Section 358) → Run `EXPLAIN (ANALYZE, BUFFERS)` to inspect physical query cost, buffer hits, and join algorithms

package/.agent/skills/supabase-postgres-best-practices/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering Supabase schemas or writing PostgreSQL migrations, you MUST inspect:
+
 1. Row Level Security Mandatory Policy (Section 28) → Always enable RLS on every table (`alter table ... enable row level security;`) before deploying
 2. Direct UID Match RLS Rule (Section 30) → Use direct equality (`auth.uid() = user_id`) in RLS policies; avoid slow `IN` subqueries
 3. SQL Migration File Requirement (Section 38) → Write explicit SQL migration files (`supabase/migrations/`) rather than manual GUI operations

package/.agent/skills/svg-animation/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering SVG path or stroke animations, you MUST inspect:
+
 1. Target SVG attributes → Ensure `fill="none"` is set on draw-on paths to prevent black fill occlusion
 2. Path Length Calibration (Section 70) → Calculate exact `path.getTotalLength()` instead of guessing `stroke-dasharray` values
 3. Non-scaling Stroke rule (Section 83) → Apply `vector-effect="non-scaling-stroke"` if vector elements scale across responsive viewports
@@ -31,10 +32,15 @@ Craft crisp, resolution-independent vector animations using CSS, Framer Motion,
 ## 3 SVG Motion Techniques
 
 ### 1. Pure CSS Stroke Draw-On Effect
+
 ```css
 @keyframes draw-path {
-  from { stroke-dashoffset: 1000; }
-  to { stroke-dashoffset: 0; }
+  from {
+    stroke-dashoffset: 1000;
+  }
+  to {
+    stroke-dashoffset: 0;
+  }
 }
 
 .draw-signature-path {
@@ -45,8 +51,9 @@ Craft crisp, resolution-independent vector animations using CSS, Framer Motion,
 ```
 
 ### 2. Framer Motion SVG Path Length Animation
+
 ```tsx
-import { motion } from "framer-motion";
+import { motion } from 'framer-motion';
 
 export function DrawCheckmark() {
   return (
@@ -55,7 +62,7 @@ export function DrawCheckmark() {
         d="M5 13l4 4L19 7"
         initial={{ pathLength: 0 }}
         animate={{ pathLength: 1 }}
-        transition={{ duration: 0.4, ease: "easeOut" }}
+        transition={{ duration: 0.4, ease: 'easeOut' }}
       />
     </svg>
   );
@@ -63,12 +70,14 @@ export function DrawCheckmark() {
 ```
 
 ### 3. SVG Path Morphing (GSAP MorphSVGPlugin)
+
 - Morph between 2 vector paths with identical point counts or using GSAP MorphSVG:
+
 ```javascript
-gsap.to("#start-shape", {
-  morphSVG: "#end-shape",
+gsap.to('#start-shape', {
+  morphSVG: '#end-shape',
   duration: 0.6,
-  ease: "power2.inOut"
+  ease: 'power2.inOut',
 });
 ```
 

package/.agent/skills/swiftui-expert/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before writing or refactoring SwiftUI components, you MUST inspect:
+
 1. Modern Observable Macro (iOS 17+) (Section 43) → Use `@Observable` macro for reference types; ban legacy `@StateObject` / `@Published` boilerplate in iOS 17+ code
 2. Identifiable Protocol in ForEach (Section 125) → Conform model types to `Identifiable` for `ForEach`; ban integer index iteration (`0..<items.count`)
 3. NavigationStack Standard (Section 18) → Use `NavigationStack` or `NavigationSplitView`; ban deprecated legacy `NavigationView`

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

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before applying Swiss Design aesthetics, you MUST inspect:
+
 1. `DESIGN.md` / `index.css` → Check grid system tokens and grotesque font declarations (Helvetica, Inter, Geist)
 2. Asymmetric Structural Balance (Section 32) → Align headings and content to strong left vertical axes; strictly prohibit `text-align: justify` or centered body paragraphs
 3. Mathematical Section Numbering (Section 35) → Enforce small uppercase badges (`SECTION 01 // OVERVIEW`) with `tabular-nums`
@@ -31,17 +32,21 @@ Architect pristine, print-inspired interfaces grounded in grid discipline, objec
 ## 4 Swiss Design Pillars
 
 ### 1. Strict Grid Alignment
+
 - Every layout element MUST align strictly to a visible or invisible 12-column grid.
 - Border dividers use thin, sharp 1px solid lines matching `--foreground` opacity (e.g. `border-color: rgba(0,0,0,0.15)`).
 
 ### 2. High-Contrast Sans-Serif Typography
+
 - Use clean grotesque sans-serif fonts (Helvetica, Inter, Geist, Neue Haas Grotesk).
 - Pair large bold display titles (`3rem+`, `font-weight: 700`, `letter-spacing: -0.03em`) with clean flush-left, rag-right body copy (`text-align: left`).
 
 ### 3. Asymmetric Structural Balance
+
 - Reject centered, symmetrical layouts. Align headings and content to strong left vertical axes, using generous negative space to anchor visual weight.
 
 ### 4. Mathematical Numbering & Labels
+
 - Use small uppercase metadata badges (`SECTION 01 // OVERVIEW`) with tracking (`letter-spacing: 0.08em`) and monospace or tabular numbers (`font-variant-numeric: tabular-nums`).
 
 ---

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

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before designing system architecture or writing scale proposals, you MUST inspect:
+
 1. 6-Step Design Framework (Section 27) → Execute Clarify Scope, Scale Estimation, API Definition, Data Model, High-Level Design, and Deep Dive in exact order
 2. Quantified Scale Estimation (Section 65) → Calculate read/write QPS, storage growth, and bandwidth before selecting database or caching tiers
 3. Monolith First Rule (Section 17) → Start with modular monolith for $<10\text{K}$ RPM; ban introducing microservices or sharding prematurely

package/.agent/skills/systematic-debugging/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before debugging issues or analyzing stack traces, you MUST inspect:
+
 1. Single Variable Isolation (Section 15) → Change ONE variable at a time when debugging; ban shotgun debugging or multi-file edits simultaneously
 2. Deterministic Reproduction Pre-requisite (Section 29) → Write a failing deterministic test/reproduction script FIRST before modifying code logic
 3. Stack Trace Application Line Extraction (Section 98) → Trace up past `node_modules` to locate the top-most application code frame you wrote

package/.agent/skills/tailwind-patterns/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering Tailwind CSS styles or themes, you MUST inspect:
+
 1. CSS-First v4 Configuration (Section 19) → Use `@import "tailwindcss";` and `@theme { }` in CSS files instead of deprecated `tailwind.config.js`
 2. Viewport Height Units (Section 151) → Use `min-h-svh` (small viewport height) or `min-h-dvh` instead of broken mobile `min-h-screen`
 3. Container Query Prefix (Section 204) → Use `@sm:`, `@md:`, `@lg:` container prefixes for component-level responsiveness rather than viewport `sm:`, `md:`, `lg:`
@@ -34,7 +35,7 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
 
 ```css
 /* app.css — THE configuration file in Tailwind v4 */
-@import "tailwindcss";
+@import 'tailwindcss';
 
 @theme {
   /* Colors */
@@ -51,8 +52,8 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
   --color-text-muted: oklch(0.45 0 0);
 
   /* Typography */
-  --font-sans: "Inter", "system-ui", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-sans: 'Inter', 'system-ui', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
   /* Spacing (extends the default scale) */
   --spacing-18: 4.5rem;
@@ -152,7 +153,9 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
   <p class="max-w-2xl text-center text-lg text-text-muted">Subtitle text</p>
   <div class="flex gap-3">
     <button class="rounded-pill bg-primary-600 px-6 py-3 text-white">Primary</button>
-    <button class="rounded-pill border border-primary-600 px-6 py-3 text-primary-600">Secondary</button>
+    <button class="rounded-pill border border-primary-600 px-6 py-3 text-primary-600">
+      Secondary
+    </button>
   </div>
 </section>
 
@@ -229,10 +232,14 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
 
 ```html
 <!-- Fluid heading — scales smoothly from 2rem to 4rem -->
-<h1 class="text-[clamp(2rem,5vw,4rem)] font-bold leading-tight tracking-tight">Responsive Heading</h1>
+<h1 class="text-[clamp(2rem,5vw,4rem)] font-bold leading-tight tracking-tight">
+  Responsive Heading
+</h1>
 
 <!-- Fluid body text -->
-<p class="text-[clamp(1rem,1.2vw,1.25rem)] leading-relaxed text-text-muted">Body text that scales with viewport</p>
+<p class="text-[clamp(1rem,1.2vw,1.25rem)] leading-relaxed text-text-muted">
+  Body text that scales with viewport
+</p>
 
 <!-- Prose (for long-form content) -->
 <article class="prose prose-lg mx-auto max-w-3xl dark:prose-invert">
@@ -247,14 +254,14 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
 ```css
 /* @font-face in your CSS (Tailwind v4 approach) */
 @font-face {
-  font-family: "Inter";
+  font-family: 'Inter';
   font-weight: 100 900;
   font-display: swap;
-  src: url("/fonts/inter-variable.woff2") format("woff2");
+  src: url('/fonts/inter-variable.woff2') format('woff2');
 }
 
 @theme {
-  --font-sans: "Inter", system-ui, sans-serif;
+  --font-sans: 'Inter', system-ui, sans-serif;
 }
 ```
 
@@ -356,7 +363,12 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
             backdrop-blur-sm animate-fade-in"
 >
   <!-- Modal -->
-  <div class="w-full max-w-md rounded-2xl bg-surface p-6 shadow-elevated animate-slide-up" role="dialog" aria-modal="true" aria-labelledby="modal-title">
+  <div
+    class="w-full max-w-md rounded-2xl bg-surface p-6 shadow-elevated animate-slide-up"
+    role="dialog"
+    aria-modal="true"
+    aria-labelledby="modal-title"
+  >
     <h2 id="modal-title" class="text-lg font-semibold">Dialog Title</h2>
     <p class="mt-2 text-sm text-text-muted">Dialog description.</p>
 
@@ -571,7 +583,9 @@ Before engineering Tailwind CSS styles or themes, you MUST inspect:
 </div>
 
 <!-- Forced colors mode (high contrast) -->
-<button class="bg-primary-600 forced-colors:bg-[Highlight] forced-colors:text-[HighlightText]">Accessible button</button>
+<button class="bg-primary-600 forced-colors:bg-[Highlight] forced-colors:text-[HighlightText]">
+  Accessible button
+</button>
 ```
 
 ---

package/.agent/skills/taste-skill/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before rendering UI components, you MUST inspect:
+
 1. Banned AI Clichés (Section 24) → Strictly ban purple/indigo gradients (`from-purple-600 to-indigo-600`), glowing neon borders, and floating 3D spheres
 2. Typography Rules (Section 30) → Apply negative tracking (`-0.025em`) + `text-wrap: balance` to display headings; cap body text at `65ch` max width
 3. Tactile Press Feedback (Section 39) → Enforce `:active` press feedback (`transform: scale(0.97)`) on all interactive buttons/cards
@@ -31,24 +32,29 @@ Enforce senior-level design taste, anti-slop constraints, and visual craft acros
 ## The 5 Rules of Design Taste
 
 ### 1. Banned AI Visual Clichés (Zero Tolerance)
+
 - ❌ Purple/violet gradient backgrounds (`from-purple-600 to-indigo-600`).
 - ❌ Glowing neon borders on every card element.
 - ❌ Floating 3D spheres or generic iridescent mesh gradients.
 - ❌ Identical Bento Box 3-column grids on every page.
 
 ### 2. High-Fidelity Typography
+
 - Typography accounts for 80% of interface perception.
 - Display headings must use negative tracking (`-0.025em`) and balanced text wrapping (`text-wrap: balance`).
 - Body text line length MUST be bounded to `65ch` max width.
 
 ### 3. Spatial System Strictness
+
 - Never use arbitrary `px` paddings or margins (`margin-top: 17px`).
 - Enforce strict 8px spatial grid math (`4px`, `8px`, `12px`, `16px`, `24px`, `32px`, `48px`, `64px`).
 
 ### 4. Tactile Micro-Feedback
+
 - All interactive controls MUST respond to press with `transform: scale(0.97)` on `:active` with transition duration $\le 160\text{ms}$.
 
 ### 5. Multi-Layer Depth Over Flat Lines
+
 - Replace harsh black borders with multi-layer ambient drop shadows and subtle 8% opacity surface outlines.
 
 ---

package/.agent/skills/tdd-workflow/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing feature logic or writing unit tests, you MUST inspect:
+
 1. Red-Green-Refactor Cycle (Section 25) → Write failing test FIRST (Red) → minimal passing code SECOND (Green) → cleanup THIRD (Refactor)
 2. Behavior-First Assertion Rule (Section 36) → Assert public contract results (GIVEN/WHEN/THEN); ban asserting internal private fields or state
 3. IO Boundary-Only Mocking (Section 50) → Mock ONLY un-owned external boundaries (DB IO, network APIs); ban mocking domain entities or pure utils
@@ -45,6 +46,7 @@ Build features and fixes one slice at a time using strict Test-Driven Developmen
 ## 4 TDD Rules
 
 ### 1. Test Behavior, Not Implementation Details
+
 - Assert GIVEN / WHEN / THEN behavior results, NOT private class methods or internal variables.
 
 ```typescript
@@ -56,12 +58,15 @@ expect(calculator.add(40, 2)).toBe(42);
 ```
 
 ### 2. The Minimal Green Rule
+
 - In Step 2 (GREEN), write ONLY the minimal code required to pass the test—even if it's hardcoding a return value initially. This forces you to write the next test that proves the hardcoded value inadequate.
 
 ### 3. Mock Only External Boundaries
+
 - Never mock internal domain entities or utility functions. Mock ONLY un-owned external boundaries (database IO, network APIs, payment gateways).
 
 ### 4. Triangulation Strategy
+
 - When uncertain about algorithm logic, write 2 or more tests with different inputs to force general implementation.
 
 ---

package/.agent/skills/test-result-analyzer/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before analyzing failing test logs or output traces, you MUST inspect:
+
 1. First Point of Failure (FPF) Isolation (Section 114) → Identify the initial root failure in execution order first; ban fixing cascading downstream failures beforehand
 2. Cluster Categorization Rule (Section 88) → Group failures by shared module/error type to resolve dozens of failures via single root fixes
 3. Literal Trace Extract Discipline (Section 257) → Quote exact Expected/Received values and line numbers strictly from actual logs; ban guessing assertion details