claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-frontend/roles/coordinator/role.md

@@ -0,0 +1,157 @@
+# Coordinator Role
+
+Orchestrate team-frontend: analyze -> dispatch -> spawn -> monitor -> report.
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
+
+## Boundaries
+
+### MUST
+- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (blockedBy)
+- Stop after spawning workers -- wait for callbacks
+- Handle GC loops (developer <-> qa) with max 2 iterations
+- Execute completion action in Phase 5
+
+### MUST NOT
+- Implement domain logic (analyzing, designing, coding, reviewing) -- workers handle this
+- Spawn workers without creating tasks first
+- Skip architecture review gate when configured (feature/system modes)
+- Force-advance pipeline past failed QA review
+- Modify source code directly -- delegate to developer worker
+
+## Command Execution Protocol
+
+When coordinator needs to execute a command:
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker callback | Message contains [analyst], [architect], [developer], [qa] | -> handleCallback (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active/paused session in .workflow/.team/FE-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/complete: load @commands/monitor.md, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/FE-*/.msg/meta.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (audit tasks.json, reset in_progress->pending, rebuild team, kick first ready task)
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse task description from $ARGUMENTS
+2. Delegate to @commands/analyze.md -> produces task-analysis.json
+3. Ask for missing parameters via request_user_input:
+
+   **Scope Selection**:
+
+   | Option | Pipeline |
+   |--------|----------|
+   | Single page | page (4-beat linear) |
+   | Multi-component feature | feature (5-beat with arch review) |
+   | Full frontend system | system (7-beat dual-track) |
+
+   **Industry Selection**:
+
+   | Option | Strictness |
+   |--------|------------|
+   | SaaS/Tech | standard |
+   | E-commerce/Retail | standard |
+   | Healthcare/Finance | strict |
+   | Other | standard |
+
+   **Design Constraints** (multi-select): Existing design system, WCAG AA, Responsive, Dark mode
+
+4. Record requirements: mode, scope, industry, constraints
+5. CRITICAL: Always proceed to Phase 2, never skip team workflow
+
+## Phase 2: Session & Team Setup
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash({ command: "pwd" })`
+   - `skill_root` = `<project_root>/.claude/skills/team-frontend`
+3. Generate session ID: `FE-<slug>-<YYYY-MM-DD>`
+4. Create session folder structure (replaces TeamCreate):
+   ```
+   mkdir -p .workflow/.team/<session-id>/{.msg,wisdom,analysis,architecture,qa,build}
+   ```
+5. Read specs/pipelines.md -> select pipeline based on scope
+6. Register roles in session state
+7. Initialize meta.json with pipeline metadata:
+```typescript
+mcp__ccw-tools__team_msg({
+  operation: "log", session_id: "<id>", from: "coordinator",
+  type: "state_update", summary: "Session initialized",
+  data: {
+    pipeline_mode: "<page|feature|system>",
+    pipeline_stages: ["analyst", "architect", "developer", "qa"],
+    roles: ["coordinator", "analyst", "architect", "developer", "qa"],
+    team_name: "frontend",
+    industry: "<industry>",
+    constraints: []
+  }
+})
+```
+9. Write session.json
+
+## Phase 3: Task Chain Creation
+
+Delegate to @commands/dispatch.md:
+1. Read specs/pipelines.md for selected pipeline task registry
+2. Build tasks array as JSON entries in `<session>/tasks.json`; set deps via `blockedBy` field in each entry
+3. Update session.json
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + blockedBy resolved)
+2. Spawn team-worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Load session state -> count completed tasks, calculate duration
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Design Intelligence | <session>/analysis/design-intelligence.json |
+| Requirements | <session>/analysis/requirements.md |
+| Design Tokens | <session>/architecture/design-tokens.json |
+| Component Specs | <session>/architecture/component-specs/ |
+| Project Structure | <session>/architecture/project-structure.md |
+| QA Audits | <session>/qa/audit-*.md |
+
+3. Output pipeline summary: task count, duration, QA scores
+4. Execute completion action per session.completion_action:
+   - interactive -> request_user_input (Archive/Keep/Export)
+   - auto_archive -> Archive & Clean (status=completed, remove/archive session folder)
+   - auto_keep -> Keep Active (status=paused)
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| Task too vague | request_user_input for clarification |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| Dependency cycle | Detect in analysis, halt |
+| QA score < 6 over 2 GC rounds | Escalate to user |
+| ui-ux-pro-max unavailable | Degrade to LLM general design knowledge |

package/.codex/skills/team-frontend/roles/developer/role.md

@@ -0,0 +1,93 @@
+---
+role: developer
+prefix: DEV
+inner_loop: true
+message_types:
+  success: dev_complete
+  error: error
+---
+
+# Frontend Developer
+
+Consume architecture artifacts (design tokens, component specs, project structure) to implement frontend code. Reference design-intelligence.json for implementation checklist, tech stack guidelines, and anti-pattern constraints.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Scope | Extracted from task description (tokens/components/full) | No (default: full) |
+| Design intelligence | <session>/analysis/design-intelligence.json | No |
+| Design tokens | <session>/architecture/design-tokens.json | Yes |
+| Component specs | <session>/architecture/component-specs/*.md | No |
+| Project structure | <session>/architecture/project-structure.md | No |
+| .msg/meta.json | <session>/.msg/meta.json | No |
+
+1. Extract session path and scope from task description
+2. Load design tokens (required -- if missing, report to coordinator)
+3. Load design intelligence for anti-patterns and guidelines
+4. Load component specs and project structure
+5. Detect tech stack from design intelligence `detected_stack`
+6. Load .msg/meta.json for shared state
+
+## Phase 3: Code Implementation
+
+**Scope selection**:
+
+| Scope | Output |
+|-------|--------|
+| `tokens` | CSS custom properties from design tokens |
+| `components` | Component code from specs |
+| `full` | Both token CSS and components |
+
+**Step 1: Generate Design Token CSS** (scope: tokens or full):
+
+Convert design-tokens.json to `src/styles/tokens.css`:
+
+| JSON Category | CSS Variable Prefix |
+|---------------|---------------------|
+| color | `--color-` |
+| typography.font-family | `--font-` |
+| typography.font-size | `--text-` |
+| spacing | `--space-` |
+| border-radius | `--radius-` |
+| shadow | `--shadow-` |
+| transition | `--duration-` |
+
+Add `@media (prefers-color-scheme: dark)` override for color tokens.
+
+**Step 2: Implement Components** (scope: components or full):
+
+Implementation strategy by complexity:
+
+| Condition | Strategy |
+|-----------|----------|
+| <= 2 components | Direct inline Edit/Write |
+| 3-5 components | Single batch implementation |
+| > 5 components | Group by module, implement per batch |
+
+**Coding standards** (mandatory):
+- Use design token CSS variables -- never hardcode colors/spacing
+- All interactive elements: `cursor: pointer`
+- Transitions: 150-300ms via `var(--duration-normal)`
+- Text contrast: minimum 4.5:1 ratio
+- Include `focus-visible` styles for keyboard navigation
+- Support `prefers-reduced-motion`
+- Responsive: mobile-first with md/lg breakpoints
+- No emoji as functional icons
+
+## Phase 4: Self-Review
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Hardcoded colors | Scan for hex codes outside tokens.css | None found |
+| cursor-pointer | Check buttons/links | All have cursor-pointer |
+| Focus styles | Check interactive elements | All have focus styles |
+| Responsive | Check for breakpoints | Breakpoints present |
+| File existence | Verify all planned files | All present |
+| Import resolution | Check no broken imports | All imports resolve |
+
+Auto-fix where possible: add missing cursor-pointer, basic focus styles.
+
+Update .msg/meta.json: merge `component_inventory` key with implemented file list.

package/.codex/skills/team-frontend/roles/qa/role.md

@@ -0,0 +1,79 @@
+---
+role: qa
+prefix: QA
+inner_loop: false
+message_types:
+  success: qa_passed
+  error: error
+---
+
+# QA Engineer
+
+Execute 5-dimension quality audit integrating ux-guidelines Do/Don't rules, pre-delivery checklist, and industry anti-pattern library. Perform CSS-level precise review on architecture artifacts and implementation code.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Review type | Extracted from task description | No (default: code-review) |
+| Design intelligence | <session>/analysis/design-intelligence.json | No |
+| Design tokens | <session>/architecture/design-tokens.json | No |
+| .msg/meta.json | <session>/.msg/meta.json | No |
+
+1. Extract session path and review type from task description
+2. Load design intelligence (for anti-patterns, must-have rules)
+3. Load design tokens (for compliance checks)
+4. Load .msg/meta.json (for industry context, strictness level)
+5. Collect files to review based on review type:
+
+| Type | Files to Review |
+|------|-----------------|
+| architecture-review | `<session>/architecture/**/*` |
+| token-review | `<session>/architecture/**/*` |
+| code-review | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
+| final | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
+
+## Phase 3: 5-Dimension Audit
+
+| Dimension | Weight | Focus |
+|-----------|--------|-------|
+| Code Quality | 0.20 | Structure, naming, maintainability |
+| Accessibility | 0.25 | WCAG compliance, keyboard nav, screen reader |
+| Design Compliance | 0.20 | Anti-pattern check, design token usage |
+| UX Best Practices | 0.20 | Interaction patterns, responsive, animations |
+| Pre-Delivery | 0.15 | Final checklist (code-review/final types only) |
+
+**Dimension 1 -- Code Quality**: File length (>300 LOC), console.log, empty catch, unused imports.
+
+**Dimension 2 -- Accessibility**: Image alt text, input labels, button text, heading hierarchy, focus styles, ARIA roles. Strict mode (medical/financial): prefers-reduced-motion required.
+
+**Dimension 3 -- Design Compliance**: Hardcoded colors (must use `var(--color-*)`), hardcoded spacing, industry anti-patterns from design intelligence.
+
+**Dimension 4 -- UX Best Practices**: cursor-pointer on clickable, transition 150-300ms, responsive design, loading states, error states.
+
+**Dimension 5 -- Pre-Delivery** (final/code-review only): No emoji icons, cursor-pointer, transitions, focus states, reduced-motion, responsive, no hardcoded colors, dark mode support.
+
+**Score calculation**: `score = sum(dimension_score * weight)`
+
+**Verdict**:
+
+| Condition | Verdict | Message Type |
+|-----------|---------|-------------|
+| score >= 8 AND critical == 0 | PASSED | `qa_passed` |
+| score >= 6 AND critical == 0 | PASSED_WITH_WARNINGS | `qa_result` |
+| score < 6 OR critical > 0 | FIX_REQUIRED | `fix_required` |
+
+## Phase 4: Self-Review
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| All dimensions scored | Check 5 dimension scores | All present |
+| Audit report written | File check | audit-NNN.md exists |
+| Verdict determined | Score calculated | Verdict assigned |
+| Issues categorized | Severity labels | All issues have severity |
+
+Write audit report to `<session>/qa/audit-<NNN>.md` with: summary, dimension scores, issues by severity, passed dimensions.
+
+Update .msg/meta.json: append to `qa_history` array.

package/.codex/skills/team-frontend/specs/pipelines.md

@@ -0,0 +1,76 @@
+# Frontend Pipeline Definitions
+
+## Pipeline Modes
+
+### Page Mode (4 beats, linear)
+
+```
+ANALYZE-001 --> ARCH-001 --> DEV-001 --> QA-001
+[analyst]       [architect]  [developer]  [qa]
+```
+
+### Feature Mode (5 beats, with architecture review gate)
+
+```
+ANALYZE-001 --> ARCH-001 --> QA-001 --> DEV-001 --> QA-002
+[analyst]       [architect]  [qa:arch]   [developer]  [qa:code]
+```
+
+### System Mode (7 beats, dual-track parallel)
+
+```
+ANALYZE-001 --> ARCH-001 --> QA-001 --> ARCH-002 ─┐
+[analyst]       [architect]  [qa:arch]  [architect] |
+                                        DEV-001   ──┘ --> QA-002 --> DEV-002 --> QA-003
+                                        [developer:tokens]  [qa]    [developer]  [qa:final]
+```
+
+### Generator-Critic Loop (developer <-> qa)
+
+```
+developer (Generator) -> QA artifact -> qa (Critic)
+                      <- QA feedback <-
+                         (max 2 rounds)
+
+Convergence: qa.score >= 8 && qa.critical_count === 0
+```
+
+## Task Metadata Registry
+
+| Task ID | Role | Pipeline | Dependencies | Description |
+|---------|------|----------|-------------|-------------|
+| ANALYZE-001 | analyst | all | (none) | Requirement analysis + design intelligence |
+| ARCH-001 | architect | all | ANALYZE-001 | Design token system + component architecture |
+| ARCH-002 | architect | system | QA-001 | Component specs refinement |
+| DEV-001 | developer | all | ARCH-001 or QA-001 | Frontend implementation |
+| DEV-002 | developer | system | QA-002 | Component implementation |
+| DEV-fix-N | developer | all | QA-N (GC loop trigger) | Fix issues from QA |
+| QA-001 | qa | all | ARCH-001 or DEV-001 | Architecture or code review |
+| QA-002 | qa | feature/system | DEV-001 | Code review |
+| QA-003 | qa | system | DEV-002 | Final quality check |
+| QA-recheck-N | qa | all | DEV-fix-N | Re-audit after developer fixes |
+
+## Pipeline Selection Logic
+
+| Score | Pipeline |
+|-------|----------|
+| 1-2 | page |
+| 3-4 | feature |
+| 5+ | system |
+
+Default: feature.
+
+## ui-ux-pro-max Integration
+
+Analyst role invokes ui-ux-pro-max via Skill to obtain industry design intelligence:
+
+| Action | Invocation |
+|--------|------------|
+| Full design system | `Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")` |
+| Domain search | `Skill(skill="ui-ux-pro-max", args="<query> --domain <domain>")` |
+| Tech stack guidance | `Skill(skill="ui-ux-pro-max", args="<query> --stack <stack>")` |
+
+**Supported Domains**: product, style, typography, color, landing, chart, ux, web
+**Supported Stacks**: html-tailwind, react, nextjs, vue, svelte, shadcn, swiftui, react-native, flutter
+
+**Fallback**: If ui-ux-pro-max skill not installed, degrade to LLM general design knowledge.

package/.codex/skills/team-frontend/specs/team-config.json

@@ -0,0 +1,84 @@
+{
+  "team_name": "frontend",
+  "skill_name": "team-frontend",
+  "team_display_name": "Frontend Development",
+  "description": "全栈前端开发团队，内置 ui-ux-pro-max 设计智能。具备需求分析、设计系统生成、前端实现、质量保证的完整能力。",
+  "pipeline_type": "adaptive",
+  "roles": [
+    {
+      "name": "coordinator",
+      "task_prefix": null,
+      "responsibility_type": "Orchestration",
+      "description": "需求澄清、行业识别、流水线编排、进度监控、GC循环控制",
+      "message_types": ["task_unblocked", "sync_checkpoint", "fix_required", "error", "shutdown"]
+    },
+    {
+      "name": "analyst",
+      "task_prefix": "ANALYZE",
+      "responsibility_type": "Read-only analysis",
+      "description": "需求分析、调用 ui-ux-pro-max 获取设计智能、行业推理规则匹配",
+      "message_types": ["analyze_ready", "analyze_progress", "error"]
+    },
+    {
+      "name": "architect",
+      "task_prefix": "ARCH",
+      "responsibility_type": "Code generation",
+      "description": "消费设计智能、定义设计令牌系统、组件架构、技术选型",
+      "message_types": ["arch_ready", "arch_revision", "arch_progress", "error"]
+    },
+    {
+      "name": "developer",
+      "task_prefix": "DEV",
+      "responsibility_type": "Code generation",
+      "description": "消费架构产出、实现前端组件/页面代码",
+      "message_types": ["dev_complete", "dev_progress", "error"]
+    },
+    {
+      "name": "qa",
+      "task_prefix": "QA",
+      "responsibility_type": "Read-only analysis",
+      "description": "5维度代码审查：代码质量、可访问性、设计合规、UX最佳实践、Pre-Delivery验证",
+      "message_types": ["qa_passed", "qa_result", "fix_required", "error"]
+    }
+  ],
+  "pipelines": {
+    "page": {
+      "description": "单页面开发：分析→架构→开发→质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "DEV-001", "QA-001"],
+      "collaboration_patterns": ["CP-1", "CP-2"],
+      "complexity": "low"
+    },
+    "feature": {
+      "description": "多组件特性：分析→架构→质检→开发→质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "QA-001", "DEV-001", "QA-002"],
+      "collaboration_patterns": ["CP-1", "CP-2", "CP-8"],
+      "complexity": "medium"
+    },
+    "system": {
+      "description": "完整前端系统：分析→架构→[开发令牌 ∥ 架构组件]→质检→开发组件→最终质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "QA-001", "ARCH-002||DEV-001", "QA-002", "DEV-002", "QA-003"],
+      "sync_points": ["QA-001", "QA-002"],
+      "collaboration_patterns": ["CP-1", "CP-2", "CP-8", "CP-9"],
+      "complexity": "high"
+    }
+  },
+  "uipro_config": {
+    "search_paths": [
+      "G:/github_lib/ui-ux-pro-max-skill/src/ui-ux-pro-max",
+      "../ui-ux-pro-max-skill/src/ui-ux-pro-max",
+      "./ui-ux-pro-max"
+    ],
+    "fallback": "LLM general design knowledge",
+    "data_domains": ["product", "style", "typography", "color", "landing", "chart", "ux", "web"],
+    "supported_stacks": ["html-tailwind", "react", "nextjs", "vue", "svelte", "shadcn"]
+  },
+  "shared_memory_schema": {
+    "design_intelligence": {},
+    "design_token_registry": {},
+    "component_inventory": [],
+    "style_decisions": [],
+    "qa_history": [],
+    "industry_context": {}
+  },
+  "generated_at": "2026-02-17T00:00:00+08:00"
+}