v0.13.0

.claude/commands/README.md

@@ -0,0 +1,165 @@
+# Claude Commands for Macroflows
+
+This directory contains Claude Code commands adapted from GitHub Copilot prompts for optimal development workflow.
+
+## Command Categories
+
+### Workflow Commands (`workflow/`)
+- **`/commit`** - Generate conventional commit messages and execute commits
+- **`/pull-request`** (`/pr`) - Create pull requests with proper formatting and metadata
+
+### Quality Assurance (`quality/`)
+- **`/fix`** - Automated codebase checks and error correction
+- **`/review`** - Comprehensive code review for PR changes
+
+### Issue Management (`issues/`)
+- **`/create-issue`** - Create GitHub issues using proper templates
+- **`/implement`** - Autonomous issue implementation after plan approval
+- **`/prioritize-milestone`** - Analyze and prioritize milestone issues for optimal capacity
+
+### Refactoring (`refactor/`)
+- **`/refactor`** - Clean architecture refactoring and modularization
+
+### Session Management (`session/`)
+- **`/end-session`** (`/end`) - Session summary and knowledge export
+
+## Quick Reference
+
+### Daily Workflow
+```bash
+# Start development
+/fix                    # Ensure clean codebase
+/create-issue feature   # Create feature request
+/implement 123          # Implement issue #123
+/commit                 # Generate and execute commit
+/pull-request          # Create PR for review
+```
+
+### Quality Assurance
+```bash
+/fix                   # Run comprehensive checks and fixes
+/review               # Generate code review for PR
+```
+
+### Project Management
+```bash
+/create-issue bug      # Report and create bug issue
+/create-issue refactor # Create refactoring task
+/prioritize-milestone  # Analyze and prioritize milestone issues
+/end-session          # Summarize learnings and export knowledge
+```
+
+## Command Features
+
+### Architecture Integration
+- **Clean Architecture Compliance:** All commands respect domain/application/infrastructure layer separation
+- **Error Handling Standards:** Enforces proper `handleApiError` usage patterns
+- **Import Standards:** Maintains absolute imports with `~/` prefix
+- **Type Safety:** Ensures TypeScript strict mode compliance
+
+### Project-Specific Adaptations
+- **Solo Project Focus:** Commands adapted for single developer workflow
+- **SolidJS Patterns:** Optimized for reactive programming patterns
+- **Supabase Integration:** Handles database and real-time patterns
+- **Portuguese UI Support:** Maintains pt-BR UI text while enforcing English code
+
+### Quality Integration
+- **Automated Validation:** Commands integrate with `npm run copilot:check`
+- **Test Updates:** Automatically updates tests for code changes
+- **Lint Compliance:** Ensures ESLint and Prettier standards
+- **Performance Focus:** Prioritizes O(n) algorithms and efficient patterns
+
+## Migration from GitHub Prompts
+
+### Mapping
+```
+.github/prompts/commit.prompt.md           → .claude/commands/workflow/commit.md
+.github/prompts/fix.prompt.md              → .claude/commands/quality/fix.md
+.github/prompts/code-review.prompt.md      → .claude/commands/quality/review.md
+.github/prompts/github-issue-unified.md    → .claude/commands/issues/create.md
+.github/prompts/issue-implementation.md    → .claude/commands/issues/implement.md
+.github/prompts/milestone-prioritization.prompt.md → .claude/commands/prioritize-milestone.md
+.github/prompts/refactor.prompt.md         → .claude/commands/refactor/clean-architecture.md
+.github/prompts/pull-request.prompt.md     → .claude/commands/workflow/pull-request.md
+.github/prompts/end-session.prompt.md      → .claude/commands/session/end.md
+```
+
+### Improvements
+- **Command Structure:** Organized into logical categories
+- **Usage Documentation:** Clear usage patterns and examples
+- **Integration Points:** Better integration with Claude Code's capabilities
+- **Error Handling:** Improved error recovery and reporting
+- **Solo Project Focus:** Removed team coordination overhead
+
+## Technical Requirements
+
+### Environment Setup
+```bash
+export GIT_PAGER=cat  # Required for git/gh commands
+```
+
+### Dependencies
+- **GitHub CLI (`gh`)** - Authenticated and functional
+- **Node.js & pnpm** - Package management and script execution
+- **Git repository** - Proper remote configuration
+- **Project scripts** - `.scripts/` directory with validation tools
+
+### File System
+- **Temp directory access** - Commands use `/tmp/` for intermediate files
+- **Write permissions** - Repository write access for commits and PRs
+- **Script execution** - Permission to execute project validation scripts
+
+## Integration with CLAUDE.md
+
+These commands are designed to work seamlessly with the patterns and standards documented in `CLAUDE.md`. They enforce:
+
+- Clean architecture layer separation
+- Absolute import requirements
+- Error handling standards
+- Commit message conventions
+- Quality validation procedures
+- Solo project adaptations
+
+## Usage Guidelines
+
+### Command Execution
+- Commands are designed for autonomous execution
+- Quality validation is integrated into all commands
+- Error recovery is built into command logic
+- User confirmation is requested for destructive operations
+
+### Workflow Integration
+- Commands chain together for complete development workflows
+- State preservation between commands
+- Quality gates prevent progression with errors
+- Continuous validation throughout process
+
+### Customization
+- Commands adapt to project-specific patterns
+- User preferences are learned and applied
+- Context is preserved across sessions
+- Patterns are documented and reused
+
+## Best Practices
+
+1. **Start with `/fix`** - Ensure clean codebase before development
+2. **Use proper issue types** - Choose correct template for `/create-issue`
+3. **Plan before implementing** - Review implementation plan in `/implement`
+4. **Validate continuously** - Let commands handle quality validation
+5. **End sessions properly** - Use `/end-session` for knowledge preservation
+
+## Troubleshooting
+
+### Common Issues
+- **Permission errors:** Ensure proper git and GitHub authentication
+- **Script failures:** Verify `.scripts/` directory and permissions
+- **Validation failures:** Run `/fix` to resolve quality issues
+- **Network issues:** Check GitHub CLI authentication and connectivity
+
+### Recovery Procedures
+- **Failed commits:** Commands will retry with proper shell escaping
+- **PR creation errors:** Automatic retry with corrected parameters
+- **Validation loops:** Commands will iterate until all checks pass
+- **Missing dependencies:** Commands provide fallback strategies
+
+For detailed usage instructions, see individual command documentation files.

.claude/commands/issues/create.md

@@ -0,0 +1,174 @@
+# GitHub Issue Creator
+
+Create any type of GitHub issue (bug, feature, improvement, refactor, task, subissue) using the correct template and workflow.
+
+## Usage
+
+```
+/create-issue [type] [description]
+```
+
+**Parameters:**
+- `type` (optional): bug, feature, improvement, refactor, task, subissue
+- `description` (optional): Brief description of the issue
+
+## Description
+
+This command creates GitHub issues using the appropriate templates from the docs/ directory. It handles all issue types with proper formatting, labels, and validation.
+
+## What it does
+
+1. **Type Clarification:**
+   - Asks for issue type if not specified or ambiguous
+   - Validates against supported types: bug, feature, improvement, refactor, task, subissue
+
+2. **Template Selection:**
+   - Uses correct template from `docs/` directory:
+     - Bug: `ISSUE_TEMPLATE_BUGFIX.md`
+     - Feature: `ISSUE_TEMPLATE_FEATURE.md`
+     - Improvement: `issue-improvement-*.md`
+     - Refactor: `ISSUE_TEMPLATE_REFACTOR.md`
+     - Task: `ISSUE_TEMPLATE_TASK.md`
+     - Subissue: `ISSUE_TEMPLATE_SUBISSUE.md`
+
+3. **Content Generation:**
+   - Fills template with provided information
+   - Uses Markdown formatting for all sections
+   - Generates in English (UI text may be pt-BR if required)
+
+4. **Investigation (for bugs):**
+   - Searches codebase for related files using error messages
+   - Adds `Related Files` section with relevant file paths
+   - Includes stack trace analysis when available
+
+5. **Environment Info:**
+   - Updates app version using `.scripts/semver.sh`
+   - Includes current environment details
+   - Validates script availability and fallbacks
+
+6. **Issue Creation:**
+   - Uses `printf` with heredoc for multi-line content
+   - Writes to temp file for shell compatibility
+   - Executes `gh issue create --body-file`
+   - Verifies content before submission
+
+## Issue Types
+
+### Bug Reports
+- **Requirements:** Error message, stack trace, or reproduction steps
+- **Investigation:** Automatic codebase search for related files
+- **Template:** Structured bug report with environment details
+- **Labels:** `bug` + complexity + area labels
+
+### Feature Requests
+- **Requirements:** Clear description of desired functionality
+- **Template:** Feature specification with acceptance criteria
+- **Solo Project Focus:** Technical implementation over business value
+- **Labels:** `feature` + complexity + area labels
+
+### Improvements
+- **Requirements:** Justification and impact assessment
+- **Template:** Technical debt or enhancement description
+- **Focus:** Code quality, performance, maintainability
+- **Labels:** `improvement` + complexity + area labels
+
+### Refactors
+- **Requirements:** Affected files and modules list
+- **Template:** Architecture improvement specification
+- **Implementation:** Clear scope and affected components
+- **Labels:** `refactor` + complexity + area labels
+
+### Tasks
+- **Requirements:** Specific actionable items
+- **Template:** Structured task with clear deliverables
+- **Focus:** Maintenance, chores, non-feature work
+- **Labels:** `task` + complexity + area labels
+
+### Subissues
+- **Requirements:** Parent issue reference
+- **Template:** Subset of larger issue work
+- **Linking:** Always references parent issue number
+- **Labels:** `subissue` + parent labels
+
+## Shell and CLI Handling
+
+### Zsh Compatibility
+- Uses `printf` with double quotes for special characters
+- Writes content to temp files before submission
+- Verifies file content with `cat` before execution
+- Handles Unicode and accented characters properly
+
+### Error Handling
+- Checks script existence before execution
+- Validates CLI command outputs
+- Retries with corrected parameters
+- Reports errors gracefully
+
+### File Operations
+- Creates temp files in `/tmp/` with unique names
+- Verifies write permissions
+- Cleans up temporary files after use
+- Handles permission issues gracefully
+
+## Labels and Validation
+
+### Required Labels
+- **Type label:** One of bug, feature, improvement, refactor, task, subissue
+- **Complexity:** low, medium, high, very-high (when assessable)
+- **Area:** ui, backend, api, performance, accessibility (when applicable)
+
+### Label Validation
+- Uses only existing labels and milestones
+- Skips missing labels rather than failing
+- Refers to `docs/labels-usage.md` for conventions
+- Avoids duplicate or conflicting labels
+
+### Content Validation
+- Verifies Markdown formatting
+- Checks template compliance
+- Validates required sections
+- Ensures English language usage
+
+## Solo Project Adaptations
+
+- **Focus:** Technical excellence over business coordination
+- **Removal:** Stakeholder approval workflows
+- **Emphasis:** Self-review and technical validation
+- **Metrics:** Technical over business/team metrics
+- **Documentation:** Implementation-focused templates
+
+## Integration Features
+
+- **Version Tracking:** Uses `.scripts/semver.sh` for app version
+- **Codebase Search:** Automatic file discovery for bugs
+- **Template System:** Consistent formatting across issue types
+- **CLI Integration:** Full GitHub CLI workflow support
+- **Error Recovery:** Graceful handling of missing dependencies
+
+## Output
+
+Creates GitHub issue and outputs the final command:
+
+```bash
+gh issue create --title "feat: add dark mode toggle" \
+  --body-file /tmp/issue-body.md \
+  --label feature,ui,complexity-medium \
+  --milestone "v0.14.0"
+```
+
+## Requirements
+
+- GitHub CLI (`gh`) installed and authenticated
+- `.scripts/semver.sh` script (with fallback)
+- Write access to repository
+- Valid issue templates in `docs/` directory
+- Shell with `printf` and heredoc support
+
+## Best Practices
+
+- **Clear titles:** Use conventional commit style when applicable
+- **Complete templates:** Fill all required sections
+- **Proper investigation:** Search codebase for bugs
+- **Accurate labels:** Use appropriate type and complexity labels
+- **Environment details:** Include version and environment info
+- **Validation:** Check content before submission