tribunal-kit 3.0.0 → 4.0.0

package/.agent/skills/project-idioms/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: project-idioms
+description: >
+  Auto-evolved skill containing project-specific architectural idioms extracted
+  from the developer's own code decisions. Generated by skill_evolution.py.
+  Commit this file to share your Engineering Culture across the team.
+  Every agent MUST respect these idioms above generic defaults.
+version: auto
+last-updated: 2026-04-09
+digest-cycles: 0
+pattern: generator
+---
+
+## Hallucination Traps (Read First)
+- ❌ Overriding project idioms without explicit justification -> ✅ Idioms represent team decisions; flag deviations with reasoning
+- ❌ Applying idioms from one project to a different project -> ✅ Idioms are project-specific; verify they apply to the current codebase
+
+---
+
+
+# Project Idioms — Auto-Evolved Skill
+
+> **Authority Level: ABSOLUTE**
+> These idioms were extracted from this project's actual code decisions.
+> They override all generic agent defaults and best practices.
+> Every agent reads this file on activation and adapts its proposals accordingly.
+
+---
+
+## How Idioms Are Born
+
+1. Developer commits code that **differs** from what the AI proposed.
+2. `skill_evolution.py digest` extracts the architectural delta (semantic filter).
+3. A minimal LLM prompt (< 500 tokens) identifies the **WHY** behind the change.
+4. The idiom is recorded here with a stable pattern + reason pair.
+5. All future code generations must align with these idioms.
+
+---
+
+## Recorded Idioms
+
+| ID | Pattern | Why This Project Uses It | Domain | Since |
+|:---|:--------|:-------------------------|:-------|:------|
+| — | — | _No idioms recorded yet. Run your first digest cycle._ | — | — |
+
+---
+
+## How to Add New Idioms
+
+Run after committing or staging a meaningful architectural change:
+
+```bash
+# Analyze staged changes (default)
+python .agent/scripts/skill_evolution.py digest
+
+# Preview without writing
+python .agent/scripts/skill_evolution.py digest --dry-run
+
+# Analyze last commit instead of staged
+python .agent/scripts/skill_evolution.py digest --head
+
+# Check current idiom count and token savings
+python .agent/scripts/skill_evolution.py status
+```
+
+---
+
+## Enforcement Rules for All Agents
+
+```
+□ Before proposing any code: scan the idiom table above
+□ If your proposal contradicts an idiom → flag it explicitly with:
+     "⚠️ Note: My proposal differs from Project Idiom #N. Reason: [explain]"
+□ Never override an idiom silently
+□ When citing an idiom in a review:
+     "Per Project Idiom #N: [pattern] — [reason]"
+□ If no idioms yet → proceed with domain-standard approaches
+```
+
+---
+
+## Digest History
+
+Last digest: `never`
+Total cycles: `0`
+
+Run `python .agent/scripts/skill_evolution.py status` to see full statistics.

package/.agent/skills/python-patterns/SKILL.md

@@ -7,23 +7,28 @@ last-updated: 2026-03-12
 applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
 ---
 
-# Python Development Principles
+## Hallucination Traps (Read First)
+- ❌ Using `dict` for structured data when a dataclass/Pydantic model exists -> ✅ Dicts have no type safety; use typed models
+- ❌ Catching bare `except:` or `except Exception:` -> ✅ Catch specific exceptions; bare except swallows KeyboardInterrupt and SystemExit
+- ❌ Using `os.path` for path operations -> ✅ Use `pathlib.Path` for modern, readable path manipulation
+
+---
 
-> Python's flexibility is its greatest weakness.
-> Without conventions, every project ends up with its own unpredictable shape.
+
+# Python Development Principles
 
 ---
 
 ## Framework Selection
 
-| Use Case | Recommended | When to Use |
+|Use Case|Recommended|When to Use|
 |---|---|---|
-| REST API, general-purpose | FastAPI | Type-safe, async, auto-docs via OpenAPI |
-| REST API, batteries-included | Django + DRF | Rapid development, ORM included, admin panel |
-| Microservice / minimal API | Flask | Simple, no overhead, full control |
-| Data pipeline / ETL | No framework | Standard library + pandas/polars as needed |
-| CLI tool | Click or Typer | Better than argparse for complex CLIs |
-| Async task queue | Celery + Redis | Background jobs, scheduled tasks |
+|REST API, general-purpose|FastAPI|Type-safe, async, auto-docs via OpenAPI|
+|REST API, batteries-included|Django + DRF|Rapid development, ORM included, admin panel|
+|Microservice / minimal API|Flask|Simple, no overhead, full control|
+|Data pipeline / ETL|No framework|Standard library + pandas/polars as needed|
+|CLI tool|Click or Typer|Better than argparse for complex CLIs|
+|Async task queue|Celery + Redis|Background jobs, scheduled tasks|
 
 **Decision question:** Does this need an ORM, admin panel, and auth out of the box? → Django. Does it need type-safe inputs with automatic validation? → FastAPI. Is it small and needs nothing? → Flask.
 
@@ -201,29 +206,4 @@ 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 Python
-
-1. **Missing Type Hints** — writing `def func(a, b):` instead of fully typing parameters and return values.
-2. **Bare `except:` blocks** — catching all exceptions blindly without logging or raising `AppError`.
-3. **`requirements.txt` over `pyproject.toml`** — hallucinating outdated dependency management practices.
-4. **Blocking the async event loop** — writing synchronous I/O or `time.sleep()` inside an `async def` FastAPI route.
-5. **Assuming Django for microservices** — defaulting to a massive framework when `FastAPI` or `Flask` fits better.
-
-### ✅ Pre-Flight Self-Audit
-
-Review these questions before generating Python code:
-```
-✅ Are all function parameters and return types strictly typed?
-✅ Did I use the modern toolchain (`uv`/`poetry`, `ruff`, `mypy`)?
-✅ Did I accidentally block the async event loop with sync code?
-✅ Are domain errors properly caught and mapped to HTTP status codes without leaking stack traces?
-✅ Is my dependency selection precise and explicitly declared in `pyproject.toml`?
-```