tribunal-kit 2.4.6 → 3.1.0

package/.agent/skills/database-design/database-selection.md

@@ -1,43 +0,0 @@
-# Database Selection (2025)
-
-> Choose database based on context, not default.
-
-## Decision Tree
-
-```
-What are your requirements?
-│
-├── Full relational features needed
-│   ├── Self-hosted → PostgreSQL
-│   └── Serverless → Neon, Supabase
-│
-├── Edge deployment / Ultra-low latency
-│   └── Turso (edge SQLite)
-│
-├── AI / Vector search
-│   └── PostgreSQL + pgvector
-│
-├── Simple / Embedded / Local
-│   └── SQLite
-│
-└── Global distribution
-    └── PlanetScale, CockroachDB, Turso
-```
-
-## Comparison
-
-| Database | Best For | Trade-offs |
-|----------|----------|------------|
-| **PostgreSQL** | Full features, complex queries | Needs hosting |
-| **Neon** | Serverless PG, branching | PG complexity |
-| **Turso** | Edge, low latency | SQLite limitations |
-| **SQLite** | Simple, embedded, local | Single-writer |
-| **PlanetScale** | MySQL, global scale | No foreign keys |
-
-## Questions to Ask
-
-1. What's the deployment environment?
-2. How complex are the queries?
-3. Is edge/serverless important?
-4. Vector search needed?
-5. Global distribution required?

package/.agent/skills/database-design/indexing.md

@@ -1,39 +0,0 @@
-# Indexing Principles
-
-> When and how to create indexes effectively.
-
-## When to Create Indexes
-
-```
-Index these:
-├── Columns in WHERE clauses
-├── Columns in JOIN conditions
-├── Columns in ORDER BY
-├── Foreign key columns
-└── Unique constraints
-
-Don't over-index:
-├── Write-heavy tables (slower inserts)
-├── Low-cardinality columns
-├── Columns rarely queried
-```
-
-## Index Type Selection
-
-| Type | Use For |
-|------|---------|
-| **B-tree** | General purpose, equality & range |
-| **Hash** | Equality only, faster |
-| **GIN** | JSONB, arrays, full-text |
-| **GiST** | Geometric, range types |
-| **HNSW/IVFFlat** | Vector similarity (pgvector) |
-
-## Composite Index Principles
-
-```
-Order matters for composite indexes:
-├── Equality columns first
-├── Range columns last
-├── Most selective first
-└── Match query pattern
-```

package/.agent/skills/database-design/migrations.md

@@ -1,48 +0,0 @@
-# Migration Principles
-
-> Safe migration strategy for zero-downtime changes.
-
-## Safe Migration Strategy
-
-```
-For zero-downtime changes:
-│
-├── Adding column
-│   └── Add as nullable → backfill → add NOT NULL
-│
-├── Removing column
-│   └── Stop using → deploy → remove column
-│
-├── Adding index
-│   └── CREATE INDEX CONCURRENTLY (non-blocking)
-│
-└── Renaming column
-    └── Add new → migrate data → deploy → drop old
-```
-
-## Migration Philosophy
-
-- Never make breaking changes in one step
-- Test migrations on data copy first
-- Have rollback plan
-- Run in transaction when possible
-
-## Serverless Databases
-
-### Neon (Serverless PostgreSQL)
-
-| Feature | Benefit |
-|---------|---------|
-| Scale to zero | Cost savings |
-| Instant branching | Dev/preview |
-| Full PostgreSQL | Compatibility |
-| Autoscaling | Traffic handling |
-
-### Turso (Edge SQLite)
-
-| Feature | Benefit |
-|---------|---------|
-| Edge locations | Ultra-low latency |
-| SQLite compatible | Simple |
-| Generous free tier | Cost |
-| Global distribution | Performance |

package/.agent/skills/database-design/optimization.md

@@ -1,36 +0,0 @@
-# Query Optimization
-
-> N+1 problem, EXPLAIN ANALYZE, optimization priorities.
-
-## N+1 Problem
-
-```
-What is N+1?
-├── 1 query to get parent records
-├── N queries to get related records
-└── Very slow!
-
-Solutions:
-├── JOIN → Single query with all data
-├── Eager loading → ORM handles JOIN
-├── DataLoader → Batch and cache (GraphQL)
-└── Subquery → Fetch related in one query
-```
-
-## Query Analysis Mindset
-
-```
-Before optimizing:
-├── EXPLAIN ANALYZE the query
-├── Look for Seq Scan (full table scan)
-├── Check actual vs estimated rows
-└── Identify missing indexes
-```
-
-## Optimization Priorities
-
-1. **Add missing indexes** (most common issue)
-2. **Select only needed columns** (not SELECT *)
-3. **Use proper JOINs** (avoid subqueries when possible)
-4. **Limit early** (pagination at database level)
-5. **Cache** (when appropriate)

package/.agent/skills/database-design/orm-selection.md

@@ -1,30 +0,0 @@
-# ORM Selection (2025)
-
-> Choose ORM based on deployment and DX needs.
-
-## Decision Tree
-
-```
-What's the context?
-│
-├── Edge deployment / Bundle size matters
-│   └── Drizzle (smallest, SQL-like)
-│
-├── Best DX / Schema-first
-│   └── Prisma (migrations, studio)
-│
-├── Maximum control
-│   └── Raw SQL with query builder
-│
-└── Python ecosystem
-    └── SQLAlchemy 2.0 (async support)
-```
-
-## Comparison
-
-| ORM | Best For | Trade-offs |
-|-----|----------|------------|
-| **Drizzle** | Edge, TypeScript | Newer, less examples |
-| **Prisma** | DX, schema management | Heavier, not edge-ready |
-| **Kysely** | Type-safe SQL builder | Manual migrations |
-| **Raw SQL** | Complex queries, control | Manual type safety |

package/.agent/skills/database-design/schema-design.md

@@ -1,56 +0,0 @@
-# Schema Design Principles
-
-> Normalization, primary keys, timestamps, relationships.
-
-## Normalization Decision
-
-```
-When to normalize (separate tables):
-├── Data is repeated across rows
-├── Updates would need multiple changes
-├── Relationships are clear
-└── Query patterns benefit
-
-When to denormalize (embed/duplicate):
-├── Read performance critical
-├── Data rarely changes
-├── Always fetched together
-└── Simpler queries needed
-```
-
-## Primary Key Selection
-
-| Type | Use When |
-|------|----------|
-| **UUID** | Distributed systems, security |
-| **ULID** | UUID + sortable by time |
-| **Auto-increment** | Simple apps, single database |
-| **Natural key** | Rarely (business meaning) |
-
-## Timestamp Strategy
-
-```
-For every table:
-├── created_at → When created
-├── updated_at → Last modified
-└── deleted_at → Soft delete (if needed)
-
-Use TIMESTAMPTZ (with timezone) not TIMESTAMP
-```
-
-## Relationship Types
-
-| Type | When | Implementation |
-|------|------|----------------|
-| **One-to-One** | Extension data | Separate table with FK |
-| **One-to-Many** | Parent-children | FK on child table |
-| **Many-to-Many** | Both sides have many | Junction table |
-
-## Foreign Key ON DELETE
-
-```
-├── CASCADE → Delete children with parent
-├── SET NULL → Children become orphans
-├── RESTRICT → Prevent delete if children exist
-└── SET DEFAULT → Children get default value
-```

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.