8.8 KiB
Phase 4 Workflow Architecture Summary
Version: v6 with Intelligent Object Analysis Date: December 4, 2025
Complete Structure
4-ux-design/
├── workflow.yaml # v6 workflow config
├── workflow.md # v6 initialization with step-file architecture
│
├── steps/ # Main workflow steps (5 steps)
│ ├── step-01-init.md # Welcome & determine what to design
│ ├── step-02-define-scenario.md # Create scenario structure
│ ├── step-03-design-page.md # Orchestrate 4A-4E for each page
│ ├── step-04-complete-scenario.md # Celebrate completion
│ └── step-05-next-steps.md # Guide to next actions
│
├── substeps/ # Page design substeps
│ ├── 4a-exploration.md # [Optional] Concept exploration
│ ├── 4b-sketch-analysis.md # [Optional] Systematic sketch analysis
│ │ # • Top-to-bottom, left-to-right
│ │ # • Section-by-section
│ │ # • Component reuse detection
│ │
│ ├── 4c-01-page-basics.md # Page fundamentals
│ ├── 4c-02-layout-sections.md # Define sections
│ ├── 4c-03-components-objects.md # Route to object-type files
│ │ # • For each section
│ │ # • For each object (top-left to bottom-right)
│ │ # • Uses object-router.md
│ ├── 4c-04-content-languages.md # Multilingual content
│ ├── 4c-05-interactions.md # Interaction behaviors
│ ├── 4c-06-states.md # All states (page & component)
│ ├── 4c-07-validation.md # Validation rules & errors
│ ├── 4c-08-generate-spec.md # Compile final document
│ │
│ ├── 4d-prototype.md # [Optional] HTML prototype
│ └── 4e-prd-update.md # [Required] Extract requirements
│
├── object-types/ # Object-specific instructions
│ ├── object-router.md # 🆕 INTELLIGENT ROUTER
│ │ # • Analyzes object
│ │ # • Suggests interpretation
│ │ # • User confirms
│ │ # • Routes to appropriate file
│ │
│ ├── button.md # Complete button documentation
│ ├── text-input.md # Complete input documentation
│ ├── link.md # Complete link documentation
│ ├── heading-text.md # Complete text documentation
│ ├── image.md # Complete image documentation
│ │
│ └── [16 more object types to create] # Each with precise examples
│ • textarea.md
│ • select-dropdown.md
│ • checkbox.md
│ • radio-button.md
│ • toggle-switch.md
│ • card.md
│ • modal-dialog.md
│ • table.md
│ • list.md
│ • navigation.md
│ • badge.md
│ • alert-toast.md
│ • progress.md
│ • video.md
│ • custom-component.md
│
└── templates/ # Document templates
├── page-specification.template.md # Complete page spec format
└── scenario-overview.template.md # Scenario structure format
Key Innovations
1. Step-File Architecture ✅
- Just-in-time loading - Only current step in memory
- Sequential enforcement - Steps load one at a time
- Clear progression - 5 main steps → substeps → object-types
- State tracking - Progress saved between sessions
2. Granular Specification (8 Micro-Steps) ✅
Instead of one large 4C step, broke into focused substeps:
- Page Basics - Fundamentals
- Layout Sections - Structure
- Components & Objects - Systematic identification
- Content & Languages - Multilingual
- Interactions - Behaviors
- States - All possibilities
- Validation - Rules & errors
- Generate Spec - Compile document
3. Object-Type Routing System ✅
- 21 specialized object-type files (6 created, 15 to create)
- Each file has precise examples for consistency
- Ensures uniform output across all WDS projects
4. Intelligent Analysis (Trust-the-Agent) ✅✨
Old Approach (Procedural):
What type of object is this?
1. Button
2. Input
3. Link
[Choose from list]
New Approach (Intelligent):
My interpretation:
This looks like a PRIMARY BUTTON.
Based on what I see:
- Prominent placement at bottom of form
- Bright blue background (primary color)
- White text saying "Save Profile"
I think this "Save Profile Button":
- Saves the form data to the database
- Updates the user's profile information
- Shows loading state during save
Does this match your intent? [Y/Clarify/No]
Benefits:
- ✅ Agent demonstrates intelligence
- ✅ Context-aware interpretation
- ✅ Natural conversation
- ✅ Quick confirmation when correct
- ✅ v6 "goal-based trust" philosophy
5. Systematic Sketch Analysis ✅
- Top-to-bottom, left-to-right within sections
- Component reuse detection across pages
- Section-by-section organization
- Prevents missing elements
Workflow Flow
Step 1: Init
↓
Step 2: Define Scenario
↓
Step 3: Design Page (LOOPS for each page)
↓
4A: Exploration (optional)
↓
4B: Sketch Analysis (optional)
• Top-left to bottom-right
• Section by section
• Check for reusable components
↓
4C: Specification (required) - 8 SUBSTEPS
↓
4C-01: Page Basics
4C-02: Layout Sections
4C-03: Components & Objects
↓
FOR EACH SECTION:
FOR EACH OBJECT (top-left to bottom-right):
↓
object-router.md
• Analyzes object intelligently
• Suggests interpretation
• User confirms
• Routes to object-type file
↓
button.md / text-input.md / link.md / etc.
• Precise documentation
• Complete examples
• Consistent format
↓
Returns to 4C-03
NEXT OBJECT
NEXT SECTION
↓
4C-04: Content & Languages
4C-05: Interactions
4C-06: States
4C-07: Validation
4C-08: Generate Spec
↓
4D: Prototype (optional)
↓
4E: PRD Update (required)
↓
NEXT PAGE or Step 4
↓
Step 4: Complete Scenario
↓
Step 5: Next Steps
v6 Best Practices Applied
✅ Micro-file design - Small, focused files ✅ Just-in-time loading - Load only current step ✅ Goal-based trust - Agent interprets intelligently ✅ Sequential enforcement - No skipping steps ✅ State tracking - Resume capability ✅ Example-driven - Show, don't tell ✅ Soft language - Collaborative, not commanding ✅ Object-specific instructions - Precise, consistent
Benefits for WDS Users
Consistency Across Projects:
- Same object types documented the same way
- Every WDS project produces uniform specs
- Developers know what to expect
Agent Clarity:
- Focused instructions prevent confusion
- Clear routing eliminates ambiguity
- Examples guide output format
User Experience:
- Intelligent suggestions feel natural
- Quick confirmations when agent is right
- Systematic coverage ensures nothing missed
Maintainability:
- Easy to add new object types
- Each file independently improvable
- Clear separation of concerns
Status
✅ Complete:
- Main workflow structure (5 steps)
- All substeps (4A, 4B, 4C-01 through 4C-08, 4D, 4E)
- Object-router with intelligent analysis
- 6 object-type files (button, text-input, link, heading-text, image, object-router)
- Templates
⏳ To Create:
- 15 additional object-type files
- Object-type files should follow same pattern with precise examples
This architecture ensures consistent, high-quality specifications across all WDS projects while making the agent experience intelligent and natural. 🎨✨