tribunal-kit 6.0.0 → 7.0.0

package/.agent/workflows/tribunal-performance.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before optimizing code or running performance reviews, you MUST inspect:
+
 1. Target Source & Heavy Import Inspection (`package.json`, `next.config.js`) → Identify heavy library imports (`moment`, full `lodash`) for tree-shaking
 2. Measured Baseline Metrics → Run `bundle_analyzer.js` or latency measurements; ban claiming performance improvements without measured proof
 3. 2-Reviewer Performance Gate → Run logic-reviewer and performance-optimizer before approving optimization diffs

package/.agent/workflows/tribunal-speed.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before running a full-stack performance audit, you MUST inspect:
+
 1. Target Full-Stack File Map → Determine frontend components, Node.js server routes, and database models
 2. Max 5 AI Call Ceiling → Cap swarm executions to 3 parallel specialists + 1 synthesis step to prevent token explosion
 3. Ranked Impact Synthesis → Output findings strictly in a single unified table prioritized by user-facing latency impact

package/.agent/workflows/tribunal-ui.md

@@ -23,6 +23,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before executing dedicated UI/UX audits or design-system reviews, you MUST inspect:
+
 1. Active Design Tokens & Guidelines (`DESIGN.md`, CSS custom properties) → Confirm typography scale, color system, and corner radius tokens
 2. Product Domain Category → Select category heuristics (Dashboard, E-Commerce, Landing Page, Mobile App, Marketing)
 3. 7-Reviewer Dedicated UI Gate → Run ux-auditor, visual-auditor, interaction-auditor, anti-pattern-auditor, product-heuristics, a11y-auditor, and visual-auditor before passing designs
@@ -31,45 +32,52 @@ Before executing dedicated UI/UX audits or design-system reviews, you MUST inspe
 
 ## When to Use /tribunal-ui
 
-| Use `/tribunal-ui` when... | Use instead when... |
-| :--- | :--- |
-| Auditing visual hierarchy & rhythm | Reviewing backend routing → `/tribunal-backend` |
-| Verifying interactive states and hover/focus | Reviewing database transaction code → `/tribunal-database` |
-| Checking responsive behavior and ergonomics | Doing general logical code checks → `/tribunal-frontend` |
-| Banning generic AI templates & purple gradients | |
-| Testing accessibility compliance (WCAG 2.2 AA) | |
+| Use `/tribunal-ui` when...                      | Use instead when...                                        |
+| :---------------------------------------------- | :--------------------------------------------------------- |
+| Auditing visual hierarchy & rhythm              | Reviewing backend routing → `/tribunal-backend`            |
+| Verifying interactive states and hover/focus    | Reviewing database transaction code → `/tribunal-database` |
+| Checking responsive behavior and ergonomics     | Doing general logical code checks → `/tribunal-frontend`   |
+| Banning generic AI templates & purple gradients |                                                            |
+| Testing accessibility compliance (WCAG 2.2 AA)  |                                                            |
 
 ---
 
 ## 7 Specialized UI Reviewers (Running Simultaneously)
 
 ### 1. ux-reviewer
-*   **Focus:** Hick's Law, Fitts's Law, cognitive load, scanning patterns, scannability, and progressive disclosure.
-*   **Check:** Are primary action targets separated from destructive ones? Is choice overload prevented?
+
+- **Focus:** Hick's Law, Fitts's Law, cognitive load, scanning patterns, scannability, and progressive disclosure.
+- **Check:** Are primary action targets separated from destructive ones? Is choice overload prevented?
 
 ### 2. visual-reviewer
-*   **Focus:** Typographical scaling, alignment, margins, 8px grid discipline, and line lengths.
-*   **Check:** Do Display headings balanced-wrap (`text-wrap: balance`)? Is negative space utilized?
+
+- **Focus:** Typographical scaling, alignment, margins, 8px grid discipline, and line lengths.
+- **Check:** Do Display headings balanced-wrap (`text-wrap: balance`)? Is negative space utilized?
 
 ### 3. interaction-reviewer
-*   **Focus:** Full interactive state styling (Default, Hover, Active/Pressed, Disabled, Focus-visible, Loading).
-*   **Check:** Is there scale-down active click feedback? Are focus outlines visible and offset?
+
+- **Focus:** Full interactive state styling (Default, Hover, Active/Pressed, Disabled, Focus-visible, Loading).
+- **Check:** Is there scale-down active click feedback? Are focus outlines visible and offset?
 
 ### 4. anti-pattern-reviewer
-*   **Focus:** Blocking generic AI visual clichés.
-*   **Check:** Blocks purple/violet primary colors, radial mesh gradients, bento grid overload, flat cards lacking depth, and card-in-card overlap.
+
+- **Focus:** Blocking generic AI visual clichés.
+- **Check:** Blocks purple/violet primary colors, radial mesh gradients, bento grid overload, flat cards lacking depth, and card-in-card overlap.
 
 ### 5. product-reviewer
-*   **Focus:** Matching the UI structure to product category heuristics (SaaS, DevTool, AI Interface, Landing, Fintech).
-*   **Check:** Tabular numbers used for financial data? Monospace code snippets for DevTools? Typing skeleton streams for AI?
+
+- **Focus:** Matching the UI structure to product category heuristics (SaaS, DevTool, AI Interface, Landing, Fintech).
+- **Check:** Tabular numbers used for financial data? Monospace code snippets for DevTools? Typing skeleton streams for AI?
 
 ### 6. accessibility-reviewer
-*   **Focus:** WCAG 2.2 Level AA compliance.
-*   **Check:** Minimum target size 24px (standard AA) and 44px (touch). Semantic headings, accessible ARIA names, and keyboard trap focus in dialogs.
+
+- **Focus:** WCAG 2.2 Level AA compliance.
+- **Check:** Minimum target size 24px (standard AA) and 44px (touch). Semantic headings, accessible ARIA names, and keyboard trap focus in dialogs.
 
 ### 7. ui-visual-auditor (Closed-Loop Visual Gate)
-*   **Focus:** Screenshot or DOM layout verification.
-*   **Check:** Checks vertical overflow, layout shifts (CLS), alignment shifts, and contrast ratios.
+
+- **Focus:** Screenshot or DOM layout verification.
+- **Check:** Checks vertical overflow, layout shifts (CLS), alignment shifts, and contrast ratios.
 
 ---
 

package/.agent/workflows/ui-ux-pro-max.md

@@ -23,6 +23,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before designing or implementing advanced UI/UX layouts, you MUST inspect:
+
 1. Active Design Tokens & System (`DESIGN.md`, CSS custom properties) → Verify OKLCH color palettes, typography scale, and spacing grid
 2. UI Reasoning Engine 16-Step Pipeline (`.agent/skills/ui-reasoning-engine/SKILL.md`) → Structure component layout, micro-interactions, and accessibility before coding
 3. Anti-Generic Aesthetic Rule → Ban plain purple/violet AI gradients and stock hero templates; enforce bespoke visual hierarchy and tactile micro-interactions
@@ -31,18 +32,19 @@ Before designing or implementing advanced UI/UX layouts, you MUST inspect:
 
 ## When to Use /ui-ux-pro-max
 
-| Use `/ui-ux-pro-max` when... | Use instead when... |
-| :--- | :--- |
+| Use `/ui-ux-pro-max` when...              | Use instead when...                     |
+| :---------------------------------------- | :-------------------------------------- |
 | Building a visually distinctive interface | Functional-only component → `/generate` |
-| Design quality is the primary goal | Fast page needed → `/enhance` |
-| Creating from a design brief | Bug fix in UI → `/debug` |
-| Mobile + web parity required | |
+| Design quality is the primary goal        | Fast page needed → `/enhance`           |
+| Creating from a design brief              | Bug fix in UI → `/debug`                |
+| Mobile + web parity required              |                                         |
 
 ---
 
 ## Phase 1 — Design Intent & Product Aware Reasoning (Mandatory)
 
 Answer these before writing any code (using the `ui-reasoning-engine` skill):
+
 1. **Who is the user?** (Casual consumer vs expert operator).
 2. **What is the product category?** (SaaS, DevTool, AI Interface, Landing, Fintech).
 3. **What is the visual direction?** (Brutalist, Editorial, Soft Minimal, Dark Luxury, Swiss).
@@ -56,17 +58,19 @@ Write the **🧠 UI Reasoning Engine Trace** in your response as a collapsed mar
 ## Phase 2 — Visual Identity & Design Tokens
 
 Every interface must use custom variables defined in `DESIGN.md` and `design-tokens.json`:
-*   ❌ **Banned Clichés:** Purple/violet accents, mesh gradients, glassmorphism overuse, default library themes.
-*   ✅ **Intentional Styling:** Dynamic OKLCH colors, 8px grid alignment, variable font sizes with CSS `clamp()`, and 1px luminous borders.
+
+- ❌ **Banned Clichés:** Purple/violet accents, mesh gradients, glassmorphism overuse, default library themes.
+- ✅ **Intentional Styling:** Dynamic OKLCH colors, 8px grid alignment, variable font sizes with CSS `clamp()`, and 1px luminous borders.
 
 ---
 
 ## Phase 3 — Interaction States & Micro-interactions
 
 Ensure every interactive element has styling defined for:
-*   `hover`, `focus-visible`, `active`/`pressed`, and `disabled` states.
-*   Confirm clicks with spring scale-down transitions (`active:scale-[0.97]`).
-*   Trap keyboard focus within modals/dialogs and return it to the trigger on close.
+
+- `hover`, `focus-visible`, `active`/`pressed`, and `disabled` states.
+- Confirm clicks with spring scale-down transitions (`active:scale-[0.97]`).
+- Trap keyboard focus within modals/dialogs and return it to the trigger on close.
 
 ---
 
@@ -92,8 +96,8 @@ Ensure every interactive element has styling defined for:
 
 ## After /ui-ux-pro-max — Next Steps
 
-| Outcome | Next Command |
-| :--- | :--- |
-| Design complete | → `/preview start` to see it in action |
-| Reviewers reject with fixes | → Apply fixes, then run `/tribunal-ui` again |
-| Performance concerns | → `/performance-benchmarker` for Lighthouse/CWV |
+| Outcome                     | Next Command                                    |
+| :-------------------------- | :---------------------------------------------- |
+| Design complete             | → `/preview start` to see it in action          |
+| Reviewers reject with fixes | → Apply fixes, then run `/tribunal-ui` again    |
+| Performance concerns        | → `/performance-benchmarker` for Lighthouse/CWV |

package/CONTRIBUTING.md

@@ -42,9 +42,9 @@ tribunal-kit/
 │   └── index.d.ts          # TypeScript declarations
 ├── crates/core/            # Rust core engine (Tokio-based)
 ├── .agent/                 # The intelligence payload (agents, skills, workflows)
-│   ├── agents/             # 51 specialist and reviewer agent definitions
+│   ├── agents/             # 52 specialist and reviewer agent definitions
 │   ├── skills/             # Reusable skill packs
-│   ├── workflows/          # 37 workflow definitions
+│   ├── workflows/          # 40 workflow definitions
 │   └── scripts/            # Automation scripts
 ├── test/
 │   ├── unit/               # Unit tests (Jest)
@@ -119,7 +119,7 @@ Tribunal Kit's value comes from its agent and skill library. To contribute:
 - **JavaScript**: CommonJS (`require`/`module.exports`), no transpilation needed
 - **Naming**: `camelCase` for functions/variables, `UPPER_SNAKE` for constants
 - **Error handling**: Always handle errors in async functions
-- **Comments**: Explain *why*, not *what*
+- **Comments**: Explain _why_, not _what_
 - **No new dependencies**: Zero production dependencies is a feature, not a limitation
 
 ## Review Process