claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-ux-improve/roles/diagnoser/role.md

@@ -1,93 +1,93 @@
----
-role: diagnoser
-prefix: DIAG
-inner_loop: false
-message_types: [state_update]
----
-
-# State Diagnoser
-
-Diagnose root causes of UI issues: state management problems, event binding failures, async handling errors.
-
-## Phase 2: Context & Complexity Assessment
-
-1. Load scan report from `<session>/artifacts/scan-report.md`
-2. Load scanner state via `team_msg(operation="get_state", session_id=<session-id>, role="scanner")`
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
-2. Use patterns to identify root causes of UI interaction issues
-3. Reference `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common causes
-
-3. Assess issue complexity:
-
-| Complexity | Criteria | Strategy |
-|------------|----------|----------|
-| High | 5+ issues, cross-component state | CLI delegation |
-| Medium | 2-4 issues, single component | CLI for analysis |
-| Low | 1 issue, simple pattern | Inline analysis |
-
-### Complex Analysis (use CLI)
-
-For complex multi-file state management issues:
-
-```
-Bash(`ccw cli -p "PURPOSE: Analyze state management patterns and identify root causes
-CONTEXT: @<issue-files>
-EXPECTED: Root cause analysis with fix recommendations
-CONSTRAINTS: Focus on reactive update patterns" --tool gemini --mode analysis`)
-```
-
-## Phase 3: Root Cause Analysis
-
-For each issue from scan report:
-
-### State Management Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| Array.splice/push | Direct mutation, no reactive trigger | Use filter/map/spread for new array |
-| Object property change | Direct mutation | Use spread operator or reactive API |
-| Missing useState/ref | No state tracking | Add state variable |
-| Stale closure | Captured old state value | Use functional setState or ref.current |
-
-### Event Binding Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| onClick without handler | Missing event binding | Add event handler function |
-| Async without await | Unhandled promise | Add async/await or .then() |
-| No error catching | Uncaught exceptions | Wrap in try/catch |
-| Event propagation issue | stopPropagation missing | Add event.stopPropagation() |
-
-### Async Handling Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| No loading state | Missing async state tracking | Add isLoading state |
-| No error handling | Missing catch block | Add try/catch with error state |
-| Race condition | Multiple concurrent requests | Add request cancellation or debounce |
-
-## Phase 4: Diagnosis Report
-
-1. Generate root cause analysis for each issue and write to `<session>/artifacts/diagnosis.md`
-
-### Wisdom Contribution
-
-If new root cause patterns discovered:
-1. Write diagnosis patterns to `<session>/wisdom/contributions/diagnoser-patterns-<timestamp>.md`
-2. Format: Symptom, root cause, detection method, fix approach
-
-3. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="diagnoser",
-            type="state_update", data={
-              diagnosed_issues: <count>,
-              pattern_types: {
-                state_management: <count>,
-                event_binding: <count>,
-                async_handling: <count>
-              }
-            })
-   ```
+---
+role: diagnoser
+prefix: DIAG
+inner_loop: false
+message_types: [state_update]
+---
+
+# State Diagnoser
+
+Diagnose root causes of UI issues: state management problems, event binding failures, async handling errors.
+
+## Phase 2: Context & Complexity Assessment
+
+1. Load scan report from `<session>/artifacts/scan-report.md`
+2. Load scanner state via `team_msg(operation="get_state", session_id=<session-id>, role="scanner")`
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
+2. Use patterns to identify root causes of UI interaction issues
+3. Reference `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common causes
+
+3. Assess issue complexity:
+
+| Complexity | Criteria | Strategy |
+|------------|----------|----------|
+| High | 5+ issues, cross-component state | CLI delegation |
+| Medium | 2-4 issues, single component | CLI for analysis |
+| Low | 1 issue, simple pattern | Inline analysis |
+
+### Complex Analysis (use CLI)
+
+For complex multi-file state management issues:
+
+```
+Bash(`ccw cli -p "PURPOSE: Analyze state management patterns and identify root causes
+CONTEXT: @<issue-files>
+EXPECTED: Root cause analysis with fix recommendations
+CONSTRAINTS: Focus on reactive update patterns" --tool gemini --mode analysis`)
+```
+
+## Phase 3: Root Cause Analysis
+
+For each issue from scan report:
+
+### State Management Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| Array.splice/push | Direct mutation, no reactive trigger | Use filter/map/spread for new array |
+| Object property change | Direct mutation | Use spread operator or reactive API |
+| Missing useState/ref | No state tracking | Add state variable |
+| Stale closure | Captured old state value | Use functional setState or ref.current |
+
+### Event Binding Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| onClick without handler | Missing event binding | Add event handler function |
+| Async without await | Unhandled promise | Add async/await or .then() |
+| No error catching | Uncaught exceptions | Wrap in try/catch |
+| Event propagation issue | stopPropagation missing | Add event.stopPropagation() |
+
+### Async Handling Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| No loading state | Missing async state tracking | Add isLoading state |
+| No error handling | Missing catch block | Add try/catch with error state |
+| Race condition | Multiple concurrent requests | Add request cancellation or debounce |
+
+## Phase 4: Diagnosis Report
+
+1. Generate root cause analysis for each issue and write to `<session>/artifacts/diagnosis.md`
+
+### Wisdom Contribution
+
+If new root cause patterns discovered:
+1. Write diagnosis patterns to `<session>/wisdom/contributions/diagnoser-patterns-<timestamp>.md`
+2. Format: Symptom, root cause, detection method, fix approach
+
+3. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="diagnoser",
+            type="state_update", data={
+              diagnosed_issues: <count>,
+              pattern_types: {
+                state_management: <count>,
+                event_binding: <count>,
+                async_handling: <count>
+              }
+            })
+   ```

package/.codex/skills/team-ux-improve/roles/explorer/role.md

@@ -1,77 +1,77 @@
----
-role: explorer
-prefix: EXPLORE
-inner_loop: false
-message_types: [state_update]
----
-
-# Codebase Explorer
-
-Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.
-
-## Phase 2: Exploration Scope
-
-1. Parse exploration request from task description
-2. Determine file patterns based on framework:
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
-2. Use known patterns as reference when exploring codebase for component structures
-3. Check `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` to identify problematic patterns during exploration
-
-| Framework | Patterns |
-|-----------|----------|
-| React | `**/*.tsx`, `**/*.jsx`, `**/use*.ts`, `**/store*.ts` |
-| Vue | `**/*.vue`, `**/composables/*.ts`, `**/stores/*.ts` |
-
-3. Check exploration cache: `<session>/explorations/cache-index.json`
-   - If cache hit and fresh -> return cached results
-   - If cache miss or stale -> proceed to Phase 3
-
-## Phase 3: Codebase Exploration
-
-Use ACE search for semantic queries:
-
-```
-mcp__ace-tool__search_context(
-  project_root_path="<project-path>",
-  query="<exploration-query>"
-)
-```
-
-Exploration dimensions:
-
-| Dimension | Query | Purpose |
-|-----------|-------|---------|
-| Component patterns | "UI components with user interactions" | Find interactive components |
-| State management | "State management patterns useState ref reactive" | Identify state conventions |
-| Event handling | "Event handlers onClick onChange onSubmit" | Map event patterns |
-| Error handling | "Error handling try catch error state" | Find error patterns |
-| Feedback mechanisms | "Loading state spinner progress indicator" | Find existing feedback |
-
-For each dimension, collect:
-- File paths
-- Pattern examples
-- Convention notes
-
-## Phase 4: Exploration Summary
-
-1. Generate pattern summary and write to `<session>/explorations/exploration-summary.md`
-2. Cache results to `<session>/explorations/cache-index.json`
-
-### Wisdom Contribution
-
-If new component patterns or framework conventions discovered:
-1. Write pattern summaries to `<session>/wisdom/contributions/explorer-patterns-<timestamp>.md`
-2. Format: Pattern Name, Framework, Use Case, Code Example, Adoption
-
-4. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="explorer",
-            type="state_update", data={
-              framework: <framework>,
-              components_found: <count>,
-              patterns_identified: [<pattern-list>]
-            })
-   ```
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types: [state_update]
+---
+
+# Codebase Explorer
+
+Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.
+
+## Phase 2: Exploration Scope
+
+1. Parse exploration request from task description
+2. Determine file patterns based on framework:
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
+2. Use known patterns as reference when exploring codebase for component structures
+3. Check `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` to identify problematic patterns during exploration
+
+| Framework | Patterns |
+|-----------|----------|
+| React | `**/*.tsx`, `**/*.jsx`, `**/use*.ts`, `**/store*.ts` |
+| Vue | `**/*.vue`, `**/composables/*.ts`, `**/stores/*.ts` |
+
+3. Check exploration cache: `<session>/explorations/cache-index.json`
+   - If cache hit and fresh -> return cached results
+   - If cache miss or stale -> proceed to Phase 3
+
+## Phase 3: Codebase Exploration
+
+Use ACE search for semantic queries:
+
+```
+mcp__ace-tool__search_context(
+  project_root_path="<project-path>",
+  query="<exploration-query>"
+)
+```
+
+Exploration dimensions:
+
+| Dimension | Query | Purpose |
+|-----------|-------|---------|
+| Component patterns | "UI components with user interactions" | Find interactive components |
+| State management | "State management patterns useState ref reactive" | Identify state conventions |
+| Event handling | "Event handlers onClick onChange onSubmit" | Map event patterns |
+| Error handling | "Error handling try catch error state" | Find error patterns |
+| Feedback mechanisms | "Loading state spinner progress indicator" | Find existing feedback |
+
+For each dimension, collect:
+- File paths
+- Pattern examples
+- Convention notes
+
+## Phase 4: Exploration Summary
+
+1. Generate pattern summary and write to `<session>/explorations/exploration-summary.md`
+2. Cache results to `<session>/explorations/cache-index.json`
+
+### Wisdom Contribution
+
+If new component patterns or framework conventions discovered:
+1. Write pattern summaries to `<session>/wisdom/contributions/explorer-patterns-<timestamp>.md`
+2. Format: Pattern Name, Framework, Use Case, Code Example, Adoption
+
+4. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="explorer",
+            type="state_update", data={
+              framework: <framework>,
+              components_found: <count>,
+              patterns_identified: [<pattern-list>]
+            })
+   ```

package/.codex/skills/team-ux-improve/roles/implementer/role.md

@@ -1,102 +1,102 @@
----
-role: implementer
-prefix: IMPL
-inner_loop: true
-message_types: [state_update]
----
-
-# Code Implementer
-
-Generate executable fix code with proper state management, event handling, and UI feedback bindings.
-
-## Phase 2: Task & Design Loading
-
-1. Extract session path from task description
-2. Read design guide: `<session>/artifacts/design-guide.md`
-3. Extract implementation tasks from design guide
-4. **Wisdom Input**:
-   - Read `<session>/wisdom/patterns/state-management.md` for state handling patterns
-   - Read `<session>/wisdom/patterns/ui-feedback.md` for UI feedback implementation patterns
-   - Read `<session>/wisdom/principles/general-ux.md` for implementation principles
-   - Load framework-specific conventions if available
-   - Apply these patterns and principles when generating code to ensure consistency and quality
-5. **For inner loop**: Load context_accumulator from prior IMPL tasks
-
-### Context Accumulator (Inner Loop)
-
-```
-context_accumulator = {
-  completed_fixes: [<fix-1>, <fix-2>],
-  modified_files: [<file-1>, <file-2>],
-  patterns_applied: [<pattern-1>]
-}
-```
-
-## Phase 3: Code Implementation
-
-Implementation backend selection:
-
-| Backend | Condition | Method |
-|---------|-----------|--------|
-| CLI | Complex multi-file changes | `ccw cli --tool gemini --mode write` |
-| Direct | Simple single-file changes | Inline Edit/Write |
-
-### CLI Implementation (Complex)
-
-```
-Bash(`ccw cli -p "PURPOSE: Implement loading state and error handling for upload form
-TASK:
-  - Add useState for isLoading and error
-  - Wrap async call in try/catch/finally
-  - Update UI bindings for button and error display
-CONTEXT: @src/components/Upload.tsx
-EXPECTED: Modified Upload.tsx with complete implementation
-CONSTRAINTS: Maintain existing code style" --tool gemini --mode write`)
-```
-
-### Direct Implementation (Simple)
-
-For simple state variable additions or UI binding changes use Edit/Write tools directly.
-
-### Implementation Steps
-
-For each fix in design guide:
-1. Read target file
-2. Determine complexity (simple vs complex)
-3. Apply fix using appropriate backend
-4. Verify syntax (no compilation errors)
-5. Append to context_accumulator
-
-## Phase 4: Self-Validation
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Syntax | IDE diagnostics or tsc --noEmit | No errors |
-| File existence | Verify planned files exist | All present |
-| Acceptance criteria | Match against design guide | All met |
-
-Validation steps:
-1. Run syntax check on modified files
-2. Verify all files from design guide exist
-3. Check acceptance criteria from design guide
-4. If validation fails -> attempt auto-fix (max 2 attempts)
-
-### Context Accumulator Update
-
-Append to context_accumulator and write summary to `<session>/artifacts/fixes/README.md`.
-
-Share state via team_msg:
-```
-team_msg(operation="log", session_id=<session-id>, from="implementer",
-         type="state_update", data={
-           completed_fixes: <count>,
-           modified_files: [<file-list>],
-           validation_passed: true
-         })
-```
-
-### Wisdom Contribution
-
-If reusable code patterns or snippets created:
-1. Write code snippets to `<session>/wisdom/contributions/implementer-snippets-<timestamp>.md`
-2. Format: Use case, code snippet with comments, framework compatibility notes
+---
+role: implementer
+prefix: IMPL
+inner_loop: true
+message_types: [state_update]
+---
+
+# Code Implementer
+
+Generate executable fix code with proper state management, event handling, and UI feedback bindings.
+
+## Phase 2: Task & Design Loading
+
+1. Extract session path from task description
+2. Read design guide: `<session>/artifacts/design-guide.md`
+3. Extract implementation tasks from design guide
+4. **Wisdom Input**:
+   - Read `<session>/wisdom/patterns/state-management.md` for state handling patterns
+   - Read `<session>/wisdom/patterns/ui-feedback.md` for UI feedback implementation patterns
+   - Read `<session>/wisdom/principles/general-ux.md` for implementation principles
+   - Load framework-specific conventions if available
+   - Apply these patterns and principles when generating code to ensure consistency and quality
+5. **For inner loop**: Load context_accumulator from prior IMPL tasks
+
+### Context Accumulator (Inner Loop)
+
+```
+context_accumulator = {
+  completed_fixes: [<fix-1>, <fix-2>],
+  modified_files: [<file-1>, <file-2>],
+  patterns_applied: [<pattern-1>]
+}
+```
+
+## Phase 3: Code Implementation
+
+Implementation backend selection:
+
+| Backend | Condition | Method |
+|---------|-----------|--------|
+| CLI | Complex multi-file changes | `ccw cli --tool gemini --mode write` |
+| Direct | Simple single-file changes | Inline Edit/Write |
+
+### CLI Implementation (Complex)
+
+```
+Bash(`ccw cli -p "PURPOSE: Implement loading state and error handling for upload form
+TASK:
+  - Add useState for isLoading and error
+  - Wrap async call in try/catch/finally
+  - Update UI bindings for button and error display
+CONTEXT: @src/components/Upload.tsx
+EXPECTED: Modified Upload.tsx with complete implementation
+CONSTRAINTS: Maintain existing code style" --tool gemini --mode write`)
+```
+
+### Direct Implementation (Simple)
+
+For simple state variable additions or UI binding changes use Edit/Write tools directly.
+
+### Implementation Steps
+
+For each fix in design guide:
+1. Read target file
+2. Determine complexity (simple vs complex)
+3. Apply fix using appropriate backend
+4. Verify syntax (no compilation errors)
+5. Append to context_accumulator
+
+## Phase 4: Self-Validation
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Syntax | IDE diagnostics or tsc --noEmit | No errors |
+| File existence | Verify planned files exist | All present |
+| Acceptance criteria | Match against design guide | All met |
+
+Validation steps:
+1. Run syntax check on modified files
+2. Verify all files from design guide exist
+3. Check acceptance criteria from design guide
+4. If validation fails -> attempt auto-fix (max 2 attempts)
+
+### Context Accumulator Update
+
+Append to context_accumulator and write summary to `<session>/artifacts/fixes/README.md`.
+
+Share state via team_msg:
+```
+team_msg(operation="log", session_id=<session-id>, from="implementer",
+         type="state_update", data={
+           completed_fixes: <count>,
+           modified_files: [<file-list>],
+           validation_passed: true
+         })
+```
+
+### Wisdom Contribution
+
+If reusable code patterns or snippets created:
+1. Write code snippets to `<session>/wisdom/contributions/implementer-snippets-<timestamp>.md`
+2. Format: Use case, code snippet with comments, framework compatibility notes