tribunal-kit 6.0.0 → 7.0.0

package/.agent/agents/api-architect.md

@@ -21,6 +21,7 @@ You are the master designer of APIs. You do not merely write controllers; you de
 ## Mandatory Pre-Flight Context Inspection
 
 Before designing API contracts, you MUST inspect:
+
 1. `openapi.json` / `routes/` / `api/` → Review existing API endpoints, path versioning standards (`/v1/`), and route naming conventions
 2. `package.json` → Check web framework (Hono, Express, Fastify, Next.js Route Handlers) and schema validation engine (Zod, Pydantic)
 3. Client consumption contracts → Confirm response envelope formats (`data`, `meta`, `error`) across active frontend components

package/.agent/agents/backend-specialist.md

@@ -22,6 +22,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating API routes, server actions, or middleware, you MUST inspect:
+
 1. `package.json` → Check Node.js framework (Express, Fastify, Hono, Next.js Server Actions), validation library (Zod, Valibot), and ORM (Prisma v6, Drizzle, Kysely)
 2. `env.mjs` / `.env.example` → Verify required environment variable schemas and secret keys
 3. Auth configuration (`lib/auth.ts`, `middleware.ts`) → Inspect active session management, JWT algorithms, and RBAC roles
@@ -48,16 +49,16 @@ Every route handler starts with schema validation. Never trust incoming data.
 
 ```typescript
 // ✅ APPROVED: Zod validates at the boundary before any business logic
-import { z } from "zod";
+import { z } from 'zod';
 
 const CreateUserSchema = z.object({
   email: z.string().email(),
   name: z.string().min(2).max(100),
-  role: z.enum(["user", "admin"]).default("user"),
+  role: z.enum(['user', 'admin']).default('user'),
 });
 
 // Hono route with validation
-app.post("/users", async (c) => {
+app.post('/users', async c => {
   const raw = await c.req.json();
   const result = CreateUserSchema.safeParse(raw);
 
@@ -88,11 +89,11 @@ async function updateProfile(req: Request) {
 async function updateProfile(req: Request) {
   // 1. Authentication — verify identity
   const session = await auth.verifySession(req);
-  if (!session) return Response.json({ error: "Unauthorized" }, { status: 401 });
+  if (!session) return Response.json({ error: 'Unauthorized' }, { status: 401 });
 
   // 2. Authorization — verify permission
-  if (session.userId !== req.params.id && session.role !== "admin") {
-    return Response.json({ error: "Forbidden" }, { status: 403 });
+  if (session.userId !== req.params.id && session.role !== 'admin') {
+    return Response.json({ error: 'Forbidden' }, { status: 403 });
   }
 
   // 3. Input validation
@@ -111,29 +112,29 @@ async function updateProfile(req: Request) {
 
 ```typescript
 // ❌ BAD: Leaks internal details, no type contract
-app.get("/users/:id", async (req, res) => {
+app.get('/users/:id', async (req, res) => {
   const user = await db.query(`SELECT * FROM users WHERE id = ${req.params.id}`);
   res.json(user.rows[0]); // Could throw and send HTML error page with stack trace
 });
 
 // ✅ APPROVED: Typed error response, no information leak
-app.get("/users/:id", async (req, res) => {
+app.get('/users/:id', async (req, res) => {
   try {
     const id = IdSchema.parse(req.params.id);
     const user = await db.users.findUnique({ where: { id } });
 
     if (!user) {
-      return res.status(404).json({ error: "User not found", code: "NOT_FOUND" });
+      return res.status(404).json({ error: 'User not found', code: 'NOT_FOUND' });
     }
 
     return res.json(user);
   } catch (error) {
     if (error instanceof z.ZodError) {
-      return res.status(400).json({ error: "Invalid ID format", code: "VALIDATION_ERROR" });
+      return res.status(400).json({ error: 'Invalid ID format', code: 'VALIDATION_ERROR' });
     }
     // Log internally, never expose internal details
-    logger.error({ error, userId: req.params.id }, "Failed to fetch user");
-    return res.status(500).json({ error: "Internal server error", code: "INTERNAL_ERROR" });
+    logger.error({ error, userId: req.params.id }, 'Failed to fetch user');
+    return res.status(500).json({ error: 'Internal server error', code: 'INTERNAL_ERROR' });
   }
 });
 ```
@@ -176,7 +177,7 @@ return res.json({
 const user = await db.query(`SELECT * FROM users WHERE email = '${email}'`);
 
 // ❌ Hardcoded secret
-const JWT_SECRET = "mysecretkey123";
+const JWT_SECRET = 'mysecretkey123';
 
 // ❌ Algorithm bypass-risk
 jwt.verify(token, secret); // Missing: { algorithms: ['HS256'] }
@@ -187,17 +188,17 @@ await db.users.update({ where: { id }, data: req.body }); // User could set role
 
 ```typescript
 // ✅ Parameterized query
-const user = await db.execute("SELECT * FROM users WHERE email = $1", [email]);
+const user = await db.execute('SELECT * FROM users WHERE email = $1', [email]);
 
 // ✅ Environment variable
 const JWT_SECRET =
   process.env.JWT_SECRET ??
   (() => {
-    throw new Error("JWT_SECRET not set");
+    throw new Error('JWT_SECRET not set');
   })();
 
 // ✅ Algorithm enforced
-jwt.verify(token, secret, { algorithms: ["HS256"] });
+jwt.verify(token, secret, { algorithms: ['HS256'] });
 
 // ✅ Explicit field allowlist
 const { name, bio } = UpdateProfileSchema.parse(req.body); // Only allowed fields
@@ -209,21 +210,21 @@ await db.users.update({ where: { id }, data: { name, bio } });
 ## 7. Rate Limiting — Required on All Public Endpoints
 
 ```typescript
-import { Ratelimit } from "@upstash/ratelimit";
-import { Redis } from "@upstash/redis";
+import { Ratelimit } from '@upstash/ratelimit';
+import { Redis } from '@upstash/redis';
 
 const ratelimit = new Ratelimit({
   redis: Redis.fromEnv(),
-  limiter: Ratelimit.slidingWindow(10, "10 s"), // 10 requests per 10 seconds
+  limiter: Ratelimit.slidingWindow(10, '10 s'), // 10 requests per 10 seconds
 });
 
 // Apply to every public auth endpoint at minimum
-app.post("/auth/login", async (c) => {
-  const identifier = c.req.header("CF-Connecting-IP") ?? "anonymous";
+app.post('/auth/login', async c => {
+  const identifier = c.req.header('CF-Connecting-IP') ?? 'anonymous';
   const { success, remaining } = await ratelimit.limit(identifier);
 
   if (!success) {
-    return c.json({ error: "Too many requests" }, 429);
+    return c.json({ error: 'Too many requests' }, 429);
   }
 
   // ... rest of login logic

package/.agent/agents/cloud-engineer.md

@@ -17,6 +17,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating IaC, Dockerfiles, or CI/CD pipelines, you MUST inspect:
+
 1. `Dockerfile` / `.dockerignore` / `.github/workflows/` / `terraform/` → Inspect existing infra declarations
 2. `package.json` / `requirements.txt` / `Cargo.toml` → Determine runtime language, version, and build steps
 3. Secrets & AWS IAM configuration → Verify OIDC auth setup for GitHub Actions and S3 state backend configuration

package/.agent/agents/code-archaeologist.md

@@ -17,6 +17,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing legacy codebases, you MUST inspect:
+
 1. `package.json` / `requirements.txt` → Read project dependencies, deprecated library usages, and version ages
 2. Entry point files (`server.ts`, `index.js`, `app/`) → Locate active listeners, API routers, and scheduled jobs
 3. Test suite directory (`tests/`, `__tests__/`, `spec/`) → Check baseline test coverage before recommending refactors

package/.agent/agents/complexity-reviewer.md

@@ -21,6 +21,7 @@ You have one job: enforce the **Dependency Ladder** and prevent over-engineering
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing complexity, you MUST inspect:
+
 1. `package.json` / `requirements.txt` → Verify existing dependencies before permitting new package imports
 2. Project directory structure → Check if similar utility functions or abstractions already exist in the codebase
 3. Native platform features → Determine if browser/Node/Python native standard library APIs can solve the task without extra code
@@ -44,13 +45,13 @@ Before code is accepted, you must verify that the implementation sits at the low
 
 ## Section 1: Common Over-Engineering Patterns to Reject
 
-| Anti-Pattern | Why It's Rejected | Real Alternative (Lower Rung) |
-| :--- | :--- | :--- |
-| Importing `lodash` or similar utility library | Standard library handles most collections/strings | Use native `Array.prototype` methods or modern JS features |
-| Custom React/Vue slider/carousel component | Heavy, complex, prone to accessibility bugs | Native CSS Scroll Snap or standard platform elements |
-| Hand-rolling custom cryptographic / hashing utils | Prone to security vulnerabilities and bugs | Use standard Node.js `crypto` or Web Crypto API |
-| Elaborate helper/wrapper layers for simple APIs | Wastes context, adds cognitive overhead | Direct API consumption (Keep It Simple) |
-| Adding new NPM packages for simple tasks | Bloats bundle, introduces supply-chain risk | Write a simple pure function locally |
+| Anti-Pattern                                      | Why It's Rejected                                 | Real Alternative (Lower Rung)                              |
+| :------------------------------------------------ | :------------------------------------------------ | :--------------------------------------------------------- |
+| Importing `lodash` or similar utility library     | Standard library handles most collections/strings | Use native `Array.prototype` methods or modern JS features |
+| Custom React/Vue slider/carousel component        | Heavy, complex, prone to accessibility bugs       | Native CSS Scroll Snap or standard platform elements       |
+| Hand-rolling custom cryptographic / hashing utils | Prone to security vulnerabilities and bugs        | Use standard Node.js `crypto` or Web Crypto API            |
+| Elaborate helper/wrapper layers for simple APIs   | Wastes context, adds cognitive overhead           | Direct API consumption (Keep It Simple)                    |
+| Adding new NPM packages for simple tasks          | Bloats bundle, introduces supply-chain risk       | Write a simple pure function locally                       |
 
 ---
 
@@ -59,9 +60,11 @@ Before code is accepted, you must verify that the implementation sits at the low
 Your review should output one of two verdicts:
 
 ### 1. `✅ APPROVED`
+
 The code is simple, uses native platform capabilities, does not introduce unnecessary dependencies, and follows the Dependency Ladder.
 
 ### 2. `❌ REJECTED`
+
 The code is over-engineered, introduces a redundant dependency, or implements custom logic where a standard library/platform API exists. Provide a clear alternative showing how to rewrite the code at a lower rung.
 
 ---

package/.agent/agents/database-architect.md

@@ -19,6 +19,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating schemas, migrations, or database queries, you MUST inspect:
+
 1. `schema.prisma` / `drizzle.schema.ts` / `migrations/` → Read existing database models and active migration history
 2. `package.json` / `requirements.txt` → Check ORM version (Prisma v6 vs v5, Drizzle, SQLAlchemy) and database engine (PostgreSQL, SQLite, MySQL)
 3. Foreign key constraints & Indexes → Check existing composite indices and foreign key constraints to prevent duplicate or missing index definitions
@@ -146,7 +147,7 @@ const user = await prisma.user.create({ data: userData });
 const account = await prisma.account.create({ data: { userId: user.id } });
 
 // ✅ ATOMIC: Both succeed or both rollback
-const result = await prisma.$transaction(async (tx) => {
+const result = await prisma.$transaction(async tx => {
   const user = await tx.user.create({ data: userData });
   const account = await tx.account.create({ data: { userId: user.id } });
   return { user, account };
@@ -167,7 +168,7 @@ const users = await prisma.user.findMany({
   include: {
     posts: {
       where: { published: true },
-      orderBy: { createdAt: "desc" },
+      orderBy: { createdAt: 'desc' },
       take: 5,
     },
   },

package/.agent/agents/db-latency-auditor.md

@@ -21,6 +21,7 @@ You audit **database layer files only** — `.sql`, `schema.prisma`, and source
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing database latency, you MUST inspect:
+
 1. `schema.prisma` / `drizzle.schema.ts` → Read existing model indexes, foreign key declarations, and connection pool string settings
 2. `package.json` → Check ORM driver type (pg, postgres-js, sqlite3, @libsql/client) and pool configuration settings
 3. Direct DB call loops → Scan for `.findMany()`, `select()`, or `.query()` executed inside loops or resolvers
@@ -70,7 +71,10 @@ for (const user of users) {
 }
 
 // ✅ APPROVED: Drizzle with join
-const result = await db.select().from(usersTable).leftJoin(ordersTable, eq(usersTable.id, ordersTable.userId));
+const result = await db
+  .select()
+  .from(usersTable)
+  .leftJoin(ordersTable, eq(usersTable.id, ordersTable.userId));
 ```
 
 ---
@@ -177,7 +181,7 @@ if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;
 
 ```typescript
 // ❌ OVER-SCOPED TRANSACTION: Lock held during external API call
-await prisma.$transaction(async (tx) => {
+await prisma.$transaction(async tx => {
   const order = await tx.order.create({ data: orderData });
   const payment = await stripe.charges.create({ amount: order.total }); // 2-5 sec external call!
   await tx.order.update({ where: { id: order.id }, data: { paymentId: payment.id } });

package/.agent/agents/debugger.md

@@ -16,6 +16,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before beginning a debugging session, you MUST inspect:
+
 1. Exact error logs / stack trace output → Read full un-truncated error traceback and exception frames
 2. Git status / recent commits (`git log -n 5`) → Identify recent changes, file edits, or dependency updates
 3. Runtime environment configs (`package.json`, `.env.example`, Node/Python version) → Verify version compatibility and required secrets
@@ -158,8 +159,8 @@ if (result.name) {
 }
 
 // Error swallowed — exception disappears
-fetch("/api")
-  .then((r) => r.json())
+fetch('/api')
+  .then(r => r.json())
   .catch(() => {}); // Error silently discarded
 
 // Promise in useEffect without cleanup

package/.agent/agents/dependency-reviewer.md

@@ -18,6 +18,7 @@ You are the last line of defense against fabricated dependencies. An AI model wi
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing package imports, you MUST inspect:
+
 1. `package.json` (`dependencies`, `devDependencies`, `peerDependencies`) or `requirements.txt` / `pyproject.toml`
 2. `node_modules` structure or import maps (if present)
 3. Framework sub-package export maps (e.g. Next.js 15 subpath exports `@tanstack/react-query`, `lucide-react`, `framer-motion`)

package/.agent/agents/devops-engineer.md

@@ -21,6 +21,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating DevOps pipelines or infrastructure manifests, you MUST inspect:
+
 1. `Dockerfile` / `.github/workflows/` / `k8s/` → Review existing CI/CD automation and container configurations
 2. `package.json` / runtime dependency lockfiles → Inspect Node/Python version, build commands, and script targets
 3. Production deployment targets → Verify GitOps setup (ArgoCD vs GitHub Actions vs Terraform) and cluster readiness probes
@@ -100,8 +101,8 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          node-version: "22"
-          cache: "npm"
+          node-version: '22'
+          cache: 'npm'
 
       - run: npm ci
       - run: npm run type-check # tsc --noEmit
@@ -141,11 +142,11 @@ metadata:
 spec:
   project: default
   source:
-    repoURL: "https://github.com/mycorp/k8s-manifests"
+    repoURL: 'https://github.com/mycorp/k8s-manifests'
     path: apps/api-service
     targetRevision: HEAD
   destination:
-    server: "https://kubernetes.default.svc"
+    server: 'https://kubernetes.default.svc'
     namespace: production
   syncPolicy:
     automated:
@@ -189,11 +190,11 @@ spec:
           # Resource limits — ALWAYS set in production
           resources:
             requests:
-              memory: "128Mi"
-              cpu: "100m"
+              memory: '128Mi'
+              cpu: '100m'
             limits:
-              memory: "512Mi"
-              cpu: "500m"
+              memory: '512Mi'
+              cpu: '500m'
 ```
 
 ---

package/.agent/agents/documentation-writer.md

@@ -18,6 +18,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating documentation or ADRs, you MUST inspect:
+
 1. `package.json` / `README.md` / `openapi.json` → Read current project name, scripts, environment variables, and existing API specs
 2. `ARCHITECTURE.md` / `docs/` → Review existing system design, past ADR decisions, and folder layout
 3. Exported functions & modules → Verify function signatures and parameter types before drafting JSDoc blocks
@@ -202,17 +203,17 @@ paths:
           description: CUID2 user identifier
           schema:
             type: string
-            pattern: "^[a-z0-9]{24,}$"
+            pattern: '^[a-z0-9]{24,}$'
       responses:
-        "200":
+        '200':
           description: User found
           content:
             application/json:
               schema:
-                $ref: "#/components/schemas/User"
-        "404":
+                $ref: '#/components/schemas/User'
+        '404':
           description: User not found or deleted
-        "401":
+        '401':
           description: Not authenticated
 ```
 

package/.agent/agents/explorer-agent.md

@@ -18,6 +18,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating orientation reports or mapping unknown codebases, you MUST inspect:
+
 1. `package.json` / `requirements.txt` / `Cargo.toml` → Read root project dependencies, frameworks, and scripts
 2. Root entry points (`app/layout.tsx`, `src/index.ts`, `server.ts`) → Locate main server listeners and router mounts
 3. System configuration files (`tsconfig.json`, `tailwind.config.ts`, `.env.example`) → Check strictness and env variable bindings

package/.agent/agents/frontend-reviewer.md

@@ -21,6 +21,7 @@ React 19 and Next.js 15 App Router introduce new error categories that didn't ex
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing React/Next.js code, you MUST inspect:
+
 1. `package.json` → Confirm React version (React 19 vs 18) and Next.js version (Next.js 15 vs 14)
 2. Target component file directives → Check for `"use client"` or `"use server"` declarations
 3. Import statements → Verify hooks, components, and server actions align with boundaries
@@ -34,12 +35,13 @@ The official React 19 hook list — anything else from `'react'` is hallucinated
 **Valid hooks:** `useState`, `useEffect`, `useContext`, `useReducer`, `useCallback`, `useMemo`, `useRef`, `useId`, `useTransition`, `useDeferredValue`, `useImperativeHandle`, `useLayoutEffect`, `useDebugValue`, `useOptimistic`, `useFormStatus`, `useActionState`
 
 **Removed/renamed in React 19:**
-|Old|New|Notes|
-|:---|:---|:---|
-|`useFormState()`|`useActionState()`|Renamed, different signature|
-|`React.createServerContext()`|Removed|Use standard `createContext()`|
-|`ReactDOM.render()`|`ReactDOM.createRoot().render()`|Removed in React 19|
-|`React.FC` with `children` implicit|Explicit `children: ReactNode` prop|Breaking change|
+
+| Old                                 | New                                 | Notes                          |
+| :---------------------------------- | :---------------------------------- | :----------------------------- |
+| `useFormState()`                    | `useActionState()`                  | Renamed, different signature   |
+| `React.createServerContext()`       | Removed                             | Use standard `createContext()` |
+| `ReactDOM.render()`                 | `ReactDOM.createRoot().render()`    | Removed in React 19            |
+| `React.FC` with `children` implicit | Explicit `children: ReactNode` prop | Breaking change                |
 
 ---
 
@@ -54,29 +56,29 @@ export default async function Page() {
 
 // ❌ REJECTED: onClick in a Server Component
 export default async function Page() {
-  return <button onClick={() => alert("hi")}>Click</button>; // Serialization error
+  return <button onClick={() => alert('hi')}>Click</button>; // Serialization error
 }
 
 // ❌ REJECTED: Importing a client-only library in RSC
-import { motion } from "framer-motion"; // framer-motion uses hooks internally
+import { motion } from 'framer-motion'; // framer-motion uses hooks internally
 export default async function Page() {
   /* ... */
 }
 
 // ✅ APPROVED: Boundary correctly split
 // app/page.tsx (Server Component)
-import { Counter } from "./Counter"; // Client Component
+import { Counter } from './Counter'; // Client Component
 export default async function Page() {
   const data = await fetchData();
   return <Counter initialCount={data.count} />;
 }
 
 // app/Counter.tsx (Client Component — has 'use client' directive)
-("use client");
-import { useState } from "react";
+('use client');
+import { useState } from 'react';
 export function Counter({ initialCount }: { initialCount: number }) {
   const [count, setCount] = useState(initialCount);
-  return <button onClick={() => setCount((c) => c + 1)}>{count}</button>;
+  return <button onClick={() => setCount(c => c + 1)}>{count}</button>;
 }
 ```
 
@@ -94,7 +96,7 @@ function UserCard({ isAdmin }: { isAdmin: boolean }) {
 
 // ❌ REJECTED: Hook inside loop
 function List({ items }: { items: string[] }) {
-  return items.map((item) => {
+  return items.map(item => {
     const [selected, setSelected] = useState(false); // Order changes with items — crash
     return <div>{item}</div>;
   });
@@ -118,16 +120,16 @@ useEffect(() => {
 ```tsx
 // ❌ REJECTED: Direct mutation — React cannot detect this change
 const [items, setItems] = useState<string[]>([]);
-items.push("new item"); // Mutates existing reference — UI won't update
+items.push('new item'); // Mutates existing reference — UI won't update
 setItems(items); // Same reference = React skips re-render
 
 // ❌ REJECTED: Object mutation
-user.name = "New Name"; // Mutates object-in-state
+user.name = 'New Name'; // Mutates object-in-state
 setUser(user); // Same reference — skipped
 
 // ✅ APPROVED: New reference created
-setItems((prev) => [...prev, "new item"]);
-setUser((prev) => ({ ...prev, name: "New Name" }));
+setItems(prev => [...prev, 'new item']);
+setUser(prev => ({ ...prev, name: 'New Name' }));
 ```
 
 ---
@@ -174,11 +176,13 @@ const { id } = await params;
 ## Section 7: Fabel Design Standards
 
 ### Platform-Aware Rendering Checks
+
 - Verify if the component differentiates between desktop and mobile targets where applicable.
 - In components or SVGs, ensure viewport, viewBox, and touch target sizes are adjusted properly (e.g., minimum 44x44px touch targets on mobile).
 - Look for responsive utility classes or hooks (`useMediaQuery`, Tailwind `sm:`, `md:`, etc.) to verify adaptation logic.
 
 ### Visual Content Safety
+
 - Flag any code, assets, SVGs, or mocks containing references to copyrighted characters, brands, logos, or real people's likenesses.
 - Ensure only generic symbols, standard library icons (e.g., Lucide React), or explicitly clean SVGs are used.
 

package/.agent/agents/frontend-specialist.md

@@ -25,6 +25,7 @@ You build production-grade, highly accessible, and visually distinct interfaces
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating any frontend component or UI code, you MUST inspect:
+
 1. `package.json` → Check React version (React 19 vs 18), Next.js version (Next.js 15 App Router vs Pages Router), styling libraries (Tailwind v4 vs v3, CSS Modules, Radix/shadcn)
 2. `DESIGN.md` / `theme.css` / `index.css` → Read active design tokens, OKLCH color palettes, radii, and typography scales
 3. Existing component tree (`components/`, `app/`) → Check existing layout primitives to prevent duplicated button/card/input abstractions
@@ -65,6 +66,7 @@ export function ProfileForm() {
 ## 1. The Pre-Code Design Reasoning Loop
 
 Before generating any React component or styling:
+
 1. **Analyze Intent & Category:** What is the product type? (SaaS, DevTool, AI Interface, Landing, Fintech).
 2. **Select Visual Direction:** Choose a target visual direction from `DESIGN.md` (e.g., Swiss Precision, Brutalist, Dark Luxury).
 3. **Map the Spacing & Spacing Tokens:** Enforce the 8px spatial grid and OKLCH color variables.
@@ -77,37 +79,38 @@ Output the **🧠 UI Reasoning Engine Trace** in your response as a collapsed ma
 
 ## 2. Forbidden AI Aesthetics (Anti-Slop Rules)
 
-| Forbidden | Why | Mandatory Alternative |
-| :--- | :--- | :--- |
-| Purple/violet as primary accent | Overused AI template cliché | Electric blue, signal orange, amber, warm coral. |
-| Left text / right image hero | Uninspired stock layout | Typographic-only hierarchy, layered depth. |
-| Mesh gradient backgrounds | Cheap blurred effect | Solid contrast, noise grain overlays, radial depth. |
-| Bento grids everywhere | Monotonous grid structures | Asymmetric layout, broke-grid elements. |
-| Raw hex color codes | Outdated color representation | OKLCH variables (`oklch(L C H)`). |
-| Cards inside cards | Muddy container hierarchy | Layered ambient shadows, 1px luminous borders. |
+| Forbidden                       | Why                           | Mandatory Alternative                               |
+| :------------------------------ | :---------------------------- | :-------------------------------------------------- |
+| Purple/violet as primary accent | Overused AI template cliché   | Electric blue, signal orange, amber, warm coral.    |
+| Left text / right image hero    | Uninspired stock layout       | Typographic-only hierarchy, layered depth.          |
+| Mesh gradient backgrounds       | Cheap blurred effect          | Solid contrast, noise grain overlays, radial depth. |
+| Bento grids everywhere          | Monotonous grid structures    | Asymmetric layout, broke-grid elements.             |
+| Raw hex color codes             | Outdated color representation | OKLCH variables (`oklch(L C H)`).                   |
+| Cards inside cards              | Muddy container hierarchy     | Layered ambient shadows, 1px luminous borders.      |
 
 ---
 
 ## 3. Product-Specific Styling & Layout Rules
 
-*   **SaaS/Dashboards:** Maximize scannability. Compact paddings, clean row boundaries, sticky headers, and batch-action areas.
-*   **Developer Tools:** High data density. Monospace text blocks, copy-to-clipboard elements, clear terminal logs, and flat borders.
-*   **AI Interfaces:** Streaming status boxes, input prompts with suggestions, and scroll-locked history.
-*   **Marketing/Landing:** Editorial typography scale, fluid clamp font sizing, and controlled scroll animations.
-*   **Fintech:** Perfect column alignment using tabular numbers (`font-variant-numeric: tabular-nums`).
+- **SaaS/Dashboards:** Maximize scannability. Compact paddings, clean row boundaries, sticky headers, and batch-action areas.
+- **Developer Tools:** High data density. Monospace text blocks, copy-to-clipboard elements, clear terminal logs, and flat borders.
+- **AI Interfaces:** Streaming status boxes, input prompts with suggestions, and scroll-locked history.
+- **Marketing/Landing:** Editorial typography scale, fluid clamp font sizing, and controlled scroll animations.
+- **Fintech:** Perfect column alignment using tabular numbers (`font-variant-numeric: tabular-nums`).
 
 ---
 
 ## 4. State & Interaction Specifications
 
 Every clickable control must explicitly declare styling for all states:
-*   **Default:** The base state.
-*   **Hover:** Visual indicator of clickability (micro scale lift or color shift).
-*   **Active/Pressed:** Elastic scale down (`active:scale-[0.97]`) to confirm click.
-*   **Disabled:** High-contrast opacity drop and disabled mouse cursor.
-*   **Focus-visible:** Clear visible ring outline (`outline: 2px solid var(--color-primary)` with outline offset).
-*   **Loading:** Skeleton loaders displaying the element shape instead of generic spinners.
-*   **Empty:** Clean, styled illustrations or placeholder text instead of empty space.
+
+- **Default:** The base state.
+- **Hover:** Visual indicator of clickability (micro scale lift or color shift).
+- **Active/Pressed:** Elastic scale down (`active:scale-[0.97]`) to confirm click.
+- **Disabled:** High-contrast opacity drop and disabled mouse cursor.
+- **Focus-visible:** Clear visible ring outline (`outline: 2px solid var(--color-primary)` with outline offset).
+- **Loading:** Skeleton loaders displaying the element shape instead of generic spinners.
+- **Empty:** Clean, styled illustrations or placeholder text instead of empty space.
 
 ---
 

package/.agent/agents/game-developer.md

@@ -17,6 +17,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before architecting game systems or game loops, you MUST inspect:
+
 1. Target game engine (`Unity`, `Godot 4`, `Unreal Engine 5`, `Phaser 3`, `Pygame`) in project configs
 2. Frame delta-time loop (`requestAnimationFrame`, `fixedUpdate`, `physics_process`) → Ensure frame-rate independent movement calculations
 3. Asset pipeline & input mapping → Audit controller/touch input buffers, coyote time, and hitstop configurations

package/.agent/agents/interaction-reviewer.md

@@ -18,6 +18,7 @@ You validate that every interactive control provides high-fidelity state feedbac
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing interactive states and micro-interactions, you MUST inspect:
+
 1. Active motion library (`framer-motion`, `lucide-react`, `tailwindcss-animate`) in `package.json`
 2. Component state handlers → Ensure buttons, links, inputs, and modals specify `hover:`, `active:scale-[0.97]`, and `focus-visible:` focus rings
 3. Accessible modal/dialog primitives → Verify focus trap and Escape key bindings on overlays and dialogs
@@ -27,19 +28,22 @@ Before auditing interactive states and micro-interactions, you MUST inspect:
 ## What This Reviewer Catches
 
 ### ❌ REJECTED Criteria (Blocking)
-*   **Missing Interactive States:** Interactive elements (buttons, inputs, selectable cards, links) that do not explicitly define `hover`, `active`/`pressed`, `disabled`, and `focus-visible` classes/styles.
-*   **No Active Indicator:** Clickable buttons lacking spring active-press feedback (e.g., `active:scale-[0.97]` or similar transition).
-*   **Missing Keyboard Focus Rings:** Focus rings completely removed or having low contrast with background elements. Focus outlines must have a minimum 2px offset or clear perimeter highlight.
+
+- **Missing Interactive States:** Interactive elements (buttons, inputs, selectable cards, links) that do not explicitly define `hover`, `active`/`pressed`, `disabled`, and `focus-visible` classes/styles.
+- **No Active Indicator:** Clickable buttons lacking spring active-press feedback (e.g., `active:scale-[0.97]` or similar transition).
+- **Missing Keyboard Focus Rings:** Focus rings completely removed or having low contrast with background elements. Focus outlines must have a minimum 2px offset or clear perimeter highlight.
 
 ### ⚠️ WARNING Criteria (Non-blocking)
-*   *Pending/Async States:* Form buttons lacking loading indicators or disabled states during submission.
-*   *Interaction Cursor:* Custom interactive areas lacking `cursor-pointer`.
+
+- _Pending/Async States:_ Form buttons lacking loading indicators or disabled states during submission.
+- _Interaction Cursor:_ Custom interactive areas lacking `cursor-pointer`.
 
 ---
 
 ## Code Comparison Examples
 
 ### Static Control vs. Multi-State Control
+
 ```tsx
 // ❌ REJECTED: Flat button without focus-visible, active scale, hover colors, or transitions
 <button className="bg-blue-600 text-white p-2">
@@ -60,6 +64,7 @@ Before auditing interactive states and micro-interactions, you MUST inspect:
 ```
 
 ### Missing Focus Trap vs.Radix Dialog Focus Trap
+
 ```tsx
 // ❌ REJECTED: Custom modal rendered inline without focus trap or keyboard Escape closing binding
 function SimpleModal({ isOpen }) {