🎨 UI Design Workflow System - Add /workflow:design:auto semi-autonomous orchestrator with interactive checkpoints - Add /workflow:design:style-extract with triple vision analysis (Claude + Gemini + Codex) - Add /workflow:design:style-consolidate for token validation and style guide generation - Add /workflow:design:ui-generate for token-driven HTML/CSS prototype generation - Add /workflow:design:design-update for design system integration 👁️ Triple Vision Analysis - Claude Code: Quick initial visual analysis using native Read tool - Gemini Vision: Deep semantic understanding of design intent - Codex Vision: Structured pattern recognition with -i parameter - Consensus synthesis with weighted combination strategy ⏸️ Interactive Checkpoints - Checkpoint 1: User selects style variants after extraction - Checkpoint 2: User confirms prototypes before design update - Pause-and-continue pattern for critical design decisions 🎯 Zero Agent Overhead - Remove Task(conceptual-planning-agent) wrappers from design commands - Direct bash execution for gemini-wrapper and codex commands - Improved performance while preserving all functionality 🎨 Design Features - OKLCH color format for perceptually uniform design tokens - W3C Design Tokens compatibility - WCAG 2.1 AA compliance validation - Style override support with --style-overrides parameter - Batch task generation with --batch-plan flag 📚 Documentation Updates - Update README.md with Phase 2 (UI Design Refinement) section - Update README_CN.md with Chinese design workflow documentation - Add comprehensive CHANGELOG entry for v3.5.0 - Add 5 new /workflow:design:* commands to command reference 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
14 KiB
name, description, usage, argument-hint, examples, allowed-tools
| name | description | usage | argument-hint | examples | allowed-tools | ||
|---|---|---|---|---|---|---|---|
| auto | Orchestrate UI design refinement workflow with interactive checkpoints for user selection | /workflow:design:auto --session <session_id> --images "<glob>" --pages "<list>" [--variants <count>] [--batch-plan] | --session WFS-session-id --images "refs/*.png" --pages "dashboard,auth" [--variants 2] [--batch-plan] |
|
SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Glob(*) |
UI Design Auto Workflow Command
Overview
Semi-autonomous UI design workflow with interactive checkpoints: style extraction → user selection → consolidation → UI generation → user confirmation → design update → optional batch planning.
Coordinator Role
Checkpoint-based orchestrator: Execute Phase 1 automatically, pause for user style selection, execute Phase 3, pause for user prototype confirmation, complete with optional batch task generation.
Execution Model - Checkpoint Workflow
This workflow runs semi-autonomously with user checkpoints:
- User triggers:
/workflow:design:auto --session WFS-xxx --images "refs/*.png" --pages "dashboard,auth" [--batch-plan] - Phase 1 executes (style-extract) → Reports style cards → ⏸️ PAUSE FOR USER SELECTION
- User selects variants → Runs
style-consolidate --variants "..."→ Auto-continues - Phase 3 executes (ui-generate) → Reports prototypes → ⏸️ PAUSE FOR USER CONFIRMATION
- User confirms prototypes → Runs
design-update --selected-prototypes "..."→ Auto-continues - Phase 5 executes (batch-plan, optional) → Reports task files
Checkpoint Mechanism:
- TodoWrite tracks current phase with "awaiting_user_confirmation" status
- System reports output location and exact command for next step
- User runs provided command to continue workflow
- Workflow resumes automatically after user input
Core Rules
- Start Immediately: First action is TodoWrite initialization, second action is Phase 1 command execution
- No Preliminary Analysis: Do not read files or validate before Phase 1 (commands handle their own validation)
- Parse Every Output: Extract required data from each command's output for next phase
- Pause at Checkpoints: After Phase 1 and Phase 3, pause and prompt user with exact command to continue
- User-Driven Continuation: Workflow resumes when user runs style-consolidate or design-update commands
- Track Progress: Update TodoWrite after every phase completion and checkpoint
Parameter Requirements
Required Parameters:
--session <session_id>: Active workflow session ID--images "<glob_pattern>": Reference image paths for style extraction--pages "<page_list>": Comma-separated list of pages to generate
Optional Parameters:
--variants <count>: Number of UI variants per page (default: 1)--batch-plan: Auto-generate implementation tasks for selected prototypes after design-update
5-Phase Execution
Phase 1: Style Extraction
Command: SlashCommand(command="/workflow:design:style-extract --session {session_id} --images \"{image_glob}\"")
Parse Output:
- Verify:
.design/style-extraction/style-cards.jsoncreated - Extract:
style_cards_countfrom output message - List available style variant IDs
Validation:
- Style cards successfully generated
- At least one style variant available
TodoWrite: Mark phase 1 completed, mark checkpoint "awaiting_user_confirmation"
⏸️ CHECKPOINT 1: Pause for User Style Selection
Phase 1 Complete: Style Extraction
Style cards generated: {count}
Available variants: {variant_ids}
Location: .workflow/WFS-{session}/.design/style-extraction/
⏸️ USER SELECTION REQUIRED
Review style cards and select your preferred variants.
Then run:
/workflow:design:style-consolidate --session WFS-{session} --variants "{variant_ids}"
Example: /workflow:design:style-consolidate --session WFS-{session} --variants "variant-1,variant-3"
Phase 2: Style Consolidation (User-Triggered)
User Command: /workflow:design:style-consolidate --session {session_id} --variants "{selected_variants}"
After user runs command:
- Workflow automatically continues to Phase 3
- Parse output: token_count, validation_status
TodoWrite: Mark phase 2 completed, phase 3 in_progress
Output:
Phase 2 Complete: Style Consolidation
Design tokens: {count}
Validation: {pass|warnings}
Location: .workflow/WFS-{session}/.design/style-consolidation/
Continuing to Phase 3: UI Generation...
Phase 3: UI Generation (Auto-Triggered after Phase 2)
Command Construction:
variants_flag = --variants present ? "--variants {variants_count}" : ""
command = "/workflow:design:ui-generate --session {session_id} --pages \"{page_list}\" {variants_flag}"
Command: SlashCommand(command="{constructed_command}")
Parse Output:
- Verify:
.design/prototypes/*.htmlfiles created - Extract:
prototype_count,page_list,generated_fileslist
Validation:
- All requested pages generated
- HTML and CSS files present for each variant
TodoWrite: Mark phase 3 completed, mark checkpoint "awaiting_user_confirmation"
⏸️ CHECKPOINT 2: Pause for User Prototype Confirmation
Phase 3 Complete: UI Generation
Prototypes generated: {count} ({page_list})
Generated files: {file_list}
Location: .workflow/WFS-{session}/.design/prototypes/
⏸️ USER CONFIRMATION REQUIRED
Review the generated prototypes and select your preferred variants.
Then run:
/workflow:design:design-update --session WFS-{session} --selected-prototypes "{prototype_ids}"
Example: /workflow:design:design-update --session WFS-{session} --selected-prototypes "dashboard-variant-1,auth-variant-2"
Or to use all generated prototypes:
/workflow:design:design-update --session WFS-{session}
Phase 4: Design System Integration (User-Triggered)
User Command: /workflow:design:design-update --session {session_id} [--selected-prototypes "{selected_prototypes}"]
After user runs command:
- Workflow updates brainstorming artifacts
- If --batch-plan flag present, automatically continues to Phase 5
Parse Output:
- Verify:
synthesis-specification.mdupdated - Verify:
ui-designer/style-guide.mdcreated/updated
TodoWrite: Mark phase 4 completed
Output (if --batch-plan NOT present):
UI Design Refinement Complete for session: WFS-{session}
Design System Summary:
- Tokens: {token_count} (OKLCH-based)
- Prototypes: {prototype_count} ({page_list})
- Validation: {pass|warnings}
Updated Artifacts:
✓ synthesis-specification.md (UI/UX Guidelines section)
✓ ui-designer/style-guide.md (comprehensive style guide)
✓ Design tokens ready for task generation
Location: .workflow/WFS-{session}/.design/
Next Steps:
1. Review prototypes: .workflow/WFS-{session}/.design/prototypes/
2. Continue to planning: /workflow:plan [--agent] "<task description>"
(The plan phase will automatically discover and utilize the design system)
Output (if --batch-plan present):
Phase 4 Complete: Design System Integration
Updated Artifacts:
✓ synthesis-specification.md
✓ ui-designer/style-guide.md
Continuing to Phase 5: Batch Task Generation...
Phase 5: Batch Task Generation (Optional, Auto-Triggered if --batch-plan)
Condition: Only executes if --batch-plan flag present
Execution:
FOR each page IN selected_prototypes_pages:
SlashCommand(command="/workflow:plan --agent \"Implement {page} page based on design system\"")
# Parse output task file location
task_files.add(output_location)
TodoWrite: Mark phase 5 completed
Return to User:
Phase 5 Complete: Batch Task Generation
Tasks generated for: {page_count} pages
Generated task files:
{task_file_list}
Design workflow complete for session: WFS-{session}
Next: /workflow:execute
TodoWrite Pattern
// Initialize (before Phase 1)
TodoWrite({todos: [
{"content": "Execute style extraction from reference images", "status": "in_progress", "activeForm": "Executing style extraction"},
{"content": "Execute style consolidation and token validation", "status": "pending", "activeForm": "Executing style consolidation"},
{"content": "Execute UI prototype generation", "status": "pending", "activeForm": "Executing UI generation"},
{"content": "Execute design system integration to brainstorming", "status": "pending", "activeForm": "Executing design system integration"}
]})
// After Phase 1
TodoWrite({todos: [
{"content": "Execute style extraction from reference images", "status": "completed", "activeForm": "Executing style extraction"},
{"content": "Execute style consolidation and token validation", "status": "in_progress", "activeForm": "Executing style consolidation"},
{"content": "Execute UI prototype generation", "status": "pending", "activeForm": "Executing UI generation"},
{"content": "Execute design system integration to brainstorming", "status": "pending", "activeForm": "Executing design system integration"}
]})
// Continue pattern for Phase 2, 3, 4...
Parameter Processing
Session Validation
# Verify active session
CHECK: .workflow/.active-* marker files
VERIFY: session_id parameter matches active session
IF mismatch:
ERROR: "Session {session_id} is not active. Active session: {active_session_id}"
Image Glob Expansion
# Expand glob pattern
expanded_paths = bash(ls {image_glob})
IF no files found:
ERROR: "No images found matching pattern: {image_glob}"
VALIDATE: All files are image formats (.png, .jpg, .jpeg, .webp)
Page List Parsing
# Parse comma-separated page list
pages = split(page_list, ",")
TRIM: whitespace from each page name
VALIDATE: page_list not empty
Data Flow
User Input
├── session_id
├── image_glob → expanded_image_paths
├── page_list → parsed_pages[]
├── --interactive → interactive_mode (bool)
└── --variants → variants_count (int)
↓
Phase 1: style-extract
Input: session_id, expanded_image_paths
Output: style-cards.json
↓
Phase 2: style-consolidate
Input: session_id, interactive_mode | auto-select
Output: design-tokens.json, style-guide.md, tailwind.config.js
↓
Phase 3: ui-generate
Input: session_id, parsed_pages[], variants_count
Output: {page}-variant-{n}.html/css for each page
↓
Phase 4: design-update
Input: session_id
Output: Updated synthesis-specification.md, ui-designer/style-guide.md
↓
Return summary to user
Error Handling
Phase Execution Failures:
- Keep phase
in_progress: Do not proceed to next phase - Report error to user: Include specific failure message from command
- Provide recovery instructions: Suggest manual command execution with corrected parameters
Common Errors:
- Session not found: Verify session exists and is active
- No images found: Check image glob pattern and file paths
- Style extraction failed: Retry with different images or manual style description
- Consolidation validation errors: Review validation-report.json and address token issues
- UI generation failed: Check synthesis-specification.md for requirements clarity
- Integration conflicts: Review synthesis-specification.md edit conflicts
Workflow Position
In Complete Development Flow:
/workflow:brainstorm:auto-parallel "{topic}"
↓ Generates synthesis-specification.md (WHAT)
↓
/workflow:design:auto --session WFS-xxx --images "refs/*.png" --pages "dashboard,auth"
↓ Refines visual design (WHAT → Visual Spec)
↓
/workflow:plan [--agent] "{task description}"
↓ Generates task breakdown (HOW)
↓
/workflow:execute
↓ Implements tasks with design system
Key Benefits:
- Visual Validation: Users confirm design before implementation
- Token Enforcement: Implementation strictly follows design system
- Accessibility: WCAG AA validated at design phase
- Consistency: Single source of truth for visual design
Coordinator Checklist
✅ Initialize TodoWrite before any command execution ✅ Validate session parameter before Phase 1 ✅ Expand image glob to concrete paths ✅ Parse page list to array ✅ Execute Phase 1 immediately (no preliminary analysis) ✅ Parse style card count from Phase 1 output ✅ Construct Phase 2 command based on --interactive flag ✅ Parse token count and validation status from Phase 2 ✅ Construct Phase 3 command with variants parameter ✅ Parse prototype count from Phase 3 output ✅ Execute Phase 4 design system integration ✅ Verify all artifacts updated successfully ✅ Update TodoWrite after each phase ✅ After each phase, automatically continue to next phase based on TodoWrite status
Integration Notes
Seamless Workflow Transition:
- Design phase is optional but recommended for UI-heavy projects
- Can be skipped entirely if visual design is not critical
- Brainstorming → Plan flow still works without design phase
- Design artifacts automatically discovered by task-generate if present
Use Cases:
- Use design workflow: User-facing applications, design systems, brand-critical UIs
- Skip design workflow: Backend APIs, CLI tools, prototypes, MVPs
Artifact Discovery:
task-generateautomatically detects.design/directory- If present, adds design system to task context.artifacts
- UI tasks automatically include
load_design_tokensin flow_control
This design ensures backward compatibility while enabling powerful visual design workflows when needed.