@allthingsclaude/blueprints 0.2.0 → 0.3.0-beta.10

package/README.md

@@ -39,11 +39,29 @@ npx @allthingsclaude/blueprints --path /path/to/install
 
 # Skip confirmation prompts
 npx @allthingsclaude/blueprints --global --yes
+
+# Set agent power level (1-5, default: 4)
+npx @allthingsclaude/blueprints --power 5
+
+# Customize tasks directory name (default: tasks)
+npx @allthingsclaude/blueprints --tasks-dir my-tasks
 ```
 
+### Agent Power Levels
+
+Control which models power your agents:
+
+| Level | Name | Lightweight | Research | Standard | Heavyweight |
+|-------|------|-------------|----------|----------|-------------|
+| 1 | Economy | Haiku | Haiku | Haiku | Sonnet |
+| 2 | Balanced | Haiku | Haiku | Sonnet | Sonnet |
+| 3 | Standard | Sonnet | Sonnet | Sonnet | Sonnet |
+| **4** | **Enhanced (default)** | **Sonnet** | **Opus** | **Opus** | **Opus** |
+| 5 | Maximum | Opus | Opus | Opus | Opus |
+
 ---
 
-## Commands by Category
+## Commands (29)
 
 ### Planning & Execution
 
@@ -53,6 +71,7 @@ npx @allthingsclaude/blueprints --global --yes
 | `/kickoff` | Execute a plan interactively with approval gates (collaborative) |
 | `/implement` | Execute a plan autonomously (hands-off) |
 | `/parallelize` | Execute independent plan tasks across multiple agents simultaneously |
+| `/auto` | Full autonomous development loop — from idea to committed code |
 | `/finalize` | Complete a work phase - update plans, commit changes, document decisions |
 
 ### Project Setup
@@ -75,7 +94,18 @@ npx @allthingsclaude/blueprints --global --yes
 | `/audit` | Pre-commit security and quality review |
 | `/test` | Run tests, analyze failures, generate test coverage |
 | `/cleanup` | Find and remove dead code, unused imports, technical debt |
-| `/refactor` | DRY analysis, pattern extraction, safe refactoring with validation |
+| `/refactor` | Safe refactoring — rename, extract, inline, or move code with validation |
+| `/dry` | Eliminate DRY violations without changing behavior |
+| `/secure` | Run a focused security scan on your codebase |
+
+### Code Operations
+
+| Command | Description |
+|---------|-------------|
+| `/commit` | Create a well-crafted git commit from your current changes |
+| `/changelog` | Generate a changelog from git history |
+| `/docs` | Generate or update project documentation |
+| `/migrate` | Upgrade dependencies or migrate between framework versions |
 
 ### Thinking Modes
 
@@ -92,13 +122,20 @@ npx @allthingsclaude/blueprints --global --yes
 |---------|-------------|
 | `/debug` | Systematic investigation with root cause analysis and fix options |
 
+### Creative
+
+| Command | Description |
+|---------|-------------|
+| `/imagine` | Generate images using Nano Banana Pro (Gemini/fal.ai) |
+| `/storyboard` | Extract UI interaction specs from video mockups |
+
 ### Session Management
 
 | Command | Description |
 |---------|-------------|
 | `/handoff` | Generate comprehensive documentation for context switching |
 | `/pickup` | Resume work from a previous handoff document |
-| `/flush` | Clear all temporary files from `.claude/temp/` |
+| `/flush` | Clear all task artifacts from `tasks/` |
 
 ---
 
@@ -349,25 +386,50 @@ When you have a plan, choose how to execute it:
 | **Interactive** | `/kickoff` | Complex changes where you want approval gates and collaboration |
 | **Autonomous** | `/implement` | Well-defined tasks you trust to run hands-off |
 | **Parallel** | `/parallelize` | Plans with independent tasks that can run simultaneously |
+| **Full Auto** | `/auto` | End-to-end: idea → plan → implement → test → commit |
 
 ---
 
-## Agents (10)
+## Agents (23)
 
-Agents are specialized workers launched by commands:
+Agents are specialized workers launched by commands. Each agent is assigned a model based on your chosen power level and its tier classification.
+
+### Agent Tiers
+
+| Tier | Agents | Description |
+|------|--------|-------------|
+| **Lightweight** | commit, changelog, handoff, cleanup, imagine | Rote tasks — fast models suffice |
+| **Research** | research-codebase, research-docs, research-web | Search and synthesize |
+| **Standard** | plan, implement, parallelize, bootstrap, refactor, test, explain, docs, dry, storyboard | Balanced reasoning |
+| **Heavyweight** | audit, debug, secure | Deep reasoning, high-stakes analysis |
+
+### Agent List
 
 | Agent | Used By | Purpose |
 |-------|---------|---------|
 | `audit` | `/audit` | Code quality and security analysis |
 | `bootstrap` | `/bootstrap` | Project scaffolding and setup |
+| `changelog` | `/changelog` | Changelog generation from git history |
+| `cleanup` | `/cleanup` | Dead code and unused import removal |
+| `commit` | `/commit` | Git commit message crafting |
+| `debug` | `/debug` | Systematic root cause investigation |
+| `docs` | `/docs` | Documentation generation and updates |
+| `dry` | `/dry` | DRY violation detection and elimination |
+| `explain` | `/explain` | Code and architecture explanations |
 | `finalize` | `/finalize` | Session wrap-up and commits |
 | `handoff` | `/handoff` | Context documentation |
+| `imagine` | `/imagine` | Image generation via Nano Banana Pro |
 | `implement` | `/implement` | Autonomous plan execution |
+| `migrate` | `/migrate` | Dependency upgrades and migrations |
 | `parallelize` | `/parallelize` | Multi-agent orchestration |
 | `plan` | `/plan` | Structured plan creation |
+| `refactor` | `/refactor` | Safe code refactoring with validation |
 | `research-codebase` | `/research` | Code exploration |
 | `research-docs` | `/research` | Library documentation lookup |
 | `research-web` | `/research` | Online resource research |
+| `secure` | `/secure` | Security scanning and vulnerability detection |
+| `storyboard` | `/storyboard` | UI interaction spec extraction |
+| `test` | `/test` | Test execution and failure analysis |
 
 ---
 
@@ -377,22 +439,28 @@ After installation, your `.claude` directory will contain:
 
 ```
 .claude/
-├── commands/          # 20 command files
+├── commands/          # 29 command files
 │   ├── audit.md
+│   ├── auto.md
 │   ├── bootstrap.md
 │   ├── brainstorm.md
 │   └── ...
-├── agents/            # 10 agent files
+├── agents/            # 23 agent files
 │   ├── audit.md
 │   ├── bootstrap.md
-│   ├── finalize.md
+│   ├── changelog.md
 │   └── ...
-└── temp/              # Runtime files (created during use)
-    ├── PLAN_*.md      # Implementation plans
-    ├── HANDOFF.md     # Session handoff document
-    └── ...
+tasks/                         # Runtime artifacts (created during use)
+├── plans/
+│   └── PLAN_*.md              # Implementation plans
+├── sessions/
+│   ├── HANDOFF.md             # Session handoff document
+│   └── PHASE_SUMMARY_*.md    # Phase summaries
+└── STATE.md                   # Active plan tracker
 ```
 
+> The `tasks/` directory name is configurable during installation via `--tasks-dir`. Template variables (`{{TASKS_DIR}}`, `{{PLANS_DIR}}`, `{{SESSIONS_DIR}}`) are resolved at install time.
+
 ---
 
 ## Platform Support

package/content/agents/audit.md

@@ -2,7 +2,7 @@
 name: audit
 description: Review code changes before committing
 tools: Bash, Read, Grep
-model: sonnet
+model: {{MODEL}}
 author: "@markoradak"
 ---
 
@@ -23,6 +23,21 @@ Review all staged and unstaged changes to:
 
 ## Analysis Steps
 
+### 0. Detect Toolchain
+
+Before running any commands, detect the project's package manager and available scripts:
+
+```bash
+cat package.json 2>/dev/null | head -30
+```
+
+- If `pnpm-lock.yaml` exists → use `pnpm`
+- If `yarn.lock` exists → use `yarn`
+- If `bun.lockb` exists → use `bun`
+- If `package-lock.json` exists → use `npm`
+- Check `scripts` in package.json for available typecheck/lint/test/build commands
+- Use the detected package manager for ALL subsequent commands
+
 ### 1. Gather Changes
 
 Run these commands to understand what's being changed:
@@ -135,13 +150,12 @@ Go through each change systematically:
 
 ### 4. Check Project-Specific Rules
 
-Review against CLAUDE.md requirements:
-- Multi-tenant considerations (site isolation)
-- Proper middleware usage
-- tRPC router patterns
-- Prisma best practices
+Review against CLAUDE.md requirements (if present):
+- Project-specific architectural patterns
+- Framework-specific conventions
+- Database/ORM best practices
 - Environment variable usage
-- Package manager (pnpm) compliance
+- Package manager compliance
 
 ### 5. Look for Common Pitfalls
 
@@ -273,9 +287,9 @@ Provide a comprehensive audit report:
 - [ ] No commented-out code (unless with explanation)
 - [ ] Environment variables properly configured
 - [ ] Database migrations created if needed
-- [ ] Type errors resolved (`pnpm typecheck`)
-- [ ] Linter passes (`pnpm lint`)
-- [ ] Build succeeds (`pnpm build`)
+- [ ] Type errors resolved (run typecheck script)
+- [ ] Linter passes (run lint script)
+- [ ] Build succeeds (run build script)
 
 ---
 
@@ -301,7 +315,7 @@ Provide a comprehensive audit report:
 
 **Next Steps**:
 1. Address critical and important issues
-2. Run `pnpm check` to verify TypeScript and linting
+2. Run typecheck and lint to verify
 3. Run tests if applicable
 4. Review this audit report items
 5. Stage final changes: `git add .`
@@ -321,7 +335,7 @@ How would you like to proceed?
 
 1. **Review only** - I'll just show the audit report (done above)
 2. **Auto-fix** - I'll attempt to automatically fix critical and important issues
-3. **Create fix plan** - I'll generate `.claude/temp/PLAN_AUDIT_FIXES.md` with systematic fixes
+3. **Create fix plan** - I'll generate `{{PLANS_DIR}}/PLAN_AUDIT_FIXES.md` with systematic fixes
 
 Type 1, 2, or 3 (or just describe what you'd like to do).
 ```
@@ -372,7 +386,12 @@ When user chooses auto-fix:
 
 When user chooses to create a fix plan:
 
-1. **Generate PLAN_AUDIT_FIXES.md** using Write tool at `.claude/temp/PLAN_AUDIT_FIXES.md`
+1. **Ensure the output directory exists**:
+   ```bash
+   mkdir -p {{PLANS_DIR}}
+   ```
+
+2. **Generate PLAN_AUDIT_FIXES.md** using Write tool at `{{PLANS_DIR}}/PLAN_AUDIT_FIXES.md`
 
 2. **Plan structure**:
    ```markdown
@@ -428,7 +447,7 @@ When user chooses to create a fix plan:
 
 3. **Inform user**:
    ```markdown
-   ✅ Fix plan created at `.claude/temp/PLAN_AUDIT_FIXES.md`
+   ✅ Fix plan created at `{{PLANS_DIR}}/PLAN_AUDIT_FIXES.md`
 
    **Next Steps**:
    1. Review the plan
@@ -471,27 +490,23 @@ When user chooses to create a fix plan:
 
 ## Special Considerations
 
-### Multi-Tenant Context
-When reviewing this project, always check:
-- Is site isolation maintained?
-- Are queries properly filtered by site/domain?
-- Could data leak between tenants?
-- Are middleware checks in place?
-
-### Type Safety
-This project uses strict TypeScript:
+### Type Safety (if TypeScript project)
 - Every `any` should be justified
 - Prefer unknown over any
 - Use proper type guards
-- Validate external data with Zod
+- Validate external data at system boundaries
 
 ### Performance
-This is an e-commerce platform:
 - Database queries must be efficient
 - Consider caching strategies
 - Check for N+1 issues
 - Validate pagination exists for lists
 
+### Project-Specific Rules
+- Read CLAUDE.md (if present) for project-specific architectural guidelines
+- Check for multi-tenant isolation if applicable
+- Verify framework-specific best practices
+
 ## Example Issues
 
 ### Critical Example

package/content/agents/bootstrap.md

@@ -2,7 +2,7 @@
 name: bootstrap
 description: Generate plan and bootstrap script for new projects
 tools: Bash, Read, Grep, Write, SlashCommand
-model: sonnet
+model: {{MODEL}}
 author: "@markoradak"
 ---
 
@@ -10,7 +10,7 @@ You are a project bootstrap specialist. Your role is to analyze a brainstorming
 
 ## Your Mission
 
-1. First, invoke the `/plan` command to generate `.claude/temp/PLAN_{NAME}.md`
+1. First, invoke the `/plan` command to generate `{{PLANS_DIR}}/PLAN_{NAME}.md`
 2. Then, create an executable `bootstrap.sh` script in the current directory
 3. Provide clear next steps for the user
 
@@ -291,7 +291,7 @@ main() {
   echo "========================================"
   echo ""
   echo "Next steps:"
-  echo "  1. Review .claude/temp/PLAN_{NAME}.md for implementation plan"
+  echo "  1. Review {{PLANS_DIR}}/PLAN_{NAME}.md for implementation plan"
   echo "  2. Update environment variables in .env"
   echo "  3. Start development: $PKG_MANAGER dev"
   echo ""
@@ -326,7 +326,7 @@ Based on the conversation, customize:
 After creating both the plan and bootstrap script, respond with:
 
 ```
-✅ Plan generated at `.claude/temp/PLAN_{NAME}.md`
+✅ Plan generated at `{{PLANS_DIR}}/PLAN_{NAME}.md`
 ✅ Bootstrap script created at `./bootstrap.sh`
 
 **Project Summary**:
@@ -339,7 +339,7 @@ After creating both the plan and bootstrap script, respond with:
 
 1. Review the plan:
    \`\`\`bash
-   cat .claude/temp/PLAN_{NAME}.md
+   cat {{PLANS_DIR}}/PLAN_{NAME}.md
    \`\`\`
 
 2. Review the bootstrap script:
@@ -366,6 +366,26 @@ After creating both the plan and bootstrap script, respond with:
 - Use `/kickoff {NAME}` when ready to start coding
 ```
 
+## Error Recovery
+
+### Plan Generation Fails
+If the `/plan` invocation fails or produces an incomplete plan:
+1. Report the error to the user
+2. Ask if they want to provide more context or try again
+3. Do NOT proceed to generating bootstrap.sh without a plan
+
+### Project Already Exists
+If the current directory already has a `package.json` or project files:
+1. Warn the user that existing files were detected
+2. List the conflicting files
+3. Ask whether to proceed (augment existing project) or abort
+4. If proceeding, ensure `bootstrap.sh` guards against overwriting existing files
+
+### Missing Prerequisites
+If the required Node.js version, package manager, or other tools aren't installed:
+1. The bootstrap script should detect this and print a clear error with install instructions
+2. Include prerequisite checks at the top of bootstrap.sh (before any file creation)
+
 ## Important Notes
 
 - The script should NEVER overwrite existing files without warning