@uniswap/ai-toolkit-nx-claude 0.5.7 → 0.5.9-next.0

package/dist/content/agents/agnostic/claude-docs-initializer.md

@@ -12,7 +12,6 @@ Perform deep repository analysis to understand structure, patterns, and architec
 ## Inputs
 
 - `target`: Natural language description of what to document
-
   - Example: "the Next.js frontend application located in /app/frontend, focusing on user-facing pages and components"
   - Example: "the authentication system across the entire codebase"
   - Example: "the Express backend API in /backend, including all routes and middleware"
@@ -20,7 +19,6 @@ Perform deep repository analysis to understand structure, patterns, and architec
   - Example: "document the shared UI components library in /packages/ui with focus on the design system"
 
 - `siblingContext`: Natural language description of what other agents are documenting
-
   - Example: "Other agents are documenting: the admin dashboard components, the backend API documentation, and the database schema documentation"
   - Example: "Another agent is documenting the user-facing frontend pages while you focus on admin pages"
   - Example: "No other agents are running" (for single-agent mode)
@@ -36,7 +34,6 @@ Perform deep repository analysis to understand structure, patterns, and architec
 ### 1. Parse Target Scope
 
 Interpret the natural language target to understand:
-
 - **Extract paths**: Identify any specific directories mentioned (e.g., "/frontend", "/app/pages")
 - **Understand scope**: Parse descriptors like "user-facing", "admin", "API routes", "shared components"
 - **Determine level**: Identify if this is for:
@@ -48,7 +45,6 @@ Interpret the natural language target to understand:
 ### 2. Respect Sibling Boundaries
 
 From siblingContext, understand coordination requirements:
-
 - **Parse sibling work**: Identify what other agents are handling
 - **Prevent overlap**: Ensure no duplicate CLAUDE.md creation
 - **Stay in bounds**: Only create documentation within assigned target
@@ -57,7 +53,6 @@ From siblingContext, understand coordination requirements:
 ### 3. Incorporate Completed Context (Area/Repository Root Only)
 
 If completedContext is provided (only for consolidation phases):
-
 - **Parse findings**: Extract key discoveries from completed agents
 - **Identify patterns**: Look for common patterns across different areas
 - **Build narrative**: Create cohesive story incorporating all findings
@@ -70,7 +65,6 @@ If completedContext is provided (only for consolidation phases):
 
 **Phase 1: Git-Based Discovery (Primary Method)**:
 If the repository is a git repository (check for .git directory):
-
 - Use `git ls-files` to get all tracked files (automatically excludes node_modules, dist, etc.)
 - Find package boundaries: `git ls-files | grep 'package\.json$'` for Node.js projects
 - Find other project files: `git ls-files | grep -E '(project\.json|go\.mod|Cargo\.toml|pyproject\.toml|pom\.xml)$'`
@@ -80,12 +74,10 @@ If the repository is a git repository (check for .git directory):
 **Phase 2: Fallback Manual Discovery (Only if not a git repo)**:
 
 **⚠️ CRITICAL: NEVER use find commands without proper exclusions!**
-
 - **WRONG**: `-not -path "./node_modules/*"` (only excludes top-level)
 - **CORRECT**: `-not -path "*/node_modules/*"` (excludes ALL nested node_modules)
 
 Use Glob/Grep with explicit exclusions:
-
 - **MUST exclude these patterns**:
   - `**/node_modules/**` (for Glob)
   - `*/node_modules/*` (for find command)
@@ -104,7 +96,6 @@ Use Glob/Grep with explicit exclusions:
 - Limit search depth to avoid excessive exploration
 
 **Technology Detection**:
-
 - Programming languages used
 - Frameworks and libraries
 - Build tools and bundlers
@@ -117,7 +108,6 @@ Use Glob/Grep with explicit exclusions:
 Based on parsed target scope, determine documentation strategy:
 
 **For Leaf-Level Documentation** (e.g., "document the user-facing frontend pages"):
-
 - Create CLAUDE.md files at multiple levels within target area
 - Include package, module, and feature-level documentation
 - Document based on these criteria:
@@ -129,21 +119,18 @@ Based on parsed target scope, determine documentation strategy:
   - **Domain boundaries**: Auth, payments, user management, etc.
 
 **For Area Root Documentation** (e.g., "create frontend root CLAUDE.md"):
-
 - Create SINGLE CLAUDE.md at the area root directory only
 - Synthesize findings from completedContext
 - Do NOT create subdirectory documentation
 - Focus on architectural overview of the entire area
 
 **For Repository Root Documentation** (e.g., "create repository root CLAUDE.md"):
-
 - Create SINGLE CLAUDE.md at repository root only
 - Synthesize all area findings from completedContext
 - Provide high-level system architecture
 - Connect patterns across different areas
 
 **NEVER create CLAUDE.md for**:
-
 - Directories outside your target scope
 - node_modules directories (any level)
 - Build output directories (dist, build, out, .next, .nuxt, .turbo)
@@ -158,7 +145,6 @@ Based on parsed target scope, determine documentation strategy:
 For each directory that will get a CLAUDE.md:
 
 **Code Analysis** (using git-tracked files only if a git repository):
-
 - Find entry points in directory: `git ls-files <directory> | grep -E '(index|main)\.(ts|js|tsx|jsx|py|go|rs|java)$'`
 - List all source files: `git ls-files <directory> | grep -E '\.(ts|tsx|js|jsx|py|go|rs|java)$'`
 - Parse main entry points and identify exported APIs
@@ -168,7 +154,6 @@ For each directory that will get a CLAUDE.md:
 - Identify coding conventions and patterns
 
 **Pattern Recognition**:
-
 - Naming conventions (files, functions, components)
 - Directory organization patterns
 - State management approach
@@ -177,7 +162,6 @@ For each directory that will get a CLAUDE.md:
 - Build and deployment patterns
 
 **Relationship Mapping**:
-
 - How this module relates to others
 - Dependencies (both internal and external)
 - Consumers of this module's exports
@@ -208,35 +192,27 @@ Every CLAUDE.md file MUST start with a timestamp header as the very first line:
 # CLAUDE.md - [Project Name]
 
 ## Project Overview
-
 [Purpose, description, and key goals]
 
 ## Tech Stack
-
 [Languages, frameworks, tools, package manager]
 
 ## Repository Structure
-
 [Tree view of major directories with brief descriptions]
 
 ## Key Modules
-
 [List of major modules/packages with brief descriptions]
 
 ## Development Workflow
-
 [Commands, scripts, testing, deployment processes]
 
 ## Code Quality
-
 [Linting, formatting, testing setup and requirements]
 
 ## Conventions and Patterns
-
 [Coding standards, naming conventions, project-wide patterns]
 
 ## Documentation Management
-
 [CLAUDE.md management rules - ALWAYS INCLUDE]
 
 <!-- CUSTOM:START -->
@@ -245,38 +221,30 @@ Every CLAUDE.md file MUST start with a timestamp header as the very first line:
 ```
 
 #### For Package/Module CLAUDE.md:
-
 ```markdown
 > **Last Updated:** YYYY-MM-DD
 
 # CLAUDE.md - [Package/Module Name]
 
 ## Overview
-
 [Purpose discovered from code analysis]
 
 ## Architecture
-
 [Internal structure based on analysis]
 
 ## Key Components
-
 [Major files/classes/components found]
 
 ## API/Exports
-
 [Public API discovered from exports]
 
 ## Dependencies
-
 [Both internal and external]
 
 ## Usage Patterns
-
 [Common patterns, examples, best practices]
 
 ## Development Guidelines
-
 [Package-specific conventions, testing approach, contribution notes]
 
 <!-- CUSTOM:START -->
@@ -285,32 +253,25 @@ Every CLAUDE.md file MUST start with a timestamp header as the very first line:
 ```
 
 #### For Feature/Component CLAUDE.md:
-
 ```markdown
 # CLAUDE.md - [Feature/Component Name]
 
 ## Purpose
-
 [Inferred from code structure and naming]
 
 ## Components
-
 [List of sub-components with descriptions]
 
 ## API
-
 [Props, methods, exports, interfaces]
 
 ## Implementation Details
-
 [Key implementation decisions, patterns used]
 
 ## Integration Points
-
 [How it connects with other parts of the system]
 
 ## Usage Examples
-
 [Code examples showing common use cases]
 
 <!-- CUSTOM:START -->
@@ -323,26 +284,22 @@ Every CLAUDE.md file MUST start with a timestamp header as the very first line:
 **Execution Strategy Based on Target Level**:
 
 **For Leaf Documentation**:
-
 1. Create multiple CLAUDE.md files within target area where necessary and appropriate
 2. Follow hierarchical order (packages → modules → features)
 3. Each level has appropriate scope without duplication
 4. Skip existing CLAUDE.md files (report in output)
 
 **For Area Root Documentation**:
-
 1. Create single CLAUDE.md at area root only
 2. Synthesize completedContext from leaf agents
 3. Focus on area-wide architecture and patterns
 
 **For Repository Root Documentation**:
-
 1. Create single CLAUDE.md at repository root only
 2. Synthesize completedContext from all area agents
 3. Provide system-wide architectural overview
 
 **Cross-Reference Management**:
-
 - Root mentions packages but doesn't detail them
 - Packages mention modules but don't detail implementations
 - Modules document their specific scope
@@ -351,7 +308,6 @@ Every CLAUDE.md file MUST start with a timestamp header as the very first line:
 ## Output
 
 Return comprehensive initialization results:
-
 ```yaml
 success: boolean
 summary: |
@@ -362,21 +318,21 @@ targetAnalysis:
   description: "What was analyzed (e.g., 'Next.js frontend user pages with 150 files')"
   filesAnalyzed: 150
   directoriesDocumented: 12
-  complexity: 'low|medium|high' # Based on code patterns and business logic
+  complexity: "low|medium|high" # Based on code patterns and business logic
   keyFindings:
-    - 'Uses Next.js App Router with RSC patterns'
-    - 'Implements atomic design system with 47 components'
-    - 'Heavy use of custom hooks for business logic'
-    - 'Follows feature-based folder structure'
+    - "Uses Next.js App Router with RSC patterns"
+    - "Implements atomic design system with 47 components"
+    - "Heavy use of custom hooks for business logic"
+    - "Follows feature-based folder structure"
 
 createdFiles:
-  - path: '/app/frontend/CLAUDE.md'
-    level: 'package|module|feature|root'
-    summary: 'Created frontend package documentation with component inventory and architectural patterns'
+  - path: "/app/frontend/CLAUDE.md"
+    level: "package|module|feature|root"
+    summary: "Created frontend package documentation with component inventory and architectural patterns"
 
-  - path: '/app/frontend/components/CLAUDE.md'
-    level: 'module'
-    summary: 'Created component library documentation with design system overview'
+  - path: "/app/frontend/components/CLAUDE.md"
+    level: "module"
+    summary: "Created component library documentation with design system overview"
 
 coordinationContext: |
   Natural language string with important findings for sibling agents.
@@ -387,18 +343,18 @@ coordinationContext: |
   Example for repository root: "Monorepo with clear frontend/backend separation. Frontend uses Next.js with modern patterns. Backend is Express with layered architecture. Database is PostgreSQL with Prisma. Authentication via Supabase. Clear API boundaries with TypeScript types shared via packages."
 
 skippedAreas: # Areas intentionally not documented (respecting siblingContext)
-  - path: '/app/frontend/admin'
-    reason: 'Another agent is documenting admin pages'
-  - path: '/backend'
-    reason: 'Backend documentation assigned to different agent'
+  - path: "/app/frontend/admin"
+    reason: "Another agent is documenting admin pages"
+  - path: "/backend"
+    reason: "Backend documentation assigned to different agent"
 
 recommendations:
-  - 'The /lib/analytics module is growing complex (8 files) and should get its own CLAUDE.md'
-  - 'Consider splitting the large UserDashboard component (500+ lines) into smaller pieces'
+  - "The /lib/analytics module is growing complex (8 files) and should get its own CLAUDE.md"
+  - "Consider splitting the large UserDashboard component (500+ lines) into smaller pieces"
 
 error: # Only if success: false
-  message: 'Error description'
-  details: 'Additional context'
+  message: "Error description"
+  details: "Additional context"
 ```
 
 ## Implementation Commands
@@ -410,38 +366,32 @@ error: # Only if success: false
 ### Essential Discovery Commands
 
 **Check if git repository**:
-
 ```bash
 test -d .git && echo "Git repo" || echo "Not a git repo"
 ```
 
 **Find all package.json files (git repos)**:
-
 ```bash
 git ls-files | grep 'package\.json$' | grep -v node_modules
 ```
 
 **Find all package.json files (non-git fallback)**:
-
 ```bash
 # IMPORTANT: Use "*/node_modules/*" to exclude ALL nested node_modules directories
 find . -name "package.json" -not -path "*/node_modules/*" -not -path "*/dist/*" -not -path "*/.next/*" -not -path "*/build/*" -maxdepth 5
 ```
 
 **List all directories with source code**:
-
 ```bash
 git ls-files | grep -E '\.(ts|tsx|js|jsx)$' | xargs dirname | sort -u
 ```
 
 **Count files per directory**:
-
 ```bash
 git ls-files | xargs dirname | sort | uniq -c | sort -rn
 ```
 
 **Find complex directories (10+ source files)**:
-
 ```bash
 for dir in $(git ls-files | xargs dirname | sort -u); do
   count=$(git ls-files "$dir" | grep -E '\.(ts|tsx|js|jsx)$' | wc -l)
@@ -461,18 +411,14 @@ done
 ## Special Considerations
 
 ### Monorepo Detection
-
 Identify monorepo tools and adjust:
-
 - Nx workspaces: Use project.json boundaries
 - Lerna: Use lerna.json configuration
 - Yarn/npm workspaces: Use workspace configuration
 - Turborepo: Identify pipeline configuration
 
 ### Framework-Specific Intelligence
-
 Recognize and document framework patterns:
-
 - Next.js: app/pages routing, API routes, middleware
 - React: Component patterns, hooks, context providers
 - Angular: Modules, services, dependency injection
@@ -481,9 +427,7 @@ Recognize and document framework patterns:
 - NestJS: Module/controller/service architecture
 
 ### Large Repository Handling
-
 For repositories with 1000+ files:
-
 - **Always use git ls-files** for file discovery (much faster than find/glob)
 - Sample files for pattern detection: `git ls-files | shuf -n 1000` for random sampling
 - Focus on entry points and exports: `git ls-files | grep -E '(index|main)\.'`
@@ -491,7 +435,6 @@ For repositories with 1000+ files:
 - Set reasonable depth limits for non-git fallback only
 
 ### Performance Optimization
-
 - Parallel analysis where possible
 - Cache file parsing results
 - Use incremental analysis for large codebases
@@ -500,7 +443,6 @@ For repositories with 1000+ files:
 ## Critical Constraints
 
 **HIERARCHICAL AWARENESS**: This agent operates at different levels based on target:
-
 - **Leaf Level**: Document specific areas with multiple CLAUDE.md files
 - **Area Root Level**: Create single area overview from leaf findings
 - **Repository Root Level**: Create single system overview from all findings
@@ -513,4 +455,4 @@ For repositories with 1000+ files:
 
 **NO ASSUMPTIONS**: All content must be derived from actual code analysis, not assumptions or templates.
 
-**HIERARCHY RESPECT**: Each documentation level should complement, not duplicate, other levels.
+**HIERARCHY RESPECT**: Each documentation level should complement, not duplicate, other levels.

package/dist/content/agents/agnostic/claude-docs-manager.md

@@ -30,14 +30,12 @@ Analyze code changes and intelligently update ALL affected CLAUDE.md documentati
 **CRITICAL: Every CLAUDE.md file operation MUST handle timestamps:**
 
 When updating any CLAUDE.md file:
-
 1. **Check for existing timestamp**: Look for `> **Last Updated:** YYYY-MM-DD` at the top of the file
 2. **If timestamp exists**: Update it to the current date (e.g., 2025-10-02)
 3. **If timestamp is missing**: Add `> **Last Updated:** YYYY-MM-DD` as the very first line
 4. **Always place timestamp first**: It must be the first line before any other content including headers
 
 When creating new CLAUDE.md files:
-
 - **Always start with timestamp**: First line must be `> **Last Updated:** YYYY-MM-DD`
 - Use current date in ISO format (YYYY-MM-DD)
 
@@ -46,7 +44,6 @@ This ensures users can immediately see documentation freshness when opening any
 ### 1. Understand Changes and Context
 
 **FIRST STEP**: Analyze what changed and why:
-
 - Review the `changes` list to understand what was modified
 - Consider the `changeContext` to understand the intent behind changes
 - Evaluate change significance and scope:
@@ -69,7 +66,6 @@ This ensures users can immediately see documentation freshness when opening any
 ### 2. Identify Affected CLAUDE.md Files
 
 Based on the changes, find all CLAUDE.md files that need updates:
-
 - **Group changes by proximity**: Organize changes by their directory locations
 - **Traverse up hierarchy**: For each change, find all CLAUDE.md files from the file's directory up to root
 - **Assess update necessity**: For each potential CLAUDE.md, determine if it needs updating based on:
@@ -78,18 +74,16 @@ Based on the changes, find all CLAUDE.md files that need updates:
   - Documentation Proximity Principle (prefer closest relevant CLAUDE.md)
 - **Configuration Detection**: Parse package.json, tsconfig.json, project.json to understand boundaries
 - **New CLAUDE.md Detection**: Identify if new CLAUDE.md files should be created:
-
+  
   **Criteria for importance** (must meet at least one):
-
   1. **Package Boundary**: Contains package.json or project.json (separate package/app)
   2. **Module Boundary**: Major architectural module with 10+ source files
   3. **API Boundary**: Exposes public API/exports (has index.ts/js exporting multiple items)
   4. **Feature Boundary**: Self-contained feature with its own components, services, and tests
   5. **Domain Boundary**: Represents distinct business domain (e.g., auth, payments, analytics)
   6. **Framework Convention**: Framework-specific important directories (e.g., Next.js `app` or `pages`)
-
+  
   **Explicitly EXCLUDE**:
-
   - Test directories (unless they contain complex test infrastructure)
   - Config directories (usually self-explanatory)
   - Build/dist/output directories
@@ -105,7 +99,6 @@ For each affected CLAUDE.md file, determine content updates:
 #### When to Create New CLAUDE.md Files:
 
 **Create a NEW CLAUDE.md when**:
-
 - Adding a new complex component (100+ lines, 3+ public methods/props)
 - Creating a new module/feature directory with multiple files
 - Establishing a new package or app directory
@@ -113,7 +106,6 @@ For each affected CLAUDE.md file, determine content updates:
 - Creating a directory with significant public API exports
 
 **DON'T create CLAUDE.md for**:
-
 - Simple single-file components
 - Utility/helper directories with just functions
 - Test directories (unless complex test infrastructure)
@@ -123,9 +115,7 @@ For each affected CLAUDE.md file, determine content updates:
 - Asset/static file directories
 
 #### If Root CLAUDE.md:
-
 Include:
-
 - Project overview and purpose
 - Tech stack and architecture
 - **CLAUDE.md Management Rules** (critical for root)
@@ -135,9 +125,7 @@ Include:
 - Code quality standards and setup
 
 #### If Package/Module CLAUDE.md:
-
 Include:
-
 - Package-specific purpose and role
 - Components/files at THIS directory level
 - API documentation for THIS level
@@ -147,9 +135,7 @@ Include:
 - Package-specific guidelines
 
 #### If Feature/Component CLAUDE.md:
-
 Include:
-
 - Component/feature purpose and role
 - Sub-components and their interactions
 - API surface (props, methods, exports)
@@ -162,9 +148,8 @@ Include:
 Process all identified CLAUDE.md files:
 
 #### For Each Affected File:
-
 1. **New CLAUDE.md**: Generate complete structure appropriate for that level
-2. **Existing CLAUDE.md**:
+2. **Existing CLAUDE.md**: 
    - Parse and preserve custom sections (marked with `<!-- CUSTOM:START -->`)
    - Update only sections affected by the changes
    - Add new components/patterns from changes
@@ -182,34 +167,29 @@ When `isRoot: true`, include these essential rules:
 
 After making any changes to files in this repository, Claude Code MUST:
 
-1. **Apply the Documentation Proximity Principle**:
-
+1. **Apply the Documentation Proximity Principle**: 
    - Find the CLOSEST CLAUDE.md file in the directory hierarchy that would benefit from documenting this change
    - Start from the immediate parent directory of changed files and work upward
    - Update the closest relevant CLAUDE.md rather than always going to package/app level
    - Only bubble up to parent CLAUDE.md files if the change affects that level's public API or architecture
 
 2. **Identify the appropriate CLAUDE.md level**:
-
    - **Component/Feature level**: For changes to a specific component or feature with its own CLAUDE.md
    - **Module level**: For changes affecting multiple components within a module
    - **Package level**: For changes to package exports, dependencies, or architecture
    - **Root level**: Only for repository-wide architectural changes
-
+   
    **Fallback for repos without package.json/project.json**:
-
    - Look for other project markers: BUILD files (Bazel), go.mod (Go), Cargo.toml (Rust), setup.py/pyproject.toml (Python), pom.xml (Maven), build.gradle (Gradle)
    - If no markers found, use directory structure heuristics (src/ boundaries, directories with README files, directories with 10+ files)
    - Default to the deepest common ancestor directory of all changes
 
 3. **Check for existing CLAUDE.md**:
-
    - If a CLAUDE.md file exists at the identified level, update it to reflect the changes
    - If no CLAUDE.md exists but changes are significant enough, consider if one should be created at this level
    - Skip creating CLAUDE.md for trivial directories (single files, pure config, test-only directories)
 
 4. **Content scope based on proximity**:
-
    - **Closest level**: Detailed implementation changes, API updates, usage examples
    - **Parent level**: Only if public API changed or architectural impact
    - **Root level**: Only if repository-wide patterns or architecture affected
@@ -226,34 +206,33 @@ After making any changes to files in this repository, Claude Code MUST:
 ## Output
 
 Return structured result:
-
 ```yaml
 success: boolean
 updatedFiles: # All CLAUDE.md files that were modified
-  - path: '/absolute/path/to/packages/ui/CLAUDE.md'
-    operation: 'updated'
+  - path: "/absolute/path/to/packages/ui/CLAUDE.md"
+    operation: "updated"
     changes:
-      - 'Added Button component to exports'
-      - 'Updated API documentation for size prop'
-  - path: '/absolute/path/to/packages/ui/src/components/CLAUDE.md'
-    operation: 'created'
+      - "Added Button component to exports"
+      - "Updated API documentation for size prop"
+  - path: "/absolute/path/to/packages/ui/src/components/CLAUDE.md"
+    operation: "created"
     changes:
-      - 'Created new CLAUDE.md for complex Button component'
-  - path: '/workspace/CLAUDE.md'
-    operation: 'updated'
+      - "Created new CLAUDE.md for complex Button component"
+  - path: "/workspace/CLAUDE.md"
+    operation: "updated" 
     changes:
-      - 'Updated architecture section with new pattern'
+      - "Updated architecture section with new pattern"
 skippedFiles: # Files considered but not updated
-  - path: '/absolute/path/to/packages/auth/CLAUDE.md'
+  - path: "/absolute/path/to/packages/auth/CLAUDE.md"
     reason: "Changes don't affect this package's API or architecture"
 recommendNewClaude: # Directories where NEW CLAUDE.md files should be created
-  - path: '/absolute/path/to/new/complex/component'
-    reason: 'New complex component added with 200+ lines and public API'
+  - path: "/absolute/path/to/new/complex/component"
+    reason: "New complex component added with 200+ lines and public API"
 content_summary: |
   Brief description of what was written to the file
 error: # Only if success: false
-  message: 'Error description'
-  details: 'Additional context'
+  message: "Error description"
+  details: "Additional context"
 ```
 
 ## Content Generation Guidelines
@@ -264,35 +243,27 @@ error: # Only if success: false
 # CLAUDE.md - [Project Name]
 
 ## Project Overview
-
 [Purpose, description, and key goals]
 
 ## Tech Stack
-
 [Languages, frameworks, tools, package manager]
 
 ## Repository Structure
-
 [Tree view of major directories with brief descriptions]
 
 ## Key Modules
-
 [List of major modules/packages with brief descriptions]
 
 ## Development Workflow
-
 [Commands, scripts, testing, deployment processes]
 
 ## Code Quality
-
 [Linting, formatting, testing setup and requirements]
 
 ## Conventions and Patterns
-
 [Coding standards, naming conventions, project-wide patterns]
 
 ## Documentation Management
-
 [CLAUDE.md management rules - ALWAYS INCLUDE]
 
 <!-- CUSTOM:START -->
@@ -306,31 +277,24 @@ error: # Only if success: false
 # CLAUDE.md - [Package/Module Name]
 
 ## Overview
-
 [Purpose and role within the larger project]
 
 ## Architecture
-
 [Internal structure, design patterns, organization]
 
 ## Key Components
-
 [Major files, classes, modules with descriptions]
 
 ## API/Exports
-
 [Public API, exported functions/classes/types]
 
 ## Dependencies
-
 [External and internal dependencies with purpose]
 
 ## Usage Patterns
-
 [Common patterns, examples, best practices]
 
 ## Development Guidelines
-
 [Package-specific conventions, testing approach, contribution notes]
 
 <!-- CUSTOM:START -->
@@ -353,27 +317,21 @@ error: # Only if success: false
 # CLAUDE.md - [Feature/Component Name]
 
 ## Purpose
-
 [What this feature/component does and why it exists]
 
 ## Components
-
 [List of sub-components with descriptions]
 
 ## API
-
 [Props, methods, exports, interfaces]
 
 ## Implementation Details
-
 [Key implementation decisions, patterns used]
 
 ## Integration Points
-
 [How it connects with other parts of the system]
 
 ## Usage Examples
-
 [Code examples showing common use cases]
 
 <!-- CUSTOM:START -->
@@ -384,7 +342,6 @@ error: # Only if success: false
 ## Directory Importance Examples
 
 ### ✅ **Deserves CLAUDE.md**:
-
 ```
 /packages/auth              # Package with package.json
 /src/modules/payments       # Domain module with 20+ files
@@ -395,7 +352,6 @@ error: # Only if success: false
 ```
 
 ### ❌ **Skip CLAUDE.md**:
-
 ```
 /src/utils                  # Just utility functions
 /tests/unit                 # Test directories
@@ -410,26 +366,20 @@ error: # Only if success: false
 ## Special Considerations
 
 ### Monorepo Detection
-
 If the project uses Nx, Lerna, or workspace configurations:
-
 - Adjust root CLAUDE.md to explain monorepo structure
 - Reference workspace configuration
 - Explain inter-package dependencies
 
 ### Framework-Specific Content
-
 Detect and document framework-specific patterns:
-
 - Next.js: app/pages structure, API routes
 - Express: Middleware, routes, controllers
 - React: Component structure, state management
 - Angular: Modules, services, components
 
 ### Testing Infrastructure
-
 Document testing setup if detected:
-
 - Test frameworks and configuration
 - Test file patterns
 - Coverage requirements
@@ -437,30 +387,26 @@ Document testing setup if detected:
 ## Critical Constraints
 
 **CHANGE-DRIVEN PROCESSING**: This agent processes changes and updates ALL affected documentation:
-
 - Analyzes the provided changes to understand what was modified
 - Finds and updates every CLAUDE.md file that should reflect these changes
 - Creates new CLAUDE.md files where appropriate
 
 **DOCUMENTATION PROXIMITY PRINCIPLE**: For each change, the agent must:
-
 - Start from the closest possible documentation level
 - Bubble up to parent levels ONLY when changes affect their concerns
 - Update multiple levels when appropriate (e.g., component detail + package API)
 - Skip levels where changes have no relevance
 
 **SCOPE ENFORCEMENT**: Documentation updates must be:
-
 - Based only on changes explicitly provided in the `changes` parameter
 - Scoped appropriately for each documentation level
 - Accurate to the actual code changes, not assumptions
 - Consistent with existing documentation patterns
 
 **HIERARCHY AWARENESS**: The agent understands documentation hierarchy:
-
 - Component level → Module level → Package level → Root level
 - Each level has different concerns (implementation → API → architecture)
 - Changes flow up only when they affect parent level's scope
 - Multiple levels can be updated in a single operation
 
-Remember: One set of changes, multiple documentation updates, all in a single intelligent operation.
+Remember: One set of changes, multiple documentation updates, all in a single intelligent operation.

package/dist/content/agents/agnostic/plan-reviewer.md

@@ -27,7 +27,6 @@ Critically analyze implementation plans WITHOUT writing any code. Focus on revie
 
 **MANDATORY DEEP THINKING PHASE:**
 Before providing any review, you MUST:
-
 1. Deeply read and understand the entire plan
 2. **Integrate context_findings if provided** - Use the deep understanding from context-loader
 3. Consider multiple potential issues with the plan
@@ -37,7 +36,6 @@ Before providing any review, you MUST:
 7. Assess conciseness vs over-documentation
 
 **Review Steps:**
-
 1. **Context Integration**: If context_findings provided, use them as foundation for review:
    - Cross-reference plan against key_components identified by context-loader
    - Verify plan follows the patterns and conventions already discovered
@@ -62,7 +60,7 @@ summary: |
 strengths:
   - [What the plan does well - be specific]
   - [Areas where plan shows good understanding]
-
+  
 concerns:
   - issue: [Specific concern about the plan]
     severity: low|medium|high|critical
@@ -70,22 +68,16 @@ concerns:
     suggestion: [How to address it in the plan]
 
 gaps:
-  - missing:
-      [
-        What's missing from the plan that's critical for implementation. Note: Do NOT flag missing testing plans,
-        success criteria,
-        risk matrices,
-        or agent assignments as gaps - these are intentionally omitted,
-      ]
+  - missing: [What's missing from the plan that's critical for implementation. Note: Do NOT flag missing testing plans, success criteria, risk matrices, or agent assignments as gaps - these are intentionally omitted]
     rationale: [Why this gap matters for the stated goal]
     suggestion: [How to fill this gap]
-
+    
 improvements:
   - area: [What could be better in the plan]
     current: [Current approach described in plan]
     suggested: [Better approach]
     rationale: [Why the suggested approach is better]
-
+    
 feasibility-assessment:
   complexity: low|medium|high
   risks:
@@ -105,7 +97,6 @@ scope-validation:
 ## Guidelines
 
 **ABSOLUTE REQUIREMENTS:**
-
 1. **NO CODE WRITING** - Do NOT write any implementation code, only review plans
 2. **NO EXTRA SUGGESTIONS** - Do NOT suggest features not in the original plan:
    - NO backwards compatibility suggestions unless plan requested it
@@ -119,7 +110,6 @@ scope-validation:
 7. **VALIDATE CONCISENESS** - Plans should be strategic roadmaps, not exhaustive documentation
 
 **Review Principles:**
-
 - **Leverage context_findings when available** - Don't duplicate analysis already done by context-loader
 - Focus on plan quality, not implementation details
 - Verify plan follows existing architectural decisions (especially those identified in context_findings)
@@ -128,14 +118,12 @@ scope-validation:
 - Be explicit about scope adherence
 
 **Context Integration Best Practices:**
-
 - If context_findings are provided, treat them as authoritative
 - Verify plan builds upon the patterns and conventions already identified
 - Flag if plan contradicts the gotchas and edge cases discovered
 - Reference specific files from key_components when assessing plan accuracy
 
 **Quality Focus Areas:**
-
 - Is the plan actionable without ambiguity?
 - Are all steps concrete and specific?
 - Have edge cases been considered (including those from context)?
@@ -145,14 +133,12 @@ scope-validation:
 - Are there any missing critical steps or considerations?
 
 **Critical Scope Enforcement:**
-
 - Flag any suggestions for backwards compatibility not explicitly requested
 - Identify any legacy support not specifically required
 - Point out future-proofing or nice-to-haves beyond current needs
 - Ensure plan implements EXACTLY what was asked for
 
 **What NOT to Flag as Problems:**
-
 - Missing testing plans (testing is handled during execution, not planning)
 - Missing success criteria checklists (implementer validates)
 - Missing comprehensive risk matrices (only critical risks should be documented)
@@ -162,7 +148,6 @@ scope-validation:
 - Plans being "too concise" if they cover all critical information
 
 **What SHOULD be Flagged:**
-
 - Over-documentation or exhaustive details that make plan hard to use
 - Missing critical implementation steps or decisions
 - Unclear API interfaces when needed
@@ -170,4 +155,4 @@ scope-validation:
 - Scope creep or extras not requested
 - Plans where strategic direction is unclear
 
-Remember: Your role is critical analysis of the plan's quality and feasibility. When context_findings are provided, you're building on deep reconnaissance already performed. Focus on ensuring the plan is complete, accurate, concise, and implementable without unnecessary additions.
+Remember: Your role is critical analysis of the plan's quality and feasibility. When context_findings are provided, you're building on deep reconnaissance already performed. Focus on ensuring the plan is complete, accurate, concise, and implementable without unnecessary additions.

package/dist/content/commands/agnostic/claude-docs.md

@@ -13,7 +13,6 @@ Intelligently manages CLAUDE.md documentation files across your repository. Supp
 Accept natural language input and extract intent:
 
 - **Input text**: Parse the user's request to understand intent
-
   - **"init" keywords**: "init", "initialize", "setup", "create", "bootstrap", "start"
     - Triggers: "init docs", "initialize documentation", "setup CLAUDE.md files"
     - Routes to: **INIT Path** (claude-docs-initializer agent)
@@ -25,7 +24,6 @@ Accept natural language input and extract intent:
     - Path references: "in packages/ui", "for the UI package", specific paths mentioned
 
 - **Mode determination**:
-
   1. Explicitly check for init keywords first → Use **INIT Path**
   2. Otherwise → Use **UPDATE Path** (default)
   3. Extract any file limit specification (e.g., "init with max 50 files per agent")
@@ -47,7 +45,6 @@ Accept natural language input and extract intent:
 ### Task for Update
 
 1. **Analyze Change Significance**:
-
    - Identify significant vs insignificant changes
    - Filter out minor fixes, typos, formatting
 
@@ -58,7 +55,6 @@ Accept natural language input and extract intent:
 ### Delegation for Update
 
 Invoke **claude-docs-manager** with:
-
 - `changes`: Complete list of all significant file changes
   - `filePath`: Absolute path to changed file
   - `changeType`: added|modified|deleted
@@ -72,7 +68,6 @@ Invoke **claude-docs-manager** with:
 - `rootGuidelines`: (Optional) Key guidelines from existing root CLAUDE.md
 
 The agent will:
-
 - Identify ALL CLAUDE.md files that need updates
 - Update each file with appropriate scope (component/module/package/root)
 - Create new CLAUDE.md files where needed
@@ -81,7 +76,6 @@ The agent will:
 ### Output for Update
 
 Return results from claude-docs-manager:
-
 ```yaml
 summary: |
   Successfully updated N CLAUDE.md files
@@ -154,14 +148,12 @@ Please be patient - the process is working even during apparent pauses.
 ### Task for Init
 
 1. **Repository Analysis**:
-
    - Use git to quickly understand structure: `git ls-files | wc -l`
    - Find major boundaries: packages, apps, services
    - Count files per area: `git ls-files [area] | wc -l`
    - Assess complexity by file types and patterns
 
 2. **Intelligent Area Splitting**:
-
    - Default: 100 files at most per agent (or user-specified limit)
    - Split areas exceeding limits into logical sub-areas
    - Identify natural boundaries (pages vs components, routes vs services)
@@ -173,7 +165,6 @@ Please be patient - the process is working even during apparent pauses.
    - Track dependencies between levels
 
 Example execution plan for large monorepo:
-
 ```
 Level 1 (Parallel leaf documentation):
   - Agent A: "Document user-facing frontend pages in /frontend/pages/user (50 files)"
@@ -204,13 +195,11 @@ Execute hierarchical parallelized documentation creation:
 #### Phase 1: Repository Analysis
 
 **⚠️ CRITICAL: ALWAYS prefer git commands over find/glob for discovery!**
-
 - Git automatically excludes node_modules, build outputs, and ignored files
 - Only use find/glob as fallback for non-git repositories
 - If using find, MUST use `*/node_modules/*` not `./node_modules/*` for exclusions
 
 Quickly analyze repository structure using git:
-
 - Get total file count: `git ls-files | wc -l`
 - Find package boundaries: `git ls-files | grep 'package\.json$'`
 - Identify tech stacks used and major directories and their sizes
@@ -225,7 +214,6 @@ Based on analysis, determine splitting strategy
 Invoke multiple **claude-docs-initializer** agents in PARALLEL:
 
 For each Level 1 agent:
-
 - `target`: "Document [specific area description] in [path]"
 - `siblingContext`: "Other agents are documenting: [list of other Level 1 areas]"
 
@@ -255,7 +243,6 @@ After all Level 2 agents complete, invoke **claude-docs-manager**:
 ### Output for Init
 
 Return aggregated results from all agents (claude-docs-initializer for all levels except repository root, claude-docs-manager for repository root only):
-
 ```yaml
 summary: |
   Repository analysis: [monorepo with X packages | single app | library]
@@ -267,42 +254,41 @@ executionPlan:
   level1Agents: 5 # Parallel leaf documentation
   level2Agents: 2 # Area roots
   level3Agents: 1 # Repository root
-  totalExecutionTime: '2m 34s'
+  totalExecutionTime: "2m 34s"
 
 createdFilesByLevel:
   leafDocumentation:
-    - agent: 'frontend-user-pages'
+    - agent: "frontend-user-pages"
       files: 3
-      paths: ['/frontend/pages/user/CLAUDE.md', ...]
-    - agent: 'frontend-admin-pages'
+      paths: ["/frontend/pages/user/CLAUDE.md", ...]
+    - agent: "frontend-admin-pages"
       files: 2
-      paths: ['/frontend/pages/admin/CLAUDE.md', ...]
+      paths: ["/frontend/pages/admin/CLAUDE.md", ...]
 
   areaRoots:
-    - path: '/frontend/CLAUDE.md'
-      synthesizedFrom:
-        ['frontend-user-pages', 'frontend-admin-pages', 'frontend-components']
-    - path: '/backend/CLAUDE.md'
-      synthesizedFrom: ['backend-routes', 'backend-services']
+    - path: "/frontend/CLAUDE.md"
+      synthesizedFrom: ["frontend-user-pages", "frontend-admin-pages", "frontend-components"]
+    - path: "/backend/CLAUDE.md"
+      synthesizedFrom: ["backend-routes", "backend-services"]
 
   repositoryRoot:
-    - path: '/CLAUDE.md'
-      synthesizedFrom: ['frontend-root', 'backend-root', 'database']
+    - path: "/CLAUDE.md"
+      synthesizedFrom: ["frontend-root", "backend-root", "database"]
 
 architecturalFindings: # Aggregated from all agents
-  frontend: 'Next.js 14 with App Router, Tailwind CSS, 234 total components'
-  backend: 'Express with layered architecture, 23 RESTful endpoints'
-  database: 'PostgreSQL with Prisma ORM, 15 models'
-  patterns: 'Consistent use of TypeScript, feature-based organization'
+  frontend: "Next.js 14 with App Router, Tailwind CSS, 234 total components"
+  backend: "Express with layered architecture, 23 RESTful endpoints"
+  database: "PostgreSQL with Prisma ORM, 15 models"
+  patterns: "Consistent use of TypeScript, feature-based organization"
 
 recommendations: # Collected from all agents
-  - 'Split large UserDashboard component (500+ lines)'
-  - 'Add CLAUDE.md for growing analytics module'
-  - 'Consider documenting complex auth flow separately'
+  - "Split large UserDashboard component (500+ lines)"
+  - "Add CLAUDE.md for growing analytics module"
+  - "Consider documenting complex auth flow separately"
 
 errors: # Any failures across all agents
-  - agent: 'frontend-utils'
-    error: 'Failed to analyze due to circular dependencies'
+  - agent: "frontend-utils"
+    error: "Failed to analyze due to circular dependencies"
 ```
 
 ### Examples for Init
@@ -334,7 +320,6 @@ errors: # Any failures across all agents
 When user runs: `/claude-docs init`
 
 1. **Quick Analysis** determines:
-
    ```
    Total files: 2500
    Frontend: /app (1800 files)
@@ -343,7 +328,6 @@ When user runs: `/claude-docs init`
    ```
 
 2. **Intelligent Splitting** creates plan:
-
    ```
    Frontend needs splitting (1800 > 100):
    - /app/(user) → 450 files (complex pages) → split to 150x3
@@ -359,7 +343,6 @@ When user runs: `/claude-docs init`
    ```
 
 3. **Hierarchical Execution**:
-
    ```
    Level 1 (14 agents in parallel):
    ├── frontend-user-1 (150 files)
@@ -407,4 +390,4 @@ When user runs: `/claude-docs init`
 5. **Parallel Execution**: Use Task tool to spawn multiple agents simultaneously
 6. **Session-First Default**: For updates, prioritize session changes unless specified
 7. **Preserve Custom Content**: Both agents respect user-added content sections
-8. **Documentation Hierarchy**: Agents create docs only at their assigned level
+8. **Documentation Hierarchy**: Agents create docs only at their assigned level

package/dist/generators/hooks/generator.cjs

@@ -819,14 +819,9 @@ function fixHookPaths(verbose = false) {
                 hook.command = hook.command.replace(homeDir, "~");
                 modified = true;
               }
-              const pathMatch = hook.command.match(
-                /\/(Users|home)\/[^/]+\/\.claude\/hooks\//
-              );
+              const pathMatch = hook.command.match(/\/(Users|home)\/[^/]+\/\.claude\/hooks\//);
               if (pathMatch) {
-                hook.command = hook.command.replace(
-                  pathMatch[0],
-                  "~/.claude/hooks/"
-                );
+                hook.command = hook.command.replace(pathMatch[0], "~/.claude/hooks/");
                 modified = true;
               }
             }
@@ -834,13 +829,7 @@ function fixHookPaths(verbose = false) {
         }
       }
     };
-    const hookTypes = [
-      "Notification",
-      "Stop",
-      "SubagentStop",
-      "PreToolUse",
-      "PostToolUse"
-    ];
+    const hookTypes = ["Notification", "Stop", "SubagentStop", "PreToolUse", "PostToolUse"];
     for (const hookType of hookTypes) {
       if (settings.hooks[hookType] && Array.isArray(settings.hooks[hookType])) {
         fixPathInHooks(settings.hooks[hookType]);
@@ -849,9 +838,7 @@ function fixHookPaths(verbose = false) {
     if (modified) {
       fs3.writeFileSync(settingsPath, JSON.stringify(settings, null, 2));
       if (verbose) {
-        import_devkit3.logger.info(
-          "\u2705 Fixed hook paths to use ~ expansion for Docker compatibility"
-        );
+        import_devkit3.logger.info("\u2705 Fixed hook paths to use ~ expansion for Docker compatibility");
       }
       return true;
     }

package/dist/generators/init/generator.cjs

@@ -1330,14 +1330,9 @@ function fixHookPaths(verbose = false) {
                 hook.command = hook.command.replace(homeDir, "~");
                 modified = true;
               }
-              const pathMatch = hook.command.match(
-                /\/(Users|home)\/[^/]+\/\.claude\/hooks\//
-              );
+              const pathMatch = hook.command.match(/\/(Users|home)\/[^/]+\/\.claude\/hooks\//);
               if (pathMatch) {
-                hook.command = hook.command.replace(
-                  pathMatch[0],
-                  "~/.claude/hooks/"
-                );
+                hook.command = hook.command.replace(pathMatch[0], "~/.claude/hooks/");
                 modified = true;
               }
             }
@@ -1345,13 +1340,7 @@ function fixHookPaths(verbose = false) {
         }
       }
     };
-    const hookTypes = [
-      "Notification",
-      "Stop",
-      "SubagentStop",
-      "PreToolUse",
-      "PostToolUse"
-    ];
+    const hookTypes = ["Notification", "Stop", "SubagentStop", "PreToolUse", "PostToolUse"];
     for (const hookType of hookTypes) {
       if (settings.hooks[hookType] && Array.isArray(settings.hooks[hookType])) {
         fixPathInHooks(settings.hooks[hookType]);
@@ -1360,9 +1349,7 @@ function fixHookPaths(verbose = false) {
     if (modified) {
       fs4.writeFileSync(settingsPath, JSON.stringify(settings, null, 2));
       if (verbose) {
-        import_devkit4.logger.info(
-          "\u2705 Fixed hook paths to use ~ expansion for Docker compatibility"
-        );
+        import_devkit4.logger.info("\u2705 Fixed hook paths to use ~ expansion for Docker compatibility");
       }
       return true;
     }

package/dist/index.cjs

@@ -880,14 +880,9 @@ function fixHookPaths(verbose = false) {
                 hook.command = hook.command.replace(homeDir, "~");
                 modified = true;
               }
-              const pathMatch = hook.command.match(
-                /\/(Users|home)\/[^/]+\/\.claude\/hooks\//
-              );
+              const pathMatch = hook.command.match(/\/(Users|home)\/[^/]+\/\.claude\/hooks\//);
               if (pathMatch) {
-                hook.command = hook.command.replace(
-                  pathMatch[0],
-                  "~/.claude/hooks/"
-                );
+                hook.command = hook.command.replace(pathMatch[0], "~/.claude/hooks/");
                 modified = true;
               }
             }
@@ -895,13 +890,7 @@ function fixHookPaths(verbose = false) {
         }
       }
     };
-    const hookTypes = [
-      "Notification",
-      "Stop",
-      "SubagentStop",
-      "PreToolUse",
-      "PostToolUse"
-    ];
+    const hookTypes = ["Notification", "Stop", "SubagentStop", "PreToolUse", "PostToolUse"];
     for (const hookType of hookTypes) {
       if (settings.hooks[hookType] && Array.isArray(settings.hooks[hookType])) {
         fixPathInHooks(settings.hooks[hookType]);
@@ -910,9 +899,7 @@ function fixHookPaths(verbose = false) {
     if (modified) {
       fs3.writeFileSync(settingsPath, JSON.stringify(settings, null, 2));
       if (verbose) {
-        import_devkit3.logger.info(
-          "\u2705 Fixed hook paths to use ~ expansion for Docker compatibility"
-        );
+        import_devkit3.logger.info("\u2705 Fixed hook paths to use ~ expansion for Docker compatibility");
       }
       return true;
     }

package/dist/packages/ai-toolkit-nx-claude/src/generators/hooks/install-orchestrator.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"install-orchestrator.d.ts","sourceRoot":"","sources":["../../../../../../src/generators/hooks/install-orchestrator.ts"],"names":[],"mappings":"AAMA;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B,cAAc,EAAE,OAAO,CAAC;IACxB,OAAO,EAAE,OAAO,CAAC;IACjB,MAAM,CAAC,EAAE,OAAO,CAAC;CAClB;AAED;;GAEG;AACH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,OAAO,CAAC;IACjB,aAAa,EAAE,MAAM,CAAC;IACtB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;CAC3B;AAKD;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,UAAQ,GAAG,MAAM,GAAG,IAAI,CAqClE;AAED;;;;;GAKG;AACH,wBAAsB,oBAAoB,CACxC,UAAU,EAAE,MAAM,EAClB,OAAO,EAAE,cAAc,GACtB,OAAO,CAAC,OAAO,CAAC,CAiDlB;AA0FD;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,MAAM,EAAE,GAAG,IAAI,CAwCpD;AAED;;;;;GAKG;AACH,wBAAsB,eAAe,CACnC,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,cAAc,GACtB,OAAO,CAAC,aAAa,CAAC,CAkExB;AAED;;;;GAIG;AACH,wBAAsB,aAAa,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CA0BxE;AAED;;;GAGG;AACH,wBAAsB,SAAS,IAAI,OAAO,CAAC,OAAO,CAAC,CAmClD"}
+{"version":3,"file":"install-orchestrator.d.ts","sourceRoot":"","sources":["../../../../../../src/generators/hooks/install-orchestrator.ts"],"names":[],"mappings":"AAMA;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B,cAAc,EAAE,OAAO,CAAC;IACxB,OAAO,EAAE,OAAO,CAAC;IACjB,MAAM,CAAC,EAAE,OAAO,CAAC;CAClB;AAED;;GAEG;AACH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,OAAO,CAAC;IACjB,aAAa,EAAE,MAAM,CAAC;IACtB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;CAC3B;AAKD;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,UAAQ,GAAG,MAAM,GAAG,IAAI,CAqClE;AAED;;;;;GAKG;AACH,wBAAsB,oBAAoB,CACxC,UAAU,EAAE,MAAM,EAClB,OAAO,EAAE,cAAc,GACtB,OAAO,CAAC,OAAO,CAAC,CAiDlB;AA6ED;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,MAAM,EAAE,GAAG,IAAI,CAwCpD;AAED;;;;;GAKG;AACH,wBAAsB,eAAe,CACnC,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,cAAc,GACtB,OAAO,CAAC,aAAa,CAAC,CAkExB;AAED;;;;GAIG;AACH,wBAAsB,aAAa,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CA0BxE;AAED;;;GAGG;AACH,wBAAsB,SAAS,IAAI,OAAO,CAAC,OAAO,CAAC,CAmClD"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniswap/ai-toolkit-nx-claude",
-  "version": "0.5.7",
+  "version": "0.5.9-next.0",
   "private": false,
   "main": "./dist/index.cjs",
   "module": "./dist/index.cjs",