moicle 1.0.2 → 1.1.1

package/assets/skills/{hotfix-workflow → hotfix}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: hotfix-workflow
+name: hotfix
 description: Quick bug fix workflow with rollback plan. Use when fixing bugs, hotfixes, urgent issues, production bugs, or when user says "fix bug", "hotfix", "urgent fix", "production issue".
 ---
 
@@ -7,6 +7,29 @@ description: Quick bug fix workflow with rollback plan. Use when fixing bugs, ho
 
 Fast-track workflow for fixing bugs with safety rollback plan.
 
+## IMPORTANT: Read Architecture First
+
+**Before fixing, you MUST read the appropriate architecture reference:**
+
+### Global Architecture Files
+```
+~/.claude/architecture/
+├── clean-architecture.md    # Core principles for all projects
+├── flutter-mobile.md        # Flutter + Riverpod
+├── react-frontend.md        # React + Vite + TypeScript
+├── go-backend.md            # Go + Gin
+├── laravel-backend.md       # Laravel + PHP
+├── remix-fullstack.md       # Remix fullstack
+└── monorepo.md              # Monorepo structure
+```
+
+### Project-specific (if exists)
+```
+.claude/architecture/        # Project overrides
+```
+
+**Understand the codebase structure before making changes.**
+
 ## Recommended Agents
 
 | Phase | Agent | Purpose |
@@ -39,8 +62,6 @@ Fast-track workflow for fixing bugs with safety rollback plan.
 
 **Goal**: Identify exactly what the bug is
 
-**Time**: 5-10 minutes
-
 ### Actions
 1. Gather information:
    - Error message / stack trace
@@ -49,7 +70,9 @@ Fast-track workflow for fixing bugs with safety rollback plan.
    - Environment (prod/staging/dev)
    - Affected users/scope
 
-2. Assess severity:
+2. **Identify project stack and read architecture doc**
+
+3. Assess severity:
    ```
    🔴 CRITICAL - Production down, data loss
    🟠 HIGH     - Major feature broken, many users affected
@@ -57,21 +80,24 @@ Fast-track workflow for fixing bugs with safety rollback plan.
    🟢 LOW      - Minor issue, cosmetic
    ```
 
-3. Document:
-   ```markdown
-   ## Bug Report
-   **Severity**: [CRITICAL/HIGH/MEDIUM/LOW]
-   **Error**: [error message]
-   **Steps**:
-   1. ...
-   2. ...
-   **Expected**: [what should happen]
-   **Actual**: [what happens]
-   **Environment**: [prod/staging/dev]
-   ```
+### Output
+```markdown
+## Bug Report
+**Severity**: [CRITICAL/HIGH/MEDIUM/LOW]
+**Stack**: [Flutter/React/Go/Laravel/Remix]
+**Architecture Doc**: [path]
+**Error**: [error message]
+**Steps**:
+1. ...
+2. ...
+**Expected**: [what should happen]
+**Actual**: [what happens]
+**Environment**: [prod/staging/dev]
+```
 
 ### Gate
 - [ ] Bug clearly described
+- [ ] Architecture doc identified
 - [ ] Severity assessed
 - [ ] Scope understood
 
@@ -81,17 +107,10 @@ Fast-track workflow for fixing bugs with safety rollback plan.
 
 **Goal**: Reproduce the bug and find root cause
 
-**Time**: 10-20 minutes
-
 ### Actions
-1. Reproduce locally:
-   ```bash
-   # Setup same environment
-   # Follow exact steps
-   # Confirm bug occurs
-   ```
-
-2. Find root cause (5 Whys):
+1. **Read architecture doc** to understand codebase structure
+2. Reproduce locally following architecture patterns
+3. Find root cause using 5 Whys:
    ```
    Why did it fail? → [answer]
    Why? → [deeper answer]
@@ -100,12 +119,12 @@ Fast-track workflow for fixing bugs with safety rollback plan.
    Why? → [ROOT CAUSE]
    ```
 
-3. Identify fix location:
+4. Identify fix location based on architecture:
+   - Which layer? (from architecture doc)
    - Which file(s)?
-   - Which function(s)?
    - What's the minimal change?
 
-4. Check git blame:
+5. Check git blame:
    ```bash
    git log --oneline -10 -- [affected_file]
    git blame [affected_file] | grep -A5 -B5 "[problem_area]"
@@ -114,33 +133,34 @@ Fast-track workflow for fixing bugs with safety rollback plan.
 ### Analysis Output
 ```markdown
 ## Root Cause Analysis
+**Architecture Reference**: [path to doc]
+**Affected Layer**: [layer from architecture doc]
 **Root Cause**: [description]
 **Introduced**: [commit/PR if known]
 **Affected Files**:
-- file1.ts:123
-- file2.ts:456
+- file1:123
+- file2:456
 
-**Fix Strategy**: [brief description of fix]
+**Fix Strategy**: [brief description following architecture patterns]
 ```
 
 ### Gate
 - [ ] Bug reproduced locally
 - [ ] Root cause identified
-- [ ] Fix location known
+- [ ] Fix location known (per architecture)
 
 ---
 
 ## Phase 3: FIX
 
-**Goal**: Implement minimal fix
-
-**Time**: 15-30 minutes
+**Goal**: Implement minimal fix following architecture
 
 ### Principles
 1. **Minimal change** - Fix only what's broken
-2. **No refactoring** - Save for later
-3. **No new features** - Stay focused
-4. **Preserve behavior** - Don't change anything else
+2. **Follow architecture** - Respect layer boundaries from doc
+3. **No refactoring** - Save for later
+4. **No new features** - Stay focused
+5. **Preserve behavior** - Don't change anything else
 
 ### Actions
 1. Create hotfix branch:
@@ -148,20 +168,22 @@ Fast-track workflow for fixing bugs with safety rollback plan.
    git checkout -b hotfix/[issue-id]-[short-description]
    ```
 
-2. Implement fix:
-   - Make smallest possible change
-   - Add defensive code if needed
-   - Add inline comment explaining fix
+2. **Read architecture doc** for the affected layer
+3. Implement fix following architecture patterns:
+   - Use correct patterns from doc
+   - Follow naming conventions from doc
+   - Respect layer boundaries
 
-3. Fix template:
-   ```typescript
+4. Add inline comment explaining fix:
+   ```
    // HOTFIX: [issue-id] - [brief description]
    // Root cause: [why this fixes it]
    [your fix code]
    ```
 
 ### Gate
-- [ ] Fix implemented
+- [ ] Fix follows architecture doc
+- [ ] Fix implemented minimally
 - [ ] Code compiles
 - [ ] No unrelated changes
 
@@ -171,24 +193,22 @@ Fast-track workflow for fixing bugs with safety rollback plan.
 
 **Goal**: Confirm fix works without breaking other things
 
-**Time**: 10-15 minutes
-
 ### Actions
 1. Test the fix:
    - [ ] Original bug no longer occurs
    - [ ] Related functionality still works
    - [ ] Edge cases handled
 
-2. Run existing tests:
+2. Run existing tests (use command from architecture doc):
    ```bash
-   # Run all tests
-   pnpm test        # JS/TS
-   go test ./...    # Go
-   flutter test     # Flutter
+   flutter test           # Flutter
+   go test ./...          # Go
+   bun test               # React/Remix
+   php artisan test       # Laravel
    ```
 
-3. Add regression test:
-   ```typescript
+3. Add regression test following architecture patterns:
+   ```
    // Test to prevent regression
    it('should [expected behavior] - fixes #[issue-id]', () => {
      // Arrange: setup that caused bug
@@ -206,14 +226,14 @@ Fast-track workflow for fixing bugs with safety rollback plan.
 ### Gate
 - [ ] Original bug fixed
 - [ ] All tests pass
-- [ ] Regression test added
+- [ ] Regression test added (following arch patterns)
 - [ ] No new issues introduced
 
 ### Feedback Loop
 If verification fails:
 1. Note what failed
 2. Return to FIX phase
-3. Adjust fix
+3. Adjust fix (following architecture)
 4. Re-verify
 
 ---
@@ -222,8 +242,6 @@ If verification fails:
 
 **Goal**: Ship the fix safely
 
-**Time**: 5-10 minutes
-
 ### Actions
 1. Commit with clear message:
    ```bash
@@ -246,7 +264,7 @@ If verification fails:
    [explanation]
 
    ## Fix
-   [what was changed]
+   [what was changed, following architecture patterns]
 
    ## Testing
    - [ ] Original bug no longer occurs
@@ -295,7 +313,7 @@ If verification fails:
    ```
 
 2. **Feature Flag** (if available):
-   ```typescript
+   ```
    // Disable the fix temporarily
    if (!featureFlags.hotfix_123_enabled) {
      // Original behavior
@@ -312,13 +330,24 @@ If verification fails:
 ### Post-Rollback
 1. Document what went wrong
 2. Return to REPRODUCE phase
-3. Analyze why fix failed
+3. Analyze why fix failed (check architecture compliance)
 4. Create better fix
 
 ---
 
 ## Quick Reference
 
+### Architecture Docs
+| Stack | Doc |
+|-------|-----|
+| All | `clean-architecture.md` |
+| Flutter | `flutter-mobile.md` |
+| React | `react-frontend.md` |
+| Go | `go-backend.md` |
+| Laravel | `laravel-backend.md` |
+| Remix | `remix-fullstack.md` |
+| Monorepo | `monorepo.md` |
+
 ### Hotfix vs Feature
 
 | Aspect | Hotfix | Feature |

package/assets/skills/new-feature/SKILL.md

@@ -0,0 +1,317 @@
+---
+name: new-feature
+description: Complete feature development workflow from start to finish. Use when implementing new features, building functionality, or when user says "implement feature", "add feature", "build feature", "create feature", "new feature".
+---
+
+# Feature Development Workflow
+
+End-to-end workflow for developing features with feedback loops and quality gates.
+
+## IMPORTANT: Read Architecture First
+
+**Before starting any phase, you MUST read the appropriate architecture reference:**
+
+### Global Architecture Files
+```
+~/.claude/architecture/
+├── clean-architecture.md    # Core principles for all projects
+├── flutter-mobile.md        # Flutter + Riverpod
+├── react-frontend.md        # React + Vite + TypeScript
+├── go-backend.md            # Go + Gin
+├── laravel-backend.md       # Laravel + PHP
+├── remix-fullstack.md       # Remix fullstack
+└── monorepo.md              # Monorepo structure
+```
+
+### Project-specific (if exists)
+```
+.claude/architecture/        # Project overrides
+```
+
+**Follow the structure and patterns defined in these files exactly.**
+
+## Recommended Agents
+
+| Phase | Agent | Purpose |
+|-------|-------|---------|
+| DESIGN | `@clean-architect` | Design based on architecture docs |
+| IMPLEMENT | `@react-frontend-dev`, `@go-backend-dev`, `@laravel-backend-dev`, `@flutter-mobile-dev`, `@remix-fullstack-dev` | Stack-specific implementation |
+| IMPLEMENT | `@db-designer` | Database schema design |
+| IMPLEMENT | `@api-designer` | API design (REST/GraphQL) |
+| REVIEW | `@code-reviewer` | Code quality review |
+| REVIEW | `@security-audit` | Security vulnerabilities check |
+| REVIEW | `@perf-optimizer` | Performance optimization |
+| TEST | `@test-writer` | Unit/integration/e2e tests |
+| COMPLETE | `@docs-writer` | Documentation (if needed) |
+
+## Workflow Overview
+
+```
+┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
+│ 1. PLAN  │──▶│ 2. DESIGN│──▶│3. IMPLEMENT──▶│ 4. REVIEW│──▶│ 5. TEST  │──▶│6. COMPLETE
+└──────────┘   └──────────┘   └──────────┘   └──────────┘   └──────────┘   └──────────┘
+                                                   │              │
+                                                   └──────◀───────┘
+                                                    Feedback Loop
+```
+
+---
+
+## Phase 1: PLAN
+
+**Goal**: Understand requirements and break down into tasks
+
+### Actions
+1. Clarify requirements with user
+2. **Identify project stack** (Flutter, React, Go, Laravel, Remix, etc.)
+3. **Read the appropriate architecture doc** for this stack
+4. Identify affected files/modules based on architecture
+5. List acceptance criteria
+6. Create task breakdown using TodoWrite
+
+### Output
+```markdown
+## Feature: [Name]
+
+### Stack & Architecture
+- Stack: [Flutter/React/Go/Laravel/Remix]
+- Architecture Doc: [path to architecture file]
+
+### Requirements
+- [ ] Requirement 1
+- [ ] Requirement 2
+
+### Affected Areas (based on architecture)
+- [Layer/Module 1]
+- [Layer/Module 2]
+
+### Tasks
+1. Task 1
+2. Task 2
+```
+
+### Gate
+- [ ] Requirements clear
+- [ ] Architecture doc read
+- [ ] Scope defined based on architecture
+- [ ] Tasks broken down
+
+---
+
+## Phase 2: DESIGN
+
+**Goal**: Design feature following the project's architecture
+
+### Actions
+1. **Re-read architecture doc** for the specific stack
+2. Apply architecture principles from the doc:
+   - Identify which layers are affected
+   - Define components for each layer
+   - Follow naming conventions from doc
+
+3. Design data flow based on architecture patterns
+
+### Design Template
+```markdown
+## Architecture Design
+
+### Reference
+- Architecture Doc: [path]
+- Pattern: [pattern from doc]
+
+### Layers Affected (from architecture doc)
+- Layer 1: [components]
+- Layer 2: [components]
+- Layer 3: [components]
+
+### Data Flow (from architecture doc)
+[Follow the data flow pattern defined in doc]
+
+### Dependencies
+[List dependencies following DI pattern from doc]
+```
+
+### Gate
+- [ ] Design follows architecture doc
+- [ ] Layers properly defined
+- [ ] Dependencies follow doc patterns
+
+---
+
+## Phase 3: IMPLEMENT
+
+**Goal**: Code the feature following the architecture doc
+
+### Actions
+1. **Read implementation order from architecture doc**
+2. Follow the directory structure from doc
+3. Follow naming conventions from doc
+4. Use patterns defined in doc (DI, state management, etc.)
+
+### Implementation Checklist
+```markdown
+## Implementation (following [stack] architecture)
+
+Reference: [architecture doc path]
+
+### Directory Structure (from doc)
+[Follow exact structure from architecture doc]
+
+### Implementation Order (from doc)
+[Follow order defined in architecture doc]
+
+### Code Conventions (from doc)
+[Follow conventions defined in architecture doc]
+```
+
+### Gate
+- [ ] Structure matches architecture doc
+- [ ] All layers implemented per doc
+- [ ] Code compiles without errors
+- [ ] Basic functionality works
+
+---
+
+## Phase 4: REVIEW
+
+**Goal**: Review code quality against architecture doc
+
+### Actions
+1. **Compare implementation with architecture doc**
+2. Check architecture rules are followed:
+   - [ ] Layer boundaries respected
+   - [ ] Dependencies flow correctly
+   - [ ] Patterns used correctly
+
+3. Security check:
+   - [ ] Input validation
+   - [ ] No sensitive data exposure
+   - [ ] Proper authentication/authorization
+
+4. Performance check:
+   - [ ] Efficient queries
+   - [ ] Proper caching (if in doc)
+   - [ ] No obvious bottlenecks
+
+### Review Output
+```markdown
+## Code Review Summary
+
+### Architecture Compliance: [Pass/Fail]
+- Reference: [architecture doc]
+- Issues: [list]
+
+### Quality: [Good/Needs Work]
+- Issues: [list]
+
+### Security: [Pass/Fail]
+- Issues: [list]
+
+### Performance: [Pass/Fail]
+- Issues: [list]
+```
+
+### Gate
+- [ ] Architecture doc followed
+- [ ] No critical issues
+- [ ] Security issues resolved
+
+### Feedback Loop
+If issues found → Return to IMPLEMENT phase → Fix → Re-review
+
+---
+
+## Phase 5: TEST
+
+**Goal**: Ensure feature works with tests
+
+### Actions
+1. **Read testing patterns from architecture doc**
+2. Write tests following doc conventions:
+   - Test locations from doc
+   - Mocking patterns from doc
+   - Coverage expectations from doc
+
+3. Run tests:
+   ```bash
+   # Use test command from architecture doc
+   flutter test           # Flutter
+   go test ./...          # Go
+   bun test               # React/Remix
+   php artisan test       # Laravel
+   ```
+
+### Gate
+- [ ] Tests follow architecture doc patterns
+- [ ] All tests pass
+- [ ] Coverage acceptable
+
+### Feedback Loop
+If tests fail → Return to IMPLEMENT → Fix → Re-test
+
+---
+
+## Phase 6: COMPLETE
+
+**Goal**: Finalize and deliver the feature
+
+### Actions
+1. Final checks:
+   - [ ] All gates passed
+   - [ ] Code formatted (use formatter from doc)
+   - [ ] No TODO comments left
+
+2. Git operations:
+   ```bash
+   git add .
+   git commit -m "feat: [feature description]"
+   ```
+
+3. Create PR (if applicable):
+   ```bash
+   gh pr create --title "feat: [feature]" --body "[description]"
+   ```
+
+### Completion Checklist
+- [ ] Feature follows architecture doc
+- [ ] Tests passing
+- [ ] Code reviewed
+- [ ] Committed/PR created
+
+---
+
+## Quick Reference
+
+### Architecture Docs
+| Stack | Doc |
+|-------|-----|
+| All | `clean-architecture.md` |
+| Flutter | `flutter-mobile.md` |
+| React | `react-frontend.md` |
+| Go | `go-backend.md` |
+| Laravel | `laravel-backend.md` |
+| Remix | `remix-fullstack.md` |
+| Monorepo | `monorepo.md` |
+
+### Phase Summary
+| Phase | Key Actions |
+|-------|-------------|
+| PLAN | Read arch doc, clarify, breakdown |
+| DESIGN | Design per arch doc |
+| IMPLEMENT | Code per arch doc |
+| REVIEW | Check arch compliance |
+| TEST | Test per arch doc patterns |
+| COMPLETE | Commit, PR |
+
+### When to Loop Back
+- **REVIEW fails** → Return to IMPLEMENT
+- **TEST fails** → Return to IMPLEMENT
+- **Requirements change** → Return to PLAN
+
+### Success Criteria
+Feature is complete when:
+1. Follows architecture doc
+2. All acceptance criteria met
+3. All tests passing
+4. Code review passed
+5. Committed/PR created

package/dist/commands/install.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"install.d.ts","sourceRoot":"","sources":["../../src/commands/install.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAmC,MAAM,aAAa,CAAC;AA6QnF,eAAO,MAAM,cAAc,GAAU,SAAS,cAAc,KAAG,OAAO,CAAC,IAAI,CAqF1E,CAAC"}
+{"version":3,"file":"install.d.ts","sourceRoot":"","sources":["../../src/commands/install.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAmC,MAAM,aAAa,CAAC;AA6QnF,eAAO,MAAM,cAAc,GAAU,SAAS,cAAc,KAAG,OAAO,CAAC,IAAI,CAsF1E,CAAC"}

package/dist/commands/install.js

@@ -271,10 +271,11 @@ export const installCommand = async (options) => {
         console.log('  Commands:');
         console.log(chalk.gray('    /bootstrap         Create new project'));
         console.log(chalk.gray('    /brainstorm        Brainstorm ideas'));
+        console.log(chalk.gray('    /doc               Generate documentation'));
         console.log('');
         console.log('  Skills (auto-triggered):');
-        console.log(chalk.gray('    feature-workflow   Feature development'));
-        console.log(chalk.gray('    hotfix-workflow    Bug fix with rollback'));
+        console.log(chalk.gray('    new-feature        Feature development'));
+        console.log(chalk.gray('    hotfix             Bug fix with rollback'));
         console.log('');
     }
     const otherTargets = targets.filter((t) => t !== 'claude');