super-opencode 1.1.0 → 1.1.1

package/.opencode/commands/soc-help.md

@@ -1,94 +1,94 @@
----
-description: Help and command reference
----
-
-# /soc-help
-
-## 1. Command Overview
-The `/soc-help` command is the "Librarian." It serves as the primary documentation interface for the agent system. It explains *how* to use the other commands, details what each agent does, and lists available skills. It uses the `researcher` agent to find answers within the system's own documentation.
-
-## 2. Triggers & Routing
-The command is self-contained but may use `researcher` for deep queries.
-
-| Trigger Scenario | Flag | Target Agent | Action |
-| :--- | :--- | :--- | :--- |
-| **Command Syntax** | `[command]` | `[System]` | Show usage and flags |
-| **Agent Roles** | `[agent]` | `[System]` | Show persona description |
-| **Workflow Guide** | `[topic]` | `[researcher]` | Summarize best practices |
-
-## 3. Usage & Arguments
-```bash
-/soc-help [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: (Optional) Specific command (`implement`), agent (`backend`), or topic (`workflows`). Default: Shows index.
-
-### Flags
--   **`--verbose`**: Show detailed descriptions and hidden flags.
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Lookup
-1.  **Index**: Check if target is a known Command, Agent, or Skill.
-2.  **Search**: If unknown, grep `.opencode/` documentation for keywords.
-
-### Phase 2: Formatting
--   **Structure**: Group by Category (Workflow vs Skill).
--   **Clarity**: Show "Quick Start" snippets.
-
-## 5. Output Guidelines (The Contract)
-
-### Help Document
-```markdown
-## Help: [Target]
-
-### Description
-[Brief summary]
-
-### Usage
-`[Command Pattern]`
-
-### Key Features
--   Feature 1
--   Feature 2
-
-### Related Commands
--   `/related-command`
-```
-
-## 6. Examples
-
-### A. Command Help
-```bash
-/soc-help implement
-```
-*Effect:* Displays usage for `/soc-implement`, including flags like `--agent` and `--test`.
-
-### B. Agent Role
-```bash
-/soc-help backend
-```
-*Effect:* Shows the `backend` agent's persona, including "Prime Directives" and "Restrictions."
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Researcher**: `@[.opencode/agents/researcher.md]` - For finding unstructured help.
-
-### Skills
--   **None**: This is a read-only command.
-
-### MCP Integration
--   **`filesystem`**: Reading documentation files.
-
-## 8. Boundaries
-
-**Will:**
--   Explain system capabilities.
--   List available tools.
--   Provide syntax examples.
-
-**Will Not:**
--   **Execute Commands**: It only explains them.
--   **Hallucinate Features**: Only lists what exists in `.opencode/`.
+---
+description: Help and command reference
+---
+
+# /soc-help
+
+## 1. Command Overview
+The `/soc-help` command is the "Librarian." It serves as the primary documentation interface for the agent system. It explains *how* to use the other commands, details what each agent does, and lists available skills. It uses the `researcher` agent to find answers within the system's own documentation.
+
+## 2. Triggers & Routing
+The command is self-contained but may use `researcher` for deep queries.
+
+| Trigger Scenario | Flag | Target Agent | Action |
+| :--- | :--- | :--- | :--- |
+| **Command Syntax** | `[command]` | `[System]` | Show usage and flags |
+| **Agent Roles** | `[agent]` | `[System]` | Show persona description |
+| **Workflow Guide** | `[topic]` | `[researcher]` | Summarize best practices |
+
+## 3. Usage & Arguments
+```bash
+/soc-help [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: (Optional) Specific command (`implement`), agent (`backend`), or topic (`workflows`). Default: Shows index.
+
+### Flags
+-   **`--verbose`**: Show detailed descriptions and hidden flags.
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Lookup
+1.  **Index**: Check if target is a known Command, Agent, or Skill.
+2.  **Search**: If unknown, grep `.opencode/` documentation for keywords.
+
+### Phase 2: Formatting
+-   **Structure**: Group by Category (Workflow vs Skill).
+-   **Clarity**: Show "Quick Start" snippets.
+
+## 5. Output Guidelines (The Contract)
+
+### Help Document
+```markdown
+## Help: [Target]
+
+### Description
+[Brief summary]
+
+### Usage
+`[Command Pattern]`
+
+### Key Features
+-   Feature 1
+-   Feature 2
+
+### Related Commands
+-   `/related-command`
+```
+
+## 6. Examples
+
+### A. Command Help
+```bash
+/soc-help implement
+```
+*Effect:* Displays usage for `/soc-implement`, including flags like `--agent` and `--test`.
+
+### B. Agent Role
+```bash
+/soc-help backend
+```
+*Effect:* Shows the `backend` agent's persona, including "Prime Directives" and "Restrictions."
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Researcher**: `@[.opencode/agents/researcher.md]` - For finding unstructured help.
+
+### Skills
+-   **None**: This is a read-only command.
+
+### MCP Integration
+-   **`filesystem`**: Reading documentation files.
+
+## 8. Boundaries
+
+**Will:**
+-   Explain system capabilities.
+-   List available tools.
+-   Provide syntax examples.
+
+**Will Not:**
+-   **Execute Commands**: It only explains them.
+-   **Hallucinate Features**: Only lists what exists in `.opencode/`.

package/.opencode/commands/soc-implement.md

@@ -1,112 +1,112 @@
----
-description: Code implementation with best practices
----
-
-# /soc-implement
-
-## 1. Command Overview
-The `/soc-implement` command is the execution engine of the agent system. It transforms approved designs and specifications into production-ready code. It enforces strict quality control, testing (TDD), and "self-correction" loops via the `reflexion` skill. It does not plan; it executes.
-
-## 2. Triggers & Routing
-The command routes to specialized sub-agents based on the `--agent` flag or file context.
-
-| Trigger Scenario | Flag | Target Agent | Context Injected |
-| :--- | :--- | :--- | :--- |
-| **API/Database Logic** | `--agent backend` | `[backend]` | DB Schemas, Error Handling Middleware |
-| **UI/Components** | `--agent frontend` | `[frontend]` | Design System, A11y Rules, Hooks |
-| **Testing/QA** | `--agent quality` | `[quality]` | Test Runner Config, Coverage Reports |
-| **Refactoring** | `--agent fullstack` | `[backend]` + `[frontend]` | Cross-layer dependencies |
-
-## 3. Usage & Arguments
-```bash
-/soc-implement [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: The feature or file to implement (e.g., "Login Flow", "src/components/Button.tsx").
-
-### Flags
--   **`--agent [backend|frontend|quality]`**: **MANDATORY**. Specifies the executing persona.
--   **`--test`**: (Default: true) Run capabilities tests after implementation.
--   **`--document`**: (Default: true) Update associated documentation/comments.
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Pre-Flight (Confidence Check)
-1.  **Read**: Review existing code and referencing `design.md` or `requirements`.
-2.  **Verify**: Check for patterns (e.g., "How do existing controllers handle errors?").
-3.  **Gate**: If confidence < 80%, ask user/PM for clarification.
-
-### Phase 2: Execution (The Loop)
-1.  **Test**: Write the test case first (TDD) if applicable.
-2.  **Edit**: Apply changes using `replace_file_content` or `write_to_file`.
-3.  **Verify**: Run the project's build/test command.
-    *   *If Fail*: Trigger `reflexion` skill (Why did it fail? -> Fix -> Retry).
-    *   *Limit*: Max 3 retries before asking for help.
-
-### Phase 3: Post-Flight (Self Check)
--   Did I leave any `console.log`?
--   Are inputs sanitized?
--   Did I break the build?
-
-## 5. Output Guidelines (The Contract)
-
-### Standard Implementation Report
-```markdown
-## Implementation: [Feature Name]
-
-### 1. Changes Summary
--   **Created:** `src/features/auth/login.ts`
--   **Modified:** `src/components/navbar.tsx`
-
-### 2. Verification
--   ✅ **Build:** Passed
--   ✅ **Tests:** 3 new tests added, all passing.
--   ✅ **Lint:** 0 errors.
-
-### 3. Key Decisions
--   Used `zod` for validation to match existing patterns.
--   Extracted `useAuth` hook for reusability.
-```
-
-## 6. Examples
-
-### A. Backend Feature
-```bash
-/soc-implement "User Registration API" --agent backend
-```
-*Effect:* `backend` agent writes `POST /register`, adds `UserSchema` validation, inputs into Postgres, and returns a sanitized User DTO.
-
-### B. Frontend Component
-```bash
-/soc-implement "DarkMode Toggle" --agent frontend
-```
-*Effect:* `frontend` agent checks `tailwind.config.js`, creates a toggle component using `Radix UI` primitives (if installed) and handles local storage state.
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Backend**: `@[.opencode/agents/backend.md]`
--   **Frontend**: `@[.opencode/agents/frontend.md]`
--   **Quality**: `@[.opencode/agents/quality.md]` - For TDD and verification.
-
-### Skills
--   **Confidence Check**: `@[.opencode/skills/confidence-check/SKILL.md]` - MANDATORY step before starting.
--   **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Validation protocol after changes.
--   **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - If implementation hits errors.
-
-### MCP Integration
--   **`context7`**: For looking up exact syntax and library API usage to prevent hallucinations.
--   **`filesystem`**: For determining current project structure and patterns.
-
-## 8. Boundaries
-
-**Will:**
--   Write code modules, tests, and documentation.
--   Fix compilation errors it causes.
--   Respect existing linters and formatters.
-
-**Will Not:**
--   **Invent Designs**: If no design exists, it will fall back to simple best practices or ask for a design.
--   **Commit Violations**: Will not commit code with secrets or critical bugs.
--   **Touch Forbidden Files**: (e.g., `package-lock.json` manual edits, `.env` manual edits).
+---
+description: Code implementation with best practices
+---
+
+# /soc-implement
+
+## 1. Command Overview
+The `/soc-implement` command is the execution engine of the agent system. It transforms approved designs and specifications into production-ready code. It enforces strict quality control, testing (TDD), and "self-correction" loops via the `reflexion` skill. It does not plan; it executes.
+
+## 2. Triggers & Routing
+The command routes to specialized sub-agents based on the `--agent` flag or file context.
+
+| Trigger Scenario | Flag | Target Agent | Context Injected |
+| :--- | :--- | :--- | :--- |
+| **API/Database Logic** | `--agent backend` | `[backend]` | DB Schemas, Error Handling Middleware |
+| **UI/Components** | `--agent frontend` | `[frontend]` | Design System, A11y Rules, Hooks |
+| **Testing/QA** | `--agent quality` | `[quality]` | Test Runner Config, Coverage Reports |
+| **Refactoring** | `--agent fullstack` | `[backend]` + `[frontend]` | Cross-layer dependencies |
+
+## 3. Usage & Arguments
+```bash
+/soc-implement [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: The feature or file to implement (e.g., "Login Flow", "src/components/Button.tsx").
+
+### Flags
+-   **`--agent [backend|frontend|quality]`**: **MANDATORY**. Specifies the executing persona.
+-   **`--test`**: (Default: true) Run capabilities tests after implementation.
+-   **`--document`**: (Default: true) Update associated documentation/comments.
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Pre-Flight (Confidence Check)
+1.  **Read**: Review existing code and referencing `design.md` or `requirements`.
+2.  **Verify**: Check for patterns (e.g., "How do existing controllers handle errors?").
+3.  **Gate**: If confidence < 80%, ask user/PM for clarification.
+
+### Phase 2: Execution (The Loop)
+1.  **Test**: Write the test case first (TDD) if applicable.
+2.  **Edit**: Apply changes using `replace_file_content` or `write_to_file`.
+3.  **Verify**: Run the project's build/test command.
+    *   *If Fail*: Trigger `reflexion` skill (Why did it fail? -> Fix -> Retry).
+    *   *Limit*: Max 3 retries before asking for help.
+
+### Phase 3: Post-Flight (Self Check)
+-   Did I leave any `console.log`?
+-   Are inputs sanitized?
+-   Did I break the build?
+
+## 5. Output Guidelines (The Contract)
+
+### Standard Implementation Report
+```markdown
+## Implementation: [Feature Name]
+
+### 1. Changes Summary
+-   **Created:** `src/features/auth/login.ts`
+-   **Modified:** `src/components/navbar.tsx`
+
+### 2. Verification
+-   ✅ **Build:** Passed
+-   ✅ **Tests:** 3 new tests added, all passing.
+-   ✅ **Lint:** 0 errors.
+
+### 3. Key Decisions
+-   Used `zod` for validation to match existing patterns.
+-   Extracted `useAuth` hook for reusability.
+```
+
+## 6. Examples
+
+### A. Backend Feature
+```bash
+/soc-implement "User Registration API" --agent backend
+```
+*Effect:* `backend` agent writes `POST /register`, adds `UserSchema` validation, inputs into Postgres, and returns a sanitized User DTO.
+
+### B. Frontend Component
+```bash
+/soc-implement "DarkMode Toggle" --agent frontend
+```
+*Effect:* `frontend` agent checks `tailwind.config.js`, creates a toggle component using `Radix UI` primitives (if installed) and handles local storage state.
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Backend**: `@[.opencode/agents/backend.md]`
+-   **Frontend**: `@[.opencode/agents/frontend.md]`
+-   **Quality**: `@[.opencode/agents/quality.md]` - For TDD and verification.
+
+### Skills
+-   **Confidence Check**: `@[.opencode/skills/confidence-check/SKILL.md]` - MANDATORY step before starting.
+-   **Self Check**: `@[.opencode/skills/self-check/SKILL.md]` - Validation protocol after changes.
+-   **Debug Protocol**: `@[.opencode/skills/debug-protocol/SKILL.md]` - If implementation hits errors.
+
+### MCP Integration
+-   **`context7`**: For looking up exact syntax and library API usage to prevent hallucinations.
+-   **`filesystem`**: For determining current project structure and patterns.
+
+## 8. Boundaries
+
+**Will:**
+-   Write code modules, tests, and documentation.
+-   Fix compilation errors it causes.
+-   Respect existing linters and formatters.
+
+**Will Not:**
+-   **Invent Designs**: If no design exists, it will fall back to simple best practices or ask for a design.
+-   **Commit Violations**: Will not commit code with secrets or critical bugs.
+-   **Touch Forbidden Files**: (e.g., `package-lock.json` manual edits, `.env` manual edits).

package/.opencode/commands/soc-improve.md

@@ -1,105 +1,105 @@
----
-description: Code improvement and optimization
----
-
-# /soc-improve
-
-## 1. Command Overview
-The `/soc-improve` command is the "Optimizer." Unlike `implement` (which builds new things) or `cleanup` (which removes dead things), `improve` makes existing *working* code *better*. It focuses on performance, readability, security, and quality benchmarks.
-
-## 2. Triggers & Routing
-The command routes to specialized agents based on the `--focus` flag.
-
-| Trigger Scenario | Flag | Target Agent | Goal |
-| :--- | :--- | :--- | :--- |
-| **Performance** | `--focus perf` | `[architect]` | Reduce latency/memory |
-| **Code Quality** | `--focus quality` | `[quality]` | Refactor/Clean Clean |
-| **Security Hardening** | `--focus security` | `[security]` | Patch vulnerabilities |
-| **UX Polish** | `--focus ux` | `[frontend]` | A11y, animations |
-
-## 3. Usage & Arguments
-```bash
-/soc-improve [target] [flags]
-```
-
-### Arguments
--   **`[target]`**: File or component to optimize.
-
-### Flags
--   **`--focus [perf|quality|security|ux]`**: **MANDATORY**.
--   **`--metric [target]`**: Optional goal (e.g., `< 100ms`).
-
-## 4. Behavioral Flow (Orchestration)
-
-### Phase 1: Benchmark (The Baseline)
-1.  **Measure**: Analyze current state (LOC, Complexity, or approximate Perf).
-2.  **Identify**: Find bottlenecks or anti-patterns.
-
-### Phase 2: Plan (The Upgrade)
--   Propose specific refactors.
--   Estimate impact (e.g., "Replacing nested loop will reduce O(n^2) to O(n)").
-
-### Phase 3: Execute (The Refactor)
-1.  **Edit**: Apply changes safely.
-2.  **Verify**: Ensure tests still pass (Regression Check).
-3.  **Compare**: Show Before vs After stats.
-
-## 5. Output Guidelines (The Contract)
-
-### Improvement Report
-```markdown
-## Improvement: [Target]
-
-### Focus: [Focus Area]
-
-### Changes Applied
-1.  **Refactor**: Extracted `LargeComponent` into 3 sub-components.
-2.  **Performance**: Memoized calculation of expensive value.
-
-### Metrics
-| Metric | Before | After | Delta |
-| :--- | :--- | :--- | :--- |
-| **Complexity** | 15 | 8 | -47% |
-| **Lines** | 200 | 120 | -40% |
-
-### Verification
-✅ Tests Passed
-```
-
-## 6. Examples
-
-### A. Performance Tuning
-```bash
-/soc-improve src/utils/sort.ts --focus perf
-```
-*Effect:* Replaces bubble sort with quicksort or uses a native method.
-
-### B. Security Hardening
-```bash
-/soc-improve src/api/user.ts --focus security
-```
-*Effect:* Adds input validation (Zod) and rate limiting to an existing endpoint.
-
-## 7. Dependencies & Capabilities
-
-### Agents
--   **Architect**: `@[.opencode/agents/architect.md]` - Performance strategy.
--   **Quality**: `@[.opencode/agents/quality.md]` - Code structure.
--   **Security**: `@[.opencode/agents/security.md]` - Hardening.
-
-### Skills
--   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - Ensuring improvements don't break logic.
-
-### MCP Integration
--   **`context7`**: Checking for modern language features (e.g., utilizing new node.js APIs).
-
-## 8. Boundaries
-
-**Will:**
--   Refactor code structure.
--   Optimize algorithms.
--   Add comments/documentation.
-
-**Will Not:**
--   **Change Behavior**: The external API/output must remain identical (unless fixing a bug).
--   **Delete Features**: Use `/soc-cleanup` for removal.
+---
+description: Code improvement and optimization
+---
+
+# /soc-improve
+
+## 1. Command Overview
+The `/soc-improve` command is the "Optimizer." Unlike `implement` (which builds new things) or `cleanup` (which removes dead things), `improve` makes existing *working* code *better*. It focuses on performance, readability, security, and quality benchmarks.
+
+## 2. Triggers & Routing
+The command routes to specialized agents based on the `--focus` flag.
+
+| Trigger Scenario | Flag | Target Agent | Goal |
+| :--- | :--- | :--- | :--- |
+| **Performance** | `--focus perf` | `[architect]` | Reduce latency/memory |
+| **Code Quality** | `--focus quality` | `[quality]` | Refactor/Clean Clean |
+| **Security Hardening** | `--focus security` | `[security]` | Patch vulnerabilities |
+| **UX Polish** | `--focus ux` | `[frontend]` | A11y, animations |
+
+## 3. Usage & Arguments
+```bash
+/soc-improve [target] [flags]
+```
+
+### Arguments
+-   **`[target]`**: File or component to optimize.
+
+### Flags
+-   **`--focus [perf|quality|security|ux]`**: **MANDATORY**.
+-   **`--metric [target]`**: Optional goal (e.g., `< 100ms`).
+
+## 4. Behavioral Flow (Orchestration)
+
+### Phase 1: Benchmark (The Baseline)
+1.  **Measure**: Analyze current state (LOC, Complexity, or approximate Perf).
+2.  **Identify**: Find bottlenecks or anti-patterns.
+
+### Phase 2: Plan (The Upgrade)
+-   Propose specific refactors.
+-   Estimate impact (e.g., "Replacing nested loop will reduce O(n^2) to O(n)").
+
+### Phase 3: Execute (The Refactor)
+1.  **Edit**: Apply changes safely.
+2.  **Verify**: Ensure tests still pass (Regression Check).
+3.  **Compare**: Show Before vs After stats.
+
+## 5. Output Guidelines (The Contract)
+
+### Improvement Report
+```markdown
+## Improvement: [Target]
+
+### Focus: [Focus Area]
+
+### Changes Applied
+1.  **Refactor**: Extracted `LargeComponent` into 3 sub-components.
+2.  **Performance**: Memoized calculation of expensive value.
+
+### Metrics
+| Metric | Before | After | Delta |
+| :--- | :--- | :--- | :--- |
+| **Complexity** | 15 | 8 | -47% |
+| **Lines** | 200 | 120 | -40% |
+
+### Verification
+✅ Tests Passed
+```
+
+## 6. Examples
+
+### A. Performance Tuning
+```bash
+/soc-improve src/utils/sort.ts --focus perf
+```
+*Effect:* Replaces bubble sort with quicksort or uses a native method.
+
+### B. Security Hardening
+```bash
+/soc-improve src/api/user.ts --focus security
+```
+*Effect:* Adds input validation (Zod) and rate limiting to an existing endpoint.
+
+## 7. Dependencies & Capabilities
+
+### Agents
+-   **Architect**: `@[.opencode/agents/architect.md]` - Performance strategy.
+-   **Quality**: `@[.opencode/agents/quality.md]` - Code structure.
+-   **Security**: `@[.opencode/agents/security.md]` - Hardening.
+
+### Skills
+-   **Reflexion**: `@[.opencode/skills/reflexion/SKILL.md]` - Ensuring improvements don't break logic.
+
+### MCP Integration
+-   **`context7`**: Checking for modern language features (e.g., utilizing new node.js APIs).
+
+## 8. Boundaries
+
+**Will:**
+-   Refactor code structure.
+-   Optimize algorithms.
+-   Add comments/documentation.
+
+**Will Not:**
+-   **Change Behavior**: The external API/output must remain identical (unless fixing a bug).
+-   **Delete Features**: Use `/soc-cleanup` for removal.