@allthingsclaude/blueprints 0.2.0 → 0.3.0-beta.10

package/content/commands/refactor.md

@@ -1,18 +1,20 @@
 ---
-description: Safely refactor code with DRY analysis, pattern extraction, and validation
-argument-hint: [operation] [target] (e.g., "dry-check", "rename:old:new", "extract:ComponentName")
+description: Safely rename, extract, inline, or move code with validation
+argument-hint: [operation] [target] (e.g., "rename:old:new", "extract:ComponentName", "move:src:dest")
 author: "@markoradak"
 ---
 
 # Refactor Assistant
 
-I'll help you safely refactor code with a focus on DRY principles, pattern extraction, and thorough validation.
+I'll help you safely restructure code — renaming, extracting, inlining, or moving — with validation after every change.
+
+> **When to use**: You know what structural change you want to make. Use `/dry` to find and consolidate duplications, `/cleanup` to remove dead/unused code, or `/audit` to review changes before committing.
 
 ## Current State
 
 **Working Directory**: !`pwd`
 
-**Branch**: !`git branch --show-current`
+**Branch**: !`git branch --show-current 2>/dev/null || echo "Not a git repository"`
 
 **Status**:
 !`git status --short`
@@ -25,382 +27,22 @@ $ARGUMENTS
 
 ---
 
-## Refactoring Operations
-
-### `dry-check` or no argument
-Analyze codebase for DRY violations and duplication opportunities.
-
-### `rename:oldName:newName`
-Safely rename a function, component, variable, or type across the codebase.
-
-### `extract:Name`
-Extract repeated code into a reusable function, component, or hook.
-
-### `inline:Name`
-Inline a function/component that's only used once or adds unnecessary abstraction.
-
-### `move:source:destination`
-Move a function/component to a different file with all imports updated.
-
-### `consolidate:pattern`
-Find and consolidate similar implementations into one.
-
----
-
-## DRY Analysis Framework
-
-### Duplication Categories
-
-**1. Exact Duplication**
-- Copy-pasted code blocks
-- Identical functions in different files
-- Repeated component structures
-
-**2. Structural Duplication**
-- Same pattern with different values
-- Similar functions with minor variations
-- Components that differ only in props
-
-**3. Logical Duplication**
-- Same business logic in multiple places
-- Repeated validation patterns
-- Similar error handling
-
-**4. Data Duplication**
-- Repeated constants/magic values
-- Similar type definitions
-- Duplicate API endpoint definitions
-
-### Detection Strategy
-
-```bash
-# Find similar code blocks (requires manual review)
-# Look for repeated patterns
-grep -rn "pattern" src/ --include="*.ts" --include="*.tsx"
-
-# Find duplicate function names
-grep -rn "function functionName\|const functionName" src/
-
-# Find similar component structures
-grep -rn "className=\"similar-class\"" src/
-```
-
----
-
-## DRY Check Output Format
-
-```markdown
-# DRY Analysis Report
-
-**Scanned**: [X] files
-**Duplications Found**: [Y] instances
-**Estimated Lines Saveable**: [Z]
-
----
-
-## High Priority (Extract Immediately)
-
-### 1. [Duplication Name]
-
-**Type**: Exact / Structural / Logical
-
-**Occurrences**:
-- `src/components/A.tsx:23-45` (22 lines)
-- `src/components/B.tsx:67-89` (22 lines)
-- `src/pages/C.tsx:12-34` (22 lines)
-
-**Current Code** (from first occurrence):
-```typescript
-// Repeated code block
-```
-
-**Proposed Extraction**:
-
-**New File**: `src/lib/extracted.ts` or `src/components/Shared.tsx`
-
-```typescript
-// Extracted reusable code
-export function extractedFunction() {
-  // ...
-}
-```
-
-**Refactored Usage**:
-```typescript
-import { extractedFunction } from '@/lib/extracted'
-
-// Use it
-extractedFunction()
-```
-
-**Impact**:
-- Lines removed: [X]
-- Files affected: [Y]
-- Maintainability: Improved (single source of truth)
-
----
-
-## Medium Priority (Consider Extracting)
-
-### 2. [Duplication Name]
-
-**Type**: Structural
-
-**Occurrences**: 2 places
-
-**Pattern**:
-```typescript
-// Similar structure, different values
-```
-
-**Options**:
-1. **Extract with parameters**: Create function with configurable parts
-2. **Leave as-is**: If variations are likely to diverge
-3. **Create factory**: If generating similar structures
-
-**Recommendation**: [Which option and why]
-
----
-
-## Low Priority (Monitor)
-
-### 3. [Duplication Name]
-
-**Note**: Only 2 occurrences, may diverge in future
-
----
-
-## Type/Interface Duplication
-
-| Type | Locations | Recommendation |
-|------|-----------|----------------|
-| `UserData` | `types/user.ts`, `api/users.ts` | Consolidate to `types/user.ts` |
-| `ApiResponse` | 5 different files | Create shared `types/api.ts` |
-
----
-
-## Constants Duplication
-
-| Value | Occurrences | Recommendation |
-|-------|-------------|----------------|
-| `"api/v1"` | 12 files | Extract to `lib/constants.ts` |
-| `3000` | 4 files | Extract as `DEFAULT_PORT` |
-
----
-
-## Summary
-
-| Priority | Count | Lines Saveable |
-|----------|-------|----------------|
-| High | X | ~Y lines |
-| Medium | X | ~Y lines |
-| Low | X | ~Y lines |
-
-**Total Potential Reduction**: ~[Z] lines ([N]% of codebase)
-
----
-
-## Recommended Actions
-
-1. [ ] Extract [high priority item 1]
-2. [ ] Extract [high priority item 2]
-3. [ ] Consolidate types to shared location
-4. [ ] Create constants file for repeated values
-
-Would you like me to perform any of these extractions?
-```
-
----
-
-## Rename Operation
-
-### Safety Protocol
-
-1. **Find all references** (not just text matches):
-   - Variable/function declarations
-   - Import statements
-   - Type references
-   - String literals (if component name)
-   - Test files
-   - Documentation/comments
-
-2. **Validate scope**:
-   - Is this a local or exported symbol?
-   - Are there name conflicts with new name?
-   - Will imports need updating?
-
-3. **Execute rename**:
-   - Update declaration
-   - Update all usages
-   - Update imports/exports
-   - Update related test files
-
-4. **Verify**:
-   - Run typecheck
-   - Run lint
-   - Run related tests
-
-### Rename Output
-
-```markdown
-# Rename: `oldName` -> `newName`
-
-## Scope Analysis
-
-**Symbol Type**: [function/component/type/variable]
-**Defined In**: `src/lib/file.ts:23`
-**Exported**: [Yes/No]
-
-## References Found
-
-| File | Line | Context |
-|------|------|---------|
-| `src/lib/file.ts` | 23 | Definition |
-| `src/components/A.tsx` | 5 | Import |
-| `src/components/A.tsx` | 34 | Usage |
-| `src/tests/file.test.ts` | 12 | Test |
-
-**Total**: [X] references in [Y] files
-
-## Changes to Make
-
-### `src/lib/file.ts`
-- Line 23: `export function oldName` -> `export function newName`
-
-### `src/components/A.tsx`
-- Line 5: `import { oldName }` -> `import { newName }`
-- Line 34: `oldName()` -> `newName()`
-
-## Verification Plan
-
-1. [ ] Apply all changes
-2. [ ] Run `pnpm typecheck`
-3. [ ] Run `pnpm lint`
-4. [ ] Run `pnpm test [related]`
-
-Proceed with rename?
-```
-
----
-
-## Extract Operation
-
-### Extraction Checklist
-
-1. **Identify boundaries**:
-   - What are the inputs?
-   - What are the outputs?
-   - What are the side effects?
-
-2. **Choose location**:
-   - Same file (private helper)?
-   - `lib/` (utility function)?
-   - `components/` (React component)?
-   - `hooks/` (custom hook)?
-
-3. **Define interface**:
-   - Function signature
-   - Props interface (for components)
-   - Return type
-
-4. **Extract and replace**:
-   - Create new function/component
-   - Replace original code with call
-   - Update imports
-
-5. **Verify**:
-   - Types match at call sites
-   - Behavior unchanged
-   - Tests pass
-
-### Extract Output
-
-```markdown
-# Extract: `NewComponentName`
-
-## Source Analysis
-
-**Extracting from**: `src/components/Large.tsx:45-78`
-**Reason**: [DRY violation / Reusability / Clarity]
-
-## Extracted Code
-
-**New File**: `src/components/NewComponentName.tsx`
-
-```typescript
-interface NewComponentNameProps {
-  // Inferred from usage
-}
-
-export function NewComponentName({ ... }: NewComponentNameProps) {
-  // Extracted code
-}
-```
-
-## Updated Original
-
-**File**: `src/components/Large.tsx`
-
-```typescript
-import { NewComponentName } from './NewComponentName'
-
-// ...
-<NewComponentName {...props} />
-```
-
-## Other Usages to Update
-
-- `src/components/Other.tsx:34` - Same pattern exists
-- `src/pages/Page.tsx:56` - Similar code
-
-Proceed with extraction?
-```
-
----
-
-## Validation Requirements
-
-After ANY refactoring operation:
-
-```bash
-# Type check - MUST pass
-pnpm typecheck
-
-# Lint - MUST pass
-pnpm lint
-
-# Tests - MUST pass
-pnpm test:run
-
-# Build - Should pass
-pnpm build
-```
-
-**If any fail**: Revert changes and investigate.
-
----
-
-## Refactoring Principles
+## Supported Operations
 
-### DO
-- Extract when 3+ occurrences exist
-- Keep extracted units focused (single responsibility)
-- Name clearly based on purpose
-- Maintain backwards compatibility when possible
-- Test before and after
+- `rename:oldName:newName` — Safe rename across all references
+- `extract:Name` — Extract repeated code into reusable unit
+- `inline:Name` — Inline unnecessary abstraction
+- `move:source:destination` — Move with all imports updated
+- `consolidate:pattern` — Consolidate similar implementations
 
-### DON'T
-- Extract prematurely (wait for patterns to emerge)
-- Create abstractions for 1-2 usages
-- Mix concerns in extracted units
-- Change behavior during refactoring
-- Skip validation steps
+## Launching Refactor Agent
 
-### DRY Balance
-- **Too DRY**: Over-abstracted, hard to understand
-- **Too WET**: Maintenance nightmare, inconsistencies
-- **Just Right**: Clear abstractions, obvious where to change things
-
----
+The refactor agent will:
+- Detect your toolchain (package manager, available scripts)
+- Capture a baseline (typecheck, lint, tests)
+- Analyze code and present a plan before making changes
+- Apply changes one at a time with validation after each
+- Revert immediately if any validation fails
+- Guarantee zero behavior change
 
-Analyze the refactoring request and execute the appropriate operation. Use Grep to find patterns, Read to understand context, Edit to make changes, and Bash to validate. Always show the plan before executing.
+Use the Task tool to launch the refactor agent (subagent_type="refactor") with the refactoring request and any additional context from arguments.

package/content/commands/release.md

@@ -0,0 +1,63 @@
+---
+description: Create a release — version bump, changelog, tag, and publish
+argument-hint: [optional: major | minor | patch | version number | --dry-run]
+author: "@markoradak"
+---
+
+# Release
+
+I'll orchestrate a complete release for your project — detecting existing release scripts and tooling first.
+
+> **When to use**: You're ready to cut a release. This handles version bumping, changelog updates, git tagging, and optionally GitHub Releases or publishing. Use `/changelog` if you only want to generate a changelog without releasing. Use `/commit` for a simple commit without release semantics.
+
+## Current State
+
+**Working Directory**: !`pwd`
+
+**Branch**: !`git branch --show-current 2>/dev/null || echo "Not a git repository"`
+
+**Status**:
+!`git status --short`
+
+**Current Version**:
+!`cat package.json 2>/dev/null | grep '"version"' | head -1 || cat Cargo.toml 2>/dev/null | grep '^version' | head -1 || cat pyproject.toml 2>/dev/null | grep '^version' | head -1 || echo "Could not detect version"`
+
+**Latest Tags**:
+!`git tag --sort=-version:refname 2>/dev/null | head -5 || echo "No tags found"`
+
+**Commits Since Last Tag**:
+!`git log $(git describe --tags --abbrev=0 2>/dev/null)..HEAD --oneline 2>/dev/null | head -15 || git log --oneline -10 2>/dev/null`
+
+**Release Scripts Detected**:
+!`cat package.json 2>/dev/null | grep -E '"(release|version|bump|publish|prepublish|postpublish|preversion|postversion|prepublishOnly)"' || echo "None in package.json"`
+!`ls .release-it.* .changeset/ .versionrc* lerna.json .releaserc* release.config.* 2>/dev/null || echo "No release tool configs found"`
+!`ls scripts/release* scripts/publish* scripts/version* Makefile 2>/dev/null || echo "No release scripts found"`
+
+---
+
+## Release Scope
+
+$ARGUMENTS
+
+---
+
+## Launching Release Agent
+
+The release agent will:
+1. **Detect existing release infrastructure** — scripts in package.json, release-it, changesets, semantic-release, standard-version, Makefile targets, scripts/ directory, CI workflows
+2. **If existing tooling found** — use it, guiding through any interactive steps
+3. **If no existing tooling** — orchestrate the release manually:
+   - Determine version bump from conventional commits (or use the specified version)
+   - Update CHANGELOG.md
+   - Bump version in manifest files
+   - Create git commit and tag
+   - Optionally create a GitHub Release
+4. **Confirm every destructive step** before executing
+
+**Workflows**:
+- No argument → Auto-detect version bump from commits (major/minor/patch)
+- `major` / `minor` / `patch` → Explicit bump type
+- `1.2.3` → Explicit version number
+- `--dry-run` → Show what would happen without making changes
+
+Use the Task tool to launch the release agent (subagent_type="release") with the scope and any additional context.

package/content/commands/research.md

@@ -32,7 +32,7 @@ Analyze the query to determine the best research agent:
 - Check package.json first to see if mentioned library is a project dependency
 
 **Use `web-research` agent when:**
-- Query asks for "latest", "best practices", "how to do X in 2025"
+- Query asks for "latest", "best practices", "how to do X"
 - Looking for online tutorials, guides, or examples
 - Researching industry standards or modern approaches
 - No specific library mentioned, or general "how to" questions

package/content/commands/secure.md

@@ -0,0 +1,51 @@
+---
+description: Run a focused security scan on your codebase
+argument-hint: [optional: file/folder path, or focus area like "deps", "auth", "api"]
+author: "@markoradak"
+---
+
+# Security Scan
+
+I'll perform a focused security audit of your codebase, checking for vulnerabilities, exposed secrets, and insecure patterns.
+
+> **When to use**: You want a dedicated security review — not a general code review. Use `/audit` for broad code quality review, or `/cleanup` to remove dead code.
+
+## Current State
+
+**Working Directory**: !`pwd`
+
+**Branch**: !`git branch --show-current 2>/dev/null || echo "Not a git repository"`
+
+**Status**:
+!`git status --short`
+
+**Dependencies**:
+!`cat package.json 2>/dev/null | grep -c '"dependencies\|"devDependencies"' || echo "No package.json"`
+
+---
+
+## Focus Area
+
+$ARGUMENTS
+
+---
+
+## Launching Security Agent
+
+The security agent will:
+- Scan source code for OWASP Top 10 vulnerabilities
+- Check for hardcoded secrets, API keys, and credentials
+- Audit dependencies for known vulnerabilities
+- Review authentication and authorization patterns
+- Check input validation and output encoding
+- Identify injection vectors (SQL, XSS, command, path traversal)
+- Provide a severity-ranked report with specific remediation steps
+
+**Scoping options**:
+- No argument → Full codebase security scan
+- `deps` → Dependency vulnerability audit only
+- `auth` → Authentication and authorization review
+- `api` → API endpoint security review
+- File/folder path → Scoped scan
+
+Use the Task tool to launch the secure agent (subagent_type="secure") which will perform a comprehensive security analysis and provide actionable remediation guidance.

package/content/commands/storyboard.md

@@ -30,15 +30,15 @@ This command extracts key frames from a screen recording or prototype demo using
 2. Extract key frames using scene-change detection (captures actual UI state changes)
 3. Read and analyze each frame to identify UI elements, states, and layout
 4. Compare consecutive frames to detect transitions and user actions
-5. Write structured interaction spec to `.claude/temp/`
+5. Write structured interaction spec to `{{SESSIONS_DIR}}/`
 
 ### Output
 
-A `INTERACTION_SPEC_{NAME}.md` file in `.claude/temp/` containing:
+A `INTERACTION_SPEC_{NAME}.md` file in `{{SESSIONS_DIR}}/` containing:
 - All detected UI states with element descriptions
 - Transitions between states with user actions and animation notes
 - Implementation checklist ready for `/implement`
 
 ---
 
-Use the Task tool to launch the storyboard agent (subagent_type="general-purpose") with the video file path and any additional context from arguments. The agent needs the full path to the video file to process it.
+Use the Task tool to launch the storyboard agent (subagent_type="storyboard") with the video file path and any additional context from arguments. The agent needs the full path to the video file to process it.