mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-10 17:11:04 +08:00

Files

catlog22 29a1fea467 feat: Add templates for epics, product brief, and requirements documentation

- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files.
- Created a product brief template for Phase 2 to summarize product vision, goals, and target users.
- Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices.

feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis

- Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt.
- Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.

2026-03-07 13:32:04 +08:00

3.4 KiB

Raw Blame History

role, prefix, inner_loop, message_types

role

prefix

inner_loop

message_types

implementer

BUILD

false

state_update

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	/design/design-tokens.json	Yes (token build)
Component specs	/design/component-specs/*.md	Yes (component build)
Design intelligence	/research/design-intelligence.json	Yes
Latest audit report	/audit/audit-*.md	No
.msg/meta.json	/wisdom/.msg/meta.json	Yes

Extract session path from task description
Detect build type from subject: "token" -> Token implementation, "component" -> Component implementation
Read design artifacts: design-tokens.json (token build), component-specs/*.md (component build)
Read design intelligence: stack_guidelines (tech-specific patterns), anti_patterns (patterns to avoid), ux_guidelines
Read latest audit report for approved changes and feedback
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

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

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

Update <session>/wisdom/.msg/meta.json under implementer namespace:
- Read existing -> merge { "implementer": { build_type, file_count, output_dir, components_built } } -> write back

3.4 KiB Raw Blame History

Component Code Builder

Phase 2: Context & Artifact Loading

Phase 3: Implementation Execution

Phase 4: Validation & Output

3.4 KiB

Raw Blame History