opencode-matrixx 0.0.1

package/dist/features/builtin-commands/templates/refactor.d.ts

@@ -0,0 +1 @@
+export declare const REFACTOR_TEMPLATE = "# Intelligent Refactor Command\n\n## Usage\n```\n/refactor <refactoring-target> [--scope=<file|module|project>] [--strategy=<safe|aggressive>]\n\nArguments:\n  refactoring-target: What to refactor. Can be:\n    - File path: src/auth/handler.ts\n    - Symbol name: \"AuthService class\"\n    - Pattern: \"all functions using deprecated API\"\n    - Description: \"extract validation logic into separate module\"\n\nOptions:\n  --scope: Refactoring scope (default: module)\n    - file: Single file only\n    - module: Module/directory scope\n    - project: Entire codebase\n\n  --strategy: Risk tolerance (default: safe)\n    - safe: Conservative, maximum test coverage required\n    - aggressive: Allow broader changes with adequate coverage\n```\n\n## What This Command Does\n\nPerforms intelligent, deterministic refactoring with full codebase awareness. Unlike blind search-and-replace, this command:\n\n1. **Understands your intent** - Analyzes what you actually want to achieve\n2. **Maps the codebase** - Builds a definitive codemap before touching anything\n3. **Assesses risk** - Evaluates test coverage and determines verification strategy\n4. **Plans meticulously** - Creates a detailed plan with Plan agent\n5. **Executes precisely** - Step-by-step refactoring with LSP and AST-grep\n6. **Verifies constantly** - Runs tests after each change to ensure zero regression\n\n---\n\n# PHASE 0: INTENT GATE (MANDATORY FIRST STEP)\n\n**BEFORE ANY ACTION, classify and validate the request.**\n\n## Step 0.1: Parse Request Type\n\n| Signal | Classification | Action |\n|--------|----------------|--------|\n| Specific file/symbol | Explicit | Proceed to codebase analysis |\n| \"Refactor X to Y\" | Clear transformation | Proceed to codebase analysis |\n| \"Improve\", \"Clean up\" | Open-ended | **MUST ask**: \"What specific improvement?\" |\n| Ambiguous scope | Uncertain | **MUST ask**: \"Which modules/files?\" |\n| Missing context | Incomplete | **MUST ask**: \"What's the desired outcome?\" |\n\n## Step 0.2: Validate Understanding\n\nBefore proceeding, confirm:\n- [ ] Target is clearly identified\n- [ ] Desired outcome is understood\n- [ ] Scope is defined (file/module/project)\n- [ ] Success criteria can be articulated\n\n**If ANY of above is unclear, ASK CLARIFYING QUESTION:**\n\n```\nI want to make sure I understand the refactoring goal correctly.\n\n**What I understood**: [interpretation]\n**What I'm unsure about**: [specific ambiguity]\n\nOptions I see:\n1. [Option A] - [implications]\n2. [Option B] - [implications]\n\n**My recommendation**: [suggestion with reasoning]\n\nShould I proceed with [recommendation], or would you prefer differently?\n```\n\n## Step 0.3: Create Initial Todos\n\n**IMMEDIATELY after understanding the request, create todos:**\n\n```\nTodoWrite([\n  {\"id\": \"phase-1\", \"content\": \"PHASE 1: Codebase Analysis - launch parallel explore agents\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-2\", \"content\": \"PHASE 2: Build Codemap - map dependencies and impact zones\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-3\", \"content\": \"PHASE 3: Test Assessment - analyze test coverage and verification strategy\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-4\", \"content\": \"PHASE 4: Plan Generation - invoke Plan agent for detailed refactoring plan\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-5\", \"content\": \"PHASE 5: Execute Refactoring - step-by-step with continuous verification\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-6\", \"content\": \"PHASE 6: Final Verification - full test suite and regression check\", \"status\": \"pending\", \"priority\": \"high\"}\n])\n```\n\n---\n\n# PHASE 1: CODEBASE ANALYSIS (PARALLEL EXPLORATION)\n\n**Mark phase-1 as in_progress.**\n\n## 1.1: Launch Parallel Explore Agents (BACKGROUND)\n\nFire ALL of these simultaneously using `call_omo_agent`:\n\n```\n// Agent 1: Find the refactoring target\ncall_omo_agent(\n  subagent_type=\"trinity\",\n  run_in_background=true,\n  prompt=\"Find all occurrences and definitions of [TARGET]. \n  Report: file paths, line numbers, usage patterns.\"\n)\n\n// Agent 2: Find related code\ncall_omo_agent(\n  subagent_type=\"trinity\", \n  run_in_background=true,\n  prompt=\"Find all code that imports, uses, or depends on [TARGET].\n  Report: dependency chains, import graphs.\"\n)\n\n// Agent 3: Find similar patterns\ncall_omo_agent(\n  subagent_type=\"trinity\",\n  run_in_background=true,\n  prompt=\"Find similar code patterns to [TARGET] in the codebase.\n  Report: analogous implementations, established conventions.\"\n)\n\n// Agent 4: Find tests\ncall_omo_agent(\n  subagent_type=\"trinity\",\n  run_in_background=true,\n  prompt=\"Find all test files related to [TARGET].\n  Report: test file paths, test case names, coverage indicators.\"\n)\n\n// Agent 5: Architecture context\ncall_omo_agent(\n  subagent_type=\"trinity\",\n  run_in_background=true,\n  prompt=\"Find architectural patterns and module organization around [TARGET].\n  Report: module boundaries, layer structure, design patterns in use.\"\n)\n```\n\n## 1.2: Direct Tool Exploration (WHILE AGENTS RUN)\n\nWhile background agents are running, use direct tools:\n\n### LSP Tools for Precise Analysis:\n\n```typescript\n// Find definition(s)\nLspGotoDefinition(filePath, line, character)  // Where is it defined?\n\n// Find ALL usages across workspace\nLspFindReferences(filePath, line, character, includeDeclaration=true)\n\n// Get file structure\nLspDocumentSymbols(filePath)  // Hierarchical outline\nLspWorkspaceSymbols(filePath, query=\"[target_symbol]\")  // Search by name\n\n// Get current diagnostics\nlsp_diagnostics(filePath)  // Errors, warnings before we start\n```\n\n### AST-Grep for Pattern Analysis:\n\n```typescript\n// Find structural patterns\nast_grep_search(\n  pattern=\"function $NAME($$$) { $$$ }\",  // or relevant pattern\n  lang=\"typescript\",  // or relevant language\n  paths=[\"src/\"]\n)\n\n// Preview refactoring (DRY RUN)\nast_grep_replace(\n  pattern=\"[old_pattern]\",\n  rewrite=\"[new_pattern]\",\n  lang=\"[language]\",\n  dryRun=true  // ALWAYS preview first\n)\n```\n\n### Grep for Text Patterns:\n\n```\ngrep(pattern=\"[search_term]\", path=\"src/\", include=\"*.ts\")\n```\n\n## 1.3: Collect Background Results\n\n```\nbackground_output(task_id=\"[agent_1_id]\")\nbackground_output(task_id=\"[agent_2_id]\")\n...\n```\n\n**Mark phase-1 as completed after all results collected.**\n\n---\n\n# PHASE 2: BUILD CODEMAP (DEPENDENCY MAPPING)\n\n**Mark phase-2 as in_progress.**\n\n## 2.1: Construct Definitive Codemap\n\nBased on Phase 1 results, build:\n\n```\n## CODEMAP: [TARGET]\n\n### Core Files (Direct Impact)\n- `path/to/file.ts:L10-L50` - Primary definition\n- `path/to/file2.ts:L25` - Key usage\n\n### Dependency Graph\n```\n[TARGET] \n\u251C\u2500\u2500 imports from: \n\u2502   \u251C\u2500\u2500 module-a (types)\n\u2502   \u2514\u2500\u2500 module-b (utils)\n\u251C\u2500\u2500 imported by:\n\u2502   \u251C\u2500\u2500 consumer-1.ts\n\u2502   \u251C\u2500\u2500 consumer-2.ts\n\u2502   \u2514\u2500\u2500 consumer-3.ts\n\u2514\u2500\u2500 used by:\n    \u251C\u2500\u2500 handler.ts (direct call)\n    \u2514\u2500\u2500 service.ts (dependency injection)\n```\n\n### Impact Zones\n| Zone | Risk Level | Files Affected | Test Coverage |\n|------|------------|----------------|---------------|\n| Core | HIGH | 3 files | 85% covered |\n| Consumers | MEDIUM | 8 files | 70% covered |\n| Edge | LOW | 2 files | 50% covered |\n\n### Established Patterns\n- Pattern A: [description] - used in N places\n- Pattern B: [description] - established convention\n```\n\n## 2.2: Identify Refactoring Constraints\n\nBased on codemap:\n- **MUST follow**: [existing patterns identified]\n- **MUST NOT break**: [critical dependencies]\n- **Safe to change**: [isolated code zones]\n- **Requires migration**: [breaking changes impact]\n\n**Mark phase-2 as completed.**\n\n---\n\n# PHASE 3: TEST ASSESSMENT (VERIFICATION STRATEGY)\n\n**Mark phase-3 as in_progress.**\n\n## 3.1: Detect Test Infrastructure\n\n```bash\n# Check for test commands\ncat package.json | jq '.scripts | keys[] | select(test(\"test\"))'\n\n# Or for Python\nls -la pytest.ini pyproject.toml setup.cfg\n\n# Or for Go\nls -la *_test.go\n```\n\n## 3.2: Analyze Test Coverage\n\n```\n// Find all tests related to target\ncall_omo_agent(\n  subagent_type=\"trinity\",\n  run_in_background=false,  // Need this synchronously\n  prompt=\"Analyze test coverage for [TARGET]:\n  1. Which test files cover this code?\n  2. What test cases exist?\n  3. Are there integration tests?\n  4. What edge cases are tested?\n  5. Estimated coverage percentage?\"\n)\n```\n\n## 3.3: Determine Verification Strategy\n\nBased on test analysis:\n\n| Coverage Level | Strategy |\n|----------------|----------|\n| HIGH (>80%) | Run existing tests after each step |\n| MEDIUM (50-80%) | Run tests + add safety assertions |\n| LOW (<50%) | **PAUSE**: Propose adding tests first |\n| NONE | **BLOCK**: Refuse aggressive refactoring |\n\n**If coverage is LOW or NONE, ask user:**\n\n```\nTest coverage for [TARGET] is [LEVEL].\n\n**Risk Assessment**: Refactoring without adequate tests is dangerous.\n\nOptions:\n1. Add tests first, then refactor (RECOMMENDED)\n2. Proceed with extra caution, manual verification required\n3. Abort refactoring\n\nWhich approach do you prefer?\n```\n\n## 3.4: Document Verification Plan\n\n```\n## VERIFICATION PLAN\n\n### Test Commands\n- Unit: `bun test` / `npm test` / `pytest` / etc.\n- Integration: [command if exists]\n- Type check: `tsc --noEmit` / `pyright` / etc.\n\n### Verification Checkpoints\nAfter each refactoring step:\n1. lsp_diagnostics \u2192 zero new errors\n2. Run test command \u2192 all pass\n3. Type check \u2192 clean\n\n### Regression Indicators\n- [Specific test that must pass]\n- [Behavior that must be preserved]\n- [API contract that must not change]\n```\n\n**Mark phase-3 as completed.**\n\n---\n\n# PHASE 4: PLAN GENERATION (PLAN AGENT)\n\n**Mark phase-4 as in_progress.**\n\n## 4.1: Invoke Plan Agent\n\n```\nTask(\n  subagent_type=\"plan\",\n  prompt=\"Create a detailed refactoring plan:\n\n  ## Refactoring Goal\n  [User's original request]\n\n  ## Codemap (from Phase 2)\n  [Insert codemap here]\n\n  ## Test Coverage (from Phase 3)\n  [Insert verification plan here]\n\n  ## Constraints\n  - MUST follow existing patterns: [list]\n  - MUST NOT break: [critical paths]\n  - MUST run tests after each step\n\n  ## Requirements\n  1. Break down into atomic refactoring steps\n  2. Each step must be independently verifiable\n  3. Order steps by dependency (what must happen first)\n  4. Specify exact files and line ranges for each step\n  5. Include rollback strategy for each step\n  6. Define commit checkpoints\"\n)\n```\n\n## 4.2: Review and Validate Plan\n\nAfter receiving plan from Plan agent:\n\n1. **Verify completeness**: All identified files addressed?\n2. **Verify safety**: Each step reversible?\n3. **Verify order**: Dependencies respected?\n4. **Verify verification**: Test commands specified?\n\n## 4.3: Register Detailed Todos\n\nConvert Plan agent output into granular todos:\n\n```\nTodoWrite([\n  // Each step from the plan becomes a todo\n  {\"id\": \"refactor-1\", \"content\": \"Step 1: [description]\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"verify-1\", \"content\": \"Verify Step 1: run tests\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"refactor-2\", \"content\": \"Step 2: [description]\", \"status\": \"pending\", \"priority\": \"medium\"},\n  {\"id\": \"verify-2\", \"content\": \"Verify Step 2: run tests\", \"status\": \"pending\", \"priority\": \"medium\"},\n  // ... continue for all steps\n])\n```\n\n**Mark phase-4 as completed.**\n\n---\n\n# PHASE 5: EXECUTE REFACTORING (DETERMINISTIC EXECUTION)\n\n**Mark phase-5 as in_progress.**\n\n## 5.1: Execution Protocol\n\nFor EACH refactoring step:\n\n### Pre-Step\n1. Mark step todo as `in_progress`\n2. Read current file state\n3. Verify lsp_diagnostics is baseline\n\n### Execute Step\nUse appropriate tool:\n\n**For Symbol Renames:**\n```typescript\nlsp_prepare_rename(filePath, line, character)  // Validate rename is possible\nlsp_rename(filePath, line, character, newName)  // Execute rename\n```\n\n**For Pattern Transformations:**\n```typescript\n// Preview first\nast_grep_replace(pattern, rewrite, lang, dryRun=true)\n\n// If preview looks good, execute\nast_grep_replace(pattern, rewrite, lang, dryRun=false)\n```\n\n**For Structural Changes:**\n```typescript\n// Use Edit tool for precise changes\nedit(filePath, oldString, newString)\n```\n\n### Post-Step Verification (MANDATORY)\n\n```typescript\n// 1. Check diagnostics\nlsp_diagnostics(filePath)  // Must be clean or same as baseline\n\n// 2. Run tests\nbash(\"bun test\")  // Or appropriate test command\n\n// 3. Type check\nbash(\"tsc --noEmit\")  // Or appropriate type check\n```\n\n### Step Completion\n1. If verification passes \u2192 Mark step todo as `completed`\n2. If verification fails \u2192 **STOP AND FIX**\n\n## 5.2: Failure Recovery Protocol\n\nIf ANY verification fails:\n\n1. **STOP** immediately\n2. **REVERT** the failed change\n3. **DIAGNOSE** what went wrong\n4. **OPTIONS**:\n   - Fix the issue and retry\n   - Skip this step (if optional)\n   - Consult oracle agent for help\n   - Ask user for guidance\n\n**NEVER proceed to next step with broken tests.**\n\n## 5.3: Commit Checkpoints\n\nAfter each logical group of changes:\n\n```bash\ngit add [changed-files]\ngit commit -m \"refactor(scope): description\n\n[details of what was changed and why]\"\n```\n\n**Mark phase-5 as completed when all refactoring steps done.**\n\n---\n\n# PHASE 6: FINAL VERIFICATION (REGRESSION CHECK)\n\n**Mark phase-6 as in_progress.**\n\n## 6.1: Full Test Suite\n\n```bash\n# Run complete test suite\nbun test  # or npm test, pytest, go test, etc.\n```\n\n## 6.2: Type Check\n\n```bash\n# Full type check\ntsc --noEmit  # or equivalent\n```\n\n## 6.3: Lint Check\n\n```bash\n# Run linter\neslint .  # or equivalent\n```\n\n## 6.4: Build Verification (if applicable)\n\n```bash\n# Ensure build still works\nbun run build  # or npm run build, etc.\n```\n\n## 6.5: Final Diagnostics\n\n```typescript\n// Check all changed files\nfor (file of changedFiles) {\n  lsp_diagnostics(file)  // Must all be clean\n}\n```\n\n## 6.6: Generate Summary\n\n```markdown\n## Refactoring Complete\n\n### What Changed\n- [List of changes made]\n\n### Files Modified\n- `path/to/file.ts` - [what changed]\n- `path/to/file2.ts` - [what changed]\n\n### Verification Results\n- Tests: PASSED (X/Y passing)\n- Type Check: CLEAN\n- Lint: CLEAN\n- Build: SUCCESS\n\n### No Regressions Detected\nAll existing tests pass. No new errors introduced.\n```\n\n**Mark phase-6 as completed.**\n\n---\n\n# CRITICAL RULES\n\n## NEVER DO\n- Skip lsp_diagnostics check after changes\n- Proceed with failing tests\n- Make changes without understanding impact\n- Use `as any`, `@ts-ignore`, `@ts-expect-error`\n- Delete tests to make them pass\n- Commit broken code\n- Refactor without understanding existing patterns\n\n## ALWAYS DO\n- Understand before changing\n- Preview before applying (ast_grep dryRun=true)\n- Verify after every change\n- Follow existing codebase patterns\n- Keep todos updated in real-time\n- Commit at logical checkpoints\n- Report issues immediately\n\n## ABORT CONDITIONS\nIf any of these occur, **STOP and consult user**:\n- Test coverage is zero for target code\n- Changes would break public API\n- Refactoring scope is unclear\n- 3 consecutive verification failures\n- User-defined constraints violated\n\n---\n\n# Tool Usage Philosophy\n\nYou already know these tools. Use them intelligently:\n\n## LSP Tools\nLeverage LSP tools for precision analysis. Key patterns:\n- **Understand before changing**: `LspGotoDefinition` to grasp context\n- **Impact analysis**: `LspFindReferences` to map all usages before modification\n- **Safe refactoring**: `lsp_prepare_rename` \u2192 `lsp_rename` for symbol renames\n- **Continuous verification**: `lsp_diagnostics` after every change\n\n## AST-Grep\nUse `ast_grep_search` and `ast_grep_replace` for structural transformations.\n**Critical**: Always `dryRun=true` first, review, then execute.\n\n## Agents\n- `explore`: Parallel codebase pattern discovery\n- `plan`: Detailed refactoring plan generation\n- `oracle`: Read-only consultation for complex architectural decisions and debugging\n- `librarian`: **Use proactively** when encountering deprecated methods or library migration tasks. Query official docs and OSS examples for modern replacements.\n\n## Deprecated Code & Library Migration\nWhen you encounter deprecated methods/APIs during refactoring:\n1. Fire `librarian` to find the recommended modern alternative\n2. **DO NOT auto-upgrade to latest version** unless user explicitly requests migration\n3. If user requests library migration, use `librarian` to fetch latest API docs before making changes\n\n---\n\n**Remember: Refactoring without tests is reckless. Refactoring without understanding is destructive. This command ensures you do neither.**\n\n<user-request>\n$ARGUMENTS\n</user-request>\n";

package/dist/features/builtin-commands/templates/remove-deadcode.d.ts

@@ -0,0 +1 @@
+export declare const REMOVE_DEADCODE_TEMPLATE = "# Remove Dead Code Command\n\n## Usage\n```\n/remove-deadcode [target-path] [--scope=<file|module|project>] [--dry-run]\n\nArguments:\n  target-path: Where to scan for dead code. Can be:\n    - File path: src/auth/handler.ts\n    - Directory: src/features/\n    - Glob: src/**/*.ts\n    - Omitted: defaults to current project src/\n\nOptions:\n  --scope: Scanning scope (default: module)\n    - file: Single file only\n    - module: Module/directory and its dependents\n    - project: Entire codebase\n\n  --dry-run: Report dead code without removing it (default: false)\n```\n\n## What This Command Does\n\nFinds and removes dead code (zero-reference symbols) using LSP analysis. Unlike grep-based approaches, this uses semantic understanding:\n\n1. **Discovers symbols** - Uses LSP to enumerate all exported and internal symbols\n2. **Counts references** - Uses LspFindReferences to find actual usage sites\n3. **Classifies confidence** - Categorizes findings by removal safety\n4. **Reports findings** - Presents dead code organized by confidence level\n5. **Removes safely** - Deletes confirmed dead code with continuous verification\n6. **Verifies integrity** - Runs build and tests after each removal batch\n\n---\n\n# PHASE 0: VALIDATE REQUEST (MANDATORY FIRST STEP)\n\n## Step 0.1: Parse Target\n\n| Input | Interpretation |\n|-------|---------------|\n| File path | Scan that file only |\n| Directory path | Scan all source files in directory |\n| Glob pattern | Scan matching files |\n| No argument | Scan project src/ directory |\n\n## Step 0.2: Detect --dry-run Flag\n\nIf --dry-run is present or user says \"just show me\" / \"report only\":\n- Set dry-run mode: report findings WITHOUT removing anything\n- Skip PHASE 4 (removal) entirely\n\n## Step 0.3: Create Initial Todos\n\n```\nTodoWrite([\n  {\"content\": \"PHASE 1: Symbol Discovery - enumerate all symbols via LSP\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"content\": \"PHASE 2: Reference Analysis - find references for each symbol\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"content\": \"PHASE 3: Dead Code Report - classify and present findings\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"content\": \"PHASE 4: Safe Removal - remove confirmed dead code with verification\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"content\": \"PHASE 5: Final Verification - build and test suite\", \"status\": \"pending\", \"priority\": \"high\"}\n])\n```\n\n---\n\n# PHASE 1: SYMBOL DISCOVERY\n\n**Mark PHASE 1 as in_progress.**\n\n## 1.1: Enumerate Source Files\n\nDetermine the set of files to scan based on target:\n\n```typescript\n// For a single file\nLspDocumentSymbols(filePath)\n\n// For a directory, use Glob to find all source files first\nGlob(pattern=\"**/*.ts\", path=\"[target-directory]\")\n// Then LspDocumentSymbols for each file\n```\n\n## 1.2: Collect All Symbols\n\nFor each source file, gather:\n- Function declarations (named functions, arrow functions assigned to const)\n- Class declarations\n- Interface and type alias declarations\n- Enum declarations\n- Variable declarations (const/let at module scope)\n- Method declarations (within classes)\n\nUse `LspDocumentSymbols(filePath)` to get the hierarchical symbol outline.\n\n## 1.3: Filter Symbol Candidates\n\n**SKIP these symbols (never flag as dead):**\n- Symbols in index.ts / barrel files (re-exports)\n- Symbols with `export default`\n- Entry point files (main, index, plugin entry)\n- Test files (`*.test.ts`, `*.spec.ts`)\n- Symbols starting with `_` (conventionally private/internal)\n- Type-only exports used in declaration files\n\n**INCLUDE these symbols:**\n- Non-exported functions/classes/types within a module\n- Exported symbols that may have zero consumers\n- Private class methods and properties\n\n**Mark PHASE 1 as completed.**\n\n---\n\n# PHASE 2: REFERENCE ANALYSIS\n\n**Mark PHASE 2 as in_progress.**\n\n## 2.1: Count References Per Symbol\n\nFor each symbol candidate from Phase 1:\n\n```typescript\n// Get all references across the workspace\nLspFindReferences(filePath, line, character, includeDeclaration=false)\n```\n\n**IMPORTANT**: Set `includeDeclaration=false` so the declaration site itself is NOT counted as a reference.\n\n## 2.2: Classify Reference Counts\n\n| References | Classification | Confidence |\n|------------|---------------|------------|\n| 0 external references | Dead code | HIGH - safe to remove |\n| 0 refs, but exported from package index | Possibly dead | MEDIUM - may be used externally |\n| 0 refs, but in a public API file | Possibly dead | LOW - may be part of public contract |\n| 1+ references | Live code | SKIP - do not flag |\n\n## 2.3: Cross-Check with AST-Grep\n\nFor HIGH confidence candidates, verify with AST-Grep to catch dynamic references:\n\n```typescript\n// Check for string-based references (dynamic imports, reflection)\nast_grep_search(\n  pattern='\"[symbol-name]\"',\n  lang=\"typescript\",\n  paths=[\"src/\"]\n)\n\n// Check for computed property access\ngrep(pattern=\"[symbol-name]\", path=\"src/\", include=\"*.ts\")\n```\n\nIf AST-Grep or grep finds string-based references, downgrade confidence from HIGH to MEDIUM.\n\n**Mark PHASE 2 as completed.**\n\n---\n\n# PHASE 3: DEAD CODE REPORT\n\n**Mark PHASE 3 as in_progress.**\n\n## 3.1: Generate Report\n\nPresent findings organized by confidence:\n\n```\n## Dead Code Analysis Report\n\n### Scan Target: [path]\n### Files Scanned: [N]\n### Symbols Analyzed: [N]\n### Dead Code Found: [N] symbols\n\n---\n\n### HIGH Confidence (Safe to Remove)\nThese symbols have zero references anywhere in the codebase.\n\n| # | Symbol | File | Line | Type |\n|---|--------|------|------|------|\n| 1 | unusedHelper | src/utils/helpers.ts | 42 | function |\n| 2 | OldConfig | src/config/legacy.ts | 15 | interface |\n\n### MEDIUM Confidence (Review Required)\nThese symbols appear unused but may have external consumers or dynamic references.\n\n| # | Symbol | File | Line | Type | Reason |\n|---|--------|------|------|------|--------|\n| 1 | exportedUtil | src/shared/utils.ts | 88 | function | exported, no internal refs |\n\n### LOW Confidence (Manual Review)\nThese symbols may be part of a public API or have indirect usage patterns.\n\n| # | Symbol | File | Line | Type | Reason |\n|---|--------|------|------|------|--------|\n| 1 | ApiResponse | src/types/api.ts | 12 | type | public API type |\n```\n\n## 3.2: If --dry-run Mode\n\nPresent the report and STOP. Do not proceed to Phase 4.\n\n```\nThis was a dry-run analysis. No code was modified.\nTo remove dead code, run: /remove-deadcode [same-target]\n```\n\n**Mark PHASE 3 as completed.**\n\n---\n\n# PHASE 4: SAFE REMOVAL\n\n**Mark PHASE 4 as in_progress.**\n\n## 4.1: Removal Strategy\n\n**Remove in order of confidence (HIGH first):**\n\n1. Start with HIGH confidence symbols\n2. After each batch, run verification\n3. Only proceed to MEDIUM confidence if user approves\n4. NEVER auto-remove LOW confidence symbols\n\n## 4.2: Batch Removal Protocol\n\nFor each removal batch:\n\n### Pre-Removal\n1. Read the file to get current state\n2. Run `lsp_diagnostics(filePath)` to establish baseline\n\n### Execute Removal\n```typescript\n// Use Edit tool to remove the dead symbol\n// Remove the entire declaration including JSDoc/comments above it\nedit(filePath, oldString=\"[full-symbol-declaration]\", newString=\"\")\n```\n\n### Post-Removal Verification (MANDATORY)\n```typescript\n// 1. Check diagnostics - no new errors\nlsp_diagnostics(filePath)\n\n// 2. Check imports - remove now-unused imports\n// If removing a symbol makes an import unused, remove the import too\nLspDocumentSymbols(filePath)\n\n// 3. Run type check\nbash(\"tsc --noEmit\")\n\n// 4. Run tests\nbash(\"bun test\")\n```\n\n## 4.3: Cascading Cleanup\n\nAfter removing a symbol, check if its removal creates new dead code:\n- Imports that are now unused\n- Helper functions only called by the removed symbol\n- Types only used by the removed symbol\n\nRemove cascading dead code in the same batch.\n\n## 4.4: MEDIUM Confidence Handling\n\nBefore removing MEDIUM confidence symbols, ask the user:\n\n```\nThe following MEDIUM confidence symbols appear unused but may have external consumers:\n\n1. [symbol] in [file] - [reason for medium confidence]\n\nShould I:\n1. Remove them (I confirm they are unused)\n2. Skip them (keep for now)\n3. Review each one individually\n```\n\n**Mark PHASE 4 as completed.**\n\n---\n\n# PHASE 5: FINAL VERIFICATION\n\n**Mark PHASE 5 as in_progress.**\n\n## 5.1: Full Build Check\n\n```bash\ntsc --noEmit\nbun run build\n```\n\n## 5.2: Full Test Suite\n\n```bash\nbun test\n```\n\n## 5.3: Diagnostics on Changed Files\n\n```typescript\n// Check all files that were modified\nfor (file of modifiedFiles) {\n  lsp_diagnostics(file)\n}\n```\n\n## 5.4: Generate Summary\n\n```\n## Dead Code Removal Complete\n\n### Removed\n- [N] HIGH confidence symbols removed\n- [N] MEDIUM confidence symbols removed (user-approved)\n- [N] cascading cleanups (unused imports, helper functions)\n\n### Preserved\n- [N] LOW confidence symbols (manual review needed)\n- [N] MEDIUM confidence symbols (user chose to keep)\n\n### Files Modified\n- \\`path/to/file.ts\\` - removed [symbol1], [symbol2]\n- \\`path/to/file2.ts\\` - removed [symbol3]\n\n### Verification\n- Type Check: PASSED\n- Build: PASSED\n- Tests: PASSED ([X] passing, [Y] pre-existing failures)\n- Diagnostics: CLEAN (no new errors)\n\n### Lines of Code Removed: [N]\n```\n\n**Mark PHASE 5 as completed.**\n\n---\n\n# CRITICAL RULES\n\n## NEVER DO\n- Remove symbols from barrel/index files without checking all consumers\n- Remove exported symbols without checking external package consumers\n- Remove symbols referenced in configuration files, scripts, or non-TS files\n- Skip lsp_diagnostics after removal\n- Proceed with failing tests after removal\n- Remove event handlers, lifecycle hooks, or decorator-referenced symbols\n- Remove symbols used in dependency injection containers\n- Use `as any`, `@ts-ignore`, `@ts-expect-error` to suppress removal side effects\n\n## ALWAYS DO\n- Use LspFindReferences (not grep) as the primary reference detection method\n- Cross-check with grep/AST-Grep for dynamic references\n- Verify build and tests after each removal batch\n- Ask for user confirmation before removing MEDIUM confidence symbols\n- Report LOW confidence findings without auto-removing\n- Clean up cascading dead code (unused imports, orphaned helpers)\n- Keep todos updated in real-time\n\n## ABORT CONDITIONS\nIf any of these occur, STOP and consult user:\n- Build fails after removal\n- Tests fail after removal (new failures, not pre-existing)\n- More than 20 symbols flagged as dead in a single file (likely misconfiguration)\n- Removed symbol is referenced in non-TypeScript files (configs, scripts)\n\n<user-request>\n$ARGUMENTS\n</user-request>\n";

package/dist/features/builtin-commands/templates/start-work.d.ts

@@ -0,0 +1 @@
+export declare const START_WORK_TEMPLATE = "You are starting a Morpheus work session.\n\n## WHAT TO DO\n\n1. **Find available plans**: Search for Oracle-generated plan files at `.matrix/plans/`\n\n2. **Check for active mission state**: Read `.matrix/mission.json` if it exists\n\n3. **Decision logic**:\n   - If `.matrix/mission.json` exists AND plan is NOT complete (has unchecked boxes):\n     - **APPEND** current session to session_ids\n     - Continue work on existing plan\n   - If no active plan OR plan is complete:\n     - List available plan files\n     - If ONE plan: auto-select it\n     - If MULTIPLE plans: show list with timestamps, ask user to select\n\n4. **Create/Update mission.json**:\n   ```json\n   {\n     \"active_plan\": \"/absolute/path/to/plan.md\",\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"session_ids\": [\"session_id_1\", \"session_id_2\"],\n     \"plan_name\": \"plan-name\"\n   }\n   ```\n\n5. **Read the plan file** and start executing tasks according to atlas workflow\n\n## OUTPUT FORMAT\n\nWhen listing plans for selection:\n```\nAvailable Work Plans\n\nCurrent Time: {ISO timestamp}\nSession ID: {current session id}\n\n1. [plan-name-1.md] - Modified: {date} - Progress: 3/10 tasks\n2. [plan-name-2.md] - Modified: {date} - Progress: 0/5 tasks\n\nWhich plan would you like to work on? (Enter number or plan name)\n```\n\nWhen resuming existing work:\n```\nResuming Work Session\n\nActive Plan: {plan-name}\nProgress: {completed}/{total} tasks\nSessions: {count} (appending current session)\n\nReading plan and continuing from last incomplete task...\n```\n\nWhen auto-selecting single plan:\n```\nStarting Work Session\n\nPlan: {plan-name}\nSession ID: {session_id}\nStarted: {timestamp}\n\nReading plan and beginning execution...\n```\n\n## CRITICAL\n\n- The session_id is injected by the hook - use it directly\n- Always update mission.json BEFORE starting work\n- Read the FULL plan file before delegating any tasks\n- Follow atlas delegation protocols (7-section format)";

package/dist/features/builtin-commands/templates/stop-continuation.d.ts

@@ -0,0 +1 @@
+export declare const STOP_CONTINUATION_TEMPLATE = "Stop all continuation mechanisms for the current session.\n\nThis command will:\n1. Stop the todo-continuation-enforcer from automatically continuing incomplete tasks\n2. Cancel any active Matrix Loop\n3. Clear the mission state for the current project\n\nAfter running this command:\n- The session will not auto-continue when idle\n- You can manually continue work when ready\n- The stop state is per-session and clears when the session ends\n\nUse this when you need to pause automated continuation and take manual control.";

package/dist/features/builtin-commands/types.d.ts

@@ -0,0 +1,6 @@
+import type { CommandDefinition } from "../claude-code-command-loader";
+export type BuiltinCommandName = "init-deep" | "matrix-loop" | "cancel-loop" | "ulw-loop" | "refactor" | "start-work" | "stop-continuation" | "handoff" | "pickup" | "remove-deadcode";
+export interface BuiltinCommandConfig {
+    disabled_commands?: BuiltinCommandName[];
+}
+export type BuiltinCommands = Record<string, CommandDefinition>;

package/dist/features/builtin-skills/index.d.ts

@@ -0,0 +1,2 @@
+export * from "./types";
+export { createBuiltinSkills, type CreateBuiltinSkillsOptions } from "./skills";

package/dist/features/builtin-skills/skills/academic-review.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const ACADEMIC_REVIEW_SKILL_NAME = "academic-review";
+export declare const ACADEMIC_REVIEW_SKILL_DESCRIPTION = "Academic paper review expertise: IMRaD analysis, review criteria, common weakness detection, structured review output, major vs minor revisions, conference vs journal conventions, and constructive feedback guidelines. Triggers: 'paper review', 'manuscript', 'peer review', 'academic review', 'journal submission'.";
+export declare const academicReviewSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/academic-writing.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const ACADEMIC_WRITING_SKILL_NAME = "academic-writing";
+export declare const ACADEMIC_WRITING_SKILL_DESCRIPTION = "Academic paper writing for journals and conferences: IMRaD structure, abstract crafting, argumentation flow, citation practices, venue-specific formatting (IEEE/ACM/Springer/Elsevier), camera-ready preparation, cover letters, rebuttals. Triggers: 'write paper', 'journal article', 'conference paper', 'abstract', 'rebuttal', 'camera-ready'.";
+export declare const academicWritingSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/data-management-plan.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DATA_MANAGEMENT_PLAN_SKILL_NAME = "data-management-plan";
+export declare const DATA_MANAGEMENT_PLAN_SKILL_DESCRIPTION = "Data management planning: FAIR principles, DMP templates (Horizon Europe, NSF, UKRI), data governance, open data repositories, metadata standards, data lifecycle management, GDPR compliance for research data. Triggers: 'DMP', 'data management plan', 'FAIR data', 'open data', 'data governance', 'metadata', 'data repository'.";
+export declare const dataManagementPlanSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/deliverable-writing.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DELIVERABLE_WRITING_SKILL_NAME = "deliverable-writing";
+export declare const DELIVERABLE_WRITING_SKILL_DESCRIPTION = "EU project deliverable writing expertise: deliverable types (R/DEM/DEC/DATA/DMP/ETHICS), dissemination levels, document structure, reporting periods, KPI tracking, risk registers, D&E plans, periodic vs final reports, and amendment procedures. Triggers: 'deliverable', 'EU report', 'periodic report', 'DMP', 'dissemination plan', 'work package report'.";
+export declare const deliverableWritingSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dev-browser.d.ts

@@ -0,0 +1,2 @@
+import type { BuiltinSkill } from "../types";
+export declare const devBrowserSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/document-reader.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DOCUMENT_READER_SKILL_NAME = "document-reader";
+export declare const DOCUMENT_READER_SKILL_DESCRIPTION = "Read and extract content from local or remote documents (PDF, DOCX, XLSX, PPTX, HTML, images). Use the document_reader MCP tool `convert_to_markdown` with a file: or https: URI. Triggers: 'read the PDF', 'analyze the document', 'extract from .docx', 'summarize the file', 'look at the spreadsheet'.";
+export declare const documentReaderSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-codegen.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_CODEGEN_SKILL_NAME = "dsl-codegen";
+export declare const DSL_CODEGEN_SKILL_DESCRIPTION = "Code generation and transpiler engineering for DSLs. Source analysis, generator architecture (template/AST-walk/IR), multi-target generation, source maps. Triggers: 'code generation', 'transpile', 'compile to', 'emit', 'codegen', 'M2T'.";
+export declare const dslCodegenSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-composition.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_COMPOSITION_SKILL_NAME = "dsl-composition";
+export declare const DSL_COMPOSITION_SKILL_DESCRIPTION = "Language composition and DSL evolution: textX multi-metamodel, grammar extension/inheritance, grammar referencing, DSL evolution (grammar versioning, backward compatibility), model migration, multiple concrete syntaxes for one abstract syntax, language embedding. Triggers: 'language composition', 'grammar extension', 'multi-metamodel', 'DSL evolution', 'model migration', 'grammar versioning', 'language embedding'.";
+export declare const dslCompositionSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-core.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_CORE_SKILL_NAME = "dsl-core";
+export declare const DSL_CORE_SKILL_DESCRIPTION = "DSL engineering foundations: expert constraints, framework selection guide, paradigm coverage, and anti-patterns. Load alongside domain-specific DSL skills (dsl-grammar, dsl-codegen, dsl-metamodel, dsl-tooling). Triggers: 'DSL', 'domain-specific language', 'language design'.";
+export declare const dslCoreSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-grammar.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_GRAMMAR_SKILL_NAME = "dsl-grammar";
+export declare const DSL_GRAMMAR_SKILL_DESCRIPTION = "Grammar design and parser implementation for DSLs. Domain analysis, formal grammar (BNF/EBNF/PEG), expression precedence, declaration patterns, error recovery, framework adaptation. Triggers: 'grammar', 'BNF', 'EBNF', 'PEG', 'parser', 'lexer', 'ANTLR', 'textX grammar', 'precedence', 'operator'.";
+export declare const dslGrammarSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-metamodel.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_METAMODEL_SKILL_NAME = "dsl-metamodel";
+export declare const DSL_METAMODEL_SKILL_DESCRIPTION = "Metamodeling for DSLs with textX, PyEcore, and EMF-style tools. Complete textX grammar reference (assignments, rule types, references, modifiers), scoping, validation, model transformations. Triggers: 'metamodel', 'PyEcore', 'EMF', 'model-driven', 'M2M', 'textX', 'Ecore', 'scoping', 'obj_processors'.";
+export declare const dslMetamodelSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-model-transformation.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_MODEL_TRANSFORMATION_SKILL_NAME = "dsl-model-transformation";
+export declare const DSL_MODEL_TRANSFORMATION_SKILL_DESCRIPTION = "Model-to-model (M2M) transformations: in-place vs out-place, rule-based mapping, transformation chaining, trace models, ATL-style patterns in Python, motra framework, M2T with Jinja2 best practices. Triggers: 'M2M', 'model transformation', 'ATL', 'motra', 'in-place transformation', 'transformation chain'.";
+export declare const dslModelTransformationSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-pyecore-advanced.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_PYECORE_ADVANCED_SKILL_NAME = "dsl-pyecore-advanced";
+export declare const DSL_PYECORE_ADVANCED_SKILL_DESCRIPTION = "Advanced PyEcore: serialization (XMI/JSON, ResourceSet, URI), dynamic vs static metamodels (DynamicEPackage, pyecoregen), notifications (EObserver), @EMetaclass decorator, loading .ecore files, EMF interchange, executable models. Triggers: 'XMI', 'ResourceSet', 'pyecoregen', 'DynamicEPackage', 'EObserver', '.ecore', 'EMF interchange'.";
+export declare const dslPyecoreAdvancedSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-testing.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_TESTING_SKILL_NAME = "dsl-testing";
+export declare const DSL_TESTING_SKILL_DESCRIPTION = "DSL testing patterns: grammar parsing tests, semantic validation testing (TextXSyntaxError/TextXSemanticError), code generator golden-file testing, property-based testing with Hypothesis, model roundtrip testing, test organization. Triggers: 'test grammar', 'test parser', 'test generator', 'golden file', 'roundtrip test', 'DSL test'.";
+export declare const dslTestingSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-textx-ecosystem.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_TEXTX_ECOSYSTEM_SKILL_NAME = "dsl-textx-ecosystem";
+export declare const DSL_TEXTX_ECOSYSTEM_SKILL_DESCRIPTION = "textX ecosystem: registration system (entry points, textx_languages/textx_generators), generator framework (textx generate CLI, Jinja2, GeneratorParam), multi-file models (ModelRepository, FQNImportURI), language composition (grammar extension, multi-metamodel), visualization (dot/PlantUML), textX-LS. Triggers: 'textx generate', 'textx_languages', 'entry points', 'multi-file model', 'language composition', 'textX-LS'.";
+export declare const dslTextxEcosystemSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-tooling.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_TOOLING_SKILL_NAME = "dsl-tooling";
+export declare const DSL_TOOLING_SKILL_DESCRIPTION = "IDE tooling and internal DSL engineering. Tree-sitter grammars, LSP implementation, syntax highlighting, formatters, fluent APIs, builder patterns, decorators. Triggers: 'tree-sitter', 'LSP', 'syntax highlighting', 'IDE support', 'formatter', 'fluent API', 'builder pattern', 'internal DSL', 'embedded DSL'.";
+export declare const dslToolingSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/dsl-validation.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const DSL_VALIDATION_SKILL_NAME = "dsl-validation";
+export declare const DSL_VALIDATION_SKILL_DESCRIPTION = "Advanced DSL model validation: OCL-style constraint patterns, well-formedness rules, multiplicity/cardinality checks, referential integrity, invariant specifications, constraint categories (structural/semantic/domain), error reporting strategy. Triggers: 'OCL', 'constraint', 'well-formedness', 'invariant', 'model validation', 'cardinality', 'referential integrity'.";
+export declare const dslValidationSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/eu-horizon.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const EU_HORIZON_SKILL_NAME = "eu-horizon";
+export declare const EU_HORIZON_SKILL_DESCRIPTION = "Horizon Europe proposal expertise: programme structure, funding instruments (RIA/IA/CSA/ERC/MSCA), evaluation criteria, Part B structure, budget rules, consortium requirements, WP conventions, TRL levels, ethics, and Open Science. Triggers: 'Horizon Europe', 'EU proposal', 'ERC', 'MSCA', 'RIA', 'work programme'.";
+export declare const euHorizonSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/frontend-ui-ux.d.ts

@@ -0,0 +1,2 @@
+import type { BuiltinSkill } from "../types";
+export declare const frontendUiUxSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/git-master-skill-metadata.d.ts

@@ -0,0 +1,2 @@
+export declare const GIT_MASTER_SKILL_NAME = "git-master";
+export declare const GIT_MASTER_SKILL_DESCRIPTION = "MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.";

package/dist/features/builtin-skills/skills/git-master.d.ts

@@ -0,0 +1,2 @@
+import type { BuiltinSkill } from "../types";
+export declare const gitMasterSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/grant-writing.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const GRANT_WRITING_SKILL_NAME = "grant-writing";
+export declare const GRANT_WRITING_SKILL_DESCRIPTION = "General grant and funding proposal writing beyond EU: NSF, NIH, ERC individual grants, national agencies, industry calls. Budget narratives, biosketches, broader impacts, evaluation criteria alignment, panel review processes. Triggers: 'grant proposal', 'NSF', 'NIH', 'funding application', 'research grant', 'budget narrative', 'broader impacts'.";
+export declare const grantWritingSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/index.d.ts

@@ -0,0 +1,38 @@
+export { playwrightSkill, agentBrowserSkill } from "./playwright";
+export { playwrightCliSkill } from "./playwright-cli";
+export { frontendUiUxSkill } from "./frontend-ui-ux";
+export { gitMasterSkill } from "./git-master";
+export { devBrowserSkill } from "./dev-browser";
+export { dslCoreSkill } from "./dsl-core";
+export { dslGrammarSkill } from "./dsl-grammar";
+export { dslCodegenSkill } from "./dsl-codegen";
+export { dslMetamodelSkill } from "./dsl-metamodel";
+export { dslToolingSkill } from "./dsl-tooling";
+export { euHorizonSkill } from "./eu-horizon";
+export { academicReviewSkill } from "./academic-review";
+export { deliverableWritingSkill } from "./deliverable-writing";
+export { projectManagementSkill } from "./project-management";
+export { technicalLeadSkill } from "./technical-lead";
+export { academicWritingSkill } from "./academic-writing";
+export { researchMethodologySkill } from "./research-methodology";
+export { literatureReviewSkill } from "./literature-review";
+export { grantWritingSkill } from "./grant-writing";
+export { scientificPresentationSkill } from "./scientific-presentation";
+export { dataManagementPlanSkill } from "./data-management-plan";
+export { ipExploitationSkill } from "./ip-exploitation";
+export { dslTextxEcosystemSkill } from "./dsl-textx-ecosystem";
+export { dslPyecoreAdvancedSkill } from "./dsl-pyecore-advanced";
+export { dslModelTransformationSkill } from "./dsl-model-transformation";
+export { dslTestingSkill } from "./dsl-testing";
+export { dslValidationSkill } from "./dsl-validation";
+export { dslCompositionSkill } from "./dsl-composition";
+export { securityCoreSkill } from "./security-core";
+export { securitySecretsSkill } from "./security-secrets";
+export { securitySastSkill } from "./security-sast";
+export { securityDastSkill } from "./security-dast";
+export { securityDependenciesSkill } from "./security-dependencies";
+export { securityApiSkill } from "./security-api";
+export { securityCryptoSkill } from "./security-crypto";
+export { securityInfraSkill } from "./security-infra";
+export { securityReviewSkill } from "./security-review";
+export { documentReaderSkill } from "./document-reader";

package/dist/features/builtin-skills/skills/ip-exploitation.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const IP_EXPLOITATION_SKILL_NAME = "ip-exploitation";
+export declare const IP_EXPLOITATION_SKILL_DESCRIPTION = "Intellectual property and exploitation strategy: patent landscaping, licensing models, TRL advancement plans, commercialization roadmaps, spin-off creation, technology transfer, IP management in consortia, exploitation plans for funded projects. Triggers: 'IP', 'patent', 'licensing', 'TRL', 'commercialization', 'spin-off', 'technology transfer', 'exploitation plan'.";
+export declare const ipExploitationSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/literature-review.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const LITERATURE_REVIEW_SKILL_NAME = "literature-review";
+export declare const LITERATURE_REVIEW_SKILL_DESCRIPTION = "Systematic literature review methodology: PRISMA guidelines, search strategy design, bibliometric analysis, gap identification, synthesis writing, scoping reviews, meta-analysis frameworks, reference management. Triggers: 'literature review', 'systematic review', 'PRISMA', 'bibliometric', 'state of the art', 'survey paper', 'meta-analysis'.";
+export declare const literatureReviewSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/playwright-cli.d.ts

@@ -0,0 +1,10 @@
+import type { BuiltinSkill } from "../types";
+/**
+ * Playwright CLI skill — token-efficient CLI alternative to the MCP-based playwright skill.
+ *
+ * Uses name "playwright" (not "playwright-cli") because agents hardcode "playwright" as the
+ * canonical browser skill name. The browserProvider config swaps the implementation behind
+ * the same name: "playwright" gives MCP, "playwright-cli" gives this CLI variant.
+ * The binary is still called `playwright-cli` (see allowedTools).
+ */
+export declare const playwrightCliSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/playwright.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const playwrightSkill: BuiltinSkill;
+export declare const agentBrowserSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/project-management.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const PROJECT_MANAGEMENT_SKILL_NAME = "project-management";
+export declare const PROJECT_MANAGEMENT_SKILL_DESCRIPTION = "Project management expertise: Agile/Scrum/Kanban, Waterfall, risk management, stakeholder engagement, resource planning, WBS, Gantt charts, earned value management, team coordination, status reporting. Triggers: 'project plan', 'sprint', 'stakeholder', 'risk register', 'Gantt', 'WBS', 'resource allocation'.";
+export declare const projectManagementSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/research-methodology.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const RESEARCH_METHODOLOGY_SKILL_NAME = "research-methodology";
+export declare const RESEARCH_METHODOLOGY_SKILL_DESCRIPTION = "Research design and methodology: quantitative/qualitative/mixed methods, hypothesis formulation, experimental design, statistical analysis, sampling strategies, validity/reliability, survey design, ethical considerations. Triggers: 'research design', 'methodology', 'hypothesis', 'statistical analysis', 'experiment design', 'sampling', 'survey'.";
+export declare const researchMethodologySkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/scientific-presentation.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SCIENTIFIC_PRESENTATION_SKILL_NAME = "scientific-presentation";
+export declare const SCIENTIFIC_PRESENTATION_SKILL_DESCRIPTION = "Scientific presentation design: conference talks, poster sessions, pitch decks for reviewers/investors, keynote structure, visual storytelling for technical audiences, demo preparation, slide design principles. Triggers: 'presentation', 'conference talk', 'poster', 'pitch deck', 'keynote', 'slides', 'demo'.";
+export declare const scientificPresentationSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-api.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_API_SKILL_NAME = "security-api";
+export declare const SECURITY_API_SKILL_DESCRIPTION = "API security patterns: authentication, authorization, input validation, rate limiting, CORS, CSRF, security headers, and error handling. Triggers: 'API security', 'authentication', 'authorization', 'JWT', 'OAuth', 'CORS', 'CSRF', 'rate limiting', 'input validation'.";
+export declare const securityApiSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-core.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_CORE_SKILL_NAME = "security-core";
+export declare const SECURITY_CORE_SKILL_DESCRIPTION = "Core security auditing principles, OWASP Top 10, CWE classification, severity scoring, and structured reporting. Triggers: 'security', 'audit', 'vulnerability', 'OWASP', 'CWE', 'security review'.";
+export declare const securityCoreSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-crypto.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_CRYPTO_SKILL_NAME = "security-crypto";
+export declare const SECURITY_CRYPTO_SKILL_DESCRIPTION = "Cryptography and key management security guidelines: algorithm selection, key management, TLS configuration, common crypto mistakes, and secure random generation. Triggers: 'cryptography', 'encryption', 'hashing', 'TLS', 'key management', 'crypto', 'password hashing', 'certificate'.";
+export declare const securityCryptoSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-dast.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_DAST_SKILL_NAME = "security-dast";
+export declare const SECURITY_DAST_SKILL_DESCRIPTION = "DAST overview: testing running applications for vulnerabilities at runtime, differs from SAST by finding issues only visible during execution. Triggers: 'DAST', 'dynamic analysis', 'ZAP', 'Nuclei', 'runtime security', 'penetration test', 'fuzzing'.";
+export declare const securityDastSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-dependencies.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_DEPENDENCIES_SKILL_NAME = "security-dependencies";
+export declare const SECURITY_DEPENDENCIES_SKILL_DESCRIPTION = "Dependency security scanning, SBOM generation, CVE lookups, remediation strategies, license compliance, and supply chain risk management. Triggers: 'dependency', 'CVE', 'npm audit', 'trivy', 'supply chain', 'vulnerability scanning', 'SBOM', 'license'.";
+export declare const securityDependenciesSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-infra.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_INFRA_SKILL_NAME = "security-infra";
+export declare const SECURITY_INFRA_SKILL_DESCRIPTION = "Infrastructure and container security guidelines: container scanning, Dockerfile hardening, Kubernetes security, IaC scanning, and cloud security fundamentals. Triggers: 'container security', 'Docker', 'Kubernetes', 'IaC', 'infrastructure', 'Checkov', 'tfsec', 'cloud security', 'Dockerfile'.";
+export declare const securityInfraSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-review.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_REVIEW_SKILL_NAME = "security-review";
+export declare const SECURITY_REVIEW_SKILL_DESCRIPTION = "Security review and threat modeling methodology: LLM-powered review phases, STRIDE threat model, attack surface mapping, architecture checklist, risk assessment, and report structure. Triggers: 'security review', 'threat model', 'STRIDE', 'attack surface', 'risk assessment', 'security architecture'.";
+export declare const securityReviewSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-sast.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_SAST_SKILL_NAME = "security-sast";
+export declare const SECURITY_SAST_SKILL_DESCRIPTION = "Static Application Security Testing (SAST), Semgrep usage, CWE-specific code patterns, and ESLint security plugins. Triggers: 'SAST', 'static analysis', 'semgrep', 'code scanning', 'vulnerability pattern'.";
+export declare const securitySastSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/security-secrets.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const SECURITY_SECRETS_SKILL_NAME = "security-secrets";
+export declare const SECURITY_SECRETS_SKILL_DESCRIPTION = "Secret scanning, entropy analysis, gitleaks usage, and remediation playbooks for exposed credentials. Triggers: 'secret', 'API key', 'credential', 'gitleaks', 'secret scanning', 'key exposure'.";
+export declare const securitySecretsSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/technical-lead.d.ts

@@ -0,0 +1,4 @@
+import type { BuiltinSkill } from "../types";
+export declare const TECHNICAL_LEAD_SKILL_NAME = "technical-lead";
+export declare const TECHNICAL_LEAD_SKILL_DESCRIPTION = "Technical leadership expertise: architecture decision records (ADRs), code review strategy, tech debt management, system design, team mentoring, technical roadmaps, incident management, build/release engineering. Triggers: 'tech lead', 'architecture decision', 'ADR', 'tech debt', 'code review', 'system design', 'technical roadmap'.";
+export declare const technicalLeadSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills.d.ts

@@ -0,0 +1,7 @@
+import type { BuiltinSkill } from "./types";
+import type { BrowserAutomationProvider } from "../../config/schema";
+export interface CreateBuiltinSkillsOptions {
+    browserProvider?: BrowserAutomationProvider;
+    disabledSkills?: Set<string>;
+}
+export declare function createBuiltinSkills(options?: CreateBuiltinSkillsOptions): BuiltinSkill[];

package/dist/features/builtin-skills/types.d.ts

@@ -0,0 +1,15 @@
+import type { SkillMcpConfig } from "../skill-mcp-manager/types";
+export interface BuiltinSkill {
+    name: string;
+    description: string;
+    template: string;
+    license?: string;
+    compatibility?: string;
+    metadata?: Record<string, unknown>;
+    allowedTools?: string[];
+    agent?: string;
+    model?: string;
+    subtask?: boolean;
+    argumentHint?: string;
+    mcpConfig?: SkillMcpConfig;
+}

package/dist/features/claude-code-agent-loader/index.d.ts

@@ -0,0 +1,2 @@
+export * from "./types";
+export * from "./loader";

package/dist/features/claude-code-agent-loader/loader.d.ts

@@ -0,0 +1,3 @@
+import type { AgentConfig } from "@opencode-ai/sdk";
+export declare function loadUserAgents(): Record<string, AgentConfig>;
+export declare function loadProjectAgents(directory?: string): Record<string, AgentConfig>;

package/dist/features/claude-code-agent-loader/types.d.ts

@@ -0,0 +1,14 @@
+import type { AgentConfig } from "@opencode-ai/sdk";
+export type AgentScope = "user" | "project";
+export interface AgentFrontmatter {
+    name?: string;
+    description?: string;
+    model?: string;
+    tools?: string;
+}
+export interface LoadedAgent {
+    name: string;
+    path: string;
+    config: AgentConfig;
+    scope: AgentScope;
+}

package/dist/features/claude-code-command-loader/index.d.ts

@@ -0,0 +1,2 @@
+export * from "./types";
+export * from "./loader";

package/dist/features/claude-code-command-loader/loader.d.ts

@@ -0,0 +1,6 @@
+import type { CommandDefinition } from "./types";
+export declare function loadUserCommands(): Promise<Record<string, CommandDefinition>>;
+export declare function loadProjectCommands(directory?: string): Promise<Record<string, CommandDefinition>>;
+export declare function loadOpencodeGlobalCommands(): Promise<Record<string, CommandDefinition>>;
+export declare function loadOpencodeProjectCommands(directory?: string): Promise<Record<string, CommandDefinition>>;
+export declare function loadAllCommands(directory?: string): Promise<Record<string, CommandDefinition>>;

package/dist/features/claude-code-command-loader/types.d.ts

@@ -0,0 +1,42 @@
+export type CommandScope = "user" | "project" | "opencode" | "opencode-project";
+/**
+ * Handoff definition for command workflows.
+ * Based on speckit's handoff pattern for multi-agent orchestration.
+ * @see https://github.com/github/spec-kit
+ */
+export interface HandoffDefinition {
+    /** Human-readable label for the handoff action */
+    label: string;
+    /** Target agent/command identifier (e.g., "speckit.tasks") */
+    agent: string;
+    /** Pre-filled prompt text for the handoff */
+    prompt: string;
+    /** If true, automatically executes after command completion; if false, shows as suggestion */
+    send?: boolean;
+}
+export interface CommandDefinition {
+    name: string;
+    description?: string;
+    template: string;
+    agent?: string;
+    model?: string;
+    subtask?: boolean;
+    argumentHint?: string;
+    /** Handoff definitions for workflow transitions */
+    handoffs?: HandoffDefinition[];
+}
+export interface CommandFrontmatter {
+    description?: string;
+    "argument-hint"?: string;
+    agent?: string;
+    model?: string;
+    subtask?: boolean;
+    /** Handoff definitions for workflow transitions */
+    handoffs?: HandoffDefinition[];
+}
+export interface LoadedCommand {
+    name: string;
+    path: string;
+    definition: CommandDefinition;
+    scope: CommandScope;
+}

package/dist/features/claude-code-mcp-loader/env-expander.d.ts

@@ -0,0 +1,2 @@
+export declare function expandEnvVars(value: string): string;
+export declare function expandEnvVarsInObject<T>(obj: T): T;

package/dist/features/claude-code-mcp-loader/index.d.ts

@@ -0,0 +1,10 @@
+/**
+ * MCP Configuration Loader
+ *
+ * Loads Claude Code .mcp.json format configurations from multiple scopes
+ * and transforms them to OpenCode SDK format
+ */
+export * from "./types";
+export * from "./loader";
+export * from "./transformer";
+export * from "./env-expander";

package/dist/features/claude-code-mcp-loader/loader.d.ts

@@ -0,0 +1,4 @@
+import type { LoadedMcpServer, McpLoadResult } from "./types";
+export declare function getSystemMcpServerNames(): Set<string>;
+export declare function loadMcpConfigs(disabledMcps?: string[]): Promise<McpLoadResult>;
+export declare function formatLoadedServersForToast(loadedServers: LoadedMcpServer[]): string;

package/dist/features/claude-code-mcp-loader/transformer.d.ts

@@ -0,0 +1,2 @@
+import type { ClaudeCodeMcpServer, McpServerConfig } from "./types";
+export declare function transformMcpServer(name: string, server: ClaudeCodeMcpServer): McpServerConfig;

package/dist/features/claude-code-mcp-loader/types.d.ts

@@ -0,0 +1,39 @@
+export type McpScope = "user" | "project" | "local";
+export interface ClaudeCodeMcpServer {
+    type?: "http" | "sse" | "stdio";
+    url?: string;
+    command?: string;
+    args?: string[];
+    env?: Record<string, string>;
+    headers?: Record<string, string>;
+    oauth?: {
+        clientId?: string;
+        scopes?: string[];
+    };
+    disabled?: boolean;
+}
+export interface ClaudeCodeMcpConfig {
+    mcpServers?: Record<string, ClaudeCodeMcpServer>;
+}
+export interface McpLocalConfig {
+    type: "local";
+    command: string[];
+    environment?: Record<string, string>;
+    enabled?: boolean;
+}
+export interface McpRemoteConfig {
+    type: "remote";
+    url: string;
+    headers?: Record<string, string>;
+    enabled?: boolean;
+}
+export type McpServerConfig = McpLocalConfig | McpRemoteConfig;
+export interface LoadedMcpServer {
+    name: string;
+    scope: McpScope;
+    config: McpServerConfig;
+}
+export interface McpLoadResult {
+    servers: Record<string, McpServerConfig>;
+    loadedServers: LoadedMcpServer[];
+}

package/dist/features/claude-code-plugin-loader/agent-loader.d.ts

@@ -0,0 +1,3 @@
+import type { AgentConfig } from "@opencode-ai/sdk";
+import type { LoadedPlugin } from "./types";
+export declare function loadPluginAgents(plugins: LoadedPlugin[]): Record<string, AgentConfig>;

package/dist/features/claude-code-plugin-loader/command-loader.d.ts

@@ -0,0 +1,3 @@
+import type { CommandDefinition } from "../claude-code-command-loader/types";
+import type { LoadedPlugin } from "./types";
+export declare function loadPluginCommands(plugins: LoadedPlugin[]): Record<string, CommandDefinition>;

package/dist/features/claude-code-plugin-loader/discovery.d.ts

@@ -0,0 +1,2 @@
+import type { PluginLoadResult, PluginLoaderOptions } from "./types";
+export declare function discoverInstalledPlugins(options?: PluginLoaderOptions): PluginLoadResult;

package/dist/features/claude-code-plugin-loader/hook-loader.d.ts

@@ -0,0 +1,2 @@
+import type { HooksConfig, LoadedPlugin } from "./types";
+export declare function loadPluginHooksConfigs(plugins: LoadedPlugin[]): HooksConfig[];