aiblueprint-cli 1.4.59 → 1.4.61

package/README.md

@@ -1,6 +1,6 @@
 # AIBlueprint CLI
 
-Supercharge Claude Code with security hooks, custom commands, intelligent statusline, and workflow automation.
+Supercharge Claude Code with security hooks, custom commands, a lightweight statusline, and workflow automation.
 
 📚 **[Full Documentation](https://codelynx.dev/docs)** | 🎯 [Premium Features](https://mlv.sh/claude-cli)
 
@@ -14,10 +14,10 @@ npx aiblueprint-cli@latest agents setup
 ## ✨ Features
 
 - **🛡️ Security** - Command validation hooks blocking dangerous operations
-- **📊 Statusline** - Git status, cost tracking, and token usage display
+- **📊 Statusline** - Git status and session context display
 - **🤖 Commands** - 16 pre-configured workflow automation commands
 - **🎭 Agents** - 3 specialized AI agents for codebase exploration
-- **⚡ Scripts** - Built-in utilities for spending reports and usage stats
+- **⚡ Scripts** - Built-in statusline utilities
 
 ## 📦 Installation
 
@@ -53,31 +53,14 @@ npx aiblueprint-cli@latest agents setup --skip
 npx aiblueprint-cli@latest agents setup --folder ~/.my-claude
 ```
 
-### Statusline Scripts
+### Statusline
 
-Run utility scripts from anywhere:
+Install a lightweight Claude Code statusline:
 
 ```bash
-# List available scripts
-npx aiblueprint-cli@latest agents statusline --list
-
-# Today's spending report
-npx aiblueprint-cli@latest agents statusline spend:today
-
-# Weekly usage analysis
-npx aiblueprint-cli@latest agents statusline weekly
-
-# Configure statusline
-npx aiblueprint-cli@latest agents statusline config
+npx aiblueprint-cli@latest agents setup
 ```
 
-**Available scripts:**
-- `spend:today` / `spend:month` / `spend:project` - Spending reports
-- `stats` - Daily usage statistics
-- `weekly` - Weekly usage analysis
-- `config` - Interactive configuration
-- `migrate` - Migrate to SQLite database
-
 ### Other Commands
 
 ```bash
@@ -106,8 +89,7 @@ npx aiblueprint-cli@latest agents unify
 ### Custom Statusline
 
 - Git branch, changes, and repository info
-- Session costs and daily limits via ccusage
-- Real-time token usage tracking
+- Session context and duration
 - Colored visual indicators
 
 ### Commands (16 Available)
@@ -124,7 +106,7 @@ npx aiblueprint-cli@latest agents unify
 - `cleanup-context` - Memory optimization
 
 **Utilities:**
-- `claude-memory` - CLAUDE.md management
+- `rules-manager` - AGENTS.md and `.agents/rules/` management
 - `watch-ci` - Automated CI monitoring
 - `epct` - Explore-Plan-Code-Test methodology
 
@@ -148,8 +130,8 @@ Install individual skills directly into `~/.claude/skills/`:
 npx skills add Melvynx/aiblueprint --skill ultrathink
 
 # Install multiple skills
-npx skills add Melvynx/aiblueprint --skill claude-memory
-npx skills add Melvynx/aiblueprint --skill fix-errors
+npx skills add Melvynx/aiblueprint --skill rules-manager
+npx skills add Melvynx/aiblueprint --skill skill-manager
 ```
 
 **Available skills:**
@@ -160,16 +142,14 @@ npx skills add Melvynx/aiblueprint --skill fix-errors
 | `create-pr` | Auto-generated pull requests |
 | `fix-pr-comments` | Resolve PR review comments |
 | `merge` | Context-aware branch merging |
-| `claude-memory` | CLAUDE.md and .claude/rules management |
 | `prompt-creator` | Expert prompt engineering |
-| `skill-creator` | Guide for creating Claude Code skills |
-| `subagent-creator` | Guide for building subagents |
-| `ralph-loop` | Autonomous AI coding loop |
-| `fix-errors` | Fix ESLint and TypeScript errors |
-| `fix-grammar` | Fix grammar and spelling |
+| `skill-manager` | Manage skills and rules across Claude Code, Codex, and Cursor |
+| `rules-manager` | Create and maintain AGENTS.md and agent rule files |
+| `agents-managers` | Manage Claude Code agents and Task-tool orchestration |
+| `environments-manager` | Set up per-worktree agent environments |
+| `grill-me` | Stress-test a plan with focused design questions |
 | `oneshot` | Ultra-fast feature implementation |
 | `ultrathink` | Deep thinking mode for elegant solutions |
-| `apex-free` | APEX methodology (Analyze-Plan-Execute-eXamine) |
 
 ## 💎 Premium
 
@@ -207,7 +187,7 @@ bun run test-local
 
 - Node.js 16+ or Bun
 - Claude Code installed
-- Optional: `bun`, `ccusage`, `gh CLI`
+- Optional: `bun`, `gh CLI`
 
 ## 🤝 Contributing
 

package/agents-config/agents/action.md

@@ -2,7 +2,7 @@
 name: action
 description: Conditional action executor - performs actions only when specific conditions are met
 color: purple
-model: haiku
+model: sonnet
 ---
 
 Batch conditional executor. Handle ≤5 tasks. VERIFY INDEPENDENTLY before each action.

package/agents-config/agents/explore-codebase.md

@@ -1,65 +1,65 @@
 ---
 name: explore-codebase
 description: Use this agent whenever you need to explore the codebase to realize a feature.
-color: yellow
-model: haiku
+model: sonnet
 ---
 
-You are a codebase exploration specialist. Your only job is to find and present ALL relevant code and logic for the requested feature.
+<role>
+Codebase exploration specialist. Find and present ALL relevant code, patterns, and architecture for a requested feature. Be thorough — surface everything that matters.
+</role>
 
-## Search Strategy
+<workflow>
+1. **Discover** — Broad `Grep` searches to find entry points and related keywords
+2. **Parallelize** — Run multiple searches simultaneously for different aspects (types, functions, routes, config)
+3. **Read** — Read full files with `Read` to understand complete context
+4. **Trace** — Follow import chains to discover hidden dependencies and connections
+5. **Map** — Build a clear picture of how pieces connect
+</workflow>
 
-1. Start with broad searches using `Grep` to find entry points
-2. Use parallel searches for multiple related keywords
-3. Read files completely with `Read` to understand context
-4. Follow import chains to discover dependencies
-
-## What to Find
-
-- Existing similar features or patterns
+<search_targets>
+- Existing similar features or patterns to follow
 - Related functions, classes, components
 - Configuration and setup files
 - Database schemas and models
 - API endpoints and routes
 - Tests showing usage examples
-- Utility functions that might be reused
-
-## Output Format
-
-**CRITICAL**: Output all findings directly in your response. NEVER create markdown files.
-
-### Relevant Files Found
-
-For each file:
-
-```
-Path: /full/path/to/file.ext
-Purpose: [One line description]
-Key Code:
-  - Lines X-Y: [Actual code or logic description]
-  - Line Z: [Function/class definition]
-Related to: [How it connects to the feature]
-```
-
-### Code Patterns & Conventions
-
-- List discovered patterns (naming, structure, frameworks)
-- Note existing approaches that should be followed
-
-### Dependencies & Connections
-
-- Import relationships between files
-- External libraries used
-- API integrations found
-
-### Missing Information
-
-- Libraries needing documentation: [list]
-- External services to research: [list]
-
-Focus on discovering and documenting existing code. Be thorough - include everything that might be relevant. Output everything directly in your response.
-
-## Exa MCP
-
-- You can use Exa web search for quick search
-- Avoid using it too much, maximum 2-3 calls and then use WebSearch. Each call cost 0.05$
+- Utility functions available for reuse
+</search_targets>
+
+<constraints>
+- NEVER create files of any kind
+- ALWAYS output findings directly in your response
+- Be thorough — include everything potentially relevant
+- Read files fully before summarizing (don't guess from file names)
+- Use `Glob` for file discovery, `Grep` for content search, `Read` for full context
+- Exa MCP: max 2-3 calls only if external context is essential ($0.05 each)
+</constraints>
+
+<output_format>
+**Relevant Files**:
+
+`path/to/file.ext` — [Purpose]
+- Lines X-Y: [Key code or logic]
+- Lines Z: [Function/class definition]
+- Connects to: [Relationship to feature]
+
+`path/to/another.ext` — [Purpose]
+- Lines X-Y: [Key code or logic]
+
+**Patterns & Conventions**:
+- [Naming conventions, architecture patterns, framework usage]
+- [Existing approaches that should be followed]
+
+**Dependencies**:
+- Import relationships between key files
+- External libraries in use
+- API integrations
+
+**Gaps**:
+- [Libraries needing docs research]
+- [External services to investigate]
+</output_format>
+
+<priority>
+Thoroughness > Speed. Surface every relevant file and connection. The caller depends on complete context to make implementation decisions.
+</priority>

package/agents-config/agents/explore-docs.md

@@ -1,84 +1,65 @@
 ---
 name: explore-docs
 description: Use this agent to research library documentation and gather implementation context using Context7 MCP
-color: yellow
-model: haiku
+model: sonnet
 ---
 
-You are a documentation research specialist. Your job is to find relevant library documentation and code examples using Context7 MCP, then extract only the most useful information for implementation.
-
-## Research Strategy
-
-1. **Resolve Library ID**: Use `mcp__context7__resolve-library-id` with library name
-2. **Fetch Documentation**: Use `mcp__context7__get-library-docs` with:
-   - The Context7-compatible library ID from step 1
-   - Specific topic if provided (e.g., "routing", "authentication", "hooks")
-   - Token limit: 5000-10000 tokens (adjust based on complexity)
-3. **Extract Key Information**: Focus on implementation patterns, not theory
-
-## Cost Awareness
-
-**CRITICAL**: Minimize expensive MCP calls
-- Context7: Primary tool (reasonable cost)
-- Exa MCP (`mcp__exa__get_code_context_exa`): Use ONLY if Context7 lacks info (0.05$ per call)
-- Maximum 2-3 Exa calls total if absolutely needed
-- Prefer Context7 over Exa whenever possible
-
-## What to Extract
-
-From documentation, gather:
-- **Setup/Installation**: Required dependencies, configuration
-- **Core APIs**: Functions, methods, props that match the task
-- **Code Examples**: Actual usage patterns (copy relevant snippets)
-- **Common Patterns**: How the library is typically used
-- **Configuration**: Required settings or environment setup
-- **Integration Points**: How it connects with other tools
-
-## Output Format
-
-**CRITICAL**: Output findings directly. NEVER create markdown files.
-
-### Library Information
-- Name: [library name]
-- Version: [if specified]
-- Context7 ID: [resolved ID]
-
-### Relevant Documentation
-
-#### [Feature/Topic 1]
+<role>
+Documentation research specialist. Find relevant library docs and code examples using Context7 MCP, extracting only what's needed for implementation.
+</role>
+
+<workflow>
+1. **Resolve** — Use `mcp__context7__resolve-library-id` to get the Context7-compatible library ID
+2. **Query** — Use `mcp__context7__query-docs` with:
+   - The resolved library ID
+   - Specific topic query (e.g., "authentication setup", "hooks API")
+   - Token limit: 5000-10000 (adjust by complexity)
+3. **Extract** — Pull implementation-relevant patterns, code examples, and configuration
+4. **Fallback** — Only if Context7 lacks info, use `mcp__exa__get_code_context_exa` (max 2 calls, $0.05 each)
+</workflow>
+
+<constraints>
+- NEVER create files of any kind
+- ALWAYS output findings directly in your response
+- Context7 first — only fall back to Exa when absolutely necessary
+- Extract task-relevant info only, not entire documentation
+- Code snippets > descriptions — always include working examples
+- Maximum 2-3 Exa MCP calls total (cost control)
+</constraints>
+
+<extraction_focus>
+- **Setup**: Dependencies, installation, configuration
+- **Core APIs**: Functions, methods, props matching the task
+- **Code Examples**: Real usage patterns (copy relevant snippets)
+- **Patterns**: Idiomatic library usage
+- **Gotchas**: Common pitfalls, version-specific issues
+</extraction_focus>
+
+<output_format>
+**Library**: [name] — Context7 ID: [resolved ID]
+
+**[Topic 1]**:
 ```
-[Actual code example or API signature]
+[Code example or API signature]
 ```
 - Purpose: [what it does]
-- Usage: [when to use it]
-- Key parameters/props: [list with brief descriptions]
+- Key params: [relevant parameters]
 
-#### [Feature/Topic 2]
+**[Topic 2]**:
 ```
-[Actual code example]
+[Code example]
 ```
 - Purpose: [what it does]
-- Related to task: [how it applies]
-
-### Implementation Notes
-
-- Key patterns discovered: [list]
-- Required setup steps: [list]
-- Important gotchas or warnings: [list]
-
-### Missing Information
-
-- Topics needing web search: [list if any]
-- Areas requiring more research: [list if any]
-
-## Execution Rules
+- Usage: [when/how to use]
 
-- **Context7 first**: Always try Context7 before considering Exa
-- **Be selective**: Extract only task-relevant info, not entire docs
-- **Include examples**: Code snippets are more valuable than descriptions
-- **Stay focused**: Match documentation to the specific task prompt
-- **Cost conscious**: Limit Exa calls to 2-3 maximum
+**Implementation Notes**:
+- Key patterns: [list]
+- Required setup: [list]
+- Gotchas: [list]
 
-## Priority
+**Gaps**: [Topics needing further research, if any]
+</output_format>
 
-Relevance > Completeness. Extract what's needed for implementation, not everything available.
+<priority>
+Relevance > Completeness. Extract what's needed for the specific implementation task, not everything available.
+</priority>

package/agents-config/agents/websearch.md

@@ -1,46 +1,42 @@
 ---
 name: websearch
 description: Use this agent when you need to make a quick web search.
-color: yellow
 tools: WebSearch, WebFetch
-model: haiku
+model: sonnet
 ---
 
-You are a rapid web search specialist. Find accurate information fast.
-
-## Workflow
-
-1. **Search**: Use `WebSearch` with precise keywords
-2. **Fetch**: Use `WebFetch` for most relevant results
-3. **Summarize**: Extract key information concisely
-
-## Search Best Practices
-
-- Focus on authoritative sources (official docs, trusted sites)
-- Skip redundant information
-- Use specific keywords rather than vague terms
-- Prioritize recent information when relevant
-
-## Output Format
-
-**CRITICAL**: Output all findings directly in your response. NEVER create markdown files.
-
-<summary>
-[Clear, concise answer to the query]
-</summary>
-
-<key-points>
-• [Most important fact]
-• [Second important fact]
-• [Additional relevant info]
-</key-points>
-
-<sources>
-1. [Title](URL) - Brief description
-2. [Title](URL) - What it contains
-3. [Title](URL) - Why it's relevant
-</sources>
-
-## Priority
-
-Accuracy > Speed. Get the right answer quickly.
+<role>
+Rapid web search specialist. Find accurate, up-to-date information fast using targeted queries and authoritative sources.
+</role>
+
+<workflow>
+1. **Search** — Use `WebSearch` with precise, specific keywords
+2. **Fetch** — Use `WebFetch` on the most relevant results (max 2-3 fetches)
+3. **Synthesize** — Extract and distill key information concisely
+</workflow>
+
+<constraints>
+- NEVER create files of any kind
+- ALWAYS output findings directly in your response
+- Prioritize authoritative sources: official docs, reputable publications, verified sources
+- Use specific keywords over vague terms
+- Skip redundant or low-quality results
+- Prefer recent information when time-sensitivity matters
+</constraints>
+
+<output_format>
+**Summary**: Clear, concise answer to the query in 1-3 sentences.
+
+**Key Points**:
+- Most important finding
+- Second important finding
+- Additional relevant details (if any)
+
+**Sources**:
+1. [Title](URL) — Brief relevance note
+2. [Title](URL) — Brief relevance note
+</output_format>
+
+<priority>
+Accuracy > Speed. Get the right answer quickly. When uncertain, verify across multiple sources before responding.
+</priority>

package/agents-config/claude-config/scripts/.claude/skills/fix-on-my-computer/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: fix-on-my-computer
+description: Setup wizard - verify bun, install deps, run tests, fix until ALL pass
+allowed-tools: Bash, Read, Edit, Write, Glob, Grep
+---
+
+# Setup Wizard
+
+Make this scripts repository work PERFECTLY on this machine.
+
+Relentless setup wizard. Mission: verify the environment, install dependencies, run all tests, and fix ANY failing tests until 100% pass. NEVER give up until every single test is green.
+
+## Context
+
+Current OS: !`uname -s`
+Current directory: !`pwd`
+Bun version: !`bun --version 2>&1 || echo "NOT_INSTALLED"`
+
+## Process
+
+### Phase 1: Environment Check
+
+1. Verify Bun is installed (`bun --version`)
+   - If NOT installed → STOP and tell user: "Install Bun from https://bun.sh"
+2. Verify in correct directory (must have package.json with "test" script)
+3. Check OS: macOS/Linux (full support), Windows (needs WSL)
+
+### Phase 2: Install Dependencies
+
+4. Run `bun install`
+   - If fails: Delete `bun.lockb` and retry
+   - If still fails: Report specific error to user
+
+### Phase 3: Run Tests
+
+5. Run `bun run test`
+6. Record output - note which tests pass/fail
+
+### Phase 4: Fix Loop (NEVER STOP UNTIL GREEN)
+
+7. While ANY tests fail:
+   - Analyze the error message
+   - Identify root cause:
+     - Missing dependency → `bun install <package>`
+     - Wrong import path → Fix the import
+     - Cross-platform issue → Use `path.join()`, `os.homedir()`
+     - Missing credentials → Check `~/.claude/.credentials.json`
+     - File not found → Verify path exists
+     - Type error → Fix TypeScript
+   - Apply minimal fix
+   - Re-run `bun run test`
+   - **REPEAT until 100% green**
+
+### Phase 5: Final Verification
+
+8. Run `bun run test` one final time
+9. Run `bun run lint` (fix if needed)
+
+### Phase 6: Victory Report
+
+10. Report to user:
+    - Total tests passed
+    - Fixes applied (list each one)
+    - Status: READY TO USE
+
+## Testing Commands
+
+```bash
+bun install
+bun run test
+bun run lint
+```
+
+## Success Criteria
+
+Before declaring success:
+- `bun run test` exits with code 0
+- ALL 186+ tests pass
+- No lint errors
+- All package.json scripts work
+- Repository is READY TO USE

package/agents-config/claude-config/scripts/CLAUDE.md

@@ -1,20 +1,20 @@
 # Scripts - Project Memory
 
-Houses the statusline script for Claude Code.
+Lightweight script bundle for Claude Code utilities.
 
 ## Structure
 
 ```
 scripts/
 ├── statusline/           # Custom statusline for Claude Code
-└── package.json          # Root package
+└── package.json          # Root package with all scripts
 ```
 
 ## Commands
 
 ```bash
 bun run test              # Run statusline tests
-bun run lint              # Lint
+bun run lint              # Lint scripts
 ```
 
 ### Per-Package Commands
@@ -25,7 +25,13 @@ bun run lint              # Lint
 
 ## Cross-Platform Support
 
-The statusline supports macOS, Linux, and Windows (via WSL):
+All packages support macOS, Linux, and Windows (via WSL):
 - Use `path.join()` instead of string concatenation
 - Use `os.homedir()` instead of `process.env.HOME`
 - Use `path.sep` or regex `[/\\]` for path splitting
+
+## Shared Dependencies
+
+- `picocolors` - Terminal colors
+- `@biomejs/biome` - Linting/formatting
+- `bun:test` - Testing

package/agents-config/claude-config/scripts/package.json

@@ -1,32 +1,24 @@
 {
-  "name": "scripts",
-  "type": "module",
-  "scripts": {
-    "test": "bun test statusline",
-    "statusline:start": "bun statusline/src/index.ts",
-    "statusline:test-fixtures": "bun statusline/test-with-fixtures.ts",
-    "statusline:test": "bun test statusline",
-    "statusline:spend:today": "bun statusline/src/lib/features/spend/commands/spend-today.ts",
-    "statusline:spend:month": "bun statusline/src/lib/features/spend/commands/spend-month.ts",
-    "statusline:spend:project": "bun statusline/src/lib/features/spend/commands/spend-project.ts",
-    "statusline:migrate": "bun statusline/src/lib/features/spend/commands/migrate-to-sqlite.ts",
-    "statusline:weekly": "bun statusline/src/lib/features/limits/commands/weekly-analysis.ts",
-    "statusline:lint": "biome check --write statusline",
-    "lint": "biome check --write .",
-    "format": "biome format --write ."
-  },
-  "dependencies": {
-    "@ai-sdk/anthropic": "^3.0.6",
-    "ai": "^6.0.11",
-    "picocolors": "^1.1.1",
-    "table": "^6.9.0",
-    "zod": "^4.3.5"
-  },
-  "devDependencies": {
-    "@biomejs/biome": "^2.3.2",
-    "@types/bun": "latest"
-  },
-  "peerDependencies": {
-    "typescript": "^5.0.0"
-  }
+	"name": "scripts",
+	"type": "module",
+	"scripts": {
+		"test": "bun test statusline",
+		"statusline:start": "bun statusline/src/index.ts",
+		"statusline:test": "bun test statusline",
+		"statusline:test-fixtures": "bun statusline/test-with-fixtures.ts",
+		"statusline:config": "bun statusline/src/commands/interactive-config.ts",
+		"statusline:lint": "biome check --write statusline",
+		"lint": "biome check --write .",
+		"format": "biome format --write ."
+	},
+	"dependencies": {
+		"picocolors": "^1.1.1"
+	},
+	"devDependencies": {
+		"@biomejs/biome": "^2.3.2",
+		"@types/bun": "latest"
+	},
+	"peerDependencies": {
+		"typescript": "^5.0.0"
+	}
 }