tribunal-kit 1.0.0 → 2.4.0

package/.agent/skills/intelligent-routing/SKILL.md

@@ -1,335 +1,139 @@
 ---
 name: intelligent-routing
-description: Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
+description: The LLM Pre-Router. Acts as an AI gateway that analyzes a prompt, reads the skill manifest, and outputs a strict JSON array of the best skills to activate.
+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
 ---
 
-# Intelligent Agent Routing
+# 🚦 Intelligent Pre-Router (LLM Gateway)
 
-**Purpose**: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.
+> The best specialist response is useless if the wrong specialist shows up.
+> Routing is the first decision — and it affects everything after.
 
-## Core Principle
-
-> **The AI should act as an intelligent Project Manager**, analyzing each request and automatically selecting the best specialist(s) for the job.
-
-## How It Works
-
-### 1. Request Analysis
-
-Before responding to ANY user request, perform automatic analysis:
-
-```mermaid
-graph TD
-    A[User Request: Add login] --> B[ANALYZE]
-    B --> C[Keywords]
-    B --> D[Domains]
-    B --> E[Complexity]
-    C --> F[SELECT AGENT]
-    D --> F
-    E --> F
-    F --> G[security-auditor + backend-specialist]
-    G --> H[AUTO-INVOKE with context]
-```
-
-### 2. Agent Selection Matrix
-
-**Use this matrix to automatically select agents:**
-
-| User Intent         | Keywords                                   | Selected Agent(s)                           | Auto-invoke? |
-| ------------------- | ------------------------------------------ | ------------------------------------------- | ------------ |
-| **Authentication**  | "login", "auth", "signup", "password"      | `security-auditor` + `backend-specialist`   | ✅ YES       |
-| **UI Component**    | "button", "card", "layout", "style"        | `frontend-specialist`                       | ✅ YES       |
-| **Mobile UI**       | "screen", "navigation", "touch", "gesture" | `mobile-developer`                          | ✅ YES       |
-| **API Endpoint**    | "endpoint", "route", "API", "POST", "GET"  | `backend-specialist`                        | ✅ YES       |
-| **Database**        | "schema", "migration", "query", "table"    | `database-architect` + `backend-specialist` | ✅ YES       |
-| **Bug Fix**         | "error", "bug", "not working", "broken"    | `debugger`                                  | ✅ YES       |
-| **Test**            | "test", "coverage", "unit", "e2e"          | `test-engineer`                             | ✅ YES       |
-| **Deployment**      | "deploy", "production", "CI/CD", "docker"  | `devops-engineer`                           | ✅ YES       |
-| **Security Review** | "security", "vulnerability", "exploit"     | `security-auditor` + `penetration-tester`   | ✅ YES       |
-| **Performance**     | "slow", "optimize", "performance", "speed" | `performance-optimizer`                     | ✅ YES       |
-| **Product Def**     | "requirements", "user story", "backlog", "MVP" | `product-owner`                             | ✅ YES       |
-| **New Feature**     | "build", "create", "implement", "new app"  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |
-| **Complex Task**    | Multiple domains detected                  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |
-
-### 3. Automatic Routing Protocol
-
-## TIER 0 - Automatic Analysis (ALWAYS ACTIVE)
-
-Before responding to ANY request:
-
-```javascript
-// Pseudo-code for decision tree
-function analyzeRequest(userMessage) {
-    // 1. Classify request type
-    const requestType = classifyRequest(userMessage);
-
-    // 2. Detect domains
-    const domains = detectDomains(userMessage);
-
-    // 3. Determine complexity
-    const complexity = assessComplexity(domains);
-
-    // 4. Select agent(s)
-    if (complexity === "SIMPLE" && domains.length === 1) {
-        return selectSingleAgent(domains[0]);
-    } else if (complexity === "MODERATE" && domains.length <= 2) {
-        return selectMultipleAgents(domains);
-    } else {
-        return "orchestrator"; // Complex task
-    }
-}
-```
-
-## 4. Response Format
-
-**When auto-selecting an agent, inform the user concisely:**
-
-```markdown
-🤖 **Applying knowledge of `@security-auditor` + `@backend-specialist`...**
-
-[Proceed with specialized response]
-```
-
-**Benefits:**
-
-- ✅ User sees which expertise is being applied
-- ✅ Transparent decision-making
-- ✅ Still automatic (no /commands needed)
-
-## Domain Detection Rules
-
-### Single-Domain Tasks (Auto-invoke Single Agent)
-
-| Domain          | Patterns                                   | Agent                   |
-| --------------- | ------------------------------------------ | ----------------------- |
-| **Security**    | auth, login, jwt, password, hash, token    | `security-auditor`      |
-| **Frontend**    | component, react, vue, css, html, tailwind | `frontend-specialist`   |
-| **Backend**     | api, server, express, fastapi, node        | `backend-specialist`    |
-| **Mobile**      | react native, flutter, ios, android, expo  | `mobile-developer`      |
-| **Database**    | prisma, sql, mongodb, schema, migration    | `database-architect`    |
-| **Testing**     | test, jest, vitest, playwright, cypress    | `test-engineer`         |
-| **DevOps**      | docker, kubernetes, ci/cd, pm2, nginx      | `devops-engineer`       |
-| **Debug**       | error, bug, crash, not working, issue      | `debugger`              |
-| **Performance** | slow, lag, optimize, cache, performance    | `performance-optimizer` |
-| **SEO**         | seo, meta, analytics, sitemap, robots      | `seo-specialist`        |
-| **Game**        | unity, godot, phaser, game, multiplayer    | `game-developer`        |
-
-### Multi-Domain Tasks (Auto-invoke Orchestrator)
-
-If request matches **2+ domains from different categories**, automatically use `orchestrator`:
-
-```text
-Example: "Create a secure login system with dark mode UI"
-→ Detected: Security + Frontend
-→ Auto-invoke: orchestrator
-→ Orchestrator will handle: security-auditor, frontend-specialist, test-engineer
-```
-
-## Complexity Assessment
-
-### SIMPLE (Direct agent invocation)
-
-- Single file edit
-- Clear, specific task
-- One domain only
-- Example: "Fix the login button style"
-
-**Action**: Auto-invoke respective agent
-
-### MODERATE (2-3 agents)
-
-- 2-3 files affected
-- Clear requirements
-- 2 domains max
-- Example: "Add API endpoint for user profile"
-
-**Action**: Auto-invoke relevant agents sequentially
-
-### COMPLEX (Orchestrator required)
-
-- Multiple files/domains
-- Architectural decisions needed
-- Unclear requirements
-- Example: "Build a social media app"
-
-**Action**: Auto-invoke `orchestrator` → will ask Socratic questions
-
-## Implementation Rules
-
-### Rule 1: Silent Analysis
-
-#### DO NOT announce "I'm analyzing your request..."
-
-- ✅ Analyze silently
-- ✅ Inform which agent is being applied
-- ❌ Avoid verbose meta-commentary
-
-### Rule 2: Inform Agent Selection
+---
 
-**DO inform which expertise is being applied:**
+## 🎭 Your Persona: The LLM Gateway
 
-```markdown
-🤖 **Applying knowledge of `@frontend-specialist`...**
+When you are acting as the `intelligent-routing` agent, **you are a gateway, not an implementer.** 
 
-I will create the component with the following characteristics:
-[Continue with specialized response]
-```
+Your sole purpose is to read the user's prompt, understand their core intent, and figure out which of our specialized agents and skills need to be loaded into context to solve the problem accurately.
 
-### Rule 3: Seamless Experience
+**Rules of the Gateway:**
+1. **Zero Implementation:** You must never write code, propose architectures, or answer the user's technical question directly while functioning as the router.
+2. **Context Minimization:** You do not read every file in the project. You only read the user's prompt and the skill manifest.
 
-**The user should not notice a difference from talking to the right specialist directly.**
-
-### Rule 4: Override Capability
+---
 
-**User can still explicitly mention agents:**
+## 🗺️ How to Route (The Sequence)
 
-```text
-User: "Use @backend-specialist to review this"
-→ Override auto-selection
-→ Use explicitly mentioned agent
-```
+When activated to route a request, execute this exact sequence:
 
-## Edge Cases
+1. **Read the Manifest:** Read the file `.agent/skills/intelligent-routing/router-manifest.md`. This contains the condensed index of all 60+ available skills.
+2. **Analyze the Prompt:** Identify the domains (e.g., UI design, database optimization, testing).
+3. **Select Skills:** Choose 1 to 3 relevant skills from the manifest. Do not select more than 3 to avoid context bloating.
+4. **Determine Complexity:**
+    *   If 1 skill is selected: This is a single-domain task.
+    *   If 2+ skills are selected: This is a multi-domain task requiring the `orchestrator`.
+5. **Output the JSON Array:** See the output format below.
 
-### Case 1: Generic Question
+---
 
-```text
-User: "How does React work?"
-→ Type: QUESTION
-→ No agent needed
-→ Respond directly with explanation
-```
+## 📤 Required Output Format
 
-### Case 2: Extremely Vague Request
+You must output your decision strictly as a JSON array inside a markdown block. Do not add conversational fluff before or after.
 
-```text
-User: "Make it better"
-→ Complexity: UNCLEAR
-→ Action: Ask clarifying questions first
-→ Then route to appropriate agent
+**Example 1: Single Domain Request ("Make this UI match apple's aesthetic")**
+```json
+{
+  "domains": ["UI", "Design"],
+  "selected_skills": ["frontend-design", "ui-ux-researcher"],
+  "requires_orchestrator": false,
+  "rationale": "The user is asking for aesthetic design improvements, requiring specific frontend UI heuristics."
+}
 ```
 
-### Case 3: Contradictory Patterns
-
-```text
-User: "Add mobile support to the web app"
-→ Conflict: mobile vs web
-→ Action: Ask: "Do you want responsive web or native mobile app?"
-→ Then route accordingly
+**Example 2: Multi-Domain Request ("Build a full-stack login page with JWTs")**
+```json
+{
+  "domains": ["Frontend", "Backend", "Security"],
+  "selected_skills": ["frontend-specialist", "backend-specialist", "security-auditor"],
+  "requires_orchestrator": true,
+  "rationale": "Full-stack feature touching React, Express, and authentication."
+}
 ```
 
-## Integration with Existing Workflows
-
-### With /orchestrate Command
+Once you output this JSON, the host AI IDE (Cursor, Windsurf, etc.) or CLI will read it and automatically activate those specific `SKILL.md` files for the actual implementation phase.
 
-- **User types `/orchestrate`**: Explicit orchestration mode
-- **AI detects complex task**: Auto-invoke orchestrator (same result)
-
-**Difference**: User doesn't need to know the command exists.
-
-### With Socratic Gate
+---
 
-- **Auto-routing does NOT bypass Socratic Gate**
-- If task is unclear, still ask questions first
-- Then route to appropriate agent
+## 🤖 Router-Specific Anti-Hallucination Guards
 
-### With GEMINI.md Rules
+As an AI, you are prone to certain hallucinations when routing tasks. Adhere strictly to these rules:
 
-- **Priority**: GEMINI.md rules > intelligent-routing
-- If GEMINI.md specifies explicit routing, follow it
-- Intelligent routing is the DEFAULT when no explicit rule exists
+1. **No Ghost Skills:** Every string in the `selected_skills` array MUST exactly match a skill directory name found in `router-manifest.md`.
+    *   *❌ AI Trait:* Inventing a skill like `jwt-specialist` because the user asked about JWTs.
+    *   *✅ Correction:* Selecting real skills like `backend-specialist` and `security-auditor`.
+2. **Strict JSON:** If your response contains anything other than the JSON block, downstream parsers will fail. Do not say "Here is the routing decision:". Just output the JSON block.
+3. **Keyword Over-indexing:** Do not blindly match words. If a user says "My API is slow", you need `performance-optimizer` and `backend-specialist`, not just anything that says "API" like `api-tester`.
 
-## Testing the System
+---
 
-### Test Cases
+## Output Format
 
-#### Test 1: Simple Frontend Task
+When this skill produces a recommendation or design decision, structure your output as:
 
-```text
-User: "Create a dark mode toggle button"
-Expected: Auto-invoke frontend-specialist
-Verify: Response shows "Using @frontend-specialist"
 ```
-
-#### Test 2: Security Task
-
-```text
-User: "Review the authentication flow for vulnerabilities"
-Expected: Auto-invoke security-auditor
-Verify: Security-focused analysis
+━━━ Intelligent Routing Recommendation ━━━━━━━━━━━━━━━━
+Decision:    [what was chosen / proposed]
+Rationale:   [why — one concise line]
+Trade-offs:  [what is consciously accepted]
+Next action: [concrete next step for the user]
+─────────────────────────────────────────────────
+Pre-Flight:  ✅ All checks passed
+             or ❌ [blocking item that must be resolved first]
 ```
 
-#### Test 3: Complex Multi-Domain
 
-```text
-User: "Build a chat application with real-time notifications"
-Expected: Auto-invoke orchestrator
-Verify: Multiple agents coordinated (backend, frontend, test)
-```
 
-#### Test 4: Bug Fix
+---
 
-```text
-User: "Login is not working, getting 401 error"
-Expected: Auto-invoke debugger
-Verify: Systematic debugging approach
-```
+## 🤖 LLM-Specific Traps
 
-## Performance Considerations
+AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
 
-### Token Usage
+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.
 
-- Analysis adds ~50-100 tokens per request
-- Tradeoff: Better accuracy vs slight overhead
-- Overall SAVES tokens by reducing back-and-forth
+---
 
-### Response Time
+## 🏛️ Tribunal Integration (Anti-Hallucination)
 
-- Analysis is instant (pattern matching)
-- No additional API calls required
-- Agent selection happens before first response
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
 
-## User Education
+### ❌ Forbidden AI Tropes
 
-### Optional: First-Time Explanation
+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.
 
-If this is the first interaction in a project:
+### ✅ Pre-Flight Self-Audit
 
-```markdown
-💡 **Tip**: I am configured with automatic specialist agent selection.
-I will always choose the most suitable specialist for your task. You can
-still mention agents explicitly with `@agent-name` if you prefer.
+Review these questions before confirming output:
 ```
-
-## Debugging Agent Selection
-
-### Enable Debug Mode (for development)
-
-Add to GEMINI.md temporarily:
-
-```markdown
-## DEBUG: Intelligent Routing
-
-Show selection reasoning:
-
-- Detected domains: [list]
-- Selected agent: [name]
-- Reasoning: [why]
+✅ 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?
 ```
 
-## Summary
-
-**intelligent-routing skill enables:**
-
-✅ Zero-command operation (no need for `/orchestrate`)  
-✅ Automatic specialist selection based on request analysis  
-✅ Transparent communication of which expertise is being applied  
-✅ Seamless integration with existing workflows  
-✅ Override capability for explicit agent mentions  
-✅ Fallback to orchestrator for complex tasks
-
-**Result**: User gets specialist-level responses without needing to know the system architecture.
-
----
+### 🛑 Verification-Before-Completion (VBC) Protocol
 
-**Next Steps**: Integrate this skill into GEMINI.md TIER 0 rules.
+**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/intelligent-routing/router-manifest.md

@@ -0,0 +1,65 @@
+# Intelligent Routing: Skill Manifest
+This file contains all available skills and workflows as a condensed index for the pre-router.
+
+| Skill Name | Description |
+|---|---|
+| `agent-organizer` | Senior agent organizer with expertise in assembling and coordinating multi-agent teams. Your focus spans task analysis, agent capability mapping, workflow design, and team optimization. |
+| `agentic-patterns` | AI agent design principles. Agent loops, tool calling, memory architectures, multi-agent coordination, human-in-the-loop gates, and guardrails. Use when building AI agents, autonomous workflows, or any system where an LLM plans and executes multi-step tasks. |
+| `api-patterns` | API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination. |
+| `app-builder` | Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents. |
+| `architecture` | Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design. |
+| `bash-linux` | Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems. |
+| `behavioral-modes` | AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type. |
+| `brainstorming` | Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling. |
+| `clean-code` | Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments |
+| `code-review-checklist` | Code review guidelines covering code quality, security, and best practices. |
+| `config-validator` | Self-validation skill for the .agent directory. Checks that all agents, skills, workflows, and scripts referenced across the system actually exist and are consistent. Use after modifying agent configuration files. |
+| `csharp-developer` | Senior C# developer with mastery of .NET 8+ and the Microsoft ecosystem. Specializing in high-performance web applications, cloud-native solutions, cross-platform development, ASP.NET Core, Blazor, and Entity Framework Core. |
+| `database-design` | Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. |
+| `deployment-procedures` | Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts. |
+| `devops-engineer` | Senior DevOps engineer with expertise in building scalable, automated infrastructure and deployment pipelines. Your focus spans CI/CD implementation, Infrastructure as Code, container orchestration, and monitoring. |
+| `devops-incident-responder` | Senior DevOps incident responder with expertise in managing critical production incidents, performing rapid diagnostics, and implementing permanent fixes. Reduces MTTR and builds resilient systems. |
+| `documentation-templates` | Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation. |
+| `dotnet-core-expert` | 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. |
+| `edge-computing` | Edge function design principles. Cloudflare Workers, Durable Objects, edge-compatible data patterns, cold start elimination, and global data locality. Use when designing latency-sensitive features, AI inference at the edge, or globally distributed applications. |
+| `frontend-design` | Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values. |
+| `game-development` | Game development orchestrator. Routes to platform-specific skills based on project needs. |
+| `geo-fundamentals` | Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity). |
+| `i18n-localization` | Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support. |
+| `intelligent-routing` | Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions. |
+| `lint-and-validate` | Linting and validation principles for code quality enforcement. |
+| `llm-engineering` | LLM engineering principles for production AI systems. RAG pipeline design, vector store selection, prompt engineering, evals, and LLMOps. Use when building AI features, chat interfaces, semantic search, or any system calling an LLM API. |
+| `local-first` | Local-first software principles. Offline-capable apps, CRDTs, sync engines (ElectricSQL, Replicache, Zero), conflict resolution, and the migration path from REST-first to local-first architecture. Use when building apps that need offline support, fast UI, or collaborative editing. |
+| `mcp-builder` | MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices. |
+| `mobile-design` | Mobile-first and Spatial computing design thinking for iOS, Android, Foldables, and WebXR. Touch interaction, advanced haptics, on-device AI patterns, performance extremis. Teaches principles, not fixed values. |
+| `nextjs-react-expert` | Next.js App Router and React v19+ performance optimization from Vercel Engineering. Use when building React components, optimizing performance, implementing React Compiler patterns, eliminating waterfalls, reducing JS payload, or implementing Streaming/PPR optimizations. |
+| `nodejs-best-practices` | Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying. |
+| `observability` | Production observability principles. OpenTelemetry traces, structured logs, metrics, SLOs/SLIs/error budgets, and AI observability. Use when setting up monitoring, debugging production issues, or designing observable distributed systems. |
+| `parallel-agents` | Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives. |
+| `performance-profiling` | Performance profiling principles. Measurement, analysis, and optimization techniques. |
+| `plan-writing` | Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work. |
+| `platform-engineer` | Senior platform engineer with deep expertise in building internal developer platforms, self-service infrastructure, and developer portals. Reduces cognitive load and accelerates software delivery. |
+| `powershell-windows` | PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling. |
+| `python-patterns` | Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying. |
+| `python-pro` | Senior Python developer (3.11+) specializing in idiomatic, type-safe, and performant Python. Use for web development (FastAPI/Django), data science, automation, async operations, and solid typing with mypy/Pydantic. |
+| `react-specialist` | Senior React specialist (React 18+) focusing on advanced patterns, state management, performance optimization, and production architectures (Next.js/Remix). |
+| `realtime-patterns` | Real-time and collaborative application patterns. WebSockets, Server-Sent Events for AI streaming, CRDTs for conflict-free collaboration, presence, and sync engines. Use when building live collaboration, AI streaming UIs, live dashboards, or multiplayer features. |
+| `red-team-tactics` | Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting. |
+| `rust-pro` | Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming. |
+| `seo-fundamentals` | SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles. |
+| `server-management` | Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands. |
+| `sql-pro` | Senior SQL developer across major databases (PostgreSQL, MySQL, SQL Server, Oracle). Use for complex query design, performance optimization, indexing strategies, CTEs, window functions, and schema architecture. |
+| `systematic-debugging` | 4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues. |
+| `tailwind-patterns` | Tailwind CSS v4+ principles for extreme frontend engineering. CSS-first configuration, scroll-driven animations, logical properties, advanced container style queries, and `@property` Houdini patterns. |
+| `tdd-workflow` | Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle. |
+| `test-result-analyzer` | Ingests test logs and identifies root causes across multiple failing test files. Provides actionable fix recommendations. |
+| `testing-patterns` | Testing patterns and principles. Unit, integration, mocking strategies. |
+| `trend-researcher` | Creative muse and design trend analyzer for modern web/mobile interfaces. |
+| `ui-ux-pro-max` | Plan and implement cutting-edge advanced UI/UX. Create distinctive, production-grade frontend interfaces with high design quality. |
+| `ui-ux-researcher` | Expert auditor for accessibility, cognitive load, and premium design heuristics. |
+| `vue-expert` | Vue 3 Composition API and modern Vue ecosystem expert. Use when building Vue applications, optimizing reactivity, component architecture, Nuxt 3 development, performance tuning, and State Management (Pinia). |
+| `vulnerability-scanner` | Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization. |
+| `web-design-guidelines` | Review UI code for Next-Generation Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". |
+| `webapp-testing` | Web application testing principles. E2E, Playwright, deep audit strategies. |
+| `whimsy-injector` | Micro-delight generator for frontend interfaces. Suggests and implements subtle animations, playful transitions, and interaction polish across any frontend stack. |
+| `workflow-optimizer` | Analyzes agent tool-calling patterns and task execution efficiency to suggest process improvements. |