@compass-ai/nova 1.0.73 → 1.0.74

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,gFAAgF;AAChF,mBAAmB;AACnB,gFAAgF;AAEhF,cAAc,kBAAkB,CAAC;AAEjC,gFAAgF;AAChF,YAAY;AACZ,gFAAgF;AAEhF,cAAc,sBAAsB,CAAC;AAErC,gFAAgF;AAChF,WAAW;AACX,gFAAgF;AAEhF,2BAA2B;AAC3B,OAAO,EAAE,gBAAgB,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAE/E,uCAAuC;AACvC,OAAO,EAAE,iBAAiB,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAElF,qBAAqB;AACrB,OAAO,EAAE,kBAAkB,EAAE,eAAe,EAAE,MAAM,gCAAgC,CAAC;AAErF,qBAAqB;AACrB,OAAO,EAAE,iBAAiB,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAElF,gBAAgB;AAChB,OAAO,EAAE,mBAAmB,EAAE,yBAAyB,EAAE,MAAM,qCAAqC,CAAC;AAErG,wCAAwC;AACxC,OAAO,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAC5E,OAAO,EAAE,eAAe,EAAE,qBAAqB,EAAE,WAAW,EAAE,cAAc,EAAE,cAAc,EAAE,MAAM,iCAAiC,CAAC;AACtI,OAAO,EAAE,WAAW,EAAE,eAAe,EAAE,iBAAiB,EAAE,oBAAoB,EAAE,MAAM,6BAA6B,CAAC;AAEpH,0EAA0E;AAC1E,OAAO,EAAE,kBAAkB,EAAE,MAAM,oCAAoC,CAAC;AAExE,kBAAkB;AAClB,OAAO,EAAE,kBAAkB,EAAE,eAAe,EAAE,MAAM,gCAAgC,CAAC;AAErF,oBAAoB;AACpB,OAAO,EAAE,gBAAgB,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAE/E,uBAAuB;AACvB,OAAO,EAAE,kBAAkB,EAAE,eAAe,EAAE,MAAM,gCAAgC,CAAC;AAErF,kBAAkB;AAClB,OAAO,EAAE,gBAAgB,EAAE,UAAU,EAAE,MAAM,2BAA2B,CAAC;AAEzE,0BAA0B;AAC1B,OAAO,EAAE,gBAAgB,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAE/E,gDAAgD;AAChD,OAAO,EAAE,wBAAwB,EAAE,+BAA+B,EAAE,MAAM,uCAAuC,CAAC;AAElH,kBAAkB;AAClB,OAAO,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAE5D,oBAAoB;AACpB,OAAO,EAAE,kBAAkB,EAAE,MAAM,gCAAgC,CAAC;AAEpE,0BAA0B;AAC1B,OAAO,EAAE,wBAAwB,EAAE,MAAM,sCAAsC,CAAC;AAEhF,gBAAgB;AAChB,OAAO,EAAE,cAAc,EAAE,WAAW,EAAE,iBAAiB,EAAE,MAAM,4BAA4B,CAAC;AAE5F,OAAO,EAAE,UAAU,EAAE,QAAQ,EAAE,UAAU,EAAE,MAAM,4BAA4B,CAAC;AAE9E,iBAAiB;AACjB,OAAO,EAAE,eAAe,EAAE,YAAY,EAAE,kBAAkB,EAAE,MAAM,6BAA6B,CAAC;AAEhG,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAEvE,gBAAgB;AAChB,OAAO,EAAE,eAAe,EAAE,YAAY,EAAE,kBAAkB,EAAE,MAAM,6BAA6B,CAAC;AAEhG,OAAO,EAAE,oBAAoB,EAAE,MAAM,kBAAkB,CAAC;AAExD,qBAAqB;AACrB,OAAO,EAAE,iBAAiB,EAAE,cAAc,EAAE,oBAAoB,EAAE,MAAM,+BAA+B,CAAC;AAExG,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAE7E,sBAAsB;AACtB,OAAO,EAAE,kBAAkB,EAAE,eAAe,EAAE,qBAAqB,EAAE,MAAM,gCAAgC,CAAC;AAE5G,OAAO,EAAE,aAAa,EAAE,iBAAiB,EAAE,MAAM,gCAAgC,CAAC;AAElF,6BAA6B;AAC7B,OAAO,EAAE,0BAA0B,EAAE,6BAA6B,EAAE,uBAAuB,EAAE,MAAM,yCAAyC,CAAC;AAG7I,4BAA4B;AAC5B,OAAO,EAAE,uBAAuB,EAAE,0BAA0B,EAAE,oBAAoB,EAAE,MAAM,qCAAqC,CAAC;AAEhI,4BAA4B;AAC5B,OAAO,EAAE,uBAAuB,EAAE,0BAA0B,EAAE,oBAAoB,EAAE,MAAM,qCAAqC,CAAC;AAEhI,kBAAkB;AAClB,OAAO,EAAE,gBAAgB,EAAE,mBAAmB,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAGpG,eAAe;AACf,OAAO,EAAE,WAAW,EAAE,cAAc,EAAE,QAAQ,EAAE,MAAM,wBAAwB,CAAC;AAG/E,yBAAyB;AACzB,OAAO,EAAE,uBAAuB,EAAE,0BAA0B,EAAE,oBAAoB,EAAE,MAAM,qCAAqC,CAAC;AAGhI,gFAAgF;AAChF,qBAAqB;AACrB,gFAAgF;AAEhF,kBAAkB;AAClB,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,mBAAmB,EAAE,eAAe,EAAE,iBAAiB,EAAE,MAAM,0BAA0B,CAAC;AAG1H,yBAAyB;AACzB,OAAO,EACL,oBAAoB,EACpB,mBAAmB,EACnB,uBAAuB,GACxB,MAAM,iCAAiC,CAAC;AAGzC,eAAe;AACf,OAAO,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,yBAAyB,CAAC;AAGxE,kBAAkB;AAClB,OAAO,EAAE,iBAAiB,EAAE,cAAc,EAAE,MAAM,2BAA2B,CAAC;AAE9E,kBAAkB;AAClB,OAAO,EAAE,cAAc,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AAGzE,kBAAkB;AAClB,OAAO,EAAE,gBAAgB,EAAE,MAAM,0BAA0B,CAAC;AAE5D,mBAAmB;AACnB,OAAO,EAAE,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AAE9D,gFAAgF;AAChF,YAAY;AACZ,gFAAgF;AAEhF,UAAU;AACV,OAAO,EAAE,MAAM,EAAE,MAAM,mBAAmB,CAAC;AAG3C,eAAe;AACf,OAAO,EAAE,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,oBAAoB,EAAE,IAAI,EAAE,aAAa,EAAE,MAAM,mBAAmB,CAAC;AAEtG,kBAAkB;AAClB,OAAO,EAAE,YAAY,EAAE,YAAY,EAAE,mBAAmB,EAAE,gBAAgB,EAAE,YAAY,EAAE,mBAAmB,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AAGnJ,aAAa;AACb,OAAO,EACL,eAAe,EACf,UAAU,EACV,cAAc,EACd,kBAAkB,EAClB,cAAc,EACd,UAAU,EACV,gBAAgB,EAChB,aAAa,EACb,QAAQ,EACR,SAAS,EACT,iBAAiB,EACjB,UAAU,EACV,aAAa,GACd,MAAM,mBAAmB,CAAC;AAE3B,yBAAyB;AACzB,OAAO,EACL,YAAY,EACZ,aAAa,EACb,YAAY,EACZ,aAAa,EACb,SAAS,EACT,UAAU,EACV,MAAM,EACN,IAAI,EACJ,IAAI,EACJ,OAAO,EACP,WAAW,EACX,MAAM,GACP,MAAM,wBAAwB,CAAC;AAGhC,iBAAiB;AACjB,OAAO,EACL,mBAAmB,EACnB,oBAAoB,EACpB,iBAAiB,EACjB,kBAAkB,EAClB,YAAY,EACZ,YAAY,EACZ,eAAe,EACf,mBAAmB,EACnB,gBAAgB,EAChB,YAAY,EACZ,WAAW,EACX,cAAc,GACf,MAAM,iBAAiB,CAAC;AAEzB,iBAAiB;AACjB,OAAO,EACL,cAAc,EACd,0BAA0B,EAC1B,0BAA0B,EAC1B,wBAAwB,EACxB,kBAAkB,EAClB,gBAAgB,IAAI,kBAAkB,EACtC,4BAA4B,EAC5B,oBAAoB,GACrB,MAAM,0BAA0B,CAAC;AAElC,gFAAgF;AAChF,YAAY;AACZ,gFAAgF;AAEhF,YAAY;AACZ,OAAO,EAAE,YAAY,EAAE,gBAAgB,EAAE,aAAa,EAAE,YAAY,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAErH,YAAY;AACZ,OAAO,EAAE,cAAc,EAAE,iBAAiB,EAAE,kBAAkB,EAAE,cAAc,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AAG1H,mBAAmB;AACnB,OAAO,EAAE,gBAAgB,EAAE,mBAAmB,EAAE,MAAM,yCAAyC,CAAC;AAEhG,gFAAgF;AAChF,sBAAsB;AACtB,gFAAgF;AAEhF;;GAEG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG,QAAQ,CAAC;AAEhC;;GAEG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,aAAa,CAAC;AAEtC;;GAEG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,oEAAoE,CAAC"}

package/dist/prompts/agent-prompt-generator.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Agent system prompt generator prompts.
+ *
+ * Contains the system prompt for LLM-powered generation of high-quality
+ * system prompts for Claude Code subagents.
+ */
+/**
+ * System prompt for generating agent system prompts.
+ *
+ * This prompt instructs the LLM on best practices for creating effective
+ * system prompts for Claude Code subagents.
+ */
+export declare const AGENT_PROMPT_GENERATOR_SYSTEM = "You are an expert at crafting effective system prompts for Claude Code subagents. Your goal is to create concise, actionable system prompts that help agents perform their specialized tasks excellently.\n\n## Best Practices for Claude Code Subagent System Prompts\n\n### 1. Core Principles\n\n**Be Specific and Focused**\n- Clearly define the agent's primary purpose\n- State what the agent should do, not what it shouldn't\n- Avoid vague or overly broad directives\n\n**Be Concise**\n- Keep prompts under 500 words for simple agents\n- Use bullet points and sections for clarity\n- Remove unnecessary explanations\n\n**Be Actionable**\n- Provide concrete steps or workflows\n- Include specific tool usage patterns when relevant\n- Give examples of expected output formats\n\n### 2. Essential Components\n\nEvery agent system prompt should include:\n\n1. **Purpose Statement** (1-2 sentences)\n   - What is this agent's primary function?\n   - When should it be invoked?\n\n2. **Core Capabilities** (bulleted list)\n   - What specific tasks can this agent perform?\n   - What tools will it primarily use?\n\n3. **Workflow/Strategy** (optional, for complex agents)\n   - Step-by-step approach to tasks\n   - Decision-making criteria\n   - Search or analysis strategies\n\n4. **Output Format** (when applicable)\n   - How should results be presented?\n   - File path format (e.g., filepath:line_number)\n   - Code block formatting\n\n5. **Guidelines** (optional)\n   - Key constraints or considerations\n   - Edge cases to handle\n   - What to prioritize\n\n### 3. Tool Usage Patterns\n\nWhen the agent has specific tool permissions:\n\n**Execution Tools** (Bash, Task, etc.)\n```\n## Your Approach\n1. Run diagnostic commands to understand the issue\n2. Execute fixes with appropriate error handling\n3. Verify the fix worked\n```\n\n**File Operations** (Read, Write, Edit)\n```\n## File Modification Strategy\n1. Read the current file state\n2. Make targeted edits preserving existing patterns\n3. Verify syntax and formatting\n```\n\n**Search Tools** (Glob, Grep)\n```\n## Search Strategy\n1. Start with Glob to find candidate files\n2. Use Grep to search within matching files\n3. Read relevant sections for context\n```\n\n### 4. Model-Specific Considerations\n\n**Haiku** (fast, efficient)\n- Shorter prompts (200-300 words)\n- Clear, simple workflows\n- Minimal examples\n- Best for: search, simple analysis, quick tasks\n\n**Sonnet** (balanced)\n- Standard prompts (300-500 words)\n- Moderate complexity workflows\n- Some examples and edge cases\n- Best for: most agents\n\n**Opus** (most capable)\n- Detailed prompts (400-600 words)\n- Complex decision trees\n- Multiple examples\n- Best for: complex reasoning, architecture decisions\n\n### 5. Common Patterns from Built-in Agents\n\n**Exploration/Search Agent:**\n```\nYou are a fast codebase exploration specialist.\n\n## Your Tools\n- Glob: Find files by pattern\n- Grep: Search file contents\n- Read: Examine specific files\n\n## Search Strategy\n1. Start broad, then narrow\n2. Use naming conventions (Service, Controller, etc.)\n3. Check standard locations (src/, lib/, app/)\n\n## Output Format\nfilepath:line_number - brief description\n```\n\n**Code Review Agent:**\n```\nYou are a senior code reviewer focused on security and quality.\n\n## Getting Started\n1. Identify what to review (git diff)\n2. Understand the context (read files)\n3. Apply the review checklist\n\n## Review Checklist\n\uD83D\uDD34 Critical: Security, data integrity\n\uD83D\uDFE1 Warnings: Error handling, performance\n\u2139\uFE0F Info: Code quality, best practices\n```\n\n**Testing Agent:**\n```\nYou write comprehensive, maintainable tests.\n\n## Your Process\n1. Understand what to test (read implementation)\n2. Identify test cases (happy path, edge cases, errors)\n3. Write tests following project patterns\n4. Run tests and fix failures\n```\n\n### 6. Anti-Patterns to Avoid\n\n\u274C **Don't:**\n- Include conversational fluff (\"As an AI assistant...\")\n- Repeat obvious information\n- Use overly formal or academic language\n- Include disclaimers or apologies\n- Define what Claude Code is (the agent already knows)\n- Explain general programming concepts\n- Add marketing language (\"world-class\", \"cutting-edge\")\n\n\u2705 **Do:**\n- Write in direct, imperative voice\n- Focus on the specific domain\n- Provide actionable workflows\n- Include concrete examples\n- Use clear section headers\n- Keep it professional but concise\n\n### 7. Tone and Voice\n\n- **Professional but direct** - \"You are a senior engineer\" not \"You are an AI\"\n- **Action-oriented** - Use imperatives: \"Check for...\", \"Review...\", \"Ensure...\"\n- **Confident** - State what to do, not what might be good to consider\n- **Domain-specific** - Use terminology from the agent's field\n\n## Your Task\n\nGenerate TWO things for a Claude Code subagent based on the provided context:\n\n1. **Description** (for agent frontmatter) - 1-2 sentences that clearly tell Claude WHEN to use this agent\n   - Focus on the trigger conditions and use cases\n   - Must be concise and scannable\n   - Examples:\n     - \"Fast codebase exploration. Use for searching files, code patterns, and understanding structure.\"\n     - \"Expert code reviewer. Use proactively after writing or modifying code to check for quality, security, and best practices.\"\n     - \"Writes comprehensive unit tests. Use when adding new features or refactoring code that needs test coverage.\"\n\n2. **System Prompt** - The full system prompt that defines how the agent behaves\n   - Follow all best practices above\n   - Be appropriate for the agent's model (adjust length/complexity)\n   - Include relevant sections (purpose, tools, workflow, output, guidelines)\n   - Use clear, actionable language\n   - Be concise and focused on the agent's specific role\n\n**Output Format**: Respond with ONLY a JSON object in this exact format:\n\n```json\n{\n  \"description\": \"Your 1-2 sentence description here\",\n  \"systemPrompt\": \"Your full system prompt here\"\n}\n```\n\nNo preamble, no explanation - just the JSON object.";
+/**
+ * User prompt builder for agent system prompt generation.
+ *
+ * @param context - Information about the agent being created
+ * @returns The user prompt for the LLM
+ */
+export declare function buildAgentPromptGenerationPrompt(context: {
+    name: string;
+    description: string;
+    tools?: string[];
+    model: string;
+}): string;
+//# sourceMappingURL=agent-prompt-generator.d.ts.map

package/dist/prompts/agent-prompt-generator.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-prompt-generator.d.ts","sourceRoot":"","sources":["../../src/prompts/agent-prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,6BAA6B,k/LAoMU,CAAC;AAErD;;;;;GAKG;AACH,wBAAgB,gCAAgC,CAAC,OAAO,EAAE;IACxD,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;IACjB,KAAK,EAAE,MAAM,CAAC;CACf,GAAG,MAAM,CA8BT"}

package/dist/prompts/agent-prompt-generator.js

@@ -0,0 +1,244 @@
+/**
+ * Agent system prompt generator prompts.
+ *
+ * Contains the system prompt for LLM-powered generation of high-quality
+ * system prompts for Claude Code subagents.
+ */
+/**
+ * System prompt for generating agent system prompts.
+ *
+ * This prompt instructs the LLM on best practices for creating effective
+ * system prompts for Claude Code subagents.
+ */
+export const AGENT_PROMPT_GENERATOR_SYSTEM = `You are an expert at crafting effective system prompts for Claude Code subagents. Your goal is to create concise, actionable system prompts that help agents perform their specialized tasks excellently.
+
+## Best Practices for Claude Code Subagent System Prompts
+
+### 1. Core Principles
+
+**Be Specific and Focused**
+- Clearly define the agent's primary purpose
+- State what the agent should do, not what it shouldn't
+- Avoid vague or overly broad directives
+
+**Be Concise**
+- Keep prompts under 500 words for simple agents
+- Use bullet points and sections for clarity
+- Remove unnecessary explanations
+
+**Be Actionable**
+- Provide concrete steps or workflows
+- Include specific tool usage patterns when relevant
+- Give examples of expected output formats
+
+### 2. Essential Components
+
+Every agent system prompt should include:
+
+1. **Purpose Statement** (1-2 sentences)
+   - What is this agent's primary function?
+   - When should it be invoked?
+
+2. **Core Capabilities** (bulleted list)
+   - What specific tasks can this agent perform?
+   - What tools will it primarily use?
+
+3. **Workflow/Strategy** (optional, for complex agents)
+   - Step-by-step approach to tasks
+   - Decision-making criteria
+   - Search or analysis strategies
+
+4. **Output Format** (when applicable)
+   - How should results be presented?
+   - File path format (e.g., filepath:line_number)
+   - Code block formatting
+
+5. **Guidelines** (optional)
+   - Key constraints or considerations
+   - Edge cases to handle
+   - What to prioritize
+
+### 3. Tool Usage Patterns
+
+When the agent has specific tool permissions:
+
+**Execution Tools** (Bash, Task, etc.)
+\`\`\`
+## Your Approach
+1. Run diagnostic commands to understand the issue
+2. Execute fixes with appropriate error handling
+3. Verify the fix worked
+\`\`\`
+
+**File Operations** (Read, Write, Edit)
+\`\`\`
+## File Modification Strategy
+1. Read the current file state
+2. Make targeted edits preserving existing patterns
+3. Verify syntax and formatting
+\`\`\`
+
+**Search Tools** (Glob, Grep)
+\`\`\`
+## Search Strategy
+1. Start with Glob to find candidate files
+2. Use Grep to search within matching files
+3. Read relevant sections for context
+\`\`\`
+
+### 4. Model-Specific Considerations
+
+**Haiku** (fast, efficient)
+- Shorter prompts (200-300 words)
+- Clear, simple workflows
+- Minimal examples
+- Best for: search, simple analysis, quick tasks
+
+**Sonnet** (balanced)
+- Standard prompts (300-500 words)
+- Moderate complexity workflows
+- Some examples and edge cases
+- Best for: most agents
+
+**Opus** (most capable)
+- Detailed prompts (400-600 words)
+- Complex decision trees
+- Multiple examples
+- Best for: complex reasoning, architecture decisions
+
+### 5. Common Patterns from Built-in Agents
+
+**Exploration/Search Agent:**
+\`\`\`
+You are a fast codebase exploration specialist.
+
+## Your Tools
+- Glob: Find files by pattern
+- Grep: Search file contents
+- Read: Examine specific files
+
+## Search Strategy
+1. Start broad, then narrow
+2. Use naming conventions (Service, Controller, etc.)
+3. Check standard locations (src/, lib/, app/)
+
+## Output Format
+filepath:line_number - brief description
+\`\`\`
+
+**Code Review Agent:**
+\`\`\`
+You are a senior code reviewer focused on security and quality.
+
+## Getting Started
+1. Identify what to review (git diff)
+2. Understand the context (read files)
+3. Apply the review checklist
+
+## Review Checklist
+🔴 Critical: Security, data integrity
+🟡 Warnings: Error handling, performance
+ℹ️ Info: Code quality, best practices
+\`\`\`
+
+**Testing Agent:**
+\`\`\`
+You write comprehensive, maintainable tests.
+
+## Your Process
+1. Understand what to test (read implementation)
+2. Identify test cases (happy path, edge cases, errors)
+3. Write tests following project patterns
+4. Run tests and fix failures
+\`\`\`
+
+### 6. Anti-Patterns to Avoid
+
+❌ **Don't:**
+- Include conversational fluff ("As an AI assistant...")
+- Repeat obvious information
+- Use overly formal or academic language
+- Include disclaimers or apologies
+- Define what Claude Code is (the agent already knows)
+- Explain general programming concepts
+- Add marketing language ("world-class", "cutting-edge")
+
+✅ **Do:**
+- Write in direct, imperative voice
+- Focus on the specific domain
+- Provide actionable workflows
+- Include concrete examples
+- Use clear section headers
+- Keep it professional but concise
+
+### 7. Tone and Voice
+
+- **Professional but direct** - "You are a senior engineer" not "You are an AI"
+- **Action-oriented** - Use imperatives: "Check for...", "Review...", "Ensure..."
+- **Confident** - State what to do, not what might be good to consider
+- **Domain-specific** - Use terminology from the agent's field
+
+## Your Task
+
+Generate TWO things for a Claude Code subagent based on the provided context:
+
+1. **Description** (for agent frontmatter) - 1-2 sentences that clearly tell Claude WHEN to use this agent
+   - Focus on the trigger conditions and use cases
+   - Must be concise and scannable
+   - Examples:
+     - "Fast codebase exploration. Use for searching files, code patterns, and understanding structure."
+     - "Expert code reviewer. Use proactively after writing or modifying code to check for quality, security, and best practices."
+     - "Writes comprehensive unit tests. Use when adding new features or refactoring code that needs test coverage."
+
+2. **System Prompt** - The full system prompt that defines how the agent behaves
+   - Follow all best practices above
+   - Be appropriate for the agent's model (adjust length/complexity)
+   - Include relevant sections (purpose, tools, workflow, output, guidelines)
+   - Use clear, actionable language
+   - Be concise and focused on the agent's specific role
+
+**Output Format**: Respond with ONLY a JSON object in this exact format:
+
+\`\`\`json
+{
+  "description": "Your 1-2 sentence description here",
+  "systemPrompt": "Your full system prompt here"
+}
+\`\`\`
+
+No preamble, no explanation - just the JSON object.`;
+/**
+ * User prompt builder for agent system prompt generation.
+ *
+ * @param context - Information about the agent being created
+ * @returns The user prompt for the LLM
+ */
+export function buildAgentPromptGenerationPrompt(context) {
+    const { name, description, tools, model } = context;
+    let prompt = `Generate an optimized description and system prompt for a Claude Code subagent with these specifications:
+
+**Agent Name:** ${name}
+
+**User's Description:** ${description}
+
+**Model:** ${model}`;
+    if (tools && tools.length > 0) {
+        prompt += `
+
+**Available Tools:** ${tools.join(', ')}`;
+    }
+    else {
+        prompt += `
+
+**Available Tools:** All tools (full access)`;
+    }
+    prompt += `
+
+Based on the user's description above, create:
+1. An optimized 1-2 sentence description that clearly tells Claude WHEN to use this agent
+2. A concise, actionable system prompt that helps this agent excel at its specialized task
+
+Follow the best practices outlined in your instructions.`;
+    return prompt;
+}
+//# sourceMappingURL=agent-prompt-generator.js.map

package/dist/prompts/agent-prompt-generator.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-prompt-generator.js","sourceRoot":"","sources":["../../src/prompts/agent-prompt-generator.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,6BAA6B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oDAoMO,CAAC;AAErD;;;;;GAKG;AACH,MAAM,UAAU,gCAAgC,CAAC,OAKhD;IACC,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,KAAK,EAAE,KAAK,EAAE,GAAG,OAAO,CAAC;IAEpD,IAAI,MAAM,GAAG;;kBAEG,IAAI;;0BAEI,WAAW;;aAExB,KAAK,EAAE,CAAC;IAEnB,IAAI,KAAK,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC9B,MAAM,IAAI;;uBAES,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;IACxC,CAAC;SAAM,CAAC;QACN,MAAM,IAAI;;6CAE+B,CAAC;IAC5C,CAAC;IAED,MAAM,IAAI;;;;;;yDAM6C,CAAC;IAExD,OAAO,MAAM,CAAC;AAChB,CAAC"}

package/dist/prompts/commit-message.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Prompts for generating conventional commit messages from git diffs.
+ *
+ * Contains prompts and guidelines for generating well-formatted conventional
+ * commit messages that follow best practices.
+ */
+/**
+ * System prompt for generating conventional commit messages.
+ * Provides comprehensive instructions for analyzing git diffs and
+ * creating appropriate commit messages following the conventional
+ * commits specification.
+ */
+export declare const COMMIT_MESSAGE_GENERATION_PROMPT = "Generate a conventional commit message that accurately and comprehensively summarizes **all** changes staged since the previous commit.\n\n**Instructions:**\n1. **Format Selection:**\n   - For **simple, focused changes** (1-2 files, single purpose): Use single-line format\n   - For **complex or multi-faceted changes** (multiple files, multiple purposes): Use multi-line format with bullet points\n\n2. **Single-Line Format:**\n   - Use format: `type(scope): description`\n   - Example: `feat(auth): add OAuth2 login integration`\n\n3. **Multi-Line Format:**\n   - **First line:** Conventional commit format (type(scope): subject)\n   - **Second line:** Empty line\n   - **Following lines:** Bullet points (using `-` or `*`) describing specific changes\n   - Each bullet point should be concise, actionable, and describe a distinct change\n\n4. **Conventional Commit Format Rules:**\n   - Use format: `type(scope): description`\n   - **Types:** feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert, prompt\n   - **Scope:** Optional, use lowercase (e.g., api, ui, auth, database)\n   - **Description:** Imperative mood, lowercase, no period, max 50 chars\n   - **Breaking changes:** Add `!` after type/scope or use `BREAKING CHANGE:` in footer\n\n5. **Best Practices:**\n   - Use imperative mood: \"add feature\" not \"added feature\"\n   - Be specific, comprehensive, and concise\n   - Focus on the \"what\" and \"why\", not the \"how\"\n   - Group related changes under appropriate types\n   - Use consistent terminology across commits\n   - Each bullet point should describe a distinct, significant change\n   - The commit message must be bounded to the actual staged code\n\n6. **Type Guidelines:**\n   - `feat`: New features or functionality\n   - `fix`: Bug fixes\n   - `docs`: Documentation changes only\n   - `style`: Code formatting, missing semicolons (no logic changes)\n   - `refactor`: Code restructuring without changing functionality\n   - `perf`: Performance improvements\n   - `test`: Adding/updating tests\n   - `build`: Build system or dependency changes\n   - `ci`: CI configuration changes\n   - `chore`: Maintenance tasks, tooling updates\n   - `revert`: Reverting previous commits\n   - `prompt`: Updates made to prompts used by LLMs\n\n**Single-Line Examples:**\n- `feat(auth): add OAuth2 login integration`\n- `fix(api): resolve memory leak in user sessions`\n- `docs: update installation guide for v2.0`\n- `refactor(utils): extract date formatting to shared helper`\n\n**Multi-Line Examples:**\n\nExample 1:\nfeat(api): implement user management endpoints\n\n- Add POST /users endpoint for user creation\n- Add GET /users/:id endpoint for user retrieval\n- Add PUT /users/:id endpoint for user updates\n- Add DELETE /users/:id endpoint for user deletion\n- Implement input validation and error handling\n\nExample 2:\nrefactor(auth): modernize authentication system\n\n- Replace session-based auth with JWT tokens\n- Update login and logout endpoints\n- Migrate user credentials to bcrypt hashing\n- Add refresh token rotation mechanism\n\nPlease analyze the following staged changes and generate an appropriate conventional commit message:";
+/**
+ * Builds the user message for commit message generation with the git diff.
+ * This should be used with COMMIT_MESSAGE_GENERATION_PROMPT as the system prompt.
+ *
+ * @param stagedDiff - The output from git diff --staged
+ * @returns Formatted user message with the diff
+ */
+export declare function buildCommitMessagePrompt(stagedDiff: string): string;
+/**
+ * Type definitions for conventional commits.
+ */
+export declare const CONVENTIONAL_COMMIT_TYPES: readonly ["feat", "fix", "docs", "style", "refactor", "perf", "test", "build", "ci", "chore", "revert", "prompt"];
+export type ConventionalCommitType = typeof CONVENTIONAL_COMMIT_TYPES[number];
+/**
+ * Description of each conventional commit type.
+ */
+export declare const COMMIT_TYPE_DESCRIPTIONS: Record<ConventionalCommitType, string>;
+/**
+ * Example commit messages for each type.
+ */
+export declare const COMMIT_MESSAGE_EXAMPLES: Record<ConventionalCommitType, string[]>;
+//# sourceMappingURL=commit-message.d.ts.map

package/dist/prompts/commit-message.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commit-message.d.ts","sourceRoot":"","sources":["../../src/prompts/commit-message.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,gCAAgC,snGAwEwD,CAAC;AAEtG;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CAOnE;AAED;;GAEG;AACH,eAAO,MAAM,yBAAyB,mHAa5B,CAAC;AAEX,MAAM,MAAM,sBAAsB,GAAG,OAAO,yBAAyB,CAAC,MAAM,CAAC,CAAC;AAE9E;;GAEG;AACH,eAAO,MAAM,wBAAwB,EAAE,MAAM,CAAC,sBAAsB,EAAE,MAAM,CAa3E,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,uBAAuB,EAAE,MAAM,CAAC,sBAAsB,EAAE,MAAM,EAAE,CAgD5E,CAAC"}

package/dist/prompts/commit-message.js

@@ -0,0 +1,187 @@
+/**
+ * Prompts for generating conventional commit messages from git diffs.
+ *
+ * Contains prompts and guidelines for generating well-formatted conventional
+ * commit messages that follow best practices.
+ */
+/**
+ * System prompt for generating conventional commit messages.
+ * Provides comprehensive instructions for analyzing git diffs and
+ * creating appropriate commit messages following the conventional
+ * commits specification.
+ */
+export const COMMIT_MESSAGE_GENERATION_PROMPT = `Generate a conventional commit message that accurately and comprehensively summarizes **all** changes staged since the previous commit.
+
+**Instructions:**
+1. **Format Selection:**
+   - For **simple, focused changes** (1-2 files, single purpose): Use single-line format
+   - For **complex or multi-faceted changes** (multiple files, multiple purposes): Use multi-line format with bullet points
+
+2. **Single-Line Format:**
+   - Use format: \`type(scope): description\`
+   - Example: \`feat(auth): add OAuth2 login integration\`
+
+3. **Multi-Line Format:**
+   - **First line:** Conventional commit format (type(scope): subject)
+   - **Second line:** Empty line
+   - **Following lines:** Bullet points (using \`-\` or \`*\`) describing specific changes
+   - Each bullet point should be concise, actionable, and describe a distinct change
+
+4. **Conventional Commit Format Rules:**
+   - Use format: \`type(scope): description\`
+   - **Types:** feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert, prompt
+   - **Scope:** Optional, use lowercase (e.g., api, ui, auth, database)
+   - **Description:** Imperative mood, lowercase, no period, max 50 chars
+   - **Breaking changes:** Add \`!\` after type/scope or use \`BREAKING CHANGE:\` in footer
+
+5. **Best Practices:**
+   - Use imperative mood: "add feature" not "added feature"
+   - Be specific, comprehensive, and concise
+   - Focus on the "what" and "why", not the "how"
+   - Group related changes under appropriate types
+   - Use consistent terminology across commits
+   - Each bullet point should describe a distinct, significant change
+   - The commit message must be bounded to the actual staged code
+
+6. **Type Guidelines:**
+   - \`feat\`: New features or functionality
+   - \`fix\`: Bug fixes
+   - \`docs\`: Documentation changes only
+   - \`style\`: Code formatting, missing semicolons (no logic changes)
+   - \`refactor\`: Code restructuring without changing functionality
+   - \`perf\`: Performance improvements
+   - \`test\`: Adding/updating tests
+   - \`build\`: Build system or dependency changes
+   - \`ci\`: CI configuration changes
+   - \`chore\`: Maintenance tasks, tooling updates
+   - \`revert\`: Reverting previous commits
+   - \`prompt\`: Updates made to prompts used by LLMs
+
+**Single-Line Examples:**
+- \`feat(auth): add OAuth2 login integration\`
+- \`fix(api): resolve memory leak in user sessions\`
+- \`docs: update installation guide for v2.0\`
+- \`refactor(utils): extract date formatting to shared helper\`
+
+**Multi-Line Examples:**
+
+Example 1:
+feat(api): implement user management endpoints
+
+- Add POST /users endpoint for user creation
+- Add GET /users/:id endpoint for user retrieval
+- Add PUT /users/:id endpoint for user updates
+- Add DELETE /users/:id endpoint for user deletion
+- Implement input validation and error handling
+
+Example 2:
+refactor(auth): modernize authentication system
+
+- Replace session-based auth with JWT tokens
+- Update login and logout endpoints
+- Migrate user credentials to bcrypt hashing
+- Add refresh token rotation mechanism
+
+Please analyze the following staged changes and generate an appropriate conventional commit message:`;
+/**
+ * Builds the user message for commit message generation with the git diff.
+ * This should be used with COMMIT_MESSAGE_GENERATION_PROMPT as the system prompt.
+ *
+ * @param stagedDiff - The output from git diff --staged
+ * @returns Formatted user message with the diff
+ */
+export function buildCommitMessagePrompt(stagedDiff) {
+    return `Please analyze the following staged changes and generate an appropriate conventional commit message. Provide only the commit message (no additional explanation or commentary).
+
+**Staged Diff:**
+\`\`\`diff
+${stagedDiff}
+\`\`\``;
+}
+/**
+ * Type definitions for conventional commits.
+ */
+export const CONVENTIONAL_COMMIT_TYPES = [
+    'feat',
+    'fix',
+    'docs',
+    'style',
+    'refactor',
+    'perf',
+    'test',
+    'build',
+    'ci',
+    'chore',
+    'revert',
+    'prompt',
+];
+/**
+ * Description of each conventional commit type.
+ */
+export const COMMIT_TYPE_DESCRIPTIONS = {
+    feat: 'New features or functionality',
+    fix: 'Bug fixes',
+    docs: 'Documentation changes only',
+    style: 'Code formatting (no logic changes)',
+    refactor: 'Code restructuring without changing functionality',
+    perf: 'Performance improvements',
+    test: 'Adding/updating tests',
+    build: 'Build system or dependency changes',
+    ci: 'CI configuration changes',
+    chore: 'Maintenance tasks, tooling updates',
+    revert: 'Reverting previous commits',
+    prompt: 'Updates to LLM prompts',
+};
+/**
+ * Example commit messages for each type.
+ */
+export const COMMIT_MESSAGE_EXAMPLES = {
+    feat: [
+        'feat(auth): add OAuth2 login integration',
+        'feat(api): implement user profile endpoints',
+    ],
+    fix: [
+        'fix(api): resolve memory leak in user sessions',
+        'fix(ui): correct button alignment on mobile',
+    ],
+    docs: [
+        'docs: update installation guide for v2.0',
+        'docs(api): add examples for authentication',
+    ],
+    style: [
+        'style: format code with prettier',
+        'style(ui): fix indentation in components',
+    ],
+    refactor: [
+        'refactor(utils): extract date formatting to shared helper',
+        'refactor(api): simplify error handling logic',
+    ],
+    perf: [
+        'perf(db): add indexes to user queries',
+        'perf(ui): optimize image loading',
+    ],
+    test: [
+        'test(api): add integration tests for user endpoints',
+        'test(utils): add unit tests for date helpers',
+    ],
+    build: [
+        'build(deps): upgrade typescript to v5.0',
+        'build: configure webpack for production',
+    ],
+    ci: [
+        'ci: add automated testing workflow',
+        'ci(github): configure dependabot',
+    ],
+    chore: [
+        'chore: update dependencies',
+        'chore(deps): bump lodash to v4.17.21',
+    ],
+    revert: [
+        'revert: revert feat(auth): add OAuth2 login',
+    ],
+    prompt: [
+        'prompt: improve commit message generation instructions',
+        'prompt(compaction): add code snippet preservation',
+    ],
+};
+//# sourceMappingURL=commit-message.js.map

package/dist/prompts/commit-message.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"commit-message.js","sourceRoot":"","sources":["../../src/prompts/commit-message.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qGAwEqD,CAAC;AAEtG;;;;;;GAMG;AACH,MAAM,UAAU,wBAAwB,CAAC,UAAkB;IACzD,OAAO;;;;EAIP,UAAU;OACL,CAAC;AACR,CAAC;AAED;;GAEG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACvC,MAAM;IACN,KAAK;IACL,MAAM;IACN,OAAO;IACP,UAAU;IACV,MAAM;IACN,MAAM;IACN,OAAO;IACP,IAAI;IACJ,OAAO;IACP,QAAQ;IACR,QAAQ;CACA,CAAC;AAIX;;GAEG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAA2C;IAC9E,IAAI,EAAE,+BAA+B;IACrC,GAAG,EAAE,WAAW;IAChB,IAAI,EAAE,4BAA4B;IAClC,KAAK,EAAE,oCAAoC;IAC3C,QAAQ,EAAE,mDAAmD;IAC7D,IAAI,EAAE,0BAA0B;IAChC,IAAI,EAAE,uBAAuB;IAC7B,KAAK,EAAE,oCAAoC;IAC3C,EAAE,EAAE,0BAA0B;IAC9B,KAAK,EAAE,oCAAoC;IAC3C,MAAM,EAAE,4BAA4B;IACpC,MAAM,EAAE,wBAAwB;CACjC,CAAC;AAEF;;GAEG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAA6C;IAC/E,IAAI,EAAE;QACJ,0CAA0C;QAC1C,6CAA6C;KAC9C;IACD,GAAG,EAAE;QACH,gDAAgD;QAChD,6CAA6C;KAC9C;IACD,IAAI,EAAE;QACJ,0CAA0C;QAC1C,4CAA4C;KAC7C;IACD,KAAK,EAAE;QACL,kCAAkC;QAClC,0CAA0C;KAC3C;IACD,QAAQ,EAAE;QACR,2DAA2D;QAC3D,8CAA8C;KAC/C;IACD,IAAI,EAAE;QACJ,uCAAuC;QACvC,kCAAkC;KACnC;IACD,IAAI,EAAE;QACJ,qDAAqD;QACrD,8CAA8C;KAC/C;IACD,KAAK,EAAE;QACL,yCAAyC;QACzC,yCAAyC;KAC1C;IACD,EAAE,EAAE;QACF,oCAAoC;QACpC,kCAAkC;KACnC;IACD,KAAK,EAAE;QACL,4BAA4B;QAC5B,sCAAsC;KACvC;IACD,MAAM,EAAE;QACN,6CAA6C;KAC9C;IACD,MAAM,EAAE;QACN,wDAAwD;QACxD,mDAAmD;KACpD;CACF,CAAC"}

package/dist/prompts/conversation.d.ts

@@ -0,0 +1,51 @@
+/**
+ * Conversation-related prompts for compaction and summarization.
+ *
+ * Contains prompts used for intelligent conversation summarization
+ * to reduce token usage while preserving essential context.
+ */
+/**
+ * System prompt for conversation compaction.
+ * Guides the AI to create concise but comprehensive summaries.
+ */
+export declare const CONVERSATION_COMPACTION_SYSTEM_PROMPT = "You are a conversation summarizer for a development assistant called Compass. Your task is to create a concise but comprehensive summary of the conversation history that preserves all essential context for continued development work.\n\nYour summary MUST include:\n1. **Key Decisions Made**: Any architectural, design, or implementation decisions\n2. **Code Changes**: Files created, modified, or deleted with brief descriptions\n3. **Current State**: What has been accomplished and what remains to be done\n4. **Important Context**: Technical constraints, user preferences, or requirements mentioned\n5. **Pending Tasks**: Any incomplete work or next steps discussed\n6. **Active Plan & Task IDs**: If there is an active plan being executed, preserve the plan ID, task IDs, and their statuses VERBATIM. These are critical references to on-disk state that cannot be reconstructed from summaries alone. Look for patterns like \"plan ID:\", \"planId:\", \"task-\", or \"[ACTIVE PLAN CONTEXT\" blocks and preserve them exactly.\n\nFormat your summary as structured markdown with clear sections. Be concise but don't omit critical information that would be needed to continue the conversation effectively.\n\nIf code snippets are essential for context (e.g., specific implementations, configurations, or patterns), include them in fenced code blocks.\n\nDo NOT include:\n- Pleasantries or conversational filler\n- Redundant information\n- Detailed explanations that can be inferred from code\n- Historical context that's no longer relevant";
+/**
+ * Options for building compaction prompts.
+ */
+export interface CompactionPromptOptions {
+    /** Whether to preserve code snippets */
+    includeCodeSnippets?: boolean;
+    /** Whether to include file paths */
+    includeFilePaths?: boolean;
+}
+/**
+ * Message structure for compaction.
+ */
+export interface CompactionMessage {
+    role: 'user' | 'assistant';
+    content: string;
+    timestamp?: string;
+}
+/**
+ * Builds the user prompt for conversation compaction.
+ *
+ * @param messages - Array of messages to summarize
+ * @param options - Compaction options
+ * @returns Formatted compaction prompt
+ */
+export declare function buildConversationCompactionPrompt(messages: CompactionMessage[], options?: CompactionPromptOptions): string;
+/**
+ * System prompt for plan-approval compaction.
+ * Used to compact exploratory context when transitioning from planning to execution.
+ * Focuses on preserving what's needed for implementation, discarding raw exploration data.
+ */
+export declare const PLAN_APPROVAL_COMPACTION_SYSTEM_PROMPT = "You are a conversation summarizer for a development assistant called Compass. A user just approved an implementation plan, and you need to summarize the exploratory conversation that preceded it so the assistant can execute the plan efficiently.\n\nYour summary MUST include:\n1. **User's Original Request**: The task or feature the user asked for, including any clarifications\n2. **Architectural Decisions**: Design choices, patterns selected, and constraints discovered\n3. **File Paths & Project Structure**: All relevant file paths, directory layout, and module relationships discovered\n4. **Coding Patterns & Conventions**: Code style, naming conventions, frameworks, and patterns observed in the codebase\n5. **The Approved Plan**: The implementation plan that was approved (task breakdown, file changes, approach)\n6. **Plan & Task IDs**: Preserve the plan ID and all task IDs VERBATIM (e.g., \"plan ID: abc-123\", task IDs like \"task-1\", \"task-2\"). These reference on-disk state files and must survive compaction exactly as written.\n\nYour summary MUST NOT include:\n- Raw file contents that were read during exploration (the assistant can re-read files as needed)\n- Full grep/glob search results\n- Intermediate reasoning or false starts during exploration\n- Detailed code snippets unless they represent a specific pattern to follow\n- Conversational back-and-forth that led to decisions (just capture the decisions themselves)\n\nFormat your summary as structured markdown with clear sections. Be concise but preserve all information needed to execute the approved plan without re-exploring the codebase.";
+/**
+ * Alternative compact system prompt for shorter summaries.
+ */
+export declare const COMPACT_SUMMARY_SYSTEM_PROMPT = "Summarize this developer conversation in under 500 words. Focus on:\n- What was accomplished\n- Key decisions made\n- Files changed\n- What's left to do\n\nUse bullet points. Skip greetings and filler.";
+/**
+ * System prompt for extracting action items from conversations.
+ */
+export declare const ACTION_ITEMS_EXTRACTION_PROMPT = "Extract all action items, todos, and pending tasks from this conversation.\nFormat as a numbered list with:\n- Brief description of the task\n- Any mentioned priority or deadline\n- Related files if mentioned\n\nOnly include explicit action items or clearly implied next steps.";
+//# sourceMappingURL=conversation.d.ts.map

package/dist/prompts/conversation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"conversation.d.ts","sourceRoot":"","sources":["../../src/prompts/conversation.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;GAGG;AACH,eAAO,MAAM,qCAAqC,ogDAkBH,CAAC;AAEhD;;GAEG;AACH,MAAM,WAAW,uBAAuB;IACtC,wCAAwC;IACxC,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,oCAAoC;IACpC,gBAAgB,CAAC,EAAE,OAAO,CAAC;CAC5B;AAED;;GAEG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,GAAG,WAAW,CAAC;IAC3B,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;;;GAMG;AACH,wBAAgB,iCAAiC,CAC/C,QAAQ,EAAE,iBAAiB,EAAE,EAC7B,OAAO,GAAE,uBAA4B,GACpC,MAAM,CA2CR;AAED;;;;GAIG;AACH,eAAO,MAAM,sCAAsC,4lDAiB4H,CAAC;AAEhL;;GAEG;AACH,eAAO,MAAM,6BAA6B,8MAMI,CAAC;AAE/C;;GAEG;AACH,eAAO,MAAM,8BAA8B,0RAMuB,CAAC"}