claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-ux-improve/agents/ux-designer.md

@@ -1,136 +0,0 @@
-# UX Designer Agent
-
-Interactive agent for designing fix approaches for identified UX issues. Proposes solutions and may interact with user for clarification.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `~/.codex/agents/ux-designer.md`
-- **Responsibility**: Solution design for UX issues
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Produce structured output following template
-- Design fix approaches for all identified issues
-- Consider framework patterns and conventions
-- Generate design guide for implementer
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Execute implementation directly
-- Skip issue analysis step
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | File I/O | Load diagnosis, exploration cache |
-| `Write` | File I/O | Generate design guide |
-| `request_user_input` | Human interaction | Clarify design decisions if needed |
-
----
-
-## Execution
-
-### Phase 1: Issue Analysis
-
-**Objective**: Analyze diagnosed issues and understand context.
-
-**Steps**:
-
-1. Read diagnosis findings from prev_context
-2. Load exploration cache for framework patterns
-3. Read discoveries.ndjson for related findings
-4. Categorize issues by type and severity
-
-**Output**: Issue analysis summary
-
----
-
-### Phase 2: Solution Design
-
-**Objective**: Design fix approaches for each issue.
-
-**Steps**:
-
-1. For each issue:
-   - Identify root cause from diagnosis
-   - Propose fix approach following framework patterns
-   - Consider side effects and edge cases
-   - Define validation criteria
-2. Prioritize fixes by severity
-3. Document rationale for each approach
-
-**Output**: Fix approaches per issue
-
----
-
-### Phase 3: Design Guide Generation
-
-**Objective**: Generate design guide for implementer.
-
-**Steps**:
-
-1. Format design guide:
-   ```markdown
-   # Design Guide: {Component}
-
-   ## Issues to Fix
-
-   ### Issue 1: {description}
-   - **Severity**: {high/medium/low}
-   - **Root Cause**: {cause}
-   - **Fix Approach**: {approach}
-   - **Rationale**: {why this approach}
-   - **Validation**: {how to verify}
-
-   ## Implementation Notes
-   - Follow {framework} patterns
-   - Test cases needed: {list}
-   ```
-2. Write design guide to artifacts/design-guide.md
-3. Share fix approaches via discoveries.ndjson
-
-**Output**: Design guide file
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Designed fixes for {N} issues in {component}
-
-## Findings
-- Issue 1: {description} → Fix: {approach}
-- Issue 2: {description} → Fix: {approach}
-
-## Deliverables
-- File: artifacts/design-guide.md
-  Content: Fix approaches with rationale and validation criteria
-
-## Output JSON
-{
-  "design_guide_path": "artifacts/design-guide.md",
-  "issues_addressed": {N},
-  "summary": "Designed fixes for {N} issues"
-}
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| No issues found | Generate empty design guide, note in findings |
-| Ambiguous fix approach | Ask user for guidance via request_user_input |
-| Conflicting patterns | Document trade-offs, recommend approach |

package/.codex/skills/team-ux-improve/agents/ux-explorer.md

@@ -1,158 +0,0 @@
-# UX Explorer Agent
-
-Interactive agent for exploring codebase to identify UI component patterns and framework conventions.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `~/.codex/agents/ux-explorer.md`
-- **Responsibility**: Framework detection and component inventory
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Produce structured output following template
-- Detect UI framework (React/Vue/etc.)
-- Build component inventory with file paths
-- Cache findings for downstream tasks
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Execute implementation or fix tasks
-- Skip framework detection step
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | File I/O | Load package.json, component files |
-| `Write` | File I/O | Generate exploration cache |
-| `Glob` | File search | Find component files |
-| `Bash` | CLI execution | Run framework detection commands |
-
----
-
-## Execution
-
-### Phase 1: Framework Detection
-
-**Objective**: Detect UI framework if not specified.
-
-**Steps**:
-
-1. If framework specified in arguments, use it
-2. Otherwise, detect from package.json:
-   - Check dependencies for react, vue, angular, svelte
-   - Check file extensions (*.tsx → React, *.vue → Vue)
-3. Validate framework detection
-
-**Output**: Framework name (react/vue/angular/svelte)
-
----
-
-### Phase 2: Component Inventory
-
-**Objective**: Build inventory of UI components.
-
-**Steps**:
-
-1. Search for component files based on framework:
-   - React: `**/*.tsx`, `**/*.jsx`
-   - Vue: `**/*.vue`
-   - Angular: `**/*.component.ts`
-2. For each component:
-   - Extract component name
-   - Record file path
-   - Identify component type (button, form, modal, etc.)
-3. Build component list
-
-**Output**: Component inventory with paths
-
----
-
-### Phase 3: Pattern Analysis
-
-**Objective**: Analyze component patterns and conventions.
-
-**Steps**:
-
-1. Sample components to identify patterns:
-   - State management (useState, Vuex, etc.)
-   - Event handling patterns
-   - Styling approach (CSS modules, styled-components, etc.)
-2. Document conventions
-3. Identify common anti-patterns
-
-**Output**: Pattern analysis summary
-
----
-
-### Phase 4: Cache Generation
-
-**Objective**: Generate exploration cache for downstream tasks.
-
-**Steps**:
-
-1. Create cache structure:
-   ```json
-   {
-     "framework": "react",
-     "components": [
-       {"name": "Button", "path": "src/components/Button.tsx", "type": "button"},
-       {"name": "Form", "path": "src/components/Form.tsx", "type": "form"}
-     ],
-     "patterns": {
-       "state_management": "React hooks",
-       "event_handling": "inline handlers",
-       "styling": "CSS modules"
-     },
-     "conventions": ["PascalCase component names", "Props interface per component"]
-   }
-   ```
-2. Write cache to explorations/cache-index.json
-
-**Output**: Exploration cache file
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Detected framework: {framework}
-- Found {N} components
-
-## Findings
-- Component inventory: {N} components identified
-- Patterns: {state management}, {event handling}, {styling}
-- Conventions: {list}
-
-## Deliverables
-- File: explorations/cache-index.json
-  Content: Component inventory and pattern analysis
-
-## Output JSON
-{
-  "framework": "{framework}",
-  "components": [{component list}],
-  "component_count": {N},
-  "summary": "Explored {N} components in {framework} project"
-}
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Framework detection fails | Ask user via request_user_input |
-| No components found | Return empty inventory, note in findings |
-| Invalid project path | Report error, request valid path |

package/.codex/skills/team-ux-improve/agents/ux-tester.md

@@ -1,174 +0,0 @@
-# UX Tester Agent
-
-Interactive agent for validating fixes and running tests. Iterates up to 5 times if tests fail.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `~/.codex/agents/ux-tester.md`
-- **Responsibility**: Fix validation and testing
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Produce structured output following template
-- Run tests and validate fixes
-- Iterate up to 5 times on test failures
-- Generate test report
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Exceed 5 test iterations
-- Skip test execution step
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Bash` | CLI execution | Run tests, linters, build |
-| `Read` | File I/O | Load implementation findings, design guide |
-| `Write` | File I/O | Generate test report |
-
----
-
-## Execution
-
-### Phase 1: Test Preparation
-
-**Objective**: Identify tests to run and prepare test environment.
-
-**Steps**:
-
-1. Read implementation findings from prev_context
-2. Load design guide for validation criteria
-3. Identify test files related to component
-4. Check test framework (Jest, Vitest, etc.)
-
-**Output**: Test plan
-
----
-
-### Phase 2: Test Execution
-
-**Objective**: Run tests and validate fixes (max 5 iterations).
-
-**Steps**:
-
-1. Run component tests:
-   ```bash
-   npm test -- {component}.test
-   ```
-2. Run linter:
-   ```bash
-   npm run lint
-   ```
-3. Check build:
-   ```bash
-   npm run build
-   ```
-4. Collect results
-5. If tests fail and iteration < 5:
-   - Analyze failures
-   - Apply quick fixes if possible
-   - Re-run tests
-6. If iteration >= 5:
-   - Accept current state
-   - Document remaining issues
-
-**Output**: Test results with pass/fail status
-
----
-
-### Phase 3: Validation
-
-**Objective**: Validate fixes against design guide criteria.
-
-**Steps**:
-
-1. For each validation criterion in design guide:
-   - Check if met by implementation
-   - Check if validated by tests
-   - Document status
-2. Calculate fix success rate
-3. Identify remaining issues
-
-**Output**: Validation summary
-
----
-
-### Phase 4: Test Report Generation
-
-**Objective**: Generate test report with results.
-
-**Steps**:
-
-1. Format test report:
-   ```markdown
-   # Test Report: {Component}
-
-   ## Test Results
-   - Tests passed: {X}/{Y}
-   - Build status: {success/failed}
-   - Linter warnings: {Z}
-
-   ## Validation Status
-   - Issue 1: {fixed/partial/unfixed}
-   - Issue 2: {fixed/partial/unfixed}
-
-   ## Remaining Issues
-   - {list if any}
-
-   ## Recommendation
-   {approve/needs_work}
-   ```
-2. Write test report to artifacts/test-report.md
-3. Share test results via discoveries.ndjson
-
-**Output**: Test report file
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Testing complete for {component}: {X}/{Y} tests passed
-
-## Findings
-- Tests passed: {X}/{Y}
-- Build status: {success/failed}
-- Issues fixed: {N}
-- Remaining issues: {M}
-
-## Deliverables
-- File: artifacts/test-report.md
-  Content: Test results and validation status
-
-## Output JSON
-{
-  "test_report_path": "artifacts/test-report.md",
-  "tests_passed": {X},
-  "tests_total": {Y},
-  "issues_fixed": {N},
-  "recommendation": "approve" | "needs_work",
-  "summary": "Testing complete: {X}/{Y} tests passed"
-}
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Tests fail to run | Document as issue, continue validation |
-| Build fails | Mark as critical issue, recommend fix |
-| Test iterations exceed 5 | Accept current state, document remaining issues |
-| No test files found | Note in findings, perform manual validation |

package/.codex/skills/team-ux-improve/instructions/ux-worker-instruction.md

@@ -1,55 +0,0 @@
-## TASK ASSIGNMENT
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: {session_folder}/discoveries.ndjson (if exists, skip if not)
-2. Read project context: .workflow/project-tech.json (if exists)
-3. Read exploration cache: {session_folder}/explorations/cache-index.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Description**: {description}
-**Role**: {role}
-**Component**: {component}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Read discoveries**: Load {session_folder}/discoveries.ndjson for shared UX findings
-2. **Use context**: Apply previous tasks' findings from prev_context above
-3. **Execute**: Perform role-specific task
-   - **Scanner**: Scan component for UX issues (unresponsive buttons, missing feedback, state refresh)
-   - **Diagnoser**: Analyze root causes of identified issues
-   - **Implementer**: Apply fixes following design guide
-4. **Share discoveries**: Append findings to shared board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> {session_folder}/discoveries.ndjson
-   ```
-5. **Report result**: Return JSON via report_agent_job_result
-
-### Discovery Types to Share
-- `ux_issue`: `{component, type, description, severity}` — UX issues discovered
-- `pattern`: `{pattern, files[], description}` — UI patterns identified
-- `fix_approach`: `{component, issue, approach, rationale}` — Fix strategies
-- `test_result`: `{component, test, status, details}` — Test outcomes
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries (max 500 chars)",
-  "issues_found": "3",
-  "issues_fixed": "3",
-  "error": ""
-}

package/.codex/skills/team-ux-improve/schemas/tasks-schema.md

@@ -1,87 +0,0 @@
-# UX Improvement — CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"SCAN-001"` |
-| `title` | string | Yes | Short task title | `"Scan Button component"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Scan Button component for UX issues..."` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"EXPLORE-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"EXPLORE-001"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-| `role` | enum | Yes | Role name: `explorer`, `scanner`, `diagnoser`, `designer`, `implementer`, `tester` | `"scanner"` |
-| `component` | string | No | Component name being processed | `"Button"` |
-
-#### Computed Columns (Set by Wave Engine)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `wave` | integer | Wave number (1-based, from topological sort) | `2` |
-| `prev_context` | string | Aggregated findings from context_from tasks (per-wave CSV only) | `"[EXPLORE-001] Found 15 components..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` → `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Found 3 UX issues: unresponsive onClick..."` |
-| `issues_found` | string | Number of issues found (scanner/diagnoser) | `"3"` |
-| `issues_fixed` | string | Number of issues fixed (implementer) | `"3"` |
-| `error` | string | Error message if failed | `""` |
-
----
-
-### exec_mode Values
-
-| Value | Mechanism | Description |
-|-------|-----------|-------------|
-| `csv-wave` | `spawn_agents_on_csv` | One-shot batch execution within wave |
-| `interactive` | `spawn_agent`/`wait`/`send_input`/`close_agent` | Multi-round individual execution |
-
----
-
-### Example Data
-
-```csv
-id,title,description,deps,context_from,exec_mode,role,component,wave,status,findings,issues_found,issues_fixed,error
-EXPLORE-001,Framework Exploration,Explore React component patterns,,,"interactive",explorer,,1,completed,"Found 15 components using React hooks","","",""
-SCAN-001,Scan Button,Scan Button for UX issues,EXPLORE-001,EXPLORE-001,"csv-wave",scanner,Button,2,pending,"","","",""
-DIAG-001,Diagnose Button,Analyze root causes in Button,SCAN-001,SCAN-001,"csv-wave",diagnoser,Button,3,pending,"","","",""
-DESIGN-001,Design Button fixes,Design fix approach for Button,DIAG-001,DIAG-001,"interactive",designer,Button,4,pending,"","","",""
-```
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `ux_issue` | `component+type` | `{component, type, description, severity}` | UX issues discovered |
-| `pattern` | `pattern` | `{pattern, files[], description}` | UI patterns identified |
-| `fix_approach` | `component+issue` | `{component, issue, approach, rationale}` | Fix strategies |
-| `test_result` | `component+test` | `{component, test, status, details}` | Test outcomes |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T14:30:22Z","worker":"SCAN-001","type":"ux_issue","data":{"component":"Button","type":"unresponsive_click","description":"onClick handler not firing","severity":"high"}}
-{"ts":"2026-03-08T14:35:10Z","worker":"DIAG-001","type":"pattern","data":{"pattern":"event delegation","files":["Button.tsx"],"description":"Using event delegation pattern"}}
-```
-
----
-
-## Validation Rules
-
-| Rule | Check | Error |
-|------|-------|-------|
-| Unique IDs | No duplicate `id` values | "Duplicate task ID: {id}" |
-| Valid deps | All dep IDs exist in tasks | "Unknown dependency: {dep_id}" |
-| No self-deps | Task cannot depend on itself | "Self-dependency: {id}" |
-| No circular deps | Topological sort completes | "Circular dependency detected" |
-| exec_mode valid | Value is `csv-wave` or `interactive` | "Invalid exec_mode: {value}" |
-| Role valid | role ∈ {explorer, scanner, diagnoser, designer, implementer, tester} | "Invalid role: {role}" |