claude-code-workflow 7.2.10 → 7.2.12

package/.claude/skills/team-tech-debt/role-specs/validator.md

@@ -1,83 +0,0 @@
----
-prefix: TDVAL
-inner_loop: false
-message_types:
-  success: validation_complete
-  error: error
-  fix: regression_found
----
-
-# Tech Debt Validator
-
-Cleanup result validator. Run test suite, type checks, lint checks, and quality analysis to verify debt cleanup introduced no regressions. Compare before/after debt scores, produce validation-report.json.
-
-## Phase 2: Load Context
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Fix log | <session>/fixes/fix-log.json | No |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for: worktree.path, debt_inventory, fix_results, debt_score_before
-3. Determine command prefix: `cd "<worktree-path>" && ` if worktree exists
-4. Read fix-log.json for modified files list
-5. Detect available validation tools in worktree:
-
-| Signal | Tool | Method |
-|--------|------|--------|
-| package.json + npm | npm test | Test suite |
-| pytest available | python -m pytest | Test suite |
-| npx tsc available | npx tsc --noEmit | Type check |
-| npx eslint available | npx eslint | Lint check |
-
-## Phase 3: Run Validation Checks
-
-Execute 4-layer validation (all commands in worktree):
-
-**1. Test Suite**:
-- Run `npm test` or `python -m pytest` in worktree
-- PASS if no FAIL/error/failed keywords; FAIL with regression count otherwise
-- Skip with "no-tests" if no test runner available
-
-**2. Type Check**:
-- Run `npx tsc --noEmit` in worktree
-- Count `error TS` occurrences for error count
-
-**3. Lint Check**:
-- Run `npx eslint --no-error-on-unmatched-pattern <modified-files>` in worktree
-- Count error occurrences
-
-**4. Quality Analysis** (optional, when > 5 modified files):
-- Use gemini CLI to compare code quality before/after
-- Assess complexity, duplication, naming quality improvements
-
-**Debt Score Calculation**:
-- debt_score_after = debt items NOT in modified files (remaining unfixed items)
-- improvement_percentage = ((before - after) / before) * 100
-
-**Auto-fix attempt** (when total_regressions <= 3):
-- Use CLI tool to fix regressions in worktree:
-  ```
-  Bash({
-    command: `cd "${worktreePath}" && ccw cli -p "PURPOSE: Fix regressions found in validation
-  TASK: ${regressionDetails}
-  MODE: write
-  CONTEXT: @${modifiedFiles.join(' @')}
-  EXPECTED: Fixed regressions
-  CONSTRAINTS: Fix only regressions | Preserve debt cleanup changes | No suppressions" --tool gemini --mode write`,
-    run_in_background: false
-  })
-  ```
-- Re-run validation checks after fix attempt
-  })
-  ```
-- Re-run checks after fix attempt
-
-## Phase 4: Compare & Report
-
-1. Calculate: total_regressions = test_regressions + type_errors + lint_errors; passed = (total_regressions === 0)
-2. Write `<session>/validation/validation-report.json` with: validation_date, passed, regressions, checks (per-check status), debt_score_before, debt_score_after, improvement_percentage
-3. Update .msg/meta.json with `validation_results` and `debt_score_after`
-4. Select message type: `validation_complete` if passed, `regression_found` if not

package/.claude/skills/team-testing/role-specs/analyst.md

@@ -1,94 +0,0 @@
----
-prefix: TESTANA
-inner_loop: false
-message_types:
-  success: analysis_ready
-  error: error
----
-
-# Test Quality Analyst
-
-Analyze defect patterns, identify coverage gaps, assess GC loop effectiveness, and generate a quality report with actionable recommendations.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Execution results | <session>/results/run-*.json | Yes |
-| Test strategy | <session>/strategy/test-strategy.md | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for execution context (executor, generator namespaces)
-3. Read all execution results:
-
-```
-Glob("<session>/results/run-*.json")
-Read("<session>/results/run-001.json")
-```
-
-4. Read test strategy:
-
-```
-Read("<session>/strategy/test-strategy.md")
-```
-
-5. Read test files for pattern analysis:
-
-```
-Glob("<session>/tests/**/*")
-```
-
-## Phase 3: Quality Analysis
-
-**Analysis dimensions**:
-
-1. **Coverage Analysis** -- Aggregate coverage by layer:
-
-| Layer | Coverage | Target | Status |
-|-------|----------|--------|--------|
-| L1 | X% | Y% | Met/Below |
-
-2. **Defect Pattern Analysis** -- Frequency and severity:
-
-| Pattern | Frequency | Severity |
-|---------|-----------|----------|
-| pattern | count | HIGH (>=3) / MEDIUM (>=2) / LOW (<2) |
-
-3. **GC Loop Effectiveness**:
-
-| Metric | Value | Assessment |
-|--------|-------|------------|
-| Rounds | N | - |
-| Coverage Improvement | +/-X% | HIGH (>10%) / MEDIUM (>5%) / LOW (<=5%) |
-
-4. **Coverage Gaps** -- per module/feature:
-   - Area, Current %, Gap %, Reason, Recommendation
-
-5. **Quality Score**:
-
-| Dimension | Score (1-10) | Weight |
-|-----------|-------------|--------|
-| Coverage Achievement | score | 30% |
-| Test Effectiveness | score | 25% |
-| Defect Detection | score | 25% |
-| GC Loop Efficiency | score | 20% |
-
-Write report to `<session>/analysis/quality-report.md`
-
-## Phase 4: Trend Analysis & State Update
-
-**Historical comparison** (if multiple sessions exist):
-
-```
-Glob(".workflow/.team/TST-*/.msg/meta.json")
-```
-
-- Track coverage trends over time
-- Identify defect pattern evolution
-- Compare GC loop effectiveness across sessions
-
-Update `<session>/wisdom/.msg/meta.json` under `analyst` namespace:
-- Merge `{ "analyst": { quality_score, coverage_gaps, top_defect_patterns, gc_effectiveness, recommendations } }`

package/.claude/skills/team-testing/role-specs/executor.md

@@ -1,97 +0,0 @@
----
-prefix: TESTRUN
-inner_loop: true
-message_types:
-  success: tests_passed
-  failure: tests_failed
-  coverage: coverage_report
-  error: error
----
-
-# Test Executor
-
-Execute tests, collect coverage, attempt auto-fix for failures. Acts as the Critic in the Generator-Critic loop. Reports pass rate and coverage for coordinator GC decisions.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Test directory | Task description (Input: <path>) | Yes |
-| Coverage target | Task description (default: 80%) | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and test directory from task description
-2. Extract coverage target (default: 80%)
-3. Read .msg/meta.json for framework info (from strategist namespace)
-4. Determine test framework:
-
-| Framework | Run Command |
-|-----------|-------------|
-| Jest | `npx jest --coverage --json --outputFile=<session>/results/jest-output.json` |
-| Pytest | `python -m pytest --cov --cov-report=json:<session>/results/coverage.json -v` |
-| Vitest | `npx vitest run --coverage --reporter=json` |
-
-5. Find test files to execute:
-
-```
-Glob("<session>/<test-dir>/**/*")
-```
-
-## Phase 3: Test Execution + Fix Cycle
-
-**Iterative test-fix cycle** (max 3 iterations):
-
-| Step | Action |
-|------|--------|
-| 1 | Run test command |
-| 2 | Parse results: pass rate + coverage |
-| 3 | pass_rate >= 0.95 AND coverage >= target -> success, exit |
-| 4 | Extract failing test details |
-| 5 | Delegate fix to CLI tool (gemini write mode) |
-| 6 | Increment iteration; >= 3 -> exit with failures |
-
-```
-Bash("<test-command> 2>&1 || true")
-```
-
-**Auto-fix delegation** (on failure):
-
-```
-Bash({
-  command: `ccw cli -p "PURPOSE: Fix test failures to achieve pass rate >= 0.95; success = all tests pass
-TASK: • Analyze test failure output • Identify root causes • Fix test code only (not source) • Preserve test intent
-MODE: write
-CONTEXT: @<session>/<test-dir>/**/* | Memory: Test framework: <framework>, iteration <N>/3
-EXPECTED: Fixed test files with: corrected assertions, proper async handling, fixed imports, maintained coverage
-CONSTRAINTS: Only modify test files | Preserve test structure | No source code changes
-Test failures:
-<test-output>" --tool gemini --mode write --cd <session>`,
-  run_in_background: false
-})
-```
-
-**Save results**: `<session>/results/run-<N>.json`
-
-## Phase 4: Defect Pattern Extraction & State Update
-
-**Extract defect patterns from failures**:
-
-| Pattern Type | Detection Keywords |
-|--------------|-------------------|
-| Null reference | "null", "undefined", "Cannot read property" |
-| Async timing | "timeout", "async", "await", "promise" |
-| Import errors | "Cannot find module", "import" |
-| Type mismatches | "type", "expected", "received" |
-
-**Record effective test patterns** (if pass_rate > 0.8):
-
-| Pattern | Detection |
-|---------|-----------|
-| Happy path | "should succeed", "valid input" |
-| Edge cases | "edge", "boundary", "limit" |
-| Error handling | "should fail", "error", "throw" |
-
-Update `<session>/wisdom/.msg/meta.json` under `executor` namespace:
-- Merge `{ "executor": { pass_rate, coverage, defect_patterns, effective_patterns, coverage_history_entry } }`

package/.claude/skills/team-testing/role-specs/generator.md

@@ -1,96 +0,0 @@
----
-prefix: TESTGEN
-inner_loop: true
-message_types:
-  success: tests_generated
-  revision: tests_revised
-  error: error
----
-
-# Test Generator
-
-Generate test code by layer (L1 unit / L2 integration / L3 E2E). Acts as the Generator in the Generator-Critic loop. Supports revision mode for GC loop iterations.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Test strategy | <session>/strategy/test-strategy.md | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and layer from task description
-2. Read test strategy:
-
-```
-Read("<session>/strategy/test-strategy.md")
-```
-
-3. Read source files to test (from strategy priority_files, limit 20)
-4. Read .msg/meta.json for framework and scope context
-
-5. Detect revision mode:
-
-| Condition | Mode |
-|-----------|------|
-| Task subject contains "fix" or "revised" | Revision -- load previous failures |
-| Otherwise | Fresh generation |
-
-For revision mode:
-- Read latest result file for failure details
-- Read effective test patterns from .msg/meta.json
-
-6. Read wisdom files if available
-
-## Phase 3: Test Generation
-
-**Strategy selection by complexity**:
-
-| File Count | Strategy |
-|------------|----------|
-| <= 3 files | Direct: inline Write/Edit |
-| 3-5 files | Single code-developer agent |
-| > 5 files | Batch: group by module, one agent per batch |
-
-**Direct generation** (per source file):
-1. Generate test path: `<session>/tests/<layer>/<test-file>`
-2. Generate test code: happy path, edge cases, error handling
-3. Write test file
-
-**CLI delegation** (medium/high complexity):
-
-```
-Bash({
-  command: `ccw cli -p "PURPOSE: Generate <layer> tests using <framework> to achieve coverage target; success = all priority files covered with quality tests
-TASK: • Analyze source files • Generate test cases (happy path, edge cases, errors) • Write test files with proper structure • Ensure import resolution
-MODE: write
-CONTEXT: @<source-files> @<session>/strategy/test-strategy.md | Memory: Framework: <framework>, Layer: <layer>, Round: <round>
-<if-revision: Previous failures: <failure-details>
-Effective patterns: <patterns-from-meta>>
-EXPECTED: Test files in <session>/tests/<layer>/ with: proper test structure, comprehensive coverage, correct imports, framework conventions
-CONSTRAINTS: Follow test strategy priorities | Use framework best practices | <layer>-appropriate assertions
-Source files to test:
-<file-list-with-content>" --tool gemini --mode write --cd <session>`,
-  run_in_background: false
-})
-```
-
-**Output verification**:
-
-```
-Glob("<session>/tests/<layer>/**/*")
-```
-
-## Phase 4: Self-Validation & State Update
-
-**Validation checks**:
-
-| Check | Method | Action on Fail |
-|-------|--------|----------------|
-| Syntax | `tsc --noEmit` or equivalent | Auto-fix imports/types |
-| File count | Count generated files | Report issue |
-| Import resolution | Check broken imports | Fix import paths |
-
-Update `<session>/wisdom/.msg/meta.json` under `generator` namespace:
-- Merge `{ "generator": { test_files, layer, round, is_revision } }`

package/.claude/skills/team-testing/role-specs/strategist.md

@@ -1,82 +0,0 @@
----
-prefix: STRATEGY
-inner_loop: false
-message_types:
-  success: strategy_ready
-  error: error
----
-
-# Test Strategist
-
-Analyze git diff, determine test layers, define coverage targets, and formulate test strategy with prioritized execution order.
-
-## Phase 2: Context & Environment Detection
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and scope from task description
-2. Get git diff for change analysis:
-
-```
-Bash("git diff HEAD~1 --name-only 2>/dev/null || git diff --cached --name-only")
-Bash("git diff HEAD~1 -- <changed-files> 2>/dev/null || git diff --cached -- <changed-files>")
-```
-
-3. Detect test framework from project files:
-
-| Signal File | Framework | Test Pattern |
-|-------------|-----------|-------------|
-| jest.config.js/ts | Jest | `**/*.test.{ts,tsx,js}` |
-| vitest.config.ts/js | Vitest | `**/*.test.{ts,tsx}` |
-| pytest.ini / pyproject.toml | Pytest | `**/test_*.py` |
-| No detection | Default | Jest patterns |
-
-4. Scan existing test patterns:
-
-```
-Glob("**/*.test.*")
-Glob("**/*.spec.*")
-```
-
-5. Read .msg/meta.json if exists for session context
-
-## Phase 3: Strategy Formulation
-
-**Change analysis dimensions**:
-
-| Change Type | Analysis | Priority |
-|-------------|----------|----------|
-| New files | Need new tests | High |
-| Modified functions | Need updated tests | Medium |
-| Deleted files | Need test cleanup | Low |
-| Config changes | May need integration tests | Variable |
-
-**Strategy output structure**:
-
-1. **Change Analysis Table**: File, Change Type, Impact, Priority
-2. **Test Layer Recommendations**:
-   - L1 Unit: Scope, Coverage Target, Priority Files, Patterns
-   - L2 Integration: Scope, Coverage Target, Integration Points
-   - L3 E2E: Scope, Coverage Target, User Scenarios
-3. **Risk Assessment**: Risk, Probability, Impact, Mitigation
-4. **Test Execution Order**: Prioritized sequence
-
-Write strategy to `<session>/strategy/test-strategy.md`
-
-**Self-validation**:
-
-| Check | Criteria | Fallback |
-|-------|----------|----------|
-| Has L1 scope | L1 scope not empty | Default to all changed files |
-| Has coverage targets | L1 target > 0 | Use defaults (80/60/40) |
-| Has priority files | List not empty | Use all changed files |
-
-## Phase 4: Wisdom & State Update
-
-1. Write discoveries to `<session>/wisdom/conventions.md` (detected framework, patterns)
-2. Update `<session>/wisdom/.msg/meta.json` under `strategist` namespace:
-   - Read existing -> merge `{ "strategist": { framework, layers, coverage_targets, priority_files, risks } }` -> write back

package/.claude/skills/team-uidesign/role-specs/designer.md

@@ -1,72 +0,0 @@
----
-prefix: DESIGN
-inner_loop: false
-message_types:
-  success: design_ready
-  revision: design_revision
-  progress: design_progress
-  error: error
----
-
-# Design Token & Component Spec Author
-
-Define visual language through design tokens (W3C Design Tokens Format) and component specifications. Consume design intelligence from researcher. Act as Generator in the designer<->reviewer Generator-Critic loop.
-
-## Phase 2: Context & Artifact Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Research artifacts | <session>/research/*.json | Yes |
-| Design intelligence | <session>/research/design-intelligence.json | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
-| Audit feedback | <session>/audit/audit-*.md | Only for GC fix tasks |
-
-1. Extract session path from task description
-2. Read research findings: design-system-analysis.json, component-inventory.json, accessibility-audit.json
-3. Read design intelligence: recommended colors/typography/style, anti-patterns, ux_guidelines
-4. Detect task type from subject: "token" -> Token design, "component" -> Component spec, "fix"/"revision" -> GC fix
-5. If GC fix task: read latest audit feedback from audit files
-
-## Phase 3: Design Execution
-
-**Token System Design (DESIGN-001)**:
-- Define complete token system following W3C Design Tokens Format
-- Categories: Color (primary, secondary, background, surface, text, semantic), Typography (font-family, font-size, font-weight, line-height), Spacing (xs-2xl), Shadow (sm/md/lg), Border (radius, width), Breakpoint (mobile/tablet/desktop/wide)
-- All color tokens must have light/dark variants using `$value: { light: ..., dark: ... }`
-- Integrate design intelligence: recommended.colors -> color tokens, recommended.typography -> font stacks
-- Document anti-patterns from design intelligence for implementer reference
-- Output: `<session>/design/design-tokens.json`
-
-**Component Specification (DESIGN-002)**:
-- Define component specs consuming design tokens
-- Each spec contains: Overview (type: atom/molecule/organism, purpose), Design Tokens Consumed (token -> usage -> value reference), States (default/hover/focus/active/disabled), Responsive Behavior (changes per breakpoint), Accessibility (role, ARIA, keyboard, focus indicator, contrast), Variants, Anti-Patterns, Implementation Hints
-- All interactive states required: default, hover (background/opacity change), focus (outline 2px solid, offset 2px), active (pressed), disabled (opacity 0.5, cursor not-allowed)
-- Output: `<session>/design/component-specs/{component-name}.md`
-
-**GC Fix Mode (DESIGN-fix-N)**:
-- Parse audit feedback for specific issues
-- Re-read affected design artifacts; apply fixes (token value adjustments, missing states, accessibility gaps, naming fixes)
-- Re-write affected files; signal `design_revision` instead of `design_ready`
-
-## Phase 4: Self-Validation & Output
-
-1. Token integrity checks:
-
-| Check | Pass Criteria |
-|-------|---------------|
-| tokens_valid | All $value fields non-empty |
-| theme_complete | Light/dark values for all color tokens |
-| values_parseable | Valid CSS-parseable values |
-| no_duplicates | No duplicate token definitions |
-
-2. Component spec checks:
-
-| Check | Pass Criteria |
-|-------|---------------|
-| states_complete | All 5 states (default/hover/focus/active/disabled) defined |
-| a11y_specified | Role, ARIA, keyboard behavior defined |
-| responsive_defined | At least mobile/desktop breakpoints |
-| token_refs_valid | All `{token.path}` references resolve to defined tokens |
-
-3. Update `<session>/wisdom/.msg/meta.json` under `designer` namespace:
-   - Read existing -> merge `{ "designer": { task_type, token_categories, component_count, style_decisions } }` -> write back

package/.claude/skills/team-uidesign/role-specs/implementer.md

@@ -1,74 +0,0 @@
----
-prefix: BUILD
-inner_loop: false
-message_types:
-  success: build_complete
-  progress: build_progress
-  error: error
----
-
-# Component Code Builder
-
-Translate design tokens and component specifications into production code. Generate CSS custom properties, TypeScript/JavaScript components, and accessibility implementations. Consume design intelligence stack guidelines for tech-specific patterns.
-
-## Phase 2: Context & Artifact Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Design tokens | <session>/design/design-tokens.json | Yes (token build) |
-| Component specs | <session>/design/component-specs/*.md | Yes (component build) |
-| Design intelligence | <session>/research/design-intelligence.json | Yes |
-| Latest audit report | <session>/audit/audit-*.md | No |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
-
-1. Extract session path from task description
-2. Detect build type from subject: "token" -> Token implementation, "component" -> Component implementation
-3. Read design artifacts: design-tokens.json (token build), component-specs/*.md (component build)
-4. Read design intelligence: stack_guidelines (tech-specific patterns), anti_patterns (patterns to avoid), ux_guidelines
-5. Read latest audit report for approved changes and feedback
-6. Detect project tech stack from package.json
-
-## Phase 3: Implementation Execution
-
-**Token Implementation (BUILD-001)**:
-- Convert design tokens to production code
-- Output files in `<session>/build/token-files/`:
-  - `tokens.css`: CSS custom properties with `:root` (light) and `[data-theme="dark"]` selectors, plus `@media (prefers-color-scheme: dark)` fallback
-  - `tokens.ts`: TypeScript constants and types for programmatic access with autocomplete support
-  - `README.md`: Token usage guide
-- All color tokens must have both light and dark values
-- Semantic token names must match design token definitions
-
-**Component Implementation (BUILD-002)**:
-- Implement component code from design specifications
-- Per-component output in `<session>/build/component-files/`:
-  - `{ComponentName}.tsx`: React/Vue/Svelte component (match detected stack)
-  - `{ComponentName}.css`: Styles consuming tokens via `var(--token-name)` only
-  - `{ComponentName}.test.tsx`: Basic render + state tests
-  - `index.ts`: Re-export
-- Requirements: no hardcoded colors/spacing (use design tokens), implement all 5 states, add ARIA attributes per spec, support responsive breakpoints, follow project component patterns
-- Accessibility: keyboard navigation, screen reader support, visible focus indicators, WCAG AA contrast
-- Check implementation against design intelligence anti_patterns
-
-## Phase 4: Validation & Output
-
-1. Token build validation:
-
-| Check | Pass Criteria |
-|-------|---------------|
-| File existence | tokens.css and tokens.ts exist |
-| Token coverage | All defined tokens present in CSS |
-| Theme support | Light/dark variants exist |
-
-2. Component build validation:
-
-| Check | Pass Criteria |
-|-------|---------------|
-| File existence | At least 3 files per component (component, style, index) |
-| No hardcoded values | No `#xxx` or `rgb()` in component CSS (only in tokens.css) |
-| Focus styles | `:focus` or `:focus-visible` defined |
-| Responsive | `@media` queries present |
-| Anti-pattern clean | No violations of design intelligence anti_patterns |
-
-3. Update `<session>/wisdom/.msg/meta.json` under `implementer` namespace:
-   - Read existing -> merge `{ "implementer": { build_type, file_count, output_dir, components_built } }` -> write back

package/.claude/skills/team-uidesign/role-specs/researcher.md

@@ -1,84 +0,0 @@
----
-prefix: RESEARCH
-inner_loop: false
-message_types:
-  success: research_ready
-  progress: research_progress
-  error: error
----
-
-# Design System Researcher
-
-Analyze existing design system, build component inventory, assess accessibility baseline, and retrieve industry-specific design intelligence via ui-ux-pro-max. Produce foundation data for downstream designer, reviewer, and implementer roles.
-
-## Phase 2: Context & Environment Detection
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and target scope from task description
-2. Detect project type and tech stack from package.json or equivalent:
-
-| Package | Detected Stack |
-|---------|---------------|
-| next | nextjs |
-| react | react |
-| vue | vue |
-| svelte | svelte |
-| @shadcn/ui | shadcn |
-| (default) | html-tailwind |
-
-3. Use CLI tools (e.g., `ccw cli -p "..." --tool gemini --mode analysis`) or direct tools (Glob, Grep, mcp__ace-tool__search_context) to scan for existing design tokens, component files, styling patterns
-4. Read industry context from session config (industry, strictness, must-have features)
-
-## Phase 3: Research Execution
-
-Execute 4 analysis streams:
-
-**Stream 1 -- Design System Analysis**:
-- Search for existing design tokens (CSS variables, theme configs, token files)
-- Identify styling patterns (CSS-in-JS, CSS modules, utility classes, SCSS)
-- Map color palette, typography scale, spacing system
-- Find component library usage (MUI, Ant Design, shadcn, custom)
-- Output: `<session>/research/design-system-analysis.json`
-
-**Stream 2 -- Component Inventory**:
-- Find all UI component files; identify props/API surface
-- Identify states supported (hover, focus, disabled, etc.)
-- Check accessibility attributes (ARIA labels, roles)
-- Map inter-component dependencies and usage counts
-- Output: `<session>/research/component-inventory.json`
-
-**Stream 3 -- Accessibility Baseline**:
-- Check ARIA attribute usage patterns, keyboard navigation support
-- Assess color contrast ratios (if design tokens found)
-- Find focus management and semantic HTML patterns
-- Output: `<session>/research/accessibility-audit.json`
-
-**Stream 4 -- Design Intelligence (ui-ux-pro-max)**:
-- Call `Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")` for design system recommendations
-- Call `Skill(skill="ui-ux-pro-max", args="accessibility animation responsive --domain ux")` for UX guidelines
-- Call `Skill(skill="ui-ux-pro-max", args="<keywords> --stack <detected-stack>")` for stack guidelines
-- Degradation: when unavailable, use LLM general knowledge, mark `_source: "llm-general-knowledge"`
-- Output: `<session>/research/design-intelligence.json`
-
-Compile research summary metrics: design_system_exists, styling_approach, total_components, accessibility_level, design_intelligence_source, anti_patterns_count.
-
-## Phase 4: Validation & Output
-
-1. Verify all 4 output files exist and contain valid JSON with required fields:
-
-| File | Required Fields |
-|------|----------------|
-| design-system-analysis.json | existing_tokens, styling_approach |
-| component-inventory.json | components array |
-| accessibility-audit.json | wcag_level |
-| design-intelligence.json | _source, design_system |
-
-2. If any file missing or invalid, re-run corresponding stream
-
-3. Update `<session>/wisdom/.msg/meta.json` under `researcher` namespace:
-   - Read existing -> merge `{ "researcher": { detected_stack, component_count, wcag_level, di_source, scope } }` -> write back