tribunal-kit 4.5.0 → 4.6.0

package/.agent/skills/doc.md

@@ -1,177 +1,209 @@
-# Antigravity Skills
-
-**Guide to creating and using Skills in the Antigravity Kit**
-
----
-
-## 📋 Overview
-
-While Antigravity's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
-
-**Antigravity Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
-
----
-
-## 📁 Structure and Scope
-
-Skills are folder-based packages. You can define these scopes based on your needs:
-
-|Scope|Path|Description|
-|-------------|---------------------------------|------------------------------------|
-|**Workspace**|`<workspace-root>/.agent/skills/`|Available only in a specific project|
-
-### Skill Directory Structure
-
-```
-my-skill/
-├── SKILL.md      # (Required) Metadata & instructions
-├── scripts/      # (Optional) Python or Bash scripts
-├── references/   # (Optional) Text, documentation, templates
-└── assets/       # (Optional) Images or logos
-```
-
----
-
-## 🔍 Example 1: Code Review Skill
-
-This is an instruction-only skill; you only need to create the `SKILL.md` file.
-
-### Step 1: Create the directory
-
-```bash
-mkdir -p .agent/skills/code-review
-```
-
-### Step 2: Create SKILL.md
-
-```markdown
----
-name: code-review
-description: Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
----
-
-# Code Review Skill
-
-When reviewing code, follow these steps:
-
-## Review checklist
-
-1. **Correctness**: Does the code do what it's supposed to?
-2. **Edge cases**: Are error conditions handled?
-3. **Style**: Does it follow project conventions?
-4. **Performance**: Are there obvious inefficiencies?
-
-## How to provide feedback
-
-- Be specific about what needs to change
-- Explain why, not just what
-- Suggest alternatives when possible
-```
-
-**Note**: The `SKILL.md` file contains metadata (name, description) at the top, followed by the instructions. The agent will only read the metadata and load the full instructions only when needed.
-
-### Try it out
-
-Create a file `demo_bad_code.py`:
-
-```python
-import time
-
-def get_user_data(users, id):
-    # Find user by ID
-    for u in users:
-        if u['id'] == id:
-            return u
-    return None
-
-def process_payments(items):
-    total = 0
-    for i in items:
-        # Calculate tax
-        tax = i['price'] * 0.1
-        total = total + i['price'] + tax
-        time.sleep(0.1)  # Simulate slow network call
-    return total
-
-def run_batch():
-    users = [{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]
-    items = [{'price': 10}, {'price': 20}, {'price': 100}]
-
-    u = get_user_data(users, 3)
-    print("User found: " + u['name'])  # Will crash if None
-
-    print("Total: " + str(process_payments(items)))
-
-if __name__ == "__main__":
-    run_batch()
-```
-
-**Prompt**: `review the @demo_bad_code.py file`
-
-The Agent will automatically identify the `code-review` skill, load the information, and follow the instructions.
-
----
-
-## 📄 Example 2: License Header Skill
-
-This skill uses a reference file in the `resources/` (or `references/`) directory.
-
-### Step 1: Create the directory
-
-```bash
-mkdir -p .agent/skills/license-header-adder/resources
-```
-
-### Step 2: Create the template file
-
-**`.agent/skills/license-header-adder/resources/HEADER.txt`**:
-
-```
-/*
- * Copyright (c) 2026 YOUR_COMPANY_NAME LLC.
- * All rights reserved.
- * This code is proprietary and confidential.
- */
-```
-
-### Step 3: Create SKILL.md
-
-**`.agent/skills/license-header-adder/SKILL.md`**:
-
-```markdown
----
-name: license-header-adder
-description: Adds the standard corporate license header to new source files.
----
-
-# License Header Adder
-
-This skill ensures that all new source files have the correct copyright header.
-
-## Instructions
-
-1. **Read the Template**: Read the content of `resources/HEADER.txt`.
-2. **Apply to File**: When creating a new file, prepend this exact content.
-3. **Adapt Syntax**:
-   - For C-style languages (Java, TS), keep the `/* */` block.
-   - For Python/Shell, convert to `#` comments.
-```
-
-### Try it out
-
-**Prompt**: `Create a new Python script named data_processor.py that prints 'Hello World'.`
-
-The Agent will read the template, convert the comments to Python style, and automatically add it to the top of the file.
-
----
-
-## 🎯 Conclusion
-
-By creating Skills, you transform a general AI model into an expert for your project:
-
-- ✅ Systematize best practices
-- ✅ Adhere to code review rules
-- ✅ Automatically add license headers
-- ✅ The Agent automatically knows how to work with your team
-
-Instead of constantly reminding the AI to "remember to add the license" or "fix the commit format," now the Agent will do it automatically!
+# Antigravity Skills
+
+**Guide to creating and using Skills in the Antigravity Kit**
+
+---
+
+## 📋 Overview
+
+While Antigravity's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
+
+**Antigravity Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
+
+---
+
+## 📁 Structure and Scope
+
+Skills are folder-based packages. You can define these scopes based on your needs:
+
+| Scope         | Path                              | Description                          |
+| ------------- | --------------------------------- | ------------------------------------ |
+| **Workspace** | `<workspace-root>/.agent/skills/` | Available only in a specific project |
+
+### Skill Directory Structure
+
+```
+my-skill/
+├── SKILL.md      # (Required) Metadata & instructions
+├── scripts/      # (Optional) Python or Bash scripts
+├── references/   # (Optional) Text, documentation, templates
+└── assets/       # (Optional) Images or logos
+```
+
+---
+
+## 🔍 Example 1: Code Review Skill
+
+This is an instruction-only skill; you only need to create the `SKILL.md` file.
+
+### Step 1: Create the directory
+
+```bash
+mkdir -p .agent/skills/code-review
+```
+
+### Step 2: Create SKILL.md
+
+```markdown
+---
+name: code-review
+description: Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
+---
+
+# Code Review Skill
+
+When reviewing code, follow these steps:
+
+## Review checklist
+
+1. **Correctness**: Does the code do what it's supposed to?
+2. **Edge cases**: Are error conditions handled?
+3. **Style**: Does it follow project conventions?
+4. **Performance**: Are there obvious inefficiencies?
+
+## How to provide feedback
+
+- Be specific about what needs to change
+- Explain why, not just what
+- Suggest alternatives when possible
+```
+
+**Note**: The `SKILL.md` file contains metadata (name, description) at the top, followed by the instructions. The agent will only read the metadata and load the full instructions only when needed.
+
+### Try it out
+
+Create a file `demo_bad_code.py`:
+
+```python
+import time
+
+def get_user_data(users, id):
+    # Find user by ID
+    for u in users:
+        if u['id'] == id:
+            return u
+    return None
+
+def process_payments(items):
+    total = 0
+    for i in items:
+        # Calculate tax
+        tax = i['price'] * 0.1
+        total = total + i['price'] + tax
+        time.sleep(0.1)  # Simulate slow network call
+    return total
+
+def run_batch():
+    users = [{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]
+    items = [{'price': 10}, {'price': 20}, {'price': 100}]
+
+    u = get_user_data(users, 3)
+    print("User found: " + u['name'])  # Will crash if None
+
+    print("Total: " + str(process_payments(items)))
+
+if __name__ == "__main__":
+    run_batch()
+```
+
+**Prompt**: `review the @demo_bad_code.py file`
+
+The Agent will automatically identify the `code-review` skill, load the information, and follow the instructions.
+
+---
+
+## 📄 Example 2: License Header Skill
+
+This skill uses a reference file in the `resources/` (or `references/`) directory.
+
+### Step 1: Create the directory
+
+```bash
+mkdir -p .agent/skills/license-header-adder/resources
+```
+
+### Step 2: Create the template file
+
+**`.agent/skills/license-header-adder/resources/HEADER.txt`**:
+
+```
+/*
+ * Copyright (c) 2026 YOUR_COMPANY_NAME LLC.
+ * All rights reserved.
+ * This code is proprietary and confidential.
+ */
+```
+
+### Step 3: Create SKILL.md
+
+**`.agent/skills/license-header-adder/SKILL.md`**:
+
+```markdown
+---
+name: license-header-adder
+description: Adds the standard corporate license header to new source files.
+---
+
+# License Header Adder
+
+This skill ensures that all new source files have the correct copyright header.
+
+## Instructions
+
+1. **Read the Template**: Read the content of `resources/HEADER.txt`.
+2. **Apply to File**: When creating a new file, prepend this exact content.
+3. **Adapt Syntax**:
+   - For C-style languages (Java, TS), keep the `/* */` block.
+   - For Python/Shell, convert to `#` comments.
+```
+
+### Try it out
+
+**Prompt**: `Create a new Python script named data_processor.py that prints 'Hello World'.`
+
+The Agent will read the template, convert the comments to Python style, and automatically add it to the top of the file.
+
+---
+
+## 🎯 Conclusion
+
+By creating Skills, you transform a general AI model into an expert for your project:
+
+- ✅ Systematize best practices
+- ✅ Adhere to code review rules
+- ✅ Automatically add license headers
+- ✅ The Agent automatically knows how to work with your team
+
+Instead of constantly reminding the AI to "remember to add the license" or "fix the commit format," now the Agent will do it automatically!
+
+---
+
+## 🚀 Industry Level 2 — Pro Skills
+
+These advanced skills are automatically loaded by the `system-architect` and `cloud-engineer` agents when the request domain matches. They are NOT loaded by default — only when explicitly needed, preventing context bloat.
+
+| Skill                  | Activation Trigger                                     | What It Knows                                                                                |
+| ---------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
+| `git-pro`              | Advanced Git operations, monorepo, release engineering | Git internals, bisect, worktrees, semantic-release, OIDC GitHub Actions, CODEOWNERS          |
+| `containerization-pro` | "containerize", "Dockerfile", "Docker", "ECR"          | Multi-stage builds (Node/Python/Rust/Go), image hardening, BuildKit, Trivy scanning, AWS ECR |
+| `cicd-pro`             | "CI/CD pipeline", "deploy to", "GitHub Actions"        | 3-stage pipeline, OIDC AWS auth, Blue/Green ECS deploy, rollback, Slack notifications        |
+| `system-design-pro`    | "design a system", "scale this", "N users", "capacity" | 6-step framework, scale estimation, CAP Theorem, database matrix, reference designs          |
+| `cloud-architect`      | "AWS", "Terraform", "ECS", "VPC", "infrastructure"     | AWS service selection, Terraform HCL, VPC design, IAM, Secrets Manager, CloudWatch           |
+
+### Golden Path (Decision 2B)
+
+All cloud/infra skills are opinionated toward:
+
+- **Cloud**: AWS
+- **Containers**: Docker + AWS ECR
+- **CI/CD**: GitHub Actions
+- **Compute**: ECS Fargate (API) / Lambda (events)
+- **IaC**: Terraform
+- **Auth**: OIDC (zero static secrets)
+
+### New Agents
+
+| Agent              | Owns                                                    | Use When                                              |
+| ------------------ | ------------------------------------------------------- | ----------------------------------------------------- |
+| `system-architect` | `system-design-pro` + `architecture`                    | Designing systems, capacity planning, scale questions |
+| `cloud-engineer`   | `cloud-architect` + `cicd-pro` + `containerization-pro` | AWS infra, Dockerfiles, CI/CD pipelines, Terraform    |