tribunal-kit 2.4.6 → 3.1.0

package/.agent/skills/trend-researcher/SKILL.md

@@ -27,12 +27,12 @@ You are a creative muse and design trend analyst. Your purpose is to bridge the
 
 Leverage `search_web` to scan top design aggregators and classify trends by maturity:
 
-| Maturity | Description | Examples (2025–2026) | Risk |
+|Maturity|Description|Examples (2025–2026)|Risk|
 |---|---|---|---|
-| **Established** | Widely adopted, safe to use | Bento Grids, Glassmorphism, Dark Mode | Low |
-| **Rising** | Gaining traction, differentiating | Claymorphism, Spatial UI, Kinetic Typography | Medium |
-| **Experimental** | Cutting-edge, high differentiation | Generative Art Backgrounds, 3D Morphing Cards, AI-Responsive Layouts | High |
-| **Declining** | Overused, losing impact | Flat Minimalism, Neumorphism, Full-bleed hero images | Avoid unless justified |
+|**Established**|Widely adopted, safe to use|Bento Grids, Glassmorphism, Dark Mode|Low|
+|**Rising**|Gaining traction, differentiating|Claymorphism, Spatial UI, Kinetic Typography|Medium|
+|**Experimental**|Cutting-edge, high differentiation|Generative Art Backgrounds, 3D Morphing Cards, AI-Responsive Layouts|High|
+|**Declining**|Overused, losing impact|Flat Minimalism, Neumorphism, Full-bleed hero images|Avoid unless justified|
 
 **Banned Clichés (Unless Explicitly Requested):**
 - ❌ Purple/violet gradients as primary AI branding
@@ -61,14 +61,14 @@ Semantic   → Success (green), Warning (amber), Error (red), Info (blue)
 
 Recommend Google Font pairings based on personality:
 
-| Personality | Heading Font | Body Font | Usage |
+|Personality|Heading Font|Body Font|Usage|
 |---|---|---|---|
-| **Elevated Minimalist** | Playfair Display | Inter | Luxury, editorial |
-| **Modern Tech** | Space Grotesk | DM Sans | SaaS, dashboards |
-| **Friendly Product** | Outfit | Source Sans 3 | Consumer apps |
-| **Bold Creative** | Clash Display | Satoshi | Portfolios, agencies |
-| **Corporate Trust** | Plus Jakarta Sans | Noto Sans | Enterprise, fintech |
-| **Editorial Long-form** | Fraunces | Literata | Blogs, magazines |
+|**Elevated Minimalist**|Playfair Display|Inter|Luxury, editorial|
+|**Modern Tech**|Space Grotesk|DM Sans|SaaS, dashboards|
+|**Friendly Product**|Outfit|Source Sans 3|Consumer apps|
+|**Bold Creative**|Clash Display|Satoshi|Portfolios, agencies|
+|**Corporate Trust**|Plus Jakarta Sans|Noto Sans|Enterprise, fintech|
+|**Editorial Long-form**|Fraunces|Literata|Blogs, magazines|
 
 **Scale:** Always recommend a modular scale (Major Third 1.25 or Perfect Fourth 1.333).
 
@@ -76,25 +76,25 @@ Recommend Google Font pairings based on personality:
 
 Translate trends into structured layout decisions:
 
-| Pattern | When to Use | CSS Approach |
+|Pattern|When to Use|CSS Approach|
 |---|---|---|
-| **Bento Grid** | Dashboards, landing page feature sections | `grid-template-areas` with varied spans |
-| **Asymmetric Split** | Hero sections, about pages | 60/40 or 70/30 grid columns |
-| **Full-bleed Cards** | Mobile-first content lists | `width: 100vw` with negative margin |
-| **Stacked Sections** | Long-form landing pages | `scroll-snap-type: y mandatory` |
-| **Sidebar + Canvas** | App layouts, admin panels | `grid-template-columns: 240px 1fr` |
-| **Overlapping Layers** | Creative portfolios, editorials | Negative margins + z-index layering |
+|**Bento Grid**|Dashboards, landing page feature sections|`grid-template-areas` with varied spans|
+|**Asymmetric Split**|Hero sections, about pages|60/40 or 70/30 grid columns|
+|**Full-bleed Cards**|Mobile-first content lists|`width: 100vw` with negative margin|
+|**Stacked Sections**|Long-form landing pages|`scroll-snap-type: y mandatory`|
+|**Sidebar + Canvas**|App layouts, admin panels|`grid-template-columns: 240px 1fr`|
+|**Overlapping Layers**|Creative portfolios, editorials|Negative margins + z-index layering|
 
 ### 5. Motion & Interaction Direction
 
 Pair with `whimsy-injector` for implementation. Here, define the *intention*:
 
-| Intent | Motion Type | Duration | Easing |
+|Intent|Motion Type|Duration|Easing|
 |---|---|---|---|
-| **Guide attention** | Subtle pulse / scale on CTA | 200ms | ease-out |
-| **Show hierarchy** | Staggered entrance on scroll | 300ms per item, 50ms stagger | cubic-bezier(0.4, 0, 0.2, 1) |
-| **Confirm action** | Checkmark draw / color flash | 150ms | ease-in-out |
-| **Create depth** | Parallax on scroll | Continuous | linear (scroll-driven) |
+|**Guide attention**|Subtle pulse / scale on CTA|200ms|ease-out|
+|**Show hierarchy**|Staggered entrance on scroll|300ms per item, 50ms stagger|cubic-bezier(0.4, 0, 0.2, 1)|
+|**Confirm action**|Checkmark draw / color flash|150ms|ease-in-out|
+|**Create depth**|Parallax on scroll|Continuous|linear (scroll-driven)|
 
 ## Interaction Protocol
 
@@ -151,13 +151,13 @@ When implementing designs:
 
 ## Cross-Skill Integration
 
-| Paired Skill | Integration Point |
+|Paired Skill|Integration Point|
 |---|---|
-| `ui-ux-researcher` | Validate palette contrast + cognitive load after applying trend |
-| `whimsy-injector` | Pass motion intent → receive implementation snippets |
-| `frontend-design` | Use as reference for component-level styling |
-| `web-design-guidelines` | Ensure trend suggestions comply with established guidelines |
-| `seo-fundamentals` | Verify that trend choices don't harm Core Web Vitals |
+|`ui-ux-researcher`|Validate palette contrast + cognitive load after applying trend|
+|`whimsy-injector`|Pass motion intent → receive implementation snippets|
+|`frontend-design`|Use as reference for component-level styling|
+|`web-design-guidelines`|Ensure trend suggestions comply with established guidelines|
+|`seo-fundamentals`|Verify that trend choices don't harm Core Web Vitals|
 
 ## Anti-Hallucination Guard
 
@@ -184,45 +184,4 @@ Pre-Flight:  ✅ All checks passed
              or ❌ [blocking item that must be resolved first]
 ```
 
-
-
 ---
-
-## 🤖 LLM-Specific Traps
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.

package/.agent/skills/ui-ux-pro-max/SKILL.md

@@ -64,45 +64,4 @@ Pre-Flight:  ✅ All checks passed
              or ❌ [blocking item that must be resolved first]
 ```
 
-
-
 ---
-
-## 🤖 LLM-Specific Traps
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.

package/.agent/skills/ui-ux-researcher/SKILL.md

@@ -45,45 +45,45 @@ Every UI element is evaluated across 3 tiers. Each tier has hard requirements th
 
 ### P0: Safety & Accessibility (BLOCKS SHIP)
 
-| # | Check | Standard | How to Verify |
+|#|Check|Standard|How to Verify|
 |---|---|---|---|
-| 0.1 | Color contrast (normal text) | ≥ 4.5:1 (WCAG AA) | Calculate `(L1 + 0.05) / (L2 + 0.05)` |
-| 0.2 | Color contrast (large text ≥18px bold or ≥24px) | ≥ 3:1 | Same formula |
-| 0.3 | Touch targets | ≥ 44×44px (WCAG 2.5.8) | Check CSS `min-width`/`min-height` or padding |
-| 0.4 | Keyboard navigation | All interactive elements focusable, visible focus ring | Check for `tabindex`, `:focus-visible` styles |
-| 0.5 | Screen reader labels | All images have `alt`, all inputs have `label`/`aria-label` | Grep for `<img` without `alt`, `<input` without label |
-| 0.6 | Semantic HTML | Single `<h1>`, proper heading hierarchy, landmark regions | Parse DOM structure |
-| 0.7 | Error prevention | Destructive actions require confirmation | Check delete/submit flows |
-| 0.8 | Escape hatches | Every modal/overlay has close, every flow has "Back" | Check for close buttons, back navigation |
-| 0.9 | Reduced motion | `prefers-reduced-motion` media query present | Grep for the media query |
-| 0.10 | Color-only indicators | Information is not conveyed by color alone | Check error states, status badges |
+|0.1|Color contrast (normal text)|≥ 4.5:1 (WCAG AA)|Calculate `(L1 + 0.05) / (L2 + 0.05)`|
+|0.2|Color contrast (large text ≥18px bold or ≥24px)|≥ 3:1|Same formula|
+|0.3|Touch targets|≥ 44×44px (WCAG 2.5.8)|Check CSS `min-width`/`min-height` or padding|
+|0.4|Keyboard navigation|All interactive elements focusable, visible focus ring|Check for `tabindex`, `:focus-visible` styles|
+|0.5|Screen reader labels|All images have `alt`, all inputs have `label`/`aria-label`|Grep for `<img` without `alt`, `<input` without label|
+|0.6|Semantic HTML|Single `<h1>`, proper heading hierarchy, landmark regions|Parse DOM structure|
+|0.7|Error prevention|Destructive actions require confirmation|Check delete/submit flows|
+|0.8|Escape hatches|Every modal/overlay has close, every flow has "Back"|Check for close buttons, back navigation|
+|0.9|Reduced motion|`prefers-reduced-motion` media query present|Grep for the media query|
+|0.10|Color-only indicators|Information is not conveyed by color alone|Check error states, status badges|
 
 ### P1: Clarity & Flow (SHOULD FIX)
 
-| # | Check | Heuristic | What to Look For |
+|#|Check|Heuristic|What to Look For|
 |---|---|---|---|
-| 1.1 | Single primary action | One dominant CTA per view | Multiple same-weight buttons competing |
-| 1.2 | Visual feedback | Every interaction has visible response | Missing hover/active/disabled states |
-| 1.3 | Loading states | Async operations show progress | Missing spinners, skeletons, or progress bars |
-| 1.4 | Empty states | Zero-data views have guidance | Blank screens with no "Get Started" |
-| 1.5 | Error messaging | Errors are specific and actionable | Generic "Something went wrong" without context |
-| 1.6 | Information scent | Users can predict what happens next | Ambiguous labels like "Submit" vs "Create Account" |
-| 1.7 | Consistency | Similar elements behave similarly | Mixed button styles, inconsistent spacing |
-| 1.8 | Progressive disclosure | Complex forms use steps or sections | 20+ fields on one page |
-| 1.9 | Alignment & grid | Elements follow a consistent grid | Misaligned elements, inconsistent gutters |
+|1.1|Single primary action|One dominant CTA per view|Multiple same-weight buttons competing|
+|1.2|Visual feedback|Every interaction has visible response|Missing hover/active/disabled states|
+|1.3|Loading states|Async operations show progress|Missing spinners, skeletons, or progress bars|
+|1.4|Empty states|Zero-data views have guidance|Blank screens with no "Get Started"|
+|1.5|Error messaging|Errors are specific and actionable|Generic "Something went wrong" without context|
+|1.6|Information scent|Users can predict what happens next|Ambiguous labels like "Submit" vs "Create Account"|
+|1.7|Consistency|Similar elements behave similarly|Mixed button styles, inconsistent spacing|
+|1.8|Progressive disclosure|Complex forms use steps or sections|20+ fields on one page|
+|1.9|Alignment & grid|Elements follow a consistent grid|Misaligned elements, inconsistent gutters|
 
 ### P2: Polish & Premium (ELEVATES QUALITY)
 
-| # | Check | Quality Signal | Implementation |
+|#|Check|Quality Signal|Implementation|
 |---|---|---|---|
-| 2.1 | Whitespace balance | Content has room to breathe | Audit `padding`/`margin` — minimum 16px sections |
-| 2.2 | Corner radius harmony | Outer radius > inner radius, consistent across components | Check `border-radius` values |
-| 2.3 | Shadow depth system | Consistent shadow levels (sm → md → lg → xl) | Verify `box-shadow` consistency |
-| 2.4 | Typography rhythm | Consistent line-height, letter-spacing across hierarchy | Check for modular type scale |
-| 2.5 | Micro-interactions | Entrances, hovers, and feedback feel intentional | Cross-reference with `whimsy-injector` |
-| 2.6 | Icon consistency | Same style family (outline vs filled, same weight) | Mixed icon sets = visual noise |
-| 2.7 | Color temperature | Warm palette stays warm, cool stays cool | Check for temperature clashes |
-| 2.8 | Content density | Not too sparse (wasted space), not too dense (overwhelming) | Subjective — use Goldilocks principle |
+|2.1|Whitespace balance|Content has room to breathe|Audit `padding`/`margin` — minimum 16px sections|
+|2.2|Corner radius harmony|Outer radius > inner radius, consistent across components|Check `border-radius` values|
+|2.3|Shadow depth system|Consistent shadow levels (sm → md → lg → xl)|Verify `box-shadow` consistency|
+|2.4|Typography rhythm|Consistent line-height, letter-spacing across hierarchy|Check for modular type scale|
+|2.5|Micro-interactions|Entrances, hovers, and feedback feel intentional|Cross-reference with `whimsy-injector`|
+|2.6|Icon consistency|Same style family (outline vs filled, same weight)|Mixed icon sets = visual noise|
+|2.7|Color temperature|Warm palette stays warm, cool stays cool|Check for temperature clashes|
+|2.8|Content density|Not too sparse (wasted space), not too dense (overwhelming)|Subjective — use Goldilocks principle|
 
 ## Scoring Protocol
 
@@ -100,11 +100,11 @@ Score = (P0_pass_rate × 0.5) + (P1_pass_rate × 0.3) + (P2_pass_rate × 0.2)
 
 ### Severity Labels
 
-| Label | Meaning | Action |
+|Label|Meaning|Action|
 |---|---|---|
-| 🔴 BLOCKER | P0 violation, breaks accessibility or safety | Must fix before ship |
-| 🟡 WARNING | P1 issue, impacts clarity or flow | Should fix |
-| 🔵 SUGGESTION | P2 opportunity, improves polish | Nice to fix |
+|🔴 BLOCKER|P0 violation, breaks accessibility or safety|Must fix before ship|
+|🟡 WARNING|P1 issue, impacts clarity or flow|Should fix|
+|🔵 SUGGESTION|P2 opportunity, improves polish|Nice to fix|
 
 ## Report Format
 
@@ -160,28 +160,28 @@ Grade:   [A/B/C/D/F]
 
 Used as the theoretical backbone for P1 checks:
 
-| # | Heuristic | What to Check |
+|#|Heuristic|What to Check|
 |---|---|---|
-| H1 | Visibility of system status | Loading indicators, progress bars |
-| H2 | Match between system and real world | Natural language labels, familiar icons |
-| H3 | User control and freedom | Undo, Back, Cancel always available |
-| H4 | Consistency and standards | Same patterns across the app |
-| H5 | Error prevention | Confirmation dialogs, input validation |
-| H6 | Recognition over recall | Labels over icons-only, visible navigation |
-| H7 | Flexibility and efficiency | Keyboard shortcuts, bulk actions |
-| H8 | Aesthetic and minimalist design | No extraneous information |
-| H9 | Help users recognize errors | Specific error messages with recovery |
-| H10 | Help and documentation | Tooltips, onboarding, contextual help |
+|H1|Visibility of system status|Loading indicators, progress bars|
+|H2|Match between system and real world|Natural language labels, familiar icons|
+|H3|User control and freedom|Undo, Back, Cancel always available|
+|H4|Consistency and standards|Same patterns across the app|
+|H5|Error prevention|Confirmation dialogs, input validation|
+|H6|Recognition over recall|Labels over icons-only, visible navigation|
+|H7|Flexibility and efficiency|Keyboard shortcuts, bulk actions|
+|H8|Aesthetic and minimalist design|No extraneous information|
+|H9|Help users recognize errors|Specific error messages with recovery|
+|H10|Help and documentation|Tooltips, onboarding, contextual help|
 
 ## Cross-Skill Integration
 
-| Paired Skill | Integration Point |
+|Paired Skill|Integration Point|
 |---|---|
-| `trend-researcher` | Validate that applied trends pass P0 contrast and P1 clarity |
-| `whimsy-injector` | P2.5 — delegate micro-interaction implementation |
-| `web-design-guidelines` | Reference for component-level design standards |
-| `frontend-design` | Token-level validation (spacing, radius, shadows) |
-| `accessibility-reviewer` | Deep-dive partner for complex ARIA patterns |
+|`trend-researcher`|Validate that applied trends pass P0 contrast and P1 clarity|
+|`whimsy-injector`|P2.5 — delegate micro-interaction implementation|
+|`web-design-guidelines`|Reference for component-level design standards|
+|`frontend-design`|Token-level validation (spacing, radius, shadows)|
+|`accessibility-reviewer`|Deep-dive partner for complex ARIA patterns|
 
 ## Anti-Hallucination Guard
 
@@ -191,44 +191,4 @@ Used as the theoretical backbone for P1 checks:
 - **Ground all UX claims** in Nielsen's heuristics or WCAG 2.2 standards — cite the specific rule.
 - **Do not invent file paths or line numbers** — only reference code that has been read.
 
-
----
-
-## 🤖 LLM-Specific Traps
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
 ---
-
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.