tribunal-kit 4.5.0 → 4.6.0

package/.agent/skills/app-builder/templates/react-native-app/TEMPLATE.md

@@ -1,119 +1,122 @@
----
-name: react-native-app
-description: React Native mobile app template principles. Expo, TypeScript, navigation.
----
-
-# React Native App Template (2026 Edition)
-
-Modern mobile app template, optimized for New Architecture and React 19.
-
-## Tech Stack
-
-|Component|Technology|Version / Notes|
-|-----------|------------|-----------------|
-|Core|React Native + Expo|SDK 52+ (New Architecture Enabled)|
-|Language|TypeScript|v5+ (Strict Mode)|
-|UI Logic|React|v19 (React Compiler, auto-memoization)|
-|Navigation|Expo Router|v4+ (File-based, Universal Links)|
-|Styling|NativeWind|v4.0 (Tailwind v4, CSS-first config)|
-|State|Zustand + React Query|v5+ (Async State Management)|
-|Storage|Expo SecureStore|Encrypted local storage|
-
----
-
-## Directory Structure
-
-Standardized structure for Expo Router and NativeWind v4.
-
-```
-project-name/
-├── app/                 # Expo Router (File-based routing)
-│   ├── _layout.tsx      # Root Layout (Stack/Tabs config)
-│   ├── index.tsx        # Main Screen
-│   ├── (tabs)/          # Route Group for Tab Bar
-│   │   ├── _layout.tsx
-│   │   ├── home.tsx
-│   │   └── profile.tsx
-│   ├── +not-found.tsx   # 404 Page
-│   └── [id].tsx         # Dynamic Route (Typed)
-├── components/
-│   ├── ui/              # Primitive Components (Button, Text)
-│   └── features/        # Complex Components
-├── hooks/               # Custom Hooks
-├── lib/
-│   ├── api.ts           # Axios/Fetch client
-│   └── storage.ts       # SecureStore wrapper
-├── store/               # Zustand stores
-├── constants/           # Colors, Theme config
-├── assets/              # Fonts, Images
-├── global.css           # Entry point for NativeWind v4
-├── tailwind.config.ts   # Tailwind Config (if custom theme needed)
-├── babel.config.js      # NativeWind Babel Plugin
-└── app.json             # Expo Config
-```
-
----
-
-## Navigation Patterns (Expo Router)
-
-|Pattern|Description|Implement|
-|---------|-------------|-----------|
-|Stack|Hierarchical navigation (Push/Pop)|`<Stack />` in `_layout.tsx`|
-|Tabs|Bottom navigation bar|`<Tabs />` in `(tabs)/_layout.tsx`|
-|Drawer|Side slide-out menu|`expo-router/drawer`|
-|Modals|Overlay screens|`presentation: 'modal'` in Stack screen|
-
----
-
-## Key Packages & Purpose
-
-|Package|Purpose|
-|---------|---------|
-|expo-router|File-based routing (Next.js like)|
-|nativewind|Use Tailwind CSS classes in React Native|
-|react-native-reanimated|Smooth animations (runs on UI thread)|
-|@tanstack/react-query|Server state management, caching, pre-fetching|
-|zustand|Global state management (lighter than Redux)|
-|expo-image|Optimized image rendering for performance|
-
----
-
-## Setup Steps (2026 Standard)
-
-1. Initialize Project:
-   ```bash
-   npx create-expo-app@latest my-app --template default
-   cd my-app
-   ```
-
-2. Install Core Dependencies:
-   ```bash
-   npx expo install expo-router react-native-safe-area-context react-native-screens expo-link expo-constants expo-status-bar
-   ```
-
-3. Install NativeWind v4:
-   ```bash
-   npm install nativewind tailwindcss react-native-reanimated
-   ```
-
-4. Configure NativeWind (Babel & CSS):
-   - Add plugin to `babel.config.js`: `plugins: ["nativewind/babel"]`.
-   - Create `global.css` with: `@import "tailwindcss";`.
-   - Import `global.css` in `app/_layout.tsx`.
-
-5. Run Project:
-   ```bash
-   npx expo start -c
-   # Press 'i' for iOS simulator or 'a' for Android emulator
-   ```
-
----
-
-## Best Practices (Updated)
-
-- **New Architecture**: Ensure `newArchEnabled: true` in `app.json` to leverage TurboModules and Fabric Renderer.
-- **Typed Routes**: Use Expo Router's "Typed Routes" feature for type-safe routing (e.g., `router.push('/path')`).
-- **React 19**: Reduce usage of `useMemo` or `useCallback` thanks to React Compiler (if enabled).
-- **Components**: Build UI primitives (Box, Text) with NativeWind className for reusability.
-- **Assets**: Use `expo-image` instead of default `<Image />` for better caching and performance.
-- **API**: Always wrap API calls with TanStack Query, avoid direct calls in `useEffect`.
+---
+name: react-native-app
+description: React Native mobile app template principles. Expo, TypeScript, navigation.
+---
+
+# React Native App Template (2026 Edition)
+
+Modern mobile app template, optimized for New Architecture and React 19.
+
+## Tech Stack
+
+| Component  | Technology            | Version / Notes                        |
+| ---------- | --------------------- | -------------------------------------- |
+| Core       | React Native + Expo   | SDK 52+ (New Architecture Enabled)     |
+| Language   | TypeScript            | v5+ (Strict Mode)                      |
+| UI Logic   | React                 | v19 (React Compiler, auto-memoization) |
+| Navigation | Expo Router           | v4+ (File-based, Universal Links)      |
+| Styling    | NativeWind            | v4.0 (Tailwind v4, CSS-first config)   |
+| State      | Zustand + React Query | v5+ (Async State Management)           |
+| Storage    | Expo SecureStore      | Encrypted local storage                |
+
+---
+
+## Directory Structure
+
+Standardized structure for Expo Router and NativeWind v4.
+
+```
+project-name/
+├── app/                 # Expo Router (File-based routing)
+│   ├── _layout.tsx      # Root Layout (Stack/Tabs config)
+│   ├── index.tsx        # Main Screen
+│   ├── (tabs)/          # Route Group for Tab Bar
+│   │   ├── _layout.tsx
+│   │   ├── home.tsx
+│   │   └── profile.tsx
+│   ├── +not-found.tsx   # 404 Page
+│   └── [id].tsx         # Dynamic Route (Typed)
+├── components/
+│   ├── ui/              # Primitive Components (Button, Text)
+│   └── features/        # Complex Components
+├── hooks/               # Custom Hooks
+├── lib/
+│   ├── api.ts           # Axios/Fetch client
+│   └── storage.ts       # SecureStore wrapper
+├── store/               # Zustand stores
+├── constants/           # Colors, Theme config
+├── assets/              # Fonts, Images
+├── global.css           # Entry point for NativeWind v4
+├── tailwind.config.ts   # Tailwind Config (if custom theme needed)
+├── babel.config.js      # NativeWind Babel Plugin
+└── app.json             # Expo Config
+```
+
+---
+
+## Navigation Patterns (Expo Router)
+
+| Pattern | Description                        | Implement                               |
+| ------- | ---------------------------------- | --------------------------------------- |
+| Stack   | Hierarchical navigation (Push/Pop) | `<Stack />` in `_layout.tsx`            |
+| Tabs    | Bottom navigation bar              | `<Tabs />` in `(tabs)/_layout.tsx`      |
+| Drawer  | Side slide-out menu                | `expo-router/drawer`                    |
+| Modals  | Overlay screens                    | `presentation: 'modal'` in Stack screen |
+
+---
+
+## Key Packages & Purpose
+
+| Package                 | Purpose                                        |
+| ----------------------- | ---------------------------------------------- |
+| expo-router             | File-based routing (Next.js like)              |
+| nativewind              | Use Tailwind CSS classes in React Native       |
+| react-native-reanimated | Smooth animations (runs on UI thread)          |
+| @tanstack/react-query   | Server state management, caching, pre-fetching |
+| zustand                 | Global state management (lighter than Redux)   |
+| expo-image              | Optimized image rendering for performance      |
+
+---
+
+## Setup Steps (2026 Standard)
+
+1. Initialize Project:
+
+   ```bash
+   npx create-expo-app@latest my-app --template default
+   cd my-app
+   ```
+
+2. Install Core Dependencies:
+
+   ```bash
+   npx expo install expo-router react-native-safe-area-context react-native-screens expo-link expo-constants expo-status-bar
+   ```
+
+3. Install NativeWind v4:
+
+   ```bash
+   npm install nativewind tailwindcss react-native-reanimated
+   ```
+
+4. Configure NativeWind (Babel & CSS):
+   - Add plugin to `babel.config.js`: `plugins: ["nativewind/babel"]`.
+   - Create `global.css` with: `@import "tailwindcss";`.
+   - Import `global.css` in `app/_layout.tsx`.
+
+5. Run Project:
+   ```bash
+   npx expo start -c
+   # Press 'i' for iOS simulator or 'a' for Android emulator
+   ```
+
+---
+
+## Best Practices (Updated)
+
+- **New Architecture**: Ensure `newArchEnabled: true` in `app.json` to leverage TurboModules and Fabric Renderer.
+- **Typed Routes**: Use Expo Router's "Typed Routes" feature for type-safe routing (e.g., `router.push('/path')`).
+- **React 19**: Reduce usage of `useMemo` or `useCallback` thanks to React Compiler (if enabled).
+- **Components**: Build UI primitives (Box, Text) with NativeWind className for reusability.
+- **Assets**: Use `expo-image` instead of default `<Image />` for better caching and performance.
+- **API**: Always wrap API calls with TanStack Query, avoid direct calls in `useEffect`.

package/.agent/skills/appflow-wireframe/SKILL.md

@@ -1,149 +1,148 @@
----
-name: appflow-wireframe
-description: Application flow and wireframing mastery. Mermaid.js flowcharting, state diagrams, user journey mapping, interaction matrices, explicit screen boundary demarcation, and accessibility flow modeling. Use when planning UI architectures, designing user onboarding flows, or visualizing complex state machines before writing code.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-02
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
----
-
-## Hallucination Traps (Read First)
-- ❌ Drawing wireframes without defined user personas -> ✅ Establish WHO uses each screen before designing
-- ❌ Skipping error/empty/loading states in flow diagrams -> ✅ Every screen needs 4 states: loading, empty, populated, error
-- ❌ Assuming linear user journeys -> ✅ Real users jump between screens, go back, and abandon flows mid-way
-
----
-
-
-# Appflow & Wireframing — Visualization Mastery
-
----
-
-## 1. The Mermaid Appflow Protocol
-
-When asked to "design the flow", do not write prose. Write deterministic Mermaid diagrams that map state interactions.
-
-### Example: E-Commerce Checkout Flow
-
-```mermaid
-stateDiagram-v2
-    [*] --> CartView
-    
-    state CartView {
-        [*] --> Empty: Load
-        Empty --> Populated: Add Item
-    }
-    
-    CartView --> CheckoutModal: Click Checkout
-    
-    state CheckoutModal {
-        [*] --> AuthCheck
-        AuthCheck --> GuestCheckout: Not Logged In
-        AuthCheck --> ProfilePreFill: Logged In
-        
-        GuestCheckout --> PaymentProcessing: Submit
-        ProfilePreFill --> PaymentProcessing: Submit
-    }
-    
-    PaymentProcessing --> Success: Stripe 200 OK
-    PaymentProcessing --> CheckoutModal: Stripe 402 Error (Retry)
-    
-    Success --> [*]: Redirect Dashboard
-```
-
----
-
-## 2. Low-Fidelity Wireframe Notation
-
-When asked to define the UI layout conceptually before building Shadcn/Tailwind components, use structural ASCII/Markdown notation to establish layout boundaries.
-
-```text
-[ HEADER: Logo (Left) | Search Bar (Center, expanding) | User Avatar (Right) ]
--------------------------------------------------------------------------
-[ SIDEBAR (Sticky, W-64) ] |  [ HERO SECTION: H1 Hook | CTA Button Primary ]
-- Dashboard                |  [ .......................................... ]
-- Analytics                |  [ FEATURE GRID (CSS Grid columns-3)        ]
-- Settings                 |  [ [Card 1]     [Card 2]      [Card 3]      ]
-[........................] |  [..........................................]
-```
-
-**Why do this?**
-Because moving an ASCII box takes 3 seconds. Rewriting 4 nested div flexbox tails takes 5 minutes. Secure the approval on the wireframe before touching code.
-
----
-
-## 3. The Empty State / Loading State Mandate
-
-When mapping application flows, AI frequently charts the "Happy Path" (User logs in -> User sees 10 items). 
-
-Every single screen designed in an App Flow MUST explicitly define:
-1. **The Loading State:** What does the user see while the network executes? (Skeleton loaders vs Spinners).
-2. **The Empty State:** What does the UI look like on Day 1 when the user has zero data? (An empty white screen is an instant bounce-rate death sentence; use an Empty State CTA).
-
----
-
-## 4. Interaction Matrices (Event Mapping)
-
-Before writing React, chart exactly what the user can do on the screen and what the system does in response.
-
-|Interaction|Trigger|System Response Hook|Edge Case|
-|:---|:---|:---|:---|
-|Click `Add to Cart`|`onClick`|Dispatch `Zustand.add(item)`|If out of stock, render Toast|
-|Scroll to Bottom|`IntersectionObserver`|`fetchNextPage()`|Reached max items, show footer|
-|Click outside Modal|`useClickAway`|`setIsOpen(false)`|Prevent close if form is dirty|
-
----
-
-
----
-
-
-
-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.
-
----
-
-
-
-**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.
-
-
-
-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.
-
-
-## Pre-Flight Checklist
-- [ ] Have I reviewed the user's specific constraints and requests?
-- [ ] Have I checked the environment for relevant existing implementations?
-
-## VBC Protocol (Verification-Before-Completion)
-You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
+---
+name: appflow-wireframe
+description: Application flow and wireframing mastery. Mermaid.js flowcharting, state diagrams, user journey mapping, interaction matrices, explicit screen boundary demarcation, and accessibility flow modeling. Use when planning UI architectures, designing user onboarding flows, or visualizing complex state machines before writing code.
+allowed-tools: Read, Write, Edit, Glob, Grep
+version: 2.0.0
+last-updated: 2026-04-02
+applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
+routing:
+  domain: general
+  tier: basic
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Drawing wireframes without defined user personas -> ✅ Establish WHO uses each screen before designing
+- ❌ Skipping error/empty/loading states in flow diagrams -> ✅ Every screen needs 4 states: loading, empty, populated, error
+- ❌ Assuming linear user journeys -> ✅ Real users jump between screens, go back, and abandon flows mid-way
+
+---
+
+# Appflow & Wireframing — Visualization Mastery
+
+---
+
+## 1. The Mermaid Appflow Protocol
+
+When asked to "design the flow", do not write prose. Write deterministic Mermaid diagrams that map state interactions.
+
+### Example: E-Commerce Checkout Flow
+
+```mermaid
+stateDiagram-v2
+    [*] --> CartView
+
+    state CartView {
+        [*] --> Empty: Load
+        Empty --> Populated: Add Item
+    }
+
+    CartView --> CheckoutModal: Click Checkout
+
+    state CheckoutModal {
+        [*] --> AuthCheck
+        AuthCheck --> GuestCheckout: Not Logged In
+        AuthCheck --> ProfilePreFill: Logged In
+
+        GuestCheckout --> PaymentProcessing: Submit
+        ProfilePreFill --> PaymentProcessing: Submit
+    }
+
+    PaymentProcessing --> Success: Stripe 200 OK
+    PaymentProcessing --> CheckoutModal: Stripe 402 Error (Retry)
+
+    Success --> [*]: Redirect Dashboard
+```
+
+---
+
+## 2. Low-Fidelity Wireframe Notation
+
+When asked to define the UI layout conceptually before building Shadcn/Tailwind components, use structural ASCII/Markdown notation to establish layout boundaries.
+
+```text
+[ HEADER: Logo (Left) | Search Bar (Center, expanding) | User Avatar (Right) ]
+-------------------------------------------------------------------------
+[ SIDEBAR (Sticky, W-64) ] |  [ HERO SECTION: H1 Hook | CTA Button Primary ]
+- Dashboard                |  [ .......................................... ]
+- Analytics                |  [ FEATURE GRID (CSS Grid columns-3)        ]
+- Settings                 |  [ [Card 1]     [Card 2]      [Card 3]      ]
+[........................] |  [..........................................]
+```
+
+**Why do this?**
+Because moving an ASCII box takes 3 seconds. Rewriting 4 nested div flexbox tails takes 5 minutes. Secure the approval on the wireframe before touching code.
+
+---
+
+## 3. The Empty State / Loading State Mandate
+
+When mapping application flows, AI frequently charts the "Happy Path" (User logs in -> User sees 10 items).
+
+Every single screen designed in an App Flow MUST explicitly define:
+
+1. **The Loading State:** What does the user see while the network executes? (Skeleton loaders vs Spinners).
+2. **The Empty State:** What does the UI look like on Day 1 when the user has zero data? (An empty white screen is an instant bounce-rate death sentence; use an Empty State CTA).
+
+---
+
+## 4. Interaction Matrices (Event Mapping)
+
+Before writing React, chart exactly what the user can do on the screen and what the system does in response.
+
+| Interaction         | Trigger                | System Response Hook         | Edge Case                      |
+| :------------------ | :--------------------- | :--------------------------- | :----------------------------- |
+| Click `Add to Cart` | `onClick`              | Dispatch `Zustand.add(item)` | If out of stock, render Toast  |
+| Scroll to Bottom    | `IntersectionObserver` | `fetchNextPage()`            | Reached max items, show footer |
+| Click outside Modal | `useClickAway`         | `setIsOpen(false)`           | Prevent close if form is dirty |
+
+---
+
+---
 
+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.
+
+---
+
+**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.
+
+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.
+
+## Pre-Flight Checklist
+
+- [ ] Have I reviewed the user's specific constraints and requests?
+- [ ] Have I checked the environment for relevant existing implementations?
+
+## VBC Protocol (Verification-Before-Completion)
+
+You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
 
 ---
 
@@ -173,6 +172,7 @@ AI coding assistants often fall into specific bad habits when dealing with this
 ### ✅ 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?
@@ -183,5 +183,6 @@ Review these questions before confirming output:
 ### 🛑 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.