tribunal-kit 9.2.4 → 9.2.6

package/.agents/skills/distill/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: distill
-description: "Use when Simplify noisy interfaces by removing non-essential visual and operational complexity. Use when a UI has too many options, crowded toolbars, redundant text, or unnecessary visual containers."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when building, styling, optimizing, and auditing distill components, responsive layouts, design systems, and frontend state."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - quieter
   - clarify
@@ -15,31 +15,101 @@ scripts-binding:
 
 # Distill — UX Simplification & Decluttering
 
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `distill` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
+
+
+## Activation Boundaries
+- **Activate when:** Use when building, styling, optimizing, and auditing distill components, responsive layouts, design systems, and frontend state.
+- **DO NOT activate when:** The task falls outside the `distill` domain or is managed by a different dedicated specialist agent.
+
+
+## 🔁 Multi-Pass Execution Protocol
+
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
+
+---
+
 ## 🛠️ Technical Architecture & Reference Recipes
 
----
+---
+
+## The 4 Distillation Steps
+
+### 1. Identify & Remove Visual Noise
+
+- **Container Reduction**: Eliminate unnecessary nested cards, boxes inside boxes, and decorative borders. Use whitespace instead of lines to separate content blocks.
+- **Icon Pruning**: Remove decorative icons that restate obvious text labels (e.g. an envelope icon next to a button that clearly says "Send Email").
+
+### 2. Collapse Secondary Actions
+
+- **Primary vs Overflow**: Keep only 1 primary action button and max 1 secondary button visible. Hide tertiary actions inside an overflow dropdown (`...` menu).
+- **Progressive Disclosure**: Hide advanced settings or non-essential controls behind an "Advanced Settings" accordion or popover.
+
+### 3. Trim Copy & Microcopy
+
+- **Cut Conversational Filler**: Strip verbose instructions. Change _"Please fill out the form below to register your account"_ to _"Create account"_.
+- **Shorten Button Labels**: Change _"Click here to update your profile settings"_ to _"Save profile"_.
+
+### 4. Group Related Fields
+
+- **Consolidate Form Inputs**: Merge separate "First Name" and "Last Name" fields into "Full Name" if separate values aren't strictly required. Merge city/state/zip into single address lookup where possible.
 
----
+## 🚨 Edge-Case & Failure Mode Matrix
 
-## The 4 Distillation Steps
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-### 1. Identify & Remove Visual Noise
 
-- **Container Reduction**: Eliminate unnecessary nested cards, boxes inside boxes, and decorative borders. Use whitespace instead of lines to separate content blocks.
-- **Icon Pruning**: Remove decorative icons that restate obvious text labels (e.g. an envelope icon next to a button that clearly says "Send Email").
+## 🤖 LLM-Specific Traps Table
 
-### 2. Collapse Secondary Actions
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **Uncontrolled Re-render Loop** | Mutating state inside render bodies or omitting hook dependencies | Wrap effects with explicit deps and isolate reactive derivations in useMemo |
+| **Accessibility Neglect** | Interactive <div> without role="button", tabIndex, or onKeyDown | Use semantic <button> or provide ARIA role, keyboard handlers, and focus ring |
+| **Layout Shift Flash** | Images/dynamic content without aspect-ratio or explicit dimensions | Enforce aspect-ratio or skeleton placeholders to guarantee zero CLS |
 
-- **Primary vs Overflow**: Keep only 1 primary action button and max 1 secondary button visible. Hide tertiary actions inside an overflow dropdown (`...` menu).
-- **Progressive Disclosure**: Hide advanced settings or non-essential controls behind an "Advanced Settings" accordion or popover.
 
-### 3. Trim Copy & Microcopy
+## 🏛️ Tribunal Verification & Guardrails
 
-- **Cut Conversational Filler**: Strip verbose instructions. Change _"Please fill out the form below to register your account"_ to _"Create account"_.
-- **Shorten Button Labels**: Change _"Click here to update your profile settings"_ to _"Save profile"_.
+**Active Reviewers:** `frontend-reviewer` · `type-safety` · `ui-ux-auditor` · `complexity-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-### 4. Group Related Fields
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
 
-- **Consolidate Form Inputs**: Merge separate "First Name" and "Last Name" fields into "Full Name" if separate values aren't strictly required. Merge city/state/zip into single address lookup where possible.
+### ✅ Pre-Flight Self-Audit Checklist
+```
+✅ Are all component props strictly typed with zero implicit "any"?
+✅ Are responsive breakpoints, fluid typography, and optical balance verified?
+✅ Is accessibility (ARIA labels, keyboard navigation, contrast ratio >= 4.5:1) validated?
+✅ Are re-renders minimized and state lifecycles cleanly separated?
+✅ Did I verify all imported UI components and icon sets actually exist?
+```
+
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/documentation-templates/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: documentation-templates
-description: "Use when Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when executing, coordinating, planning, or reviewing documentation templates agent workflows, cognitive loops, and architecture standards."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - readme-builder
   - geo-fundamentals
@@ -15,237 +15,295 @@ scripts-binding:
 
 # Documentation Standards
 
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `documentation-templates` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-## Hallucination Traps (Read First)
 
-- ❌ Writing documentation that only AI-generated code can understand -> ✅ Docs are for HUMANS; use clear language and real examples
-- ❌ Documenting implementation details instead of behavior -> ✅ Document WHAT it does and WHY, not HOW (code shows how)
-- ❌ Skipping the 'Quick Start' section -> ✅ The first 30 seconds of a README determine if someone uses your project
+## Activation Boundaries
+- **Activate when:** Use when executing, coordinating, planning, or reviewing documentation templates agent workflows, cognitive loops, and architecture standards.
+- **DO NOT activate when:** The task falls outside the `documentation-templates` domain or is managed by a different dedicated specialist agent.
 
----
-
----
 
-## Documentation Types and Their Audiences
+## 🔁 Multi-Pass Execution Protocol
 
-| Type                        | Audience                                | Goal                                                     |
-| --------------------------- | --------------------------------------- | -------------------------------------------------------- |
-| README                      | New developer joining the project       | "Get me running in 10 minutes"                           |
-| API docs                    | External integrator or frontend dev     | "Tell me exactly what I can call and what I'll get back" |
-| Architecture decision (ADR) | Future engineer inheriting the codebase | "Tell me why it works this way, not just how"            |
-| Code comment                | Reviewer, maintainer                    | "Explain the non-obvious; skip the obvious"              |
-| Runbook                     | On-call engineer at 2am                 | "Tell me what to do, not what to think about"            |
-
----
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
-## Skill Pattern Inheritance
 
-The Tribunal Agent Kit supports 5 standard Agent Design Kit (ADK) base patterns.
-To build a skill using a robust, tested agent behavior model, add `pattern: [pattern-name]` to the YAML frontmatter of your `SKILL.md`.
-
-| Pattern          | Value                   | When to use                                                                       |
-| ---------------- | ----------------------- | --------------------------------------------------------------------------------- |
-| **Inversion**    | `pattern: inversion`    | Forces the agent to interview the user (Socratic Gate) before acting.             |
-| **Reviewer**     | `pattern: reviewer`     | Evaluates artifacts against a checklist and severity levels.                      |
-| **Tool Wrapper** | `pattern: tool-wrapper` | Strictly executes external CLI tools via provided documentation without guessing. |
-| **Generator**    | `pattern: generator`    | Produces structured output (docs, boilerplate) by filling a rigid template.       |
-| **Pipeline**     | `pattern: pipeline`     | Executes sequential tasks with strict halting gates between steps.                |
-
-_Templates defining the specific rules for these patterns live in `.agent/patterns/`._
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
+## Hallucination Traps (Read First)
+
+- ❌ Writing documentation that only AI-generated code can understand -> ✅ Docs are for HUMANS; use clear language and real examples
+- ❌ Documenting implementation details instead of behavior -> ✅ Document WHAT it does and WHY, not HOW (code shows how)
+- ❌ Skipping the 'Quick Start' section -> ✅ The first 30 seconds of a README determine if someone uses your project
+
 ---
-
-## README Template
-
-```markdown
-# Project Name
-
-One sentence: what this is and what problem it solves.
-
-## Quick Start
-
-\`\`\`bash
-git clone ...
-cd project
-npm install
-cp .env.example .env
-npm run dev
-\`\`\`
-
-Open http://localhost:3000
-
-## Requirements
-
-- Node.js 20+
-- PostgreSQL 15+
-- [Any other hard requirements]
-
-## Project Structure
-
-\`\`\`
-src/
-api/ API routes
-lib/ Shared utilities
-services/ Business logic
-\`\`\`
-
-## Environment Variables
-
-| Variable     | Required | Description                  |
-| ------------ | -------- | ---------------------------- |
-| DATABASE_URL | Yes      | PostgreSQL connection string |
-| JWT_SECRET   | Yes      | Secret for signing JWTs      |
-
-## Running Tests
-
-\`\`\`bash
-npm test # unit tests
-npm run test:e2e # end-to-end tests
-\`\`\`
-
-## Contributing
-
-[Brief contribution guide or link to CONTRIBUTING.md]
+## Documentation Types and Their Audiences
+
+| Type                        | Audience                                | Goal                                                     |
+| --------------------------- | --------------------------------------- | -------------------------------------------------------- |
+| README                      | New developer joining the project       | "Get me running in 10 minutes"                           |
+| API docs                    | External integrator or frontend dev     | "Tell me exactly what I can call and what I'll get back" |
+| Architecture decision (ADR) | Future engineer inheriting the codebase | "Tell me why it works this way, not just how"            |
+| Code comment                | Reviewer, maintainer                    | "Explain the non-obvious; skip the obvious"              |
+| Runbook                     | On-call engineer at 2am                 | "Tell me what to do, not what to think about"            |
+
+---
+
+## Skill Pattern Inheritance
+
+The Tribunal Agent Kit supports 5 standard Agent Design Kit (ADK) base patterns.
+To build a skill using a robust, tested agent behavior model, add `pattern: [pattern-name]` to the YAML frontmatter of your `SKILL.md`.
+
+| Pattern          | Value                   | When to use                                                                       |
+| ---------------- | ----------------------- | --------------------------------------------------------------------------------- |
+| **Inversion**    | `pattern: inversion`    | Forces the agent to interview the user (Socratic Gate) before acting.             |
+| **Reviewer**     | `pattern: reviewer`     | Evaluates artifacts against a checklist and severity levels.                      |
+| **Tool Wrapper** | `pattern: tool-wrapper` | Strictly executes external CLI tools via provided documentation without guessing. |
+| **Generator**    | `pattern: generator`    | Produces structured output (docs, boilerplate) by filling a rigid template.       |
+| **Pipeline**     | `pattern: pipeline`     | Executes sequential tasks with strict halting gates between steps.                |
+
+_Templates defining the specific rules for these patterns live in `.agent/patterns/`._
+
+---
+
+## README Template
+
+```markdown
+# Project Name
+
+One sentence: what this is and what problem it solves.
+
+## Quick Start
+
+\`\`\`bash
+git clone ...
+cd project
+npm install
+cp .env.example .env
+npm run dev
+\`\`\`
+
+Open http://localhost:3000
+
+## Requirements
+
+- Node.js 20+
+- PostgreSQL 15+
+- [Any other hard requirements]
+
+## Project Structure
+
+\`\`\`
+src/
+api/ API routes
+lib/ Shared utilities
+services/ Business logic
+\`\`\`
+
+## Environment Variables
+
+| Variable     | Required | Description                  |
+| ------------ | -------- | ---------------------------- |
+| DATABASE_URL | Yes      | PostgreSQL connection string |
+| JWT_SECRET   | Yes      | Secret for signing JWTs      |
+
+## Running Tests
+
+\`\`\`bash
+npm test # unit tests
+npm run test:e2e # end-to-end tests
+\`\`\`
+
+## Contributing
+
+[Brief contribution guide or link to CONTRIBUTING.md]
+```
+
+---
+
+## API Documentation Standards
+
+For each endpoint, document:
+
+```markdown
+### POST /api/users
+
+Creates a new user account.
+
+**Request Body**
+\`\`\`json
+{
+"email": "string (required, valid email)",
+"name": "string (required, 2–100 chars)",
+"role": "admin | user (optional, default: user)"
+}
+\`\`\`
+
+**Responses**
+
+| Status | Meaning              | Body                                   |
+| ------ | -------------------- | -------------------------------------- |
+| 201    | User created         | `{ data: User }`                       |
+| 400    | Validation failed    | `{ error: string, details: string[] }` |
+| 409    | Email already exists | `{ error: string }`                    |
+
+**Example**
+\`\`\`bash
+curl -X POST /api/users \
+-H "Content-Type: application/json" \
+-d '{"email": "user@example.com", "name": "Jane"}'
+\`\`\`
+```
+
+---
+
+## Code Comment Rules
+
+**Comment the why, not the what:**
+
+```ts
+// ❌ States what the code does (obvious from reading it)
+// Multiply price by tax rate
+const total = price * taxRate;
+
+// ✅ Explains why this specific value exists
+// Vietnamese tax law requires 10% VAT on all digital goods (Circular 92/2015)
+const VN_DIGITAL_TAX_RATE = 1.1;
+const total = price * VN_DIGITAL_TAX_RATE;
+```
+
+**When to always comment:**
+
+- Non-obvious business rules
+- Workarounds for external library bugs (with issue link if possible)
+- Performance decisions that look like premature optimization but aren't
+- Magic numbers and why they have that value
+
+---
+
+## AI-Friendly Documentation
+
+When a codebase will be worked on by AI assistants:
+
+- Keep a `CODEBASE.md` at root with: tech stack, folder structure, key conventions
+- Add a `ARCHITECTURE.md` with: system boundaries, data flow, key decisions
+- Add `// @purpose:` comments on complex functions so AI can understand intent without reading the full implementation
+- Document which files are auto-generated and should not be edited directly
+
+---
+
+## Runbook Template
+
+```markdown
+# Runbook: [Service or Incident Type]
+
+## Symptoms
+
+- [What the user or monitor reports]
+
+## Likely Causes
+
+1. [Most common cause]
+2. [Second most common]
+
+## Investigation Steps
+
+\`\`\`bash
+
+# Check service health
+
+kubectl get pods -n production
+
+# Check recent errors
+
+kubectl logs deployment/api --since=15m | grep ERROR
+\`\`\`
+
+## Resolution Steps
+
+### If Cause 1:
+
+[Exact steps to resolve]
+
+### If Cause 2:
+
+[Exact steps to resolve]
+
+## Escalation
+
+If unresolved after 30 minutes → page @on-call-lead
+
+## Post-Incident
+
+[ ] Write incident report
+[ ] Add monitoring for this failure mode
+[ ] Update this runbook if steps changed
+```
+
+---
+
+## Output Format
+
+When this skill completes a task, structure your output as:
+
+```
+━━━ Documentation Templates Output ━━━━━━━━━━━━━━━━━━━━━━━━
+Task:        [what was performed]
+Result:      [outcome summary — one line]
+─────────────────────────────────────────────────
+Checks:      ✅ [N passed] · ⚠️  [N warnings] · ❌ [N blocked]
+VBC status:  PENDING → VERIFIED
+Evidence:    [link to terminal output, test result, or file diff]
 ```
 
----
-
-## API Documentation Standards
-
-For each endpoint, document:
+## 🚨 Edge-Case & Failure Mode Matrix
 
-```markdown
-### POST /api/users
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-Creates a new user account.
 
-**Request Body**
-\`\`\`json
-{
-"email": "string (required, valid email)",
-"name": "string (required, 2–100 chars)",
-"role": "admin | user (optional, default: user)"
-}
-\`\`\`
+## 🏛️ Tribunal Verification & Guardrails
 
-**Responses**
+**Active Reviewers:** `orchestrator` · `agent-organizer` · `logic-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-| Status | Meaning              | Body                                   |
-| ------ | -------------------- | -------------------------------------- |
-| 201    | User created         | `{ data: User }`                       |
-| 400    | Validation failed    | `{ error: string, details: string[] }` |
-| 409    | Email already exists | `{ error: string }`                    |
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
 
-**Example**
-\`\`\`bash
-curl -X POST /api/users \
--H "Content-Type: application/json" \
--d '{"email": "user@example.com", "name": "Jane"}'
-\`\`\`
+### ✅ Pre-Flight Self-Audit Checklist
 ```
-
----
-
-## Code Comment Rules
-
-**Comment the why, not the what:**
-
-```ts
-// ❌ States what the code does (obvious from reading it)
-// Multiply price by tax rate
-const total = price * taxRate;
-
-// ✅ Explains why this specific value exists
-// Vietnamese tax law requires 10% VAT on all digital goods (Circular 92/2015)
-const VN_DIGITAL_TAX_RATE = 1.1;
-const total = price * VN_DIGITAL_TAX_RATE;
+✅ Did I deconstruct the root objective before proposing architecture?
+✅ Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
+✅ Did I avoid over-engineering and select the simplest effective pattern?
+✅ Did I verify assumptions with concrete file reads instead of speculation?
+✅ Did I establish measurable verification criteria before completion?
 ```
 
-**When to always comment:**
-
-- Non-obvious business rules
-- Workarounds for external library bugs (with issue link if possible)
-- Performance decisions that look like premature optimization but aren't
-- Magic numbers and why they have that value
-
----
-
-## AI-Friendly Documentation
-
-When a codebase will be worked on by AI assistants:
-
-- Keep a `CODEBASE.md` at root with: tech stack, folder structure, key conventions
-- Add a `ARCHITECTURE.md` with: system boundaries, data flow, key decisions
-- Add `// @purpose:` comments on complex functions so AI can understand intent without reading the full implementation
-- Document which files are auto-generated and should not be edited directly
-
----
-
-## Runbook Template
-
-```markdown
-# Runbook: [Service or Incident Type]
-
-## Symptoms
-
-- [What the user or monitor reports]
-
-## Likely Causes
-
-1. [Most common cause]
-2. [Second most common]
-
-## Investigation Steps
-
-\`\`\`bash
-
-# Check service health
-
-kubectl get pods -n production
-
-# Check recent errors
-
-kubectl logs deployment/api --since=15m | grep ERROR
-\`\`\`
-
-## Resolution Steps
-
-### If Cause 1:
-
-[Exact steps to resolve]
-
-### If Cause 2:
-
-[Exact steps to resolve]
-
-## Escalation
-
-If unresolved after 30 minutes → page @on-call-lead
-
-## Post-Incident
-
-[ ] Write incident report
-[ ] Add monitoring for this failure mode
-[ ] Update this runbook if steps changed
-```
-
----
-
-## Output Format
-
-When this skill completes a task, structure your output as:
-
-```
-━━━ Documentation Templates Output ━━━━━━━━━━━━━━━━━━━━━━━━
-Task:        [what was performed]
-Result:      [outcome summary — one line]
-─────────────────────────────────────────────────
-Checks:      ✅ [N passed] · ⚠️  [N warnings] · ❌ [N blocked]
-VBC status:  PENDING → VERIFIED
-Evidence:    [link to terminal output, test result, or file diff]
-```
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.