opencode-matrixx 1.1.0 → 2.0.0

package/dist/create-hooks.d.ts

@@ -1,7 +1,7 @@
 import type { AvailableSkill } from "./agents/dynamic-agent-prompt-builder";
 import type { HookName, MatrixxConfig } from "./config";
-import type { LoadedSkill } from "./features/opencode-skill-loader/types";
 import type { BackgroundManager } from "./features/background-agent";
+import type { LoadedSkill } from "./features/opencode-skill-loader/types";
 import type { PluginContext } from "./plugin/types";
 export type CreatedHooks = ReturnType<typeof createHooks>;
 export declare function createHooks(args: {
@@ -22,11 +22,11 @@ export declare function createHooks(args: {
     unstableAgentBabysitter: ReturnType<typeof import("./plugin/unstable-agent-babysitter").createUnstableAgentBabysitter> | null;
     backgroundNotificationHook: ReturnType<typeof import("./hooks").createBackgroundNotificationHook> | null;
     atlasHook: ReturnType<typeof import("./hooks").createAtlasHook> | null;
-    claudeCodeHooks: ReturnType<typeof import("./hooks").createClaudeCodeHooksHook>;
     keywordDetector: ReturnType<typeof import("./hooks").createKeywordDetectorHook> | null;
     contextInjectorMessagesTransform: ReturnType<typeof import("./features/context-injector").createContextInjectorMessagesTransformHook>;
     thinkingBlockValidator: ReturnType<typeof import("./hooks").createThinkingBlockValidatorHook> | null;
     toolPairValidator: ReturnType<typeof import("./hooks").createToolPairValidatorHook> | null;
+    designIntentPreserver: ReturnType<typeof import("./hooks").createDesignIntentPreserverHook> | null;
     commentChecker: ReturnType<typeof import("./hooks").createCommentCheckerHooks> | null;
     toolOutputTruncator: ReturnType<typeof import("./hooks").createToolOutputTruncatorHook> | null;
     directoryAgentsInjector: ReturnType<typeof import("./hooks").createDirectoryAgentsInjectorHook> | null;
@@ -44,6 +44,8 @@ export declare function createHooks(args: {
     readImageResizer: ReturnType<typeof import("./hooks").createReadImageResizerHook> | null;
     webfetchRedirectGuard: ReturnType<typeof import("./hooks").createWebFetchRedirectGuardHook> | null;
     hashlineEditDiffEnhancer: ReturnType<typeof import("./hooks").createHashlineEditDiffEnhancerHook> | null;
+    qualityGate: ReturnType<typeof import("./hooks").createQualityGateHook> | null;
+    taskNotepad: ReturnType<typeof import("./hooks").createTaskNotepadHook> | null;
     contextWindowMonitor: ReturnType<typeof import("./hooks").createContextWindowMonitorHook> | null;
     preemptiveCompaction: ReturnType<typeof import("./hooks").createPreemptiveCompactionHook> | null;
     sessionRecovery: ReturnType<typeof import("./hooks").createSessionRecoveryHook> | null;

package/dist/create-managers.d.ts

@@ -1,10 +1,10 @@
 import type { MatrixxConfig } from "./config";
-import type { ModelCacheState } from "./plugin-state";
-import type { PluginContext, TmuxConfig } from "./plugin/types";
 import { BackgroundManager } from "./features/background-agent";
 import { SkillMcpManager } from "./features/skill-mcp-manager";
 import { TmuxSessionManager } from "./features/tmux-subagent";
+import type { PluginContext, TmuxConfig } from "./plugin/types";
 import { createConfigHandler } from "./plugin-handlers";
+import type { ModelCacheState } from "./plugin-state";
 export type Managers = {
     tmuxSessionManager: TmuxSessionManager;
     backgroundManager: BackgroundManager;

package/dist/create-tools.d.ts

@@ -1,10 +1,10 @@
 import type { AvailableCategory, AvailableSkill } from "./agents/dynamic-agent-prompt-builder";
 import type { MatrixxConfig } from "./config";
 import type { BrowserAutomationProvider } from "./config/schema/browser-automation";
+import type { Managers } from "./create-managers";
 import type { LoadedSkill } from "./features/opencode-skill-loader/types";
 import type { PluginContext, ToolsRecord } from "./plugin/types";
-import type { Managers } from "./create-managers";
-export type CreateToolsResult = {
+type CreateToolsResult = {
     filteredTools: ToolsRecord;
     mergedSkills: LoadedSkill[];
     availableSkills: AvailableSkill[];
@@ -18,3 +18,4 @@ export declare function createTools(args: {
     pluginConfig: MatrixxConfig;
     managers: Pick<Managers, "backgroundManager" | "tmuxSessionManager" | "skillMcpManager">;
 }): Promise<CreateToolsResult>;
+export {};

package/dist/features/background-agent/background-task-notification-template.d.ts

@@ -1,5 +1,5 @@
 import type { BackgroundTask } from "./types";
-export type BackgroundTaskNotificationStatus = "COMPLETED" | "CANCELLED" | "INTERRUPTED";
+type BackgroundTaskNotificationStatus = "COMPLETED" | "CANCELLED" | "INTERRUPTED";
 export declare function buildBackgroundTaskNotificationText(input: {
     task: BackgroundTask;
     duration: string;
@@ -8,3 +8,4 @@ export declare function buildBackgroundTaskNotificationText(input: {
     remainingCount: number;
     completedTasks: BackgroundTask[];
 }): string;
+export {};

package/dist/features/background-agent/constants.d.ts

@@ -10,8 +10,8 @@ export declare const DEFAULT_CIRCUIT_BREAKER_ENABLED = true;
 export declare const MIN_RUNTIME_BEFORE_STALE_MS = 30000;
 export declare const MIN_IDLE_TIME_MS = 5000;
 export declare const POLLING_INTERVAL_MS = 3000;
+export declare const PRUNE_THROTTLE_MS = 30000;
 export declare const TASK_CLEANUP_DELAY_MS: number;
-export declare const TMUX_CALLBACK_DELAY_MS = 200;
 export type ProcessCleanupEvent = NodeJS.Signals | "beforeExit" | "exit";
 export type OpencodeClient = PluginInput["client"];
 export interface MessagePartInfo {
@@ -26,10 +26,6 @@ export interface EventProperties {
     };
     [key: string]: unknown;
 }
-export interface BackgroundEvent {
-    type: string;
-    properties?: EventProperties;
-}
 export interface Todo {
     content: string;
     status: string;

package/dist/features/background-agent/index.d.ts

@@ -1,5 +1,5 @@
-export * from "./types";
-export { BackgroundManager, type SubagentSessionCreatedEvent, type OnSubagentSessionCreated } from "./manager";
-export { TaskHistory, type TaskHistoryEntry } from "./task-history";
 export { ConcurrencyManager } from "./concurrency";
+export { BackgroundManager, type OnSubagentSessionCreated, type SubagentSessionCreatedEvent } from "./manager";
 export { TaskStateManager } from "./state";
+export { TaskHistory, type TaskHistoryEntry } from "./task-history";
+export * from "./types";

package/dist/features/background-agent/loop-detector.d.ts

@@ -5,12 +5,12 @@ export interface CircuitBreakerSettings {
     maxToolCalls: number;
     consecutiveThreshold: number;
 }
-export interface ToolLoopDetectionResult {
+interface ToolLoopDetectionResult {
     triggered: boolean;
     toolName?: string;
     repeatedCount?: number;
 }
 export declare function resolveCircuitBreakerSettings(config?: BackgroundTaskConfig): CircuitBreakerSettings;
 export declare function recordToolCall(window: ToolCallWindow | undefined, toolName: string, settings: CircuitBreakerSettings, toolInput?: Record<string, unknown> | null): ToolCallWindow;
-export declare function createToolCallSignature(toolName: string, toolInput?: Record<string, unknown> | null): string;
 export declare function detectRepetitiveToolUse(window: ToolCallWindow | undefined): ToolLoopDetectionResult;
+export {};

package/dist/features/background-agent/manager.d.ts

@@ -1,7 +1,7 @@
 import type { PluginInput } from "@opencode-ai/plugin";
-import type { BackgroundTask, LaunchInput, ResumeInput } from "./types";
-import { TaskHistory } from "./task-history";
 import type { BackgroundTaskConfig, TmuxConfig } from "../../config/schema";
+import { TaskHistory } from "./task-history";
+import type { BackgroundTask, LaunchInput, ResumeInput } from "./types";
 interface EventProperties {
     sessionID?: string;
     info?: {
@@ -30,6 +30,7 @@ export declare class BackgroundManager {
     private directory;
     private pollingInterval?;
     private pollingInFlight;
+    private lastPruneAt;
     private concurrencyManager;
     private shutdownTriggered;
     private config?;
@@ -76,6 +77,13 @@ export declare class BackgroundManager {
     handleEvent(event: Event): void;
     markForNotification(task: BackgroundTask): void;
     getPendingNotifications(sessionID: string): BackgroundTask[];
+    /**
+     * Check whether a parent-wake notification is currently in flight
+     * for the given parent session.  Used by sync-task polling to avoid
+     * concluding when a background task just completed but its
+     * parent notification hasn't been delivered yet.
+     */
+    hasInFlightNotificationForParent(sessionID: string): boolean;
     clearNotifications(sessionID: string): void;
     /**
      * Validates that a session has actual assistant/tool output before marking complete.
@@ -139,4 +147,7 @@ export declare class BackgroundManager {
     shutdown(): void;
     private enqueueNotificationForParent;
 }
+export declare function getMessageDir(sessionID: string): string | null;
+export declare function _resetMessageDirCacheForTesting(): void;
+export declare function _resetPruneThrottleForTesting(): void;
 export {};

package/dist/features/background-agent/state.d.ts

@@ -1,5 +1,5 @@
-import type { BackgroundTask, LaunchInput } from "./types";
 import type { QueueItem } from "./constants";
+import type { BackgroundTask, LaunchInput } from "./types";
 export declare class TaskStateManager {
     readonly tasks: Map<string, BackgroundTask>;
     readonly notifications: Map<string, BackgroundTask[]>;

package/dist/features/background-agent/task-poller.d.ts

@@ -1,13 +1,13 @@
 import type { BackgroundTaskConfig } from "../../config/schema";
-import type { BackgroundTask } from "./types";
 import type { ConcurrencyManager } from "./concurrency";
 import type { OpencodeClient } from "./opencode-client";
+import type { BackgroundTask } from "./types";
 export declare function pruneStaleTasksAndNotifications(args: {
     tasks: Map<string, BackgroundTask>;
     notifications: Map<string, BackgroundTask[]>;
     onTaskPruned: (taskId: string, task: BackgroundTask, errorMessage: string) => void;
 }): void;
-export type SessionStatusMap = Record<string, {
+type SessionStatusMap = Record<string, {
     type: string;
 }>;
 export declare function checkAndInterruptStaleTasks(args: {
@@ -18,3 +18,4 @@ export declare function checkAndInterruptStaleTasks(args: {
     notifyParentSession: (task: BackgroundTask) => Promise<void>;
     sessionStatuses?: SessionStatusMap;
 }): Promise<void>;
+export {};

package/dist/features/background-agent/types.d.ts

@@ -4,7 +4,7 @@ export interface ToolCallWindow {
     consecutiveCount: number;
     threshold: number;
 }
-export interface TaskProgress {
+interface TaskProgress {
     toolCalls: number;
     lastTool?: string;
     toolCallWindow?: ToolCallWindow;
@@ -36,6 +36,7 @@ export interface BackgroundTask {
         providerID: string;
         modelID: string;
         variant?: string;
+        temperature?: number;
     };
     /** Active concurrency slot key */
     concurrencyKey?: string;
@@ -70,6 +71,7 @@ export interface LaunchInput {
         providerID: string;
         modelID: string;
         variant?: string;
+        temperature?: number;
     };
     isUnstableAgent?: boolean;
     skills?: string[];
@@ -88,3 +90,4 @@ export interface ResumeInput {
     parentAgent?: string;
     parentTools?: Record<string, boolean>;
 }
+export {};

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

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

package/dist/features/builtin-commands/templates/end-ultrawork.d.ts

@@ -0,0 +1 @@
+export declare const END_ULTRAWORK_TEMPLATE = "Deactivate ultrawork mode for the current session.\n\nThis command will:\n1. Remove the <ultrawork-mode> rules block from the active context\n2. Restore default Matrixx behavior (no enforced certainty protocol, no mandatory plan agent, no required acceptance criteria)\n3. Stop ultrawork-specific parallel delegation pressure\n\nAfter running this command:\n- The session continues with normal Matrixx rules\n- Existing todos and plans remain unchanged\n- Already-spawned background tasks continue to completion\n- The deactivation is per-session and clears when the session ends\n\nUse this when you want to exit ultrawork mode explicitly and return to standard behavior. Useful for sub-tasks that should not inherit ultrawork rules, or when switching from heavy-execution to lighter reasoning.";

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

@@ -1 +1 @@
-export declare const HANDOFF_TEMPLATE = "# Handoff Command\n\n## Purpose\n\nUse /handoff when:\n- The current session context is getting too long and quality is degrading\n- You want to start fresh while preserving essential context from this session\n- The context window is approaching capacity\n\nThis creates a detailed context summary that can be used to continue work in a new session.\n\n---\n\n# PHASE 0: VALIDATE REQUEST\n\nBefore proceeding, confirm:\n- [ ] There is meaningful work or context in this session to preserve\n- [ ] The user wants to create a handoff summary (not just asking about it)\n\nIf the session is nearly empty or has no meaningful context, inform the user there is nothing substantial to hand off.\n\n---\n\n# PHASE 1: GATHER PROGRAMMATIC CONTEXT\n\nExecute these tools to gather concrete data:\n\n1. session_read({ session_id: \"$SESSION_ID\" }) \u2014 full session history\n2. todoread() \u2014 current task progress\n3. Bash({ command: \"git diff --stat HEAD~10..HEAD\" }) \u2014 recent file changes\n4. Bash({ command: \"git status --porcelain\" }) \u2014 uncommitted changes\n\nSuggested execution order:\n\n```\nsession_read({ session_id: \"$SESSION_ID\" })\ntodoread()\nBash({ command: \"git diff --stat HEAD~10..HEAD\" })\nBash({ command: \"git status --porcelain\" })\n```\n\nAnalyze the gathered outputs to understand:\n- What the user asked for (exact wording)\n- What work was completed\n- What tasks remain incomplete (include todo state)\n- What decisions were made\n- What files were modified or discussed (include git diff/stat + status)\n- What patterns, constraints, or preferences were established\n\n---\n\n# PHASE 2: EXTRACT CONTEXT\n\nWrite the context summary from first person perspective (\"I did...\", \"I told you...\").\n\nFocus on:\n- Capabilities and behavior, not file-by-file implementation details\n- What matters for continuing the work\n- Avoiding excessive implementation details (variable names, storage keys, constants) unless critical\n- USER REQUESTS (AS-IS) must be verbatim (do not paraphrase)\n- EXPLICIT CONSTRAINTS must be verbatim only (do not invent)\n\nQuestions to consider when extracting:\n- What did I just do or implement?\n- What instructions did I already give which are still relevant (e.g. follow patterns in the codebase)?\n- What files did I tell you are important or that I am working on?\n- Did I provide a plan or spec that should be included?\n- What did I already tell you that is important (libraries, patterns, constraints, preferences)?\n- What important technical details did I discover (APIs, methods, patterns)?\n- What caveats, limitations, or open questions did I find?\n\n---\n\n# PHASE 3: FORMAT OUTPUT\n\nGenerate a handoff summary. WRITE the summary to .matrixx/handoff.md using the Write tool. Use this exact format:\n\n```\nHANDOFF CONTEXT\n===============\n\nUSER REQUESTS (AS-IS)\n---------------------\n- [Exact verbatim user requests - NOT paraphrased]\n\nGOAL\n----\n[One sentence describing what should be done next]\n\nWORK COMPLETED\n--------------\n- [First person bullet points of what was done]\n- [Include specific file paths when relevant]\n- [Note key implementation decisions]\n\nCURRENT STATE\n-------------\n- [Current state of the codebase or task]\n- [Build/test status if applicable]\n- [Any environment or configuration state]\n\nPENDING TASKS\n-------------\n- [Tasks that were planned but not completed]\n- [Next logical steps to take]\n- [Any blockers or issues encountered]\n- [Include current todo state from todoread()]\n\nKEY FILES\n---------\n- [path/to/file1] - [brief role description]\n- [path/to/file2] - [brief role description]\n(Maximum 10 files, prioritized by importance)\n- (Include files from git diff/stat and git status)\n\nIMPORTANT DECISIONS\n-------------------\n- [Technical decisions that were made and why]\n- [Trade-offs that were considered]\n- [Patterns or conventions established]\n\nEXPLICIT CONSTRAINTS\n--------------------\n- [Verbatim constraints only - from user or existing AGENTS.md]\n- If none, write: None\n\nCONTEXT FOR CONTINUATION\n------------------------\n- [What the next session needs to know to continue]\n- [Warnings or gotchas to be aware of]\n- [References to documentation if relevant]\n```\n\nWrite this content to .matrixx/handoff.md using the Write tool. This file will be automatically loaded when a new session starts.\n\nRules for the summary:\n- Plain text with bullets\n- No markdown headers with # (use the format above with dashes)\n- No bold, italic, or code fences within content\n- Use workspace-relative paths for files\n- Keep it focused - only include what matters for continuation\n- Pick an appropriate length based on complexity\n- USER REQUESTS (AS-IS) and EXPLICIT CONSTRAINTS must be verbatim only\n\n---\n\n# PHASE 4: PROVIDE INSTRUCTIONS\n\nAfter writing the file, inform the user:\n\n```\n---\n\nHANDOFF COMPLETE:\n\nContext saved to .matrixx/handoff.md\n\nTo continue in a new session:\n1. Press 'n' in OpenCode TUI to open a new session, or run 'opencode' in a new terminal\n2. Your context will be loaded automatically \u2014 no copy-paste needed\n3. Start with your next task: \"Continue from where I left off. [Your next task]\"\n```\n\n---\n\n# IMPORTANT CONSTRAINTS\n\n- DO NOT attempt to programmatically create new sessions (no API available to agents)\n- DO provide a self-contained summary in the .matrixx/handoff.md file\n- DO include workspace-relative file paths\n- DO NOT include sensitive information (API keys, credentials, secrets)\n- DO NOT exceed 10 files in the KEY FILES section\n- DO keep the GOAL section to a single sentence or short paragraph\n\n---\n\n# EXECUTE NOW\n\nBegin by gathering programmatic context, then synthesize the handoff summary.\n";
+export declare const HANDOFF_TEMPLATE = "# Handoff Command\n\n## Purpose\n\nUse /handoff when:\n- The current session context is getting too long and quality is degrading\n- You want to start fresh while preserving essential context from this session\n- The context window is approaching capacity\n\nThis creates a detailed context summary written to .matrixx/handoff.md. The next session loads it via /pickup.\n\n---\n\n# PHASE 0: VALIDATE REQUEST\n\nBefore proceeding, confirm:\n- [ ] There is meaningful work or context in this session to preserve\n- [ ] The user wants to create a handoff summary (not just asking about it)\n\nIf the session is nearly empty or has no meaningful context, inform the user there is nothing substantial to hand off.\n\n---\n\n# PHASE 1: GATHER PROGRAMMATIC CONTEXT\n\nExecute these tools to gather concrete data:\n\n1. session_read({ session_id: \"$SESSION_ID\" }) \u2014 full session history\n2. todoread() \u2014 current task progress\n3. Bash({ command: \"git diff --stat HEAD~10..HEAD\" }) \u2014 recent file changes\n4. Bash({ command: \"git status --porcelain\" }) \u2014 uncommitted changes\n\nAnalyze the gathered outputs to understand:\n- What the user asked for (exact wording)\n- What work was completed\n- What tasks remain incomplete\n- What decisions were made\n- What files were modified or discussed\n- What patterns, constraints, or preferences were established\n\n---\n\n# PHASE 2: CALL HANDOFF TOOL\n\nCall the `handoff` tool with `action=\"create\"` and the data you gathered. The tool validates the input and writes the handoff file automatically \u2014 no manual file writing needed.\n\nUse these field mappings for the tool arguments:\n\n```\nhandoff({\n  action: \"create\",\n  topics: [\"tag1\", \"tag2\"],              // Min 1 topic tag, from session context\n  user_requests: \"verbatim user msg\",     // REQUIRED \u2014 exact wording from session_read\n  goal: \"single sentence\",                // REQUIRED \u2014 what should be done next\n  work_completed: [\"did X\", \"did Y\"],     // REQUIRED \u2014 first-person bullet points\n  current_state: \"state description\",     // REQUIRED \u2014 current codebase/task state\n  pending_tasks: [\"task1\", \"task2\"],      // Optional \u2014 tasks not yet completed\n  key_files: [{path, purpose}],           // Optional \u2014 max 10, workspace-relative paths\n  important_decisions: [{decision, rationale}], // Optional \u2014 key decisions made\n  explicit_constraints: [\"verbatim\"],     // Optional \u2014 verbatim constraints only\n  context_for_continuation: \"...\"         // Optional \u2014 additional context\n})\n```\n\n---\n\n# PHASE 3: INFORM USER\n\nAfter the tool call completes, inform the user:\n\n```\nHandoff saved to .matrixx/handoff.md. Use /pickup in a new opencode session to load this context.\n```\n\n---\n\n# IMPORTANT CONSTRAINTS\n\n- DO gather programmatic context before calling the tool (Phase 1 is mandatory)\n- DO extract user_requests verbatim from session_read output (do not paraphrase)\n- DO keep goal to a single sentence\n- DO use workspace-relative paths for key_files\n- DO NOT attempt to create new sessions programmatically\n- DO NOT exceed 10 files in key_files (max 10)\n- DO NOT include sensitive information (API keys, credentials, secrets)\n- DO use first person perspective for work_completed items\n- DO use plain text with bullets for descriptions (no markdown headers)\n";

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

@@ -1 +1 @@
-export declare const PICKUP_TEMPLATE = "# Pickup Command\n\n## Purpose\n\nUse /pickup to load handoff context from a previous session.\nThis reads the .matrixx/handoff.md file created by /handoff and uses it as context for this session.\n\n---\n\n# PHASE 1: LOAD HANDOFF FILE\n\n1. Read the file .matrixx/handoff.md using the Read tool\n2. If the file does not exist, inform the user:\n   \"No handoff context found. Run /handoff in a previous session first to create one.\"\n   Then STOP \u2014 do not proceed to Phase 2.\n\n---\n\n# PHASE 2: ARCHIVE THE FILE\n\nAfter successfully reading the handoff content:\n\n1. Rename .matrixx/handoff.md to .matrixx/handoff.consumed.md using Bash:\n   Bash({ command: \"mv .matrixx/handoff.md .matrixx/handoff.consumed.md\" })\n\nThis prevents the same handoff from being picked up again.\n\n---\n\n# PHASE 3: APPLY CONTEXT\n\n1. Acknowledge the loaded context to the user with a brief summary:\n   - What the previous session was working on (from GOAL section)\n   - What was completed (from WORK COMPLETED section)\n   - What remains (from PENDING TASKS section)\n\n2. State: \"Handoff context loaded. Ready to continue.\"\n\n3. If the user provided additional instructions with the /pickup command, begin working on those immediately using the handoff context.\n\n---\n\n# IMPORTANT CONSTRAINTS\n\n- DO read the handoff file using the Read tool \u2014 do not guess or fabricate context\n- DO archive the file after reading to prevent duplicate pickups\n- DO NOT modify the handoff content \u2014 use it as-is for context\n- DO NOT attempt to load handoff.consumed.md \u2014 that is a previously consumed handoff\n- DO summarize the context briefly \u2014 the user wants to know what was picked up\n- DO begin working immediately if the user provided a task alongside /pickup\n";
+export declare const PICKUP_TEMPLATE = "# Pickup Command\n\n## Purpose\n\nUse /pickup to load handoff context from a previous session.\n\n---\n\n# PHASE 1: READ HANDOFF\n\nCall handoff({ action: \"read\" }) to load the handoff context.\n\nIf the response starts with Error:, inform the user:\n\"No handoff context found. Run /handoff in a previous session first to create one.\"\nThen STOP \u2014 do not proceed.\n\n---\n\n# PHASE 2: ACKNOWLEDGE\n\nSummarize the loaded context to the user:\n- What the previous session was working on (Goal)\n- What was completed (Work Completed)\n- What remains (Pending Tasks)\n\nThen state: \"Handoff context loaded. Ready to continue.\"\n\n---\n\n# PHASE 3: ARCHIVE\n\nCall handoff({ action: \"archive\" }) to mark the handoff as consumed.\nThis prevents it from being picked up again.\n\n---\n\n# CONSTRAINTS\n\n- DO call the handoff tool \u2014 do not read files directly\n- DO NOT modify the handoff content \u2014 use it as-is\n- DO begin working immediately if the user included a task with /pickup\n";

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

@@ -0,0 +1 @@
+export declare const PROFILE_TEMPLATE = "# /profile Command\n\n## Usage\n\n```\n/profile                  \u2192 List available profiles and show current\n/profile list            \u2192 List available profiles\n/profile show            \u2192 Show currently active profile\n/profile set <name>      \u2192 Change profile (edits project config, instructs to start new session)\n/profile set <name> --global  \u2192 Change profile globally (~/.config/opencode/matrixx.jsonc)\n/profile set <name> --project \u2192 Change profile project-scoped (.opencode/matrixx.jsonc)\n```\n\n## Available Profiles\n\n| Profile | Description | Key Characteristic |\n|---------|-------------|-------------------|\n| free | Zero-cost, uses only free/open models | Kimi K2.5 Free, Grok (free), GLM |\n| budget | Cost-optimized for tight budgets | Sonnet/Haiku mix, no Opus |\n| economy | Balanced cost and capability | Primarily Sonnet/Haiku |\n| balanced | Default \u2014 best overall value | Opus/Sonnet/Haiku tiered |\n| performance | Maximum quality, no compromises | Opus for all heavy agents |\n| go | Premium OpenCode Go subscription | Kimi K2.6, DeepSeek V4 Pro, GLM 5.1 |\n\n## How It Works\n\nEach profile sets the `model` field on every agent and category in Matrixx's configuration. When you switch profiles, the agent models are swapped accordingly.\n\nThe profile name is stored in your `matrixx.json` or `matrixx.jsonc` config file. On the next session, Matrixx reads it and applies the profile's model mapping, merging it with any explicit per-agent overrides you may have set.\n\n## Task: Change the Profile\n\nFollow these steps:\n\n### Step 1: Know the Current Config Location\n\nMatrixx reads config from two locations (user config wins over project config):\n- **Project**: `.opencode/matrixx.json` or `.opencode/matrixx.jsonc`\n- **Global**: `~/.config/opencode/matrixx.json` or `~/.config/opencode/matrixx.jsonc`\n\n### Step 2: Determine Which Config File to Edit\n\n- `--global` \u2192 Edit `~/.config/opencode/matrixx.jsonc`\n- `--project` (default) \u2192 Edit `.opencode/matrixx.jsonc`\n- If no flag and neither file exists, use `--project`\n\n### Step 3: Read the Target Config File\n\nUse the `read` tool to read the config file.\n\n### Step 4: Validate the Requested Profile\n\nIf the user asked for `/profile set <name>`, verify `<name>` is in the table above. If not, report the valid profiles and stop.\n\n### Step 5: Update the `profile` Key\n\nSet `\"profile\": \"<name>\"` in the config JSON. If the `profile` key already exists, update it. If it doesn't exist, add it at the top level. Do NOT modify any other keys.\n\n### Step 6: Write the Config File Back\n\nUse the `write` tool (or `edit` tool for minimal changes) to save the updated config.\n\n### Step 7: Confirm and Advise\n\nTell the user:\n1. The profile has been changed to `<name>`\n2. For the change to take effect, they MUST start a new session (`/new` or restart OpenCode)\n3. If they want session-level switching without restarting, suggest using the profile with `--global` or `--project` as appropriate\n\n### Step 8: If `/profile` Was Called Without Arguments\n\nJust list the available profiles and show the current configuration's profile value.";

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

@@ -1 +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";
+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 `delegate_agent`:\n\n```\n// Agent 1: Find the refactoring target\ndelegate_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\ndelegate_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\ndelegate_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\ndelegate_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\ndelegate_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\ndelegate_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/types.d.ts

@@ -1,6 +1,3 @@
 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 BuiltinCommandName = "init-deep" | "matrix-loop" | "cancel-loop" | "ulw-loop" | "refactor" | "start-work" | "stop-continuation" | "handoff" | "pickup" | "remove-deadcode" | "profile" | "end-ultrawork";
 export type BuiltinCommands = Record<string, CommandDefinition>;

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

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

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

@@ -1,4 +1,2 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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

@@ -1,4 +1,3 @@
 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/frontend-a11y.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_A11Y_SKILL_NAME = "frontend-a11y";
+export declare const frontendA11ySkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/frontend-build-tooling.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_BUILD_TOOLING_SKILL_NAME = "frontend-build-tooling";
+export declare const frontendBuildToolingSkill: BuiltinSkill;

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

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_PERF_SKILL_NAME = "frontend-perf";
+export declare const frontendPerfSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/frontend-react-nextjs.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_REACT_NEXTJS_SKILL_NAME = "react-nextjs-patterns";
+export declare const reactNextjsPatternsSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/frontend-state-data.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_STATE_DATA_SKILL_NAME = "frontend-state-data";
+export declare const frontendStateDataSkill: BuiltinSkill;

package/dist/features/builtin-skills/skills/frontend-svelte-sveltekit.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_SVELTE_SVELTEKIT_SKILL_NAME = "svelte-sveltekit-patterns";
+export declare const svelteSveltekitPatternsSkill: BuiltinSkill;

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

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+export declare const FRONTEND_TESTING_SKILL_NAME = "frontend-testing";
+export declare const frontendTestingSkill: BuiltinSkill;

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

@@ -1,43 +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 { documentReaderSkill } from "./document-reader";
+export { dslCodegenSkill } from "./dsl-codegen";
+export { dslCompositionSkill } from "./dsl-composition";
 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 { dslPyecoreAdvancedSkill } from "./dsl-pyecore-advanced";
 export { dslTestingSkill } from "./dsl-testing";
+export { dslTextxEcosystemSkill } from "./dsl-textx-ecosystem";
+export { dslToolingSkill } from "./dsl-tooling";
 export { dslValidationSkill } from "./dsl-validation";
-export { dslCompositionSkill } from "./dsl-composition";
+export { frontendA11ySkill } from "./frontend-a11y";
+export { frontendBuildToolingSkill } from "./frontend-build-tooling";
+export { frontendPerfSkill } from "./frontend-perf";
+export { reactNextjsPatternsSkill } from "./frontend-react-nextjs";
+export { frontendStateDataSkill } from "./frontend-state-data";
+export { svelteSveltekitPatternsSkill } from "./frontend-svelte-sveltekit";
+export { frontendTestingSkill } from "./frontend-testing";
+export { frontendUiUxSkill } from "./frontend-ui-ux";
+export { gitMasterSkill } from "./git-master";
+export { matrixxSelfConfigSkill } from "./matrixx-self-config";
+export { agentBrowserSkill, playwrightSkill } from "./playwright";
+export { playwrightCliSkill } from "./playwright-cli";
+export { qualityGateSkill } from "./quality-gate";
+export { reviewWorkSkill } from "./review-work";
+export { securityApiSkill } from "./security-api";
 export { securityCoreSkill } from "./security-core";
-export { securitySecretsSkill } from "./security-secrets";
-export { securitySastSkill } from "./security-sast";
+export { securityCryptoSkill } from "./security-crypto";
 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";
-export { cryptoMarketAnalysisSkill } from "./crypto-market-analysis";
-export { cryptoTradingSkill } from "./crypto-trading";
-export { cryptoOnchainSkill } from "./crypto-onchain";
+export { securitySastSkill } from "./security-sast";
+export { securitySecretsSkill } from "./security-secrets";
+export { softwareDevSkill } from "./software-dev";
 export { tddEnforcerSkill } from "./tdd-enforcer";
-export { reviewWorkSkill } from "./review-work";

package/dist/features/builtin-skills/skills/matrixx-self-config.d.ts

@@ -0,0 +1,3 @@
+import type { BuiltinSkill } from "../types";
+/** Built-in skill for safe matrixx configuration editing by the orchestrator agent. */
+export declare const matrixxSelfConfigSkill: BuiltinSkill;

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

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

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

@@ -1,4 +1,2 @@
 import type { BuiltinSkill } from "../types";
-export declare const REVIEW_WORK_SKILL_NAME = "review-work";
-export declare const REVIEW_WORK_SKILL_DESCRIPTION = "Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE after completing any significant implementation work. Triggers: 'review work', 'review my work', 'review changes', 'QA my work', 'verify implementation', 'check my work', 'validate changes', 'post-implementation review'.";
 export declare const reviewWorkSkill: BuiltinSkill;