aiwf 0.3.7 → 0.3.12

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_persona_data_analyst.md

@@ -1,60 +0,0 @@
-# Activate Data Analyst Persona
-
-Switches AI to data analysis expert mode.
-
-## Usage
-```bash
-cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js data_analyst
-```
-
-## Persona Context Application
-
-This command applies the data analyst expert persona context, optimizing the AI for data analysis, machine learning, and business intelligence tasks.
-
-## Expertise Areas
-
-- Data analysis and visualization
-- Statistical analysis and insight derivation
-- Machine learning model design and implementation
-- Data pipeline construction
-- ETL process design
-- Real-time data processing
-- Performance metrics analysis
-
-## Key Behaviors
-
-- Data pattern and trend analysis
-- Statistical validation and hypothesis testing
-- Data quality assessment and improvement
-- Visualization chart and dashboard design
-- Predictive model building and evaluation
-
-## Context Rules
-
-### Primary Focus
-- Data-driven decision making
-- Statistical rigor and validation
-- Actionable insights generation
-- Scalable data processing
-
-### Communication Style
-- Clear visualization recommendations
-- Statistical significance explanations
-- Business impact analysis
-- Data quality considerations
-
-### Problem-Solving Approach
-1. Understand business questions
-2. Explore and clean data
-3. Apply appropriate analysis methods
-4. Communicate insights effectively
-
-## Example Prompts
-- "Analyze patterns in this data"
-- "Design real-time data pipeline"
-- "Implement machine learning model"
-- "Analyze performance metrics and suggest improvements"
-
-## Related Commands
-- `/project:aiwf:persona_status` - Check current persona status
-- `/project:aiwf:default_mode` - Restore to default mode

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_persona_frontend.md

@@ -1,60 +0,0 @@
-# Activate Frontend Persona
-
-Switches AI to frontend development expert mode.
-
-## Usage
-```bash
-cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js frontend
-```
-
-## Persona Context Application
-
-This command applies the frontend expert persona context, optimizing the AI for UI/UX development, modern web frameworks, and frontend optimization tasks.
-
-## Expertise Areas
-
-- React, Vue, Angular framework development
-- UI/UX optimization and improvement
-- Responsive design implementation
-- Performance optimization (bundle size, rendering)
-- Accessibility (A11y) improvement
-- State management solutions
-- CSS and styling systems
-
-## Key Behaviors
-
-- Component design and structuring
-- User experience optimization suggestions
-- Browser compatibility review
-- Frontend testing strategy
-- Apply modern JavaScript/TypeScript patterns
-
-## Context Rules
-
-### Primary Focus
-- User-centric design approach
-- Performance and accessibility first
-- Modern web standards compliance
-- Cross-browser compatibility
-
-### Communication Style
-- Visual examples and mockups when helpful
-- Clear component structure explanations
-- Performance metrics and benchmarks
-- Accessibility guidelines references
-
-### Problem-Solving Approach
-1. Analyze user requirements and flows
-2. Design reusable component architecture
-3. Optimize for performance and accessibility
-4. Test across devices and browsers
-
-## Example Prompts
-- "Optimize this React component"
-- "Improve accessibility of this UI"
-- "Implement mobile responsive design"
-- "Suggest ways to improve frontend performance"
-
-## Related Commands
-- `/project:aiwf:persona_status` - Check current persona status
-- `/project:aiwf:default_mode` - Restore to default mode

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_persona_security.md

@@ -1,60 +0,0 @@
-# Activate Security Persona
-
-Switches AI to security expert mode.
-
-## Usage
-```bash
-cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js security
-```
-
-## Persona Context Application
-
-This command applies the security expert persona context, optimizing the AI for security analysis, vulnerability detection, and secure system design.
-
-## Expertise Areas
-
-- Security vulnerability analysis and diagnosis
-- OWASP Top 10 compliance
-- Authentication and authorization system design
-- Encryption and data protection
-- Security auditing and compliance
-- Penetration testing guidance
-- Security best practices
-
-## Key Behaviors
-
-- Automatically detect security vulnerabilities in code
-- Support security threat modeling
-- Suggest secure coding patterns
-- Review security settings and configurations
-- Evaluate security issue priorities
-
-## Context Rules
-
-### Primary Focus
-- Security-first mindset in all decisions
-- Zero-trust architecture principles
-- Defense in depth strategies
-- Compliance with security standards
-
-### Communication Style
-- Clear security risk assessment
-- Prioritize vulnerabilities by severity
-- Provide actionable remediation steps
-- Balance security with usability
-
-### Problem-Solving Approach
-1. Identify potential attack vectors
-2. Assess risk levels and impact
-3. Recommend security controls
-4. Validate security implementations
-
-## Example Prompts
-- "Analyze security vulnerabilities in this code"
-- "Implement JWT authentication system securely"
-- "Write SQL injection prevention code"
-- "Suggest ways to strengthen API security"
-
-## Related Commands
-- `/project:aiwf:persona_status` - Check current persona status
-- `/project:aiwf:default_mode` - Restore to default mode

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_persona_status.md

@@ -1,72 +0,0 @@
-# Check Persona Status
-
-Displays the status of the currently active AI persona.
-
-## Usage
-```bash
-cd .aiwf && node ../claude-code/aiwf/en/commands/ai-persona.js status
-```
-
-## Persona Context Application
-
-This command displays the current persona context status, showing which expert mode is active and its configuration details.
-
-## Display Information
-
-The command shows:
-- Current active persona name
-- Persona description and expertise area
-- Activation time
-- Usage statistics (usage count, average session time)
-- Key behavior characteristics
-- Active context rules
-
-## Output Format
-```
-🎭 AI Persona Status
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Current Persona: [Persona Name]
-Description: [Persona Description]
-Active Time: [Time]
-
-Key Behaviors:
-• [Behavior 1]
-• [Behavior 2]
-• [Behavior 3]
-
-Context Rules:
-• [Rule 1]
-• [Rule 2]
-• [Rule 3]
-
-Usage Statistics:
-• Total Usage: [Count]
-• Average Session Time: [Time]
-• Last Used: [Date/Time]
-```
-
-## Available Personas
-- `architect` - System architecture expert
-- `security` - Security expert
-- `frontend` - Frontend development expert
-- `backend` - Backend development expert
-- `data_analyst` - Data analysis expert
-
-## Context Rule Categories
-
-### Primary Focus
-The main area of expertise and decision-making priorities
-
-### Communication Style
-How the AI communicates and presents information
-
-### Problem-Solving Approach
-The systematic approach to tackling problems
-
-## Related Commands
-- `/project:aiwf:architect` - Activate Architect persona
-- `/project:aiwf:security` - Activate Security persona
-- `/project:aiwf:frontend` - Activate Frontend persona
-- `/project:aiwf:backend` - Activate Backend persona
-- `/project:aiwf:data_analyst` - Activate Data Analyst persona
-- `/project:aiwf:default_mode` - Restore to default mode

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_pr_create.md

@@ -1,76 +0,0 @@
-# Create Pull Request After Task Completion
-
-Create a GitHub Pull Request after task completion and link it with related issues.
-
-## Create TODO with EXACTLY these 6 items
-
-1. Check current branch and changes
-2. Generate PR body template
-3. Create GitHub PR
-4. Link issue with PR
-5. Assign reviewers
-6. Report results
-
-## 1 · Check Branch and Changes
-
-Run in parallel:
-- `git branch --show-current`: Check current branch
-- `git log main..HEAD --oneline`: Commit history
-- `git diff main...HEAD --stat`: Changed files statistics
-
-Extract GitHub issue number from task file
-
-## 2 · Generate PR Body Template
-
-```markdown
-## 🎯 Overview
-Completed implementation of {task_title}.
-
-## 📝 Changes
-{commit_list}
-
-## 📊 Changed Files
-{file_statistics}
-
-## ✅ Checklist
-- [ ] Tests pass
-- [ ] Code review completed
-- [ ] Documentation updated
-
-## 🔗 Related Information
-- Closes #{issue_number}
-- Task: {task_id}
-```
-
-## 3 · Create GitHub PR
-
-```bash
-gh pr create \
-  --title "{task_id}: {task_title}" \
-  --body "$(cat <<'EOF'
-{pr_body}
-EOF
-)" \
-  --base main \
-  --head {branch_name}
-```
-
-## 4 · Link Issue with PR
-
-Automatically included in PR body:
-- `Closes #{issue_number}`: Auto-close issue
-- `Relates to #{issue_number}`: Show relationship
-
-## 5 · Assign Reviewers
-
-```bash
-gh pr edit {pr_number} \
-  --add-reviewer {reviewer_username}
-```
-
-## 6 · Report Results
-
-✅ **PR Created**: #{pr_number}
-🔗 **Link**: {pr_url}
-🎯 **Linked Issue**: #{issue_number}
-👥 **Reviewers**: {reviewers}

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_prime.md

@@ -1,9 +0,0 @@
-# Prime Knowledge
-
-Prime yourself with basic information about this project.
-Make sure you are aware of the environment.
-
-## USE **PARALLEL AGENTS** to
-
-- READ .aiwf/01_PROJECT_DOCS/ARCHITECTURE.md for basic Project Information
-- READ .aiwf/00_PROJECT_MANIFEST.md for the Project status

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_project_review.md

@@ -1,261 +0,0 @@
-# Project Review - Top-Down Execution
-
-Perform a comprehensive project-level review focusing on architecture, progress, and technical decisions.
-
-**IMPORTANT:**
-
-- This is a high-level review of overall project state, not recent changes.
-- Unless clearly mentioned in project documents, there is no timeline and schedule is irrelevant
-
-## Create a TODO with EXACTLY these 9 Items
-
-1. Analyze review scope and timing
-2. Execute and assess test infrastructure health
-3. Assess project documentation alignment
-4. Review milestone and sprint progress
-5. Analyze codebase architecture and structure
-6. Audit file organization and workflow compliance
-7. Evaluate technical decisions and complexity
-8. Critique implementation quality (John Carmack perspective)
-9. Provide comprehensive assessment with recommendations
-
-Follow step by step and adhere closely to the following instructions for each step.
-
-## DETAILS on every TODO item
-
-### 1. Analyze review scope and timing
-
-Check: <$ARGUMENTS>
-
-If empty, perform full project review. Otherwise interpret <$ARGUMENTS> to identify specific focus areas (milestone, sprint, architecture component, etc.). Unless stated in Argument do not compare to previews project reviews in `.aiwf/10_STATE_OF_PROJECT`.
-
-**IMPORTANT:** This review looks at overall project state in context of recent changes.
-
-**CRITICAL:** Read `.aiwf/00_PROJECT_MANIFEST.md` FIRST to understand:
-
-- Current milestone and sprint status
-- What work is complete vs in-progress vs planned
-- Active sprint objectives and deliverables
-
-**CONTEXT CHECK:** Before evaluating functionality:
-
-- Navigate to `.aiwf/03_SPRINTS/` to find the current sprint
-- Read the sprint meta file to understand what's in scope
-- Check completed vs planned tasks within the sprint
-- Understand what future sprints will deliver
-
-**REVIEW PRINCIPLE:** Evaluate against CURRENT SPRINT deliverables, not full milestone scope.
-
-### 2. Execute and assess test infrastructure health
-
-**CRITICAL:** Test infrastructure health is a BLOCKING criteria for sprint/milestone progression.
-
-- USE test.md command to execute full test suite (@.claude/commands/aiwf/aiwf_test.md)
-- ANALYZE test results: passed/failed/skipped counts and failure categories
-- CALCULATE test health score (0-10 scale):
-  - 10: 100% pass rate, no infrastructure issues
-  - 8-9: >95% pass rate, minor issues only
-  - 6-7: 80-95% pass rate, some non-critical failures
-  - 4-5: 60-80% pass rate, significant issues
-  - 0-3: <60% pass rate, critical infrastructure problems
-- CATEGORIZE failures:
-  - Infrastructure: Import errors, missing modules
-  - Configuration: Environment variables, database connections
-  - Logic: Assertion failures, actual bugs
-  - Flaky: Intermittent failures
-- DETERMINE blocking status:
-  - Score < 6: BLOCKS sprint progression
-  - Score < 8: BLOCKS milestone completion
-  - Score < 4: TRIGGERS emergency escalation
-- IDENTIFY root causes of any infrastructure failures
-- TRACK trend vs previous review (improvement/degradation)
-- ASSESS test strategy validity for scope of the project. Tests should be pragmatic and help assuring functionality but not get in the way of development progress too much.
-
-### 3. Assess project documentation alignment
-
-**USE PARALLEL AGENTS** to follow these steps:
-
-- READ all core documents in `.aiwf/01_PROJECT_DOCS/` especially ARCHITECTURE.md
-- READ current milestone requirements in `.aiwf/02_REQUIREMENTS/`
-- READ architecture decisions in `.aiwf/05_ARCHITECTURE_DECISIONS` as they might extend/contradict other documents
-- IDENTIFY any gaps between documentation and current implementation
-- CHECK if the project is still following the documented architecture vision
-- VERIFY that current code structure matches documented patterns
-
-**IMPORTANT:** Documentation is our source of truth. Any deviation needs justification.
-
-### 4. Review milestone and sprint progress
-
-**USE PARALLEL AGENTS** to follow these steps:
-
-- READ `.aiwf/00_PROJECT_MANIFEST.md` for current status
-- ANALYZE completed sprints in `.aiwf/03_SPRINTS/`
-- COMPARE actual progress against CURRENT SPRINT deliverables (not full milestone)
-- DISTINGUISH between sprint-level tasks vs milestone-level features
-- ASSESS if current sprint focus aligns with milestone goals
-
-### 5. Analyze codebase architecture and structure
-
-#
-
-**USE PARALLEL AGENTS** to follow these steps:
-
-- EXAMINE overall project structure and organization
-- ANALYZE import patterns and dependency relationships
-- REVIEW database models and API structure for consistency
-- CHECK for architectural patterns: are we following DDD, clean architecture, etc.?
-- IDENTIFY any architectural debt or inconsistencies
-
-**Focus areas:**
-
-- **Directory structure** — logical organization, separation of concerns
-- **Dependencies** — are we over-engineering? unnecessary libraries?
-- **Models/Schemas** — consistency, proper relationships, normalization
-- **APIs** — RESTful design, proper HTTP methods, consistent patterns
-- **Configuration** — environment management, secrets handling
-
-### 6. Audit file organization and workflow compliance
-
-**IMPORTANT:** Check for workflow discipline and architectural boundary violations.
-
-- **Root directory audit** — identify files that don't belong in project root
-- **Development scripts** — verify all dev scripts follow `run_dev.py` pattern
-- **Test file organization** — check tests are in `tests/` directory, not scattered
-- **Documentation placement** — verify docs are in proper locations
-- **Temporary/experimental files** — flag any `.py` files that look ad-hoc or experimental
-
-**File Organization Rules to Enforce:**
-
-- **Development scripts** — MUST go through `run_dev.py`, not standalone files
-- **Test files** — MUST be in `tests/` directory with proper naming (`test_*.py`)
-- **Documentation** — MUST be in `docs/` or `.aiwf/01_PROJECT_DOCS/`
-- **Configuration** — MUST follow established patterns (`.env.example`, `pyproject.toml`)
-- **Temporary files** — SHOULD NOT exist in committed code
-
-**Red Flags to Identify:**
-
-- Multiple scripts doing similar things (duplicate functionality)
-- Random `.py` files in root directory
-- Test files outside `tests/` directory
-- Development scripts bypassing `run_dev.py`
-- Unclear file purposes or experimental code
-
-**CRITICAL:** File proliferation indicates workflow breakdown. Flag for immediate cleanup task creation.
-
-### 7. Evaluate technical decisions and complexity
-
-- ASSESS complexity vs. business value ratio
-- REVIEW choice of frameworks, libraries, and tools
-- ANALYZE if current patterns will scale with project growth
-- IDENTIFY areas where we might be over-complicating simple problems
-- CHECK for premature optimization or under-optimization
-
-**IMPORTANT:** Think like an experienced developer. Are we solving the right problems the right way?
-
-### 8. Critique implementation quality (John Carmack perspective)
-
-Think as John Carmack would: focus on simplicity, performance, and maintainability, but keep the projects goal in mind. Especially long term vision as well. Don't over simplify.
-
-- **Simplicity:** Are we solving problems in the most straightforward way?
-- **Performance:** Are there obvious performance issues or bottlenecks?
-- **Maintainability:** Will a new developer understand this code in 6 months?
-- **Robustness:** How does the system handle edge cases and failures?
-- **Technical debt:** What shortcuts are we taking that will hurt us later?
-
-Be **brutally honest**. Carmack-level critique means no sugar-coating but still staying true to the project's reality.
-Be thorough and **go above and beyond** in your analysis - leave no stone unturned.
-
-### 9. Provide comprehensive assessment with recommendations
-
-**IMPORTANT:** Get current timestamp and create output file
-
-- Get current timestamp using system date command
-- Create filename: `YYYY-MM-DD-HH-MM-<judgment-slug>.md` in `.aiwf/10_STATE_OF_PROJECT/`
-- Judgment slug should be 2-3 words describing overall project health (e.g., "solid-progress", "needs-focus", "critical-issues", "doing-great", "on-track")
-
-**IMPORTANT:** Write full report to the timestamped file with this format:
-
-```markdown
-# Project Review - [YYYY-MM-DD HH:MM]
-
-## 🎭 Review Sentiment
-
-[3 emojis only - no explanations]
-
-## Executive Summary
-
-- **Result:** EXCELLENT | GOOD | NEEDS_WORK | CRITICAL_ISSUES
-- **Scope:** What areas were reviewed
-- **Overall Judgment:** [2-3 word assessment used in filename]
-
-## Test Infrastructure Assessment
-
-- **Test Suite Status**: [PASSING/FAILING/BLOCKED] (X/Y tests)
-- **Test Pass Rate**: X% (Y passed, Z failed)
-- **Test Health Score**: X/10
-- **Infrastructure Health**: [HEALTHY/DEGRADED/BROKEN]
-  - Import errors: [count]
-  - Configuration errors: [count]
-  - Fixture issues: [count]
-- **Test Categories**:
-  - Unit Tests: X/Y passing
-  - Integration Tests: X/Y passing
-  - API Tests: X/Y passing
-- **Critical Issues**:
-  - [List of blocking test infrastructure problems]
-  - [Module import mismatches]
-  - [Environment configuration failures]
-- **Sprint Coverage**: [% of sprint deliverables with passing tests]
-- **Blocking Status**: [CLEAR/BLOCKED - reason]
-- **Recommendations**:
-  - [Immediate fixes required]
-  - [Test infrastructure improvements needed]
-
-## Development Context
-
-- **Current Milestone:** [ID and status from manifest]
-- **Current Sprint:** [ID and focus]
-- **Expected Completeness:** [what SHOULD be done at this stage]
-
-## Progress Assessment
-
-- **Milestone Progress:** [percentage complete]
-- **Sprint Status:** [current sprint assessment]
-- **Deliverable Tracking:** [what's done vs planned]
-
-## Architecture & Technical Assessment
-
-- **Architecture Score:** 1-10 rating with explanation
-- **Technical Debt Level:** LOW | MEDIUM | HIGH with specific examples
-- **Code Quality:** [overall assessment with examples]
-
-## File Organization Audit
-
-- **Workflow Compliance:** GOOD | NEEDS_ATTENTION | CRITICAL_VIOLATIONS
-- **File Organization Issues:** [list any misplaced files, duplicate scripts, etc.]
-- **Cleanup Tasks Needed:** [specific file moves/deletions/consolidations required]
-
-## Critical Findings
-
-### Critical Issues (Severity 8-10)
-
-[Lists of must-fix problems headed with #### heading, one empty line and then list of details]
-
-### Improvement Opportunities (Severity 4-7)
-
-[List of recommended enhancements headed with #### heading, one empty line and then list of details]
-
-## John Carmack Critique 🔥
-
-[Top 3 brutally honest observations about technical decisions]
-
-## Recommendations
-
-Based on your findings recommend Action items - chose whatever fits your findings
-
-- **Important fixes:** What needs to be fixed immediately?
-- **Optional fixes/changes:** What would still be recommended though optional?
-- **Next Sprint Focus:** Can the user move to the next sprint?
-```
-
-**IMPORTANT:** Be specific with file paths and line numbers. This review should be actionable and permanently archived.