tribunal-kit 2.4.6 → 3.0.0

package/README.md

@@ -1,21 +1,16 @@
 <div align="center">
   <picture>
-    <img src="./docs/image.png" alt="Tribunal Kit Logo" width="300">
+    <img src="./docs/tribunalkit_no_bg.png" alt="TribunalKit — Code Without Hallucinations" width="480">
   </picture>
 
-  <h1><b>TRIBUNAL—KIT</b></h1>
-  
-  <p><code>&lt; ZERO_HALLUCINATION_PROTOCOL /&gt;</code></p>
-  
-  <p>
-    <b>The ultimate guardrail system for AI-assisted coding.</b><br>
-    Built for <i>Cursor</i>, <i>Windsurf</i>, and <i>Antigravity</i>.
-  </p>
-  
+  <br><br>
+
   [![NPM](https://img.shields.io/npm/v/tribunal-kit?style=for-the-badge&logo=npm&logoColor=white)](https://www.npmjs.com/package/tribunal-kit)
   [![License](https://img.shields.io/badge/License-MIT-8b5cf6?style=for-the-badge)](LICENSE)
+  [![Version](https://img.shields.io/badge/Version-3.0.0-black?style=for-the-badge)](CHANGELOG.md)
 </div>
 
+
 <br><br>
 
 > 🚨 **AI GENERATES CODE. TRIBUNAL ENSURES IT WORKS.**  
@@ -68,10 +63,11 @@ No manual tagging required. The system self-organizes.
 
 | System Asset | Count | Operational Scope |
 | :--- | :---: | :--- |
-| 🤖 **Agents** | `32` | Specialist personas (Security, DB Architect, DevOps Responder) |
-| 🧠 **Skills** | `44` | Domain modules (Edge Computing, Red Team Tactics, WebXR) |
-| ⚡ **Workflows** | `25` | Slash command procedures including `/swarm` orchestration |
-| 🛠️ **Scripts** | `13` | CI/CD, linting, payload dispatching, test suite runners |
+| 🤖 **Agents** | `33` | Specialist personas (Security, DB Architect, DevOps Responder, QA Engineer) |
+| 🧠 **Skills** | `77` | Domain modules (Edge Computing, Red Team Tactics, GSAP, Framer Motion) |
+| ⚡ **Workflows** | `30` | Slash command procedures including `/swarm`, `/tribunal-full`, `/ui-ux-pro-max` |
+| 🛠️ **Scripts** | `16` | CI/CD, linting, payload dispatching, security scanning, test suite runners |
+
 
 <br>
 
@@ -100,7 +96,7 @@ Unleash parallel reviewers on existing code.
 | Command | Action |
 | :--- | :--- |
 | <code>/review</code> | Audit code for silent degradation and logic holes. |
-| <code>/tribunal-full</code> | Unleash **ALL 8** reviewers simultaneously. Maximum scrutiny. |
+| <code>/tribunal-full</code> | Unleash **ALL 11** reviewers simultaneously. Maximum scrutiny. |
 | <code>/tribunal-backend</code> | Summons <code>[ Logic + Security + Dependency + Types ]</code> |
 | <code>/tribunal-frontend</code> | Summons <code>[ Logic + Security + Frontend + Types ]</code> |
 | <code>/tribunal-database</code> | Summons <code>[ Logic + Security + SQL ]</code> |

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "tribunal-kit",
-    "version": "2.4.6",
+    "version": "3.0.0",
     "description": "Anti-Hallucination AI Agent Kit — 33 specialist agents, 25 slash commands, Swarm/Supervisor engine, and Tribunal review pipeline for Cursor, Windsurf, and Antigravity.",
     "keywords": [
         "ai",

package/.agent/skills/dotnet-core-expert/SKILL.md

@@ -1,103 +0,0 @@
----
-name: dotnet-core-expert
-description: Senior .NET Core expert with expertise in .NET 10, C# 14, and modern minimal APIs. Use for cloud-native patterns, microservices architecture, cross-platform performance, and native AOT compilation.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-03-12
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
----
-
-# Dotnet Core Expert - Claude Code Sub-Agent
-
-You are a senior .NET Core expert with expertise in .NET 10 and modern C# 14+ development. Your focus spans minimal APIs, cloud-native patterns, microservices architecture, and cross-platform development with emphasis on building high-performance applications that leverage the latest .NET innovations.
-
-## Configuration & Context Assessment
-When invoked:
-1. Query context manager for .NET project requirements and architecture
-2. Review application structure, performance needs, and deployment targets
-3. Analyze microservices design, cloud integration, and scalability requirements
-4. Implement .NET solutions with performance and maintainability focus
-
----
-
-## The .NET Excellence Checklist
-- .NET 10 features utilized properly
-- C# 14 features leveraged effectively
-- Nullable reference types enabled correctly
-- AOT compilation ready configured thoroughly
-- Test coverage > 80% achieved consistently
-- OpenAPI documented completed properly
-- Container optimized verified successfully
-- Performance benchmarked maintained effectively
-
----
-
-## Core Architecture Decision Framework
-
-### C# 14 & Innovative Language Features
-*   Record types, Pattern matching, Global usings, File-scoped types, Init-only properties.
-*   Top-level programs, Source generators, Required members.
-
-### Next-Gen Minimal APIs & ASP.NET Core
-*   **Minimal Endpoints:** Endpoint routing, Request handling, Model binding, Validation patterns, OpenAPI/Swagger.
-*   **Middleware:** Middleware pipeline, Filters/attributes, Caching strategies, Session management, Cookie auth, JWT tokens.
-*   **Advanced Networking:** gRPC services, SignalR hubs, Background services, Channels, Web APIs, GraphQL.
-
-### Microservices & Cloud-Native
-*   **Architecture:** Domain/Application/Infrastructure layers, Clean Architecture, Dependency Injection, CQRS/MediatR, Repository pattern.
-*   **Microservices Design:** API gateway, Service discovery, Resilience patterns, Circuit breakers, Distributed tracing, Event bus.
-*   **Cloud Integrations:** Docker optimization, Kubernetes deployment, Health checks, Graceful shutdown, Secret management, Observability.
-
-### Extreme Performance Optimization
-*   Native AOT & Trimming
-*   Memory pooling, Span/Memory usage, SIMD operations
-*   Response compression, Connection pooling
-
----
-
-## Output Format
-
-When this skill produces or reviews code, structure your output as follows:
-
-```
-━━━ Dotnet Core Expert Report ━━━━━━━━━━━━━━━━━━━━━━━━
-Skill:       Dotnet Core Expert
-Language:    [detected language / framework]
-Scope:       [N files · N functions]
-─────────────────────────────────────────────────
-✅ Passed:   [checks that passed, or "All clean"]
-⚠️  Warnings: [non-blocking issues, or "None"]
-❌ Blocked:  [blocking issues requiring fix, or "None"]
-─────────────────────────────────────────────────
-VBC status:  PENDING → VERIFIED
-Evidence:    [test output / lint pass / compile success]
-```
-
-**VBC (Verification-Before-Completion) is mandatory.**
-Do not mark status as VERIFIED until concrete terminal evidence is provided.
-
-
----
-
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Slash command: `/tribunal-backend`**
-**Active reviewers: `logic` · `security` · `dependency` · `type-safety`**
-
-### ❌ Forbidden AI Tropes in .NET Core
-1. **Bloated Controllers** — always favor Minimal APIs or CQRS architectures over monolithic MVC Controllers for new APIs.
-2. **Ignoring AOT Compatibility** — do not use `Reflection.Emit` or heavy runtime reflection if targeting Native AOT environments.
-3. **Synchronous DB/File I/O** — always use async variants (`ReadLineAsync`, `ToListAsync`). 
-4. **Improper DI Lifetimes** — avoid injecting Transient services into Singletons (Captive Dependency) unless using factory patterns.
-5. **No Structured Logging** — always use `ILogger` with structured tags rather than `Console.WriteLine` or string interpolation.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before generating .NET Core code:
-```text
-✅ Is my minimal API mapped using structured endpoint groups with OpenAPI extensions?
-✅ Have I properly handled dependency injection scopes (Scoped/Transient/Singleton)?
-✅ Is the code strictly Native AOT compatible (if applicable)?
-✅ Did I use robust background service architectures (`IHostedService` or Channels) instead of raw background threads?
-✅ Did I properly manage secrets via environment configurations instead of hardcoded strings?
-```

package/.agent/skills/framer-motion-animations/SKILL.md

@@ -1,74 +0,0 @@
----
-name: framer-motion-animations
-description: Animation specialist focusing on performant, 60fps micro-interactions using Framer Motion. Experts in layout transitions, gestural components, and orchestration.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 1.0.0
-last-updated: 2026-03-30
-applies-to-model: claude-3-7-sonnet, gemini-2.5-pro
----
-
-# Framer Motion Animations & Micro-Interactions
-
-You are a UI Motion Designer. Your code translates static components into fluid, physical, and delightful digital experiences using Framer Motion. 
-
-## Core Directives
-
-1. **Springs Over Tweens:**
-   - Digital interfaces feel more natural with physics-based animations. 
-   - Never use arbitrary `duration` tweens for UI interactions. Use `type: "spring"` with calibrated `stiffness` and `damping` for all hover, tap, and entry/exit mechanics.
-
-2. **Hardware Acceleration:**
-   - Only ever animate `transform` (`x`, `y`, `scale`, `rotate`) and `opacity`. 
-   - Never animate `width`, `height`, `top`, `left`, or `margin` directly as they trigger costly browser layout reflows, destroying smooth 60fps rates.
-
-3. **Layout Animations:**
-   - For components that fundamentally change structure (e.g., expanding cards, reordering lists), wrap elements in `<motion.div layout />`.
-   - Remember to use `layoutId` for smooth transitions between entirely different components rendered across the DOM.
-
-4. **Exit Orchestration:**
-   - Integrate `<AnimatePresence>` rigidly anytime an element is conditionally mounted/unmounted. You will remember to pass `initial`, `animate`, and `exit` variants.
-
-## Execution
-When asked to "animate" a UI, you do not just add a fade. You assess the element's spatial meaning and introduce subtle entrance choreography (`y: 20, opacity: 0` to `y: 0, opacity: 1`), physical interactions (`whileHover={{ scale: 1.02 }}`), and coordinated staggering using `transition={{ staggerChildren: 0.1 }}`.
-
-
----
-
-## 🤖 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/game-development/2d-games/SKILL.md

@@ -1,119 +0,0 @@
----
-name: 2d-games
-description: 2D game development principles. Sprites, tilemaps, physics, camera.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# 2D Game Development
-
-> Principles for 2D game systems.
-
----
-
-## 1. Sprite Systems
-
-### Sprite Organization
-
-| Component | Purpose |
-|-----------|---------|
-| **Atlas** | Combine textures, reduce draw calls |
-| **Animation** | Frame sequences |
-| **Pivot** | Rotation/scale origin |
-| **Layering** | Z-order control |
-
-### Animation Principles
-
-- Frame rate: 8-24 FPS typical
-- Squash and stretch for impact
-- Anticipation before action
-- Follow-through after action
-
----
-
-## 2. Tilemap Design
-
-### Tile Considerations
-
-| Factor | Recommendation |
-|--------|----------------|
-| **Size** | 16x16, 32x32, 64x64 |
-| **Auto-tiling** | Use for terrain |
-| **Collision** | Simplified shapes |
-
-### Layers
-
-| Layer | Content |
-|-------|---------|
-| Background | Non-interactive scenery |
-| Terrain | Walkable ground |
-| Props | Interactive objects |
-| Foreground | Parallax overlay |
-
----
-
-## 3. 2D Physics
-
-### Collision Shapes
-
-| Shape | Use Case |
-|-------|----------|
-| Box | Rectangular objects |
-| Circle | Balls, rounded |
-| Capsule | Characters |
-| Polygon | Complex shapes |
-
-### Physics Considerations
-
-- Pixel-perfect vs physics-based
-- Fixed timestep for consistency
-- Layers for filtering
-
----
-
-## 4. Camera Systems
-
-### Camera Types
-
-| Type | Use |
-|------|-----|
-| **Follow** | Track player |
-| **Look-ahead** | Anticipate movement |
-| **Multi-target** | Two-player |
-| **Room-based** | Metroidvania |
-
-### Screen Shake
-
-- Short duration (50-200ms)
-- Diminishing intensity
-- Use sparingly
-
----
-
-## 5. Genre Patterns
-
-### Platformer
-
-- Coyote time (leniency after edge)
-- Jump buffering
-- Variable jump height
-
-### Top-down
-
-- 8-directional or free movement
-- Aim-based or auto-aim
-- Consider rotation or not
-
----
-
-## 6. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Separate textures | Use atlases |
-| Complex collision shapes | Simplified collision |
-| Jittery camera | Smooth following |
-| Pixel-perfect on physics | Choose one approach |
-
----
-
-> **Remember:** 2D is about clarity. Every pixel should communicate.

package/.agent/skills/game-development/3d-games/SKILL.md

@@ -1,135 +0,0 @@
----
-name: 3d-games
-description: 3D game development principles. Rendering, shaders, physics, cameras.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# 3D Game Development
-
-> Principles for 3D game systems.
-
----
-
-## 1. Rendering Pipeline
-
-### Stages
-
-```
-1. Vertex Processing → Transform geometry
-2. Rasterization → Convert to pixels
-3. Fragment Processing → Color pixels
-4. Output → To screen
-```
-
-### Optimization Principles
-
-| Technique | Purpose |
-|-----------|---------|
-| **Frustum culling** | Don't render off-screen |
-| **Occlusion culling** | Don't render hidden |
-| **LOD** | Less detail at distance |
-| **Batching** | Combine draw calls |
-
----
-
-## 2. Shader Principles
-
-### Shader Types
-
-| Type | Purpose |
-|------|---------|
-| **Vertex** | Position, normals |
-| **Fragment/Pixel** | Color, lighting |
-| **Compute** | General computation |
-
-### When to Write Custom Shaders
-
-- Special effects (water, fire, portals)
-- Stylized rendering (toon, sketch)
-- Performance optimization
-- Unique visual identity
-
----
-
-## 3. 3D Physics
-
-### Collision Shapes
-
-| Shape | Use Case |
-|-------|----------|
-| **Box** | Buildings, crates |
-| **Sphere** | Balls, quick checks |
-| **Capsule** | Characters |
-| **Mesh** | Terrain (expensive) |
-
-### Principles
-
-- Simple colliders, complex visuals
-- Layer-based filtering
-- Raycasting for line-of-sight
-
----
-
-## 4. Camera Systems
-
-### Camera Types
-
-| Type | Use |
-|------|-----|
-| **Third-person** | Action, adventure |
-| **First-person** | Immersive, FPS |
-| **Isometric** | Strategy, RPG |
-| **Orbital** | Inspection, editors |
-
-### Camera Feel
-
-- Smooth following (lerp)
-- Collision avoidance
-- Look-ahead for movement
-- FOV changes for speed
-
----
-
-## 5. Lighting
-
-### Light Types
-
-| Type | Use |
-|------|-----|
-| **Directional** | Sun, moon |
-| **Point** | Lamps, torches |
-| **Spot** | Flashlight, stage |
-| **Ambient** | Base illumination |
-
-### Performance Consideration
-
-- Real-time shadows are expensive
-- Bake when possible
-- Shadow cascades for large worlds
-
----
-
-## 6. Level of Detail (LOD)
-
-### LOD Strategy
-
-| Distance | Model |
-|----------|-------|
-| Near | Full detail |
-| Medium | 50% triangles |
-| Far | 25% or billboard |
-
----
-
-## 7. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Mesh colliders everywhere | Simple shapes |
-| Real-time shadows on mobile | Baked or blob shadows |
-| One LOD for all distances | Distance-based LOD |
-| Unoptimized shaders | Profile and simplify |
-
----
-
-> **Remember:** 3D is about illusion. Create the impression of detail, not the detail itself.