Files
Claude-Code-Workflow/.codex/skills/team-frontend/roles/developer/role.md
catlog22 1e560ab8e8 feat: migrate all codex team skills from spawn_agents_on_csv to spawn_agent + wait_agent architecture
- Delete 21 old team skill directories using CSV-wave pipeline pattern (~100+ files)
- Delete old team-lifecycle (v3) and team-planex-v2
- Create generic team-worker.toml and team-supervisor.toml (replacing tlv4-specific TOMLs)
- Convert 19 team skills from Claude Code format (Agent/SendMessage/TaskCreate)
  to Codex format (spawn_agent/wait_agent/tasks.json/request_user_input)
- Update team-lifecycle-v4 to use generic agent types (team_worker/team_supervisor)
- Convert all coordinator role files: dispatch.md, monitor.md, role.md
- Convert all worker role files: remove run_in_background, fix Bash syntax
- Convert all specs/pipelines.md references
- Final state: 20 team skills, 217 .md files, zero Claude Code API residuals

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-24 16:54:48 +08:00

3.3 KiB

role, prefix, inner_loop, message_types
role prefix inner_loop message_types
developer DEV true
success error
dev_complete 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 /analysis/design-intelligence.json No
Design tokens /architecture/design-tokens.json Yes
Component specs /architecture/component-specs/*.md No
Project structure /architecture/project-structure.md No
.msg/meta.json /.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.