tribunal-kit 4.5.1 → 4.6.1

package/.agent/skills/app-builder/templates/SKILL.md

@@ -1,115 +1,108 @@
----
-name: templates
-description: Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
-allowed-tools: Read, Glob, Grep
----
-
-# Project Templates
-
----
-
-## 🎯 Selective Reading Rule
-
-**Read ONLY the template matching user's project type!**
-
-|Template|Tech Stack|When to Use|
-|----------|------------|-------------|
-|[nextjs-fullstack](nextjs-fullstack/TEMPLATE.md)|Next.js + Prisma|Full-stack web app|
-|[nextjs-saas](nextjs-saas/TEMPLATE.md)|Next.js + Stripe|SaaS product|
-|[nextjs-static](nextjs-static/TEMPLATE.md)|Next.js + Framer|Landing page|
-|[express-api](express-api/TEMPLATE.md)|Express + JWT|REST API|
-|[python-fastapi](python-fastapi/TEMPLATE.md)|FastAPI|Python API|
-|[react-native-app](react-native-app/TEMPLATE.md)|Expo + Zustand|Mobile app|
-|[flutter-app](flutter-app/TEMPLATE.md)|Flutter + Riverpod|Cross-platform|
-|[electron-desktop](electron-desktop/TEMPLATE.md)|Electron + React|Desktop app|
-|[chrome-extension](chrome-extension/TEMPLATE.md)|Chrome MV3|Browser extension|
-|[cli-tool](cli-tool/TEMPLATE.md)|Node.js + Commander|CLI app|
-|[monorepo-turborepo](monorepo-turborepo/TEMPLATE.md)|Turborepo + pnpm|Monorepo|
-|[astro-static](astro-static/TEMPLATE.md)|Astro + MDX|Blog / Docs|
-
----
-
-## Usage
-
-1. User says "create [type] app"
-2. Match to appropriate template
-3. Read ONLY that template's TEMPLATE.md
-4. Follow its tech stack and structure
-
----
-
-## 🚨 LLM Trap Table
-
-|Pattern|What AI Does Wrong|What Is Actually Correct|
-|:---|:---|:---|
-|[domain-specific trap 1]|[hallucination]|[correct behavior]|
-|[domain-specific trap 2]|[hallucination]|[correct behavior]|
-|[domain-specific trap 3]|[hallucination]|[correct behavior]|
-
----
-
-## ✅ Pre-Flight Self-Audit
-
-Before producing any output, verify:
-``
-✅ Did I read the actual files before making claims about them?
-✅ Did I verify all method names against official documentation?
-✅ Did I add // VERIFY: on any uncertain API calls?
-✅ Are all imports from packages that actually exist in package.json?
-✅ Did I test my logic with edge cases (null, empty, 0, max)?
-✅ Did I avoid generating code for more than one module at a time?
-✅ Am I working from evidence, not assumption?
-``
-
----
-
-## 🔁 VBC Protocol (Verify → Build → Confirm)
-
-``
-VERIFY:  Read the actual codebase before writing anything
-BUILD:   Generate the smallest meaningful unit of code
-CONFIRM: Verify the output is correct before presenting
-``
-
----
-
-## 🚨 LLM Trap Table
-
-|Pattern|What AI Does Wrong|What Is Actually Correct|
-|:---|:---|:---|
-|[domain-specific trap 1]|[hallucination]|[correct behavior]|
-|[domain-specific trap 2]|[hallucination]|[correct behavior]|
-|[domain-specific trap 3]|[hallucination]|[correct behavior]|
-
----
-
-## ✅ Pre-Flight Self-Audit
-
-Before producing any output, verify:
-``
-✅ Did I read the actual files before making claims about them?
-✅ Did I verify all method names against official documentation?
-✅ Did I add // VERIFY: on any uncertain API calls?
-✅ Are all imports from packages that actually exist in package.json?
-✅ Did I test my logic with edge cases (null, empty, 0, max)?
-✅ Did I avoid generating code for more than one module at a time?
-✅ Am I working from evidence, not assumption?
-``
-
----
-
-## 🔁 VBC Protocol (Verify → Build → Confirm)
-
-``
-VERIFY:  Read the actual codebase before writing anything
-BUILD:   Generate the smallest meaningful unit of code
-CONFIRM: Verify the output is correct before presenting
-``
-
-
-## 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: templates
+description: Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
+allowed-tools: Read, Glob, Grep
+---
+
+# Project Templates
+
+---
+
+## 🎯 Selective Reading Rule
+
+**Read ONLY the template matching user's project type!**
+
+| Template                                             | Tech Stack          | When to Use        |
+| ---------------------------------------------------- | ------------------- | ------------------ |
+| [nextjs-fullstack](nextjs-fullstack/TEMPLATE.md)     | Next.js + Prisma    | Full-stack web app |
+| [nextjs-saas](nextjs-saas/TEMPLATE.md)               | Next.js + Stripe    | SaaS product       |
+| [nextjs-static](nextjs-static/TEMPLATE.md)           | Next.js + Framer    | Landing page       |
+| [express-api](express-api/TEMPLATE.md)               | Express + JWT       | REST API           |
+| [python-fastapi](python-fastapi/TEMPLATE.md)         | FastAPI             | Python API         |
+| [react-native-app](react-native-app/TEMPLATE.md)     | Expo + Zustand      | Mobile app         |
+| [flutter-app](flutter-app/TEMPLATE.md)               | Flutter + Riverpod  | Cross-platform     |
+| [electron-desktop](electron-desktop/TEMPLATE.md)     | Electron + React    | Desktop app        |
+| [chrome-extension](chrome-extension/TEMPLATE.md)     | Chrome MV3          | Browser extension  |
+| [cli-tool](cli-tool/TEMPLATE.md)                     | Node.js + Commander | CLI app            |
+| [monorepo-turborepo](monorepo-turborepo/TEMPLATE.md) | Turborepo + pnpm    | Monorepo           |
+| [astro-static](astro-static/TEMPLATE.md)             | Astro + MDX         | Blog / Docs        |
+
+---
+
+## Usage
+
+1. User says "create [type] app"
+2. Match to appropriate template
+3. Read ONLY that template's TEMPLATE.md
+4. Follow its tech stack and structure
+
+---
+
+## 🚨 LLM Trap Table
+
+| Pattern                  | What AI Does Wrong | What Is Actually Correct |
+| :----------------------- | :----------------- | :----------------------- |
+| [domain-specific trap 1] | [hallucination]    | [correct behavior]       |
+| [domain-specific trap 2] | [hallucination]    | [correct behavior]       |
+| [domain-specific trap 3] | [hallucination]    | [correct behavior]       |
+
+---
+
+## ✅ Pre-Flight Self-Audit
+
+Before producing any output, verify:
+`✅ Did I read the actual files before making claims about them?
+✅ Did I verify all method names against official documentation?
+✅ Did I add // VERIFY: on any uncertain API calls?
+✅ Are all imports from packages that actually exist in package.json?
+✅ Did I test my logic with edge cases (null, empty, 0, max)?
+✅ Did I avoid generating code for more than one module at a time?
+✅ Am I working from evidence, not assumption?`
+
+---
+
+## 🔁 VBC Protocol (Verify → Build → Confirm)
+
+`VERIFY:  Read the actual codebase before writing anything
+BUILD:   Generate the smallest meaningful unit of code
+CONFIRM: Verify the output is correct before presenting`
+
+---
+
+## 🚨 LLM Trap Table
+
+| Pattern                  | What AI Does Wrong | What Is Actually Correct |
+| :----------------------- | :----------------- | :----------------------- |
+| [domain-specific trap 1] | [hallucination]    | [correct behavior]       |
+| [domain-specific trap 2] | [hallucination]    | [correct behavior]       |
+| [domain-specific trap 3] | [hallucination]    | [correct behavior]       |
+
+---
+
+## ✅ Pre-Flight Self-Audit
+
+Before producing any output, verify:
+`✅ Did I read the actual files before making claims about them?
+✅ Did I verify all method names against official documentation?
+✅ Did I add // VERIFY: on any uncertain API calls?
+✅ Are all imports from packages that actually exist in package.json?
+✅ Did I test my logic with edge cases (null, empty, 0, max)?
+✅ Did I avoid generating code for more than one module at a time?
+✅ Am I working from evidence, not assumption?`
+
+---
+
+## 🔁 VBC Protocol (Verify → Build → Confirm)
+
+`VERIFY:  Read the actual codebase before writing anything
+BUILD:   Generate the smallest meaningful unit of code
+CONFIRM: Verify the output is correct before presenting`
+
+## 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.

package/.agent/skills/app-builder/templates/astro-static/TEMPLATE.md

@@ -1,76 +1,76 @@
----
-name: astro-static
-description: Astro static site template principles. Content-focused websites, blogs, documentation.
----
-
-# Astro Static Site Template
-
-## Tech Stack
-
-|Component|Technology|
-|-----------|------------|
-|Framework|Astro 4.x|
-|Content|MDX + Content Collections|
-|Styling|Tailwind CSS|
-|Integrations|Sitemap, RSS, SEO|
-|Output|Static/SSG|
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── components/      # .astro components
-│   ├── content/         # MDX content
-│   │   ├── blog/
-│   │   └── config.ts    # Collection schemas
-│   ├── layouts/         # Page layouts
-│   ├── pages/           # File-based routing
-│   └── styles/
-├── public/              # Static assets
-├── astro.config.mjs
-└── package.json
-```
-
----
-
-## Key Concepts
-
-|Concept|Description|
-|---------|-------------|
-|Content Collections|Type-safe content with Zod schemas|
-|Islands Architecture|Partial hydration for interactivity|
-|Zero JS by default|Static HTML unless needed|
-|MDX Support|Markdown with components|
-
----
-
-## Setup Steps
-
-1. `npm create astro@latest {{name}}`
-2. Add integrations: `npx astro add mdx tailwind sitemap`
-3. Configure `astro.config.mjs`
-4. Create content collections
-5. `npm run dev`
-
----
-
-## Deployment
-
-|Platform|Method|
-|----------|--------|
-|Vercel|Auto-detected|
-|Netlify|Auto-detected|
-|Cloudflare Pages|Auto-detected|
-|GitHub Pages|Build + deploy action|
-
----
-
-## Best Practices
-
-- Use Content Collections for type safety
-- Leverage static generation
-- Add islands only where needed
-- Optimize images with Astro Image
+---
+name: astro-static
+description: Astro static site template principles. Content-focused websites, blogs, documentation.
+---
+
+# Astro Static Site Template
+
+## Tech Stack
+
+| Component    | Technology                |
+| ------------ | ------------------------- |
+| Framework    | Astro 4.x                 |
+| Content      | MDX + Content Collections |
+| Styling      | Tailwind CSS              |
+| Integrations | Sitemap, RSS, SEO         |
+| Output       | Static/SSG                |
+
+---
+
+## Directory Structure
+
+```
+project-name/
+├── src/
+│   ├── components/      # .astro components
+│   ├── content/         # MDX content
+│   │   ├── blog/
+│   │   └── config.ts    # Collection schemas
+│   ├── layouts/         # Page layouts
+│   ├── pages/           # File-based routing
+│   └── styles/
+├── public/              # Static assets
+├── astro.config.mjs
+└── package.json
+```
+
+---
+
+## Key Concepts
+
+| Concept              | Description                         |
+| -------------------- | ----------------------------------- |
+| Content Collections  | Type-safe content with Zod schemas  |
+| Islands Architecture | Partial hydration for interactivity |
+| Zero JS by default   | Static HTML unless needed           |
+| MDX Support          | Markdown with components            |
+
+---
+
+## Setup Steps
+
+1. `npm create astro@latest {{name}}`
+2. Add integrations: `npx astro add mdx tailwind sitemap`
+3. Configure `astro.config.mjs`
+4. Create content collections
+5. `npm run dev`
+
+---
+
+## Deployment
+
+| Platform         | Method                |
+| ---------------- | --------------------- |
+| Vercel           | Auto-detected         |
+| Netlify          | Auto-detected         |
+| Cloudflare Pages | Auto-detected         |
+| GitHub Pages     | Build + deploy action |
+
+---
+
+## Best Practices
+
+- Use Content Collections for type safety
+- Leverage static generation
+- Add islands only where needed
+- Optimize images with Astro Image

package/.agent/skills/app-builder/templates/chrome-extension/TEMPLATE.md

@@ -1,92 +1,92 @@
----
-name: chrome-extension
-description: Chrome Extension template principles. Manifest V3, React, TypeScript.
----
-
-# Chrome Extension Template
-
-## Tech Stack
-
-|Component|Technology|
-|-----------|------------|
-|Manifest|V3|
-|UI|React 19|
-|Language|TypeScript|
-|Styling|Tailwind CSS|
-|Bundler|Vite|
-|Storage|Chrome Storage API|
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── popup/           # Extension popup
-│   ├── options/         # Options page
-│   ├── background/      # Service worker
-│   ├── content/         # Content scripts
-│   ├── components/
-│   ├── hooks/
-│   └── lib/
-│       ├── storage.ts   # Chrome storage helpers
-│       └── messaging.ts # Message passing
-├── public/
-│   ├── icons/
-│   └── manifest.json
-└── package.json
-```
-
----
-
-## Manifest V3 Concepts
-
-|Component|Purpose|
-|-----------|---------|
-|Service Worker|Background processing|
-|Content Scripts|Page injection|
-|Popup|User interface|
-|Options Page|Settings|
-
----
-
-## Permissions
-
-|Permission|Use|
-|------------|-----|
-|storage|Save user data|
-|activeTab|Current tab access|
-|scripting|Inject scripts|
-|host_permissions|Site access|
-
----
-
-## Setup Steps
-
-1. `npm create vite {{name}} -- --template react-ts`
-2. Add Chrome types: `npm install -D @types/chrome`
-3. Configure Vite for multi-entry
-4. Create manifest.json
-5. `npm run dev` (watch mode)
-6. Load in Chrome: `chrome://extensions` → Load unpacked
-
----
-
-## Development Tips
-
-|Task|Method|
-|------|--------|
-|Debug Popup|Right-click icon → Inspect|
-|Debug Background|Extensions page → Service worker|
-|Debug Content|DevTools console on page|
-|Hot Reload|`npm run dev` with watch|
-
----
-
-## Best Practices
-
-- Use type-safe messaging
-- Wrap Chrome APIs in promises
-- Minimize permissions
-- Handle offline gracefully
+---
+name: chrome-extension
+description: Chrome Extension template principles. Manifest V3, React, TypeScript.
+---
+
+# Chrome Extension Template
+
+## Tech Stack
+
+| Component | Technology         |
+| --------- | ------------------ |
+| Manifest  | V3                 |
+| UI        | React 19           |
+| Language  | TypeScript         |
+| Styling   | Tailwind CSS       |
+| Bundler   | Vite               |
+| Storage   | Chrome Storage API |
+
+---
+
+## Directory Structure
+
+```
+project-name/
+├── src/
+│   ├── popup/           # Extension popup
+│   ├── options/         # Options page
+│   ├── background/      # Service worker
+│   ├── content/         # Content scripts
+│   ├── components/
+│   ├── hooks/
+│   └── lib/
+│       ├── storage.ts   # Chrome storage helpers
+│       └── messaging.ts # Message passing
+├── public/
+│   ├── icons/
+│   └── manifest.json
+└── package.json
+```
+
+---
+
+## Manifest V3 Concepts
+
+| Component       | Purpose               |
+| --------------- | --------------------- |
+| Service Worker  | Background processing |
+| Content Scripts | Page injection        |
+| Popup           | User interface        |
+| Options Page    | Settings              |
+
+---
+
+## Permissions
+
+| Permission       | Use                |
+| ---------------- | ------------------ |
+| storage          | Save user data     |
+| activeTab        | Current tab access |
+| scripting        | Inject scripts     |
+| host_permissions | Site access        |
+
+---
+
+## Setup Steps
+
+1. `npm create vite {{name}} -- --template react-ts`
+2. Add Chrome types: `npm install -D @types/chrome`
+3. Configure Vite for multi-entry
+4. Create manifest.json
+5. `npm run dev` (watch mode)
+6. Load in Chrome: `chrome://extensions` → Load unpacked
+
+---
+
+## Development Tips
+
+| Task             | Method                           |
+| ---------------- | -------------------------------- |
+| Debug Popup      | Right-click icon → Inspect       |
+| Debug Background | Extensions page → Service worker |
+| Debug Content    | DevTools console on page         |
+| Hot Reload       | `npm run dev` with watch         |
+
+---
+
+## Best Practices
+
+- Use type-safe messaging
+- Wrap Chrome APIs in promises
+- Minimize permissions
+- Handle offline gracefully