claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/testing/prime.md

@@ -1,314 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Prime Testing Environment
-
-This command prepares the testing environment by detecting the test framework, validating dependencies, and configuring the test-runner agent for optimal test execution.
-
-## Preflight Checklist
-
-Before proceeding, complete these validation steps.
-Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.
-
-### 1. Test Framework Detection
-
-**JavaScript/Node.js:**
-- Check package.json for test scripts: `grep -E '"test"|"spec"|"jest"|"mocha"' package.json 2>/dev/null`
-- Look for test config files: `ls -la jest.config.* mocha.opts .mocharc.* 2>/dev/null`
-- Check for test directories: `find . -type d \( -name "test" -o -name "tests" -o -name "__tests__" -o -name "spec" \) -maxdepth 3 2>/dev/null`
-
-**Python:**
-- Check for pytest: `find . -name "pytest.ini" -o -name "conftest.py" -o -name "setup.cfg" 2>/dev/null | head -5`
-- Check for unittest: `find . -path "*/test*.py" -o -path "*/test_*.py" 2>/dev/null | head -5`
-- Check requirements: `grep -E "pytest|unittest|nose" requirements.txt 2>/dev/null`
-
-**Rust:**
-- Check for Cargo tests: `grep -E '\[dev-dependencies\]' Cargo.toml 2>/dev/null`
-- Look for test modules: `find . -name "*.rs" -exec grep -l "#\[cfg(test)\]" {} \; 2>/dev/null | head -5`
-
-**Go:**
-- Check for test files: `find . -name "*_test.go" 2>/dev/null | head -5`
-- Check go.mod exists: `test -f go.mod && echo "Go module found"`
-
-**Other Languages:**
-- Ruby: Check for RSpec: `find . -name ".rspec" -o -name "spec_helper.rb" 2>/dev/null`
-- Java: Check for JUnit: `find . -name "pom.xml" -exec grep -l "junit" {} \; 2>/dev/null`
-
-### 2. Test Environment Validation
-
-If no test framework detected:
-- Tell user: "⚠️ No test framework detected. Please specify your testing setup."
-- Ask: "What test command should I use? (e.g., npm test, pytest, cargo test)"
-- Store response for future use
-
-### 3. Dependency Check
-
-**For detected framework:**
-- Node.js: Run `npm list --depth=0 2>/dev/null | grep -E "jest|mocha|chai|jasmine"`
-- Python: Run `pip list 2>/dev/null | grep -E "pytest|unittest|nose"`
-- Verify test dependencies are installed
-
-If dependencies missing:
-- Tell user: "❌ Test dependencies not installed"
-- Suggest: "Run: npm install (or pip install -r requirements.txt)"
-
-## Required Documentation Access
-
-**MANDATORY:** Before testing workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/testing/strategy` - strategy best practices
-- `mcp://context7/testing/automation` - automation best practices
-- `mcp://context7/tdd/workflow` - workflow best practices
-- `mcp://context7/testing/best-practices` - best practices best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-## Instructions
-
-### 1. Framework-Specific Configuration
-
-Based on detected framework, create test configuration:
-
-#### JavaScript/Node.js (Jest)
-```yaml
-framework: jest
-test_command: npm test
-test_directory: __tests__
-config_file: jest.config.js
-options:
-  - --verbose
-  - --no-coverage
-  - --runInBand
-environment:
-  NODE_ENV: test
-```
-
-#### JavaScript/Node.js (Mocha)
-```yaml
-framework: mocha
-test_command: npm test
-test_directory: test
-config_file: .mocharc.js
-options:
-  - --reporter spec
-  - --recursive
-  - --bail
-environment:
-  NODE_ENV: test
-```
-
-#### Python (Pytest)
-```yaml
-framework: pytest
-test_command: pytest
-test_directory: tests
-config_file: pytest.ini
-options:
-  - -v
-  - --tb=short
-  - --strict-markers
-environment:
-  PYTHONPATH: .
-```
-
-#### Rust
-```yaml
-framework: cargo
-test_command: cargo test
-test_directory: tests
-config_file: Cargo.toml
-options:
-  - --verbose
-  - --nocapture
-environment: {}
-```
-
-#### Go
-```yaml
-framework: go
-test_command: go test
-test_directory: .
-config_file: go.mod
-options:
-  - -v
-  - ./...
-environment: {}
-```
-
-### 2. Test Discovery
-
-Scan for test files:
-- Count total test files found
-- Identify test naming patterns used
-- Note any test utilities or helpers
-- Check for test fixtures or data
-
-```bash
-# Example for Node.js
-find . -path "*/node_modules" -prune -o -name "*.test.js" -o -name "*.spec.js" | wc -l
-```
-
-### 3. Create Test Runner Configuration
-
-Create `.claude/testing-config.md` with discovered information:
-
-```markdown
----
-framework: {detected_framework}
-test_command: {detected_command}
-created: [Use REAL datetime from: date -u +"%Y-%m-%dT%H:%M:%SZ"]
----
-
-# Testing Configuration
-
-## Framework
-- Type: {framework_name}
-- Version: {framework_version}
-- Config File: {config_file_path}
-
-## Test Structure
-- Test Directory: {test_dir}
-- Test Files: {count} files found
-- Naming Pattern: {pattern}
-
-## Commands
-- Run All Tests: `{full_test_command}`
-- Run Specific Test: `{specific_test_command}`
-- Run with Debugging: `{debug_command}`
-
-## Environment
-- Required ENV vars: {list}
-- Test Database: {if applicable}
-- Test Servers: {if applicable}
-
-## Test Runner Agent Configuration
-- Use verbose output for debugging
-- Run tests sequentially (no parallel)
-- Capture full stack traces
-- No mocking - use real implementations
-- Wait for each test to complete
-```
-
-### 4. Configure Test-Runner Agent
-
-Prepare agent context based on framework:
-
-```markdown
-# Test-Runner Agent Configuration
-
-## Project Testing Setup
-- Framework: {framework}
-- Test Location: {directories}
-- Total Tests: {count}
-- Last Run: Never
-
-## Execution Rules
-1. Always use the test-runner agent from `.claude/agents/test-runner.md`
-2. Run with maximum verbosity for debugging
-3. No mock services - use real implementations
-4. Execute tests sequentially - no parallel execution
-5. Capture complete output including stack traces
-6. If test fails, analyze test structure before assuming code issue
-7. Report detailed failure analysis with context
-
-## Test Command Templates
-- Full Suite: `{full_command}`
-- Single File: `{single_file_command}`
-- Pattern Match: `{pattern_command}`
-- Watch Mode: `{watch_command}` (if available)
-
-## Common Issues to Check
-- Environment variables properly set
-- Test database/services running
-- Dependencies installed
-- Proper file permissions
-- Clean test state between runs
-```
-
-### 5. Validation Steps
-
-After configuration:
-- Try running a simple test to validate setup
-- Check if test command works: `{test_command} --version` or equivalent
-- Verify test files are discoverable
-- Ensure no permission issues
-
-### 6. Output Summary
-
-```
-🧪 Testing Environment Primed
-
-🔍 Detection Results:
-  ✅ Framework: {framework_name} {version}
-  ✅ Test Files: {count} files in {directories}
-  ✅ Config: {config_file}
-  ✅ Dependencies: All installed
-
-📋 Test Structure:
-  - Pattern: {test_file_pattern}
-  - Directories: {test_directories}
-  - Utilities: {test_helpers}
-
-🤖 Agent Configuration:
-  ✅ Test-runner agent configured
-  ✅ Verbose output enabled
-  ✅ Sequential execution set
-  ✅ Real services (no mocks)
-
-⚡ Ready Commands:
-  - Run all tests: /testing:run
-  - Run specific: /testing:run {test_file}
-  - Run pattern: /testing:run {pattern}
-
-💡 Tips:
-  - Always run tests with verbose output
-  - Check test structure if tests fail
-  - Use real services, not mocks
-  - Let each test complete fully
-```
-
-### 7. Error Handling
-
-**Common Issues:**
-
-**No Framework Detected:**
-- Message: "⚠️ No test framework found"
-- Solution: "Please specify test command manually"
-- Store user's response for future use
-
-**Missing Dependencies:**
-- Message: "❌ Test framework not installed"
-- Solution: "Install dependencies first: npm install / pip install -r requirements.txt"
-
-**No Test Files:**
-- Message: "⚠️ No test files found"
-- Solution: "Create tests first or check test directory location"
-
-**Permission Issues:**
-- Message: "❌ Cannot access test files"
-- Solution: "Check file permissions"
-
-### 8. Save Configuration
-
-If successful, save configuration for future sessions:
-- Store in `.claude/testing-config.md`
-- Include all discovered settings
-- Update on subsequent runs if changes detected
-
-## Important Notes
-
-- **Always detect** rather than assume test framework
-- **Validate dependencies** before claiming ready
-- **Configure for debugging** - verbose output is critical
-- **No mocking** - use real services for accurate testing
-- **Sequential execution** - avoid parallel test issues
-- **Store configuration** for consistent future runs
-
-$ARGUMENTS

package/autopm/.claude/commands/testing/run.md

@@ -1,125 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS, Task
----
-
-# Run Tests
-
-Execute tests with the configured test-runner agent.
-
-## Usage
-```
-/testing:run [test_target]
-```
-
-Where `test_target` can be:
-- Empty (run all tests)
-- Test file path
-- Test pattern
-- Test suite name
-
-## Required Documentation Access
-
-**MANDATORY:** Before testing workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/testing/strategy` - strategy best practices
-- `mcp://context7/testing/automation` - automation best practices
-- `mcp://context7/tdd/workflow` - workflow best practices
-- `mcp://context7/testing/best-practices` - best practices best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-## Quick Check
-
-```bash
-# Check if testing is configured
-test -f .claude/testing-config.md || echo "❌ Testing not configured. Run /testing:prime first"
-```
-
-If test target provided, verify it exists:
-```bash
-# For file targets
-test -f "$ARGUMENTS" || echo "⚠️ Test file not found: $ARGUMENTS"
-```
-
-## Instructions
-
-### 1. Determine Test Command
-
-Based on testing-config.md and target:
-- No arguments → Run full test suite from config
-- File path → Run specific test file
-- Pattern → Run tests matching pattern
-
-### 2. Execute Tests
-
-Use the test-runner agent from `.claude/agents/test-runner.md`:
-
-```markdown
-Execute tests for: $ARGUMENTS (or "all" if empty)
-
-Requirements:
-- Run with verbose output for debugging
-- No mocks - use real services
-- Capture full output including stack traces
-- If test fails, check test structure before assuming code issue
-```
-
-### 3. Monitor Execution
-
-- Show test progress
-- Capture stdout and stderr
-- Note execution time
-
-### 4. Report Results
-
-**Success:**
-```
-✅ All tests passed ({count} tests in {time}s)
-```
-
-**Failure:**
-```
-❌ Test failures: {failed_count} of {total_count}
-
-{test_name} - {file}:{line}
-  Error: {error_message}
-  Likely: {test issue | code issue}
-  Fix: {suggestion}
-
-Run with more detail: /testing:run {specific_test}
-```
-
-**Mixed:**
-```
-Tests complete: {passed} passed, {failed} failed, {skipped} skipped
-
-Failed:
-- {test_1}: {brief_reason}
-- {test_2}: {brief_reason}
-```
-
-### 5. Cleanup
-
-```bash
-# Kill any hanging test processes
-pkill -f "jest|mocha|pytest" 2>/dev/null || true
-```
-
-## Error Handling
-
-- Test command fails → "❌ Test execution failed: {error}. Check test framework is installed."
-- Timeout → Kill process and report: "❌ Tests timed out after {time}s"
-- No tests found → "❌ No tests found matching: $ARGUMENTS"
-
-## Important Notes
-
-- Always use test-runner agent for analysis
-- No mocking - real services only
-- Check test structure if failures occur
-- Keep output focused on failures

package/autopm/.claude/commands/ui/bootstrap-scaffold.md

@@ -1,65 +0,0 @@
----
-name: bootstrap-scaffold
-type: epic-management
-category: ui
----
-
-claude# Bootstrap UI Scaffold Command
-
-Create a complete Bootstrap-based UI structure with responsive components and themes.
-
-## Command
-```
-/ui:bootstrap-scaffold
-```
-
-## Purpose
-Use the react-ui-expert agent (with framework=bootstrap) to create a complete Bootstrap application scaffold with modern components, responsive design, and customizable themes.
-
-## Parameters
-- `theme`: Theme variant (light, dark, corporate, minimal)
-- `components`: Required components (navbar, cards, forms, modals)
-- `responsive`: Breakpoints to support (sm, md, lg, xl, xxl)
-- `features`: Additional features (dark-mode-toggle, form-validation, animations)
-
-## Agent Usage
-```
-Use the react-ui-expert agent with framework=bootstrap to create a complete Bootstrap application scaffold.
-```
-
-## Expected Outcome
-- Complete HTML structure with Bootstrap components
-- Custom SCSS configuration with theme variables
-- JavaScript for interactive components
-- Responsive design implementation
-- Form validation and accessibility features
-- Dark mode toggle functionality
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before UI framework setup, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/ui/bootstrap` - bootstrap best practices
-- `mcp://context7/ui/tailwind` - tailwind best practices
-- `mcp://context7/frontend/design-systems` - design systems best practices
-- `mcp://context7/css/frameworks` - frameworks best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-Task: Create Bootstrap dashboard with sidebar navigation, responsive cards grid, and contact forms
-Agent: react-ui-expert
-Parameters: framework=bootstrap, theme=corporate, components=navbar,sidebar,cards,forms,modals, responsive=all, features=dark-mode,validation
-```
-
-## Related Agents
-- tailwindcss-expert: For utility-first alternative
-- react-frontend-engineer: For React + Bootstrap integration
-- react-ui-expert: Main agent for UI component architecture

package/autopm/.claude/commands/ui/tailwind-system.md

@@ -1,64 +0,0 @@
----
-name: tailwindcss-design-system
-type: task-management
-category: ui
----
-
-# TailwindCSS Design System Command
-
-Create a custom design system using TailwindCSS with utility classes and component patterns.
-
-## Command
-```
-/ui:tailwind-system
-```
-
-## Purpose
-Use the tailwindcss-expert agent to create a complete TailwindCSS design system with custom utilities, components, and theme configuration.
-
-## Parameters
-- `theme`: Color scheme (modern, minimal, vibrant, corporate)
-- `utilities`: Custom utilities to generate (spacing, gradients, animations)
-- `components`: Component patterns to create (buttons, cards, forms, layouts)
-- `plugins`: TailwindCSS plugins to include (@tailwindcss/forms, @tailwindcss/typography)
-
-## Agent Usage
-```
-Use the tailwindcss-expert agent to create a comprehensive TailwindCSS design system.
-```
-
-## Expected Outcome
-- Custom tailwind.config.js with design tokens
-- Component library with utility combinations
-- Custom plugin for project-specific utilities
-- Production-optimized build configuration
-- Dark mode implementation
-- Responsive design patterns
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before UI framework setup, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/ui/bootstrap` - bootstrap best practices
-- `mcp://context7/ui/tailwind` - tailwind best practices
-- `mcp://context7/frontend/design-systems` - design systems best practices
-- `mcp://context7/css/frameworks` - frameworks best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-Task: Create TailwindCSS design system with custom color palette, typography scale, and component library
-Agent: tailwindcss-expert
-Parameters: theme=modern, utilities=custom-spacing,gradients,animations, components=buttons,cards,forms, plugins=forms,typography
-```
-
-## Related Agents
-- react-ui-expert: For component-based alternative
-- react-frontend-engineer: For React + Tailwind integration