@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.3

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -1,127 +1,127 @@
-# Step 5: UX Pattern Analysis & Inspiration
-
-Analyze inspiring products and UX patterns to inform design decisions for the current project.
-
-## INSPIRATION ANALYSIS SEQUENCE
-
-### 1. Identify User's Favorite Apps
-
-"Let's learn from products your users already love and use regularly.
-
-**Inspiration Questions:**
-- Name 2-3 apps your target users already love and USE frequently
-- For each one, what do they do well from a UX perspective?
-- What makes the experience compelling or delightful?
-- What keeps users coming back to these apps?
-
-Think about apps in your category or even unrelated products that have great UX."
-
-### 2. Analyze UX Patterns and Principles
-
-For each inspiring app:
-
-"**For [App Name]:**
-- What core problem does it solve elegantly?
-- What makes the onboarding experience effective?
-- How do they handle navigation and information hierarchy?
-- What are their most innovative or delightful interactions?
-- What visual design choices support the user experience?
-- How do they handle errors or edge cases?"
-
-### 3. Extract Transferable Patterns
-
-"**Transferable UX Patterns:**
-Looking across these inspiring apps, I see patterns we could adapt:
-
-**Navigation Patterns:**
-- [Pattern 1] - could work for your [specific use case]
-- [Pattern 2] - might solve your [specific challenge]
-
-**Interaction Patterns:**
-- [Pattern 1] - excellent for [your user goal]
-- [Pattern 2] - addresses [your user pain point]
-
-**Visual Patterns:**
-- [Pattern 1] - supports your [emotional goal]
-- [Pattern 2] - aligns with your [platform requirements]
-
-Which of these patterns resonate most for your product?"
-
-### 4. Identify Anti-Patterns to Avoid
-
-"**UX Anti-Patterns to Avoid:**
-From analyzing both successes and failures in your space, here are patterns to avoid:
-
-- [Anti-pattern 1] - users find this confusing/frustrating
-- [Anti-pattern 2] - this creates unnecessary friction
-- [Anti-pattern 3] - doesn't align with your [emotional goals]
-
-Learning from others' mistakes is as important as learning from their successes."
-
-### 5. Define Design Inspiration Strategy
-
-"**Design Inspiration Strategy:**
-
-**What to Adopt:**
-- [Specific pattern] - because it supports [your core experience]
-- [Specific pattern] - because it aligns with [user needs]
-
-**What to Adapt:**
-- [Specific pattern] - modify for [your unique requirements]
-- [Specific pattern] - simplify for [your user skill level]
-
-**What to Avoid:**
-- [Specific anti-pattern] - conflicts with [your goals]
-- [Specific anti-pattern] - doesn't fit [your platform]
-
-This strategy will guide our design decisions while keeping {{project_name}} unique."
-
-### 6. Generate Inspiration Analysis Content
-
-When saving to document, append these sections:
-
-```markdown
-## UX Pattern Analysis & Inspiration
-
-### Inspiring Products Analysis
-
-[Analysis of inspiring products based on conversation]
-
-### Transferable UX Patterns
-
-[Transferable patterns identified based on conversation]
-
-### Anti-Patterns to Avoid
-
-[Anti-patterns to avoid based on conversation]
-
-### Design Inspiration Strategy
-
-[Strategy for using inspiration based on conversation]
-```
-
-### 7. Present Content and Menu
-
-"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 6]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Let's deepen our UX pattern analysis
-[P] Party Mode - Bring different perspectives on inspiration sources
-[AR] Adversarial Review [C] Continue - Save this to the document and move to design system choice"
-
-### 8. Handle Menu Selection
-
-**If A:** Read fully and follow `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` with the current content. Ask user to accept/reject improvements, then return to menu.
-
-**If P:** Read fully and follow `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with the current content. Ask user to accept/reject changes, then return to menu.
-
-**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings with recommendations; then redisplay this menu.
-
-**If C:**
-- Append the final content to `{planning_artifacts}/ux-design-specification.md`
-- Update frontmatter: append step to end of stepsCompleted array
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md`
+# Step 5: UX Pattern Analysis & Inspiration
+
+Analyze inspiring products and UX patterns to inform design decisions for the current project.
+
+## INSPIRATION ANALYSIS SEQUENCE
+
+### 1. Identify User's Favorite Apps
+
+"Let's learn from products your users already love and use regularly.
+
+**Inspiration Questions:**
+- Name 2-3 apps your target users already love and USE frequently
+- For each one, what do they do well from a UX perspective?
+- What makes the experience compelling or delightful?
+- What keeps users coming back to these apps?
+
+Think about apps in your category or even unrelated products that have great UX."
+
+### 2. Analyze UX Patterns and Principles
+
+For each inspiring app:
+
+"**For [App Name]:**
+- What core problem does it solve elegantly?
+- What makes the onboarding experience effective?
+- How do they handle navigation and information hierarchy?
+- What are their most innovative or delightful interactions?
+- What visual design choices support the user experience?
+- How do they handle errors or edge cases?"
+
+### 3. Extract Transferable Patterns
+
+"**Transferable UX Patterns:**
+Looking across these inspiring apps, I see patterns we could adapt:
+
+**Navigation Patterns:**
+- [Pattern 1] - could work for your [specific use case]
+- [Pattern 2] - might solve your [specific challenge]
+
+**Interaction Patterns:**
+- [Pattern 1] - excellent for [your user goal]
+- [Pattern 2] - addresses [your user pain point]
+
+**Visual Patterns:**
+- [Pattern 1] - supports your [emotional goal]
+- [Pattern 2] - aligns with your [platform requirements]
+
+Which of these patterns resonate most for your product?"
+
+### 4. Identify Anti-Patterns to Avoid
+
+"**UX Anti-Patterns to Avoid:**
+From analyzing both successes and failures in your space, here are patterns to avoid:
+
+- [Anti-pattern 1] - users find this confusing/frustrating
+- [Anti-pattern 2] - this creates unnecessary friction
+- [Anti-pattern 3] - doesn't align with your [emotional goals]
+
+Learning from others' mistakes is as important as learning from their successes."
+
+### 5. Define Design Inspiration Strategy
+
+"**Design Inspiration Strategy:**
+
+**What to Adopt:**
+- [Specific pattern] - because it supports [your core experience]
+- [Specific pattern] - because it aligns with [user needs]
+
+**What to Adapt:**
+- [Specific pattern] - modify for [your unique requirements]
+- [Specific pattern] - simplify for [your user skill level]
+
+**What to Avoid:**
+- [Specific anti-pattern] - conflicts with [your goals]
+- [Specific anti-pattern] - doesn't fit [your platform]
+
+This strategy will guide our design decisions while keeping {{project_name}} unique."
+
+### 6. Generate Inspiration Analysis Content
+
+When saving to document, append these sections:
+
+```markdown
+## UX Pattern Analysis & Inspiration
+
+### Inspiring Products Analysis
+
+[Analysis of inspiring products based on conversation]
+
+### Transferable UX Patterns
+
+[Transferable patterns identified based on conversation]
+
+### Anti-Patterns to Avoid
+
+[Anti-patterns to avoid based on conversation]
+
+### Design Inspiration Strategy
+
+[Strategy for using inspiration based on conversation]
+```
+
+### 7. Present Content and Menu
+
+"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
+
+**Here's what I'll add to the document:**
+
+[Show the complete markdown content from step 6]
+
+**What would you like to do?**
+[A] Advanced Elicitation - Let's deepen our UX pattern analysis
+[P] Party Mode - Bring different perspectives on inspiration sources
+[AR] Adversarial Review [C] Continue - Save this to the document and move to design system choice"
+
+### 8. Handle Menu Selection
+
+**If A:** Read fully and follow `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` with the current content. Ask user to accept/reject improvements, then return to menu.
+
+**If P:** Read fully and follow `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with the current content. Ask user to accept/reject changes, then return to menu.
+
+**If AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings with recommendations; then redisplay this menu.
+
+**If C:**
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: append step to end of stepsCompleted array
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md`

package/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md

@@ -1,167 +1,167 @@
-# Step 6: Design System Choice
-
-Choose appropriate design system approach based on project requirements and constraints.
-
-## DESIGN SYSTEM CHOICE SEQUENCE
-
-### 1. Present Design System Options
-
-"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI — they provide proven components and patterns, ensuring consistency and speeding development.
-
-**Design System Approaches:**
-
-**1. Custom Design System**
-
-- Complete visual uniqueness
-- Full control over every component
-- Higher initial investment
-- Perfect for established brands with unique needs
-
-**2. Established System (Material Design, Ant Design, etc.)**
-
-- Fast development with proven patterns
-- Great defaults and accessibility built-in
-- Less visual differentiation
-- Ideal for startups or internal tools
-
-**3. Themeable System (MUI, Chakra UI, Tailwind UI)**
-
-- Customizable with strong foundation
-- Brand flexibility with proven components
-- Moderate learning curve
-- Good balance of speed and uniqueness
-
-Which direction feels right for your project?"
-
-### 2. Analyze Project Requirements
-
-"**Let's consider your specific needs:**
-
-**Based on our previous conversations:**
-
-- Platform: [platform from step 3]
-- Timeline: [inferred from user conversation]
-- Team Size: [inferred from user conversation]
-- Brand Requirements: [inferred from user conversation]
-- Technical Constraints: [inferred from user conversation]
-
-**Decision Factors:**
-
-- Need for speed vs. need for uniqueness
-- Brand guidelines or existing visual identity
-- Team's design expertise
-- Long-term maintenance considerations
-- Integration requirements with existing systems"
-
-### 3. Explore Specific Design System Options
-
-"**Recommended Options Based on Your Needs:**
-
-**For [Your Platform Type]:**
-
-- [Option 1] - [Key benefit] - [Best for scenario]
-- [Option 2] - [Key benefit] - [Best for scenario]
-- [Option 3] - [Key benefit] - [Best for scenario]
-
-**Considerations:**
-
-- Component library size and quality
-- Documentation and community support
-- Customization capabilities
-- Accessibility compliance
-- Performance characteristics
-- Learning curve for your team"
-
-### 4. Facilitate Decision Process
-
-"**Decision Framework:**
-
-1. What's most important: Speed, uniqueness, or balance?
-2. How much design expertise does your team have?
-3. Are there existing brand guidelines to follow?
-4. What's your timeline and budget?
-5. Long-term maintenance needs?
-
-Let's evaluate options based on your answers to these questions."
-
-### 5. Finalize Design System Choice
-
-"Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
-
-**Rationale:**
-
-- [Reason 1 based on project needs]
-- [Reason 2 based on constraints]
-- [Reason 3 based on team considerations]
-
-Does this design system choice feel right to you?"
-
-### 6. Generate Design System Content
-
-When saving to document, append these sections:
-
-```markdown
-## Design System Foundation
-
-### Design System Choice
-
-[Design system choice based on conversation]
-
-### Rationale for Selection
-
-[Rationale for design system selection based on conversation]
-
-### Implementation Approach
-
-[Implementation approach based on chosen system]
-
-### Customization Strategy
-
-[Customization strategy based on project needs]
-
-### Design Token Mapping
-
-The execution agent MUST explicitly search for the project's design token definitions before generating any component code. Required search targets:
-
-- `tailwind.config.ts` or `tailwind.config.js` — for Tailwind token colors, spacing, fonts
-- `globals.css` or `variables.css` — for CSS custom property tokens
-- `theme.ts` or `themes/index.ts` — for JS-defined theme objects
-
-After searching the token files above, populate this table completely. A row with "TBD" is a compliance failure — every role MUST be resolved before generating any components:
-
-| Role        | Token Name                   | Value            |
-| ----------- | ---------------------------- | ---------------- |
-| Primary     | [resolved from token search] | [hex or CSS var] |
-| Secondary   | [resolved from token search] | [hex or CSS var] |
-| Background  | [resolved from token search] | [hex or CSS var] |
-| Foreground  | [resolved from token search] | [hex or CSS var] |
-| Muted       | [resolved from token search] | [hex or CSS var] |
-| Accent      | [resolved from token search] | [hex or CSS var] |
-| Destructive | [resolved from token search] | [hex or CSS var] |
-| Border      | [resolved from token search] | [hex or CSS var] |
-
-> **Completeness Rule:** NEVER generate component code with hardcoded hex values or arbitrary CSS. All style values MUST reference the mapped token names. If a token file cannot be found, explicitly report it to the user and ask how to proceed.
-```
-
-### 7. Auto-Initialize Design System via Script
-
-Immediately attempt to auto-initialize the design system. Do NOT ask the user for permission — run the script silently:
-
-```bash
-python skills/ui-ux-pro-custom/scripts/search.py "<product_type> <industry> <keywords>" --design-system -p "Project Name"
-# If python fails, try python3
-```
-
-- **On success:** Announce `"✅ Design system initialized from ui-ux-pro-custom intelligence."` and incorporate the generated tokens into the Design Token Mapping table.
-- **On failure:** Announce `"⚠️ Script unavailable — continuing with manual token definition."` and proceed with the manually defined tokens from conversation. Do NOT halt.
-
-### 8. Auto-Save and Advance
-
-Without presenting a menu or waiting for user input:
-
-- Append the final content to `{planning_artifacts}/ux-design-specification.md`
-- Update frontmatter: append step to end of stepsCompleted array
-- Announce: `"✅ Design System Foundation saved. Advancing to next step..."`
-- Immediately load and execute: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md`
-
-> **HALT ONLY IF:** The design token search found zero token files AND the user has provided no token information. In that case, ask once: "I couldn't find any design token files in this project. Can you point me to your token definitions, or shall I use Tailwind defaults?"
+# Step 6: Design System Choice
+
+Choose appropriate design system approach based on project requirements and constraints.
+
+## DESIGN SYSTEM CHOICE SEQUENCE
+
+### 1. Present Design System Options
+
+"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI — they provide proven components and patterns, ensuring consistency and speeding development.
+
+**Design System Approaches:**
+
+**1. Custom Design System**
+
+- Complete visual uniqueness
+- Full control over every component
+- Higher initial investment
+- Perfect for established brands with unique needs
+
+**2. Established System (Material Design, Ant Design, etc.)**
+
+- Fast development with proven patterns
+- Great defaults and accessibility built-in
+- Less visual differentiation
+- Ideal for startups or internal tools
+
+**3. Themeable System (MUI, Chakra UI, Tailwind UI)**
+
+- Customizable with strong foundation
+- Brand flexibility with proven components
+- Moderate learning curve
+- Good balance of speed and uniqueness
+
+Which direction feels right for your project?"
+
+### 2. Analyze Project Requirements
+
+"**Let's consider your specific needs:**
+
+**Based on our previous conversations:**
+
+- Platform: [platform from step 3]
+- Timeline: [inferred from user conversation]
+- Team Size: [inferred from user conversation]
+- Brand Requirements: [inferred from user conversation]
+- Technical Constraints: [inferred from user conversation]
+
+**Decision Factors:**
+
+- Need for speed vs. need for uniqueness
+- Brand guidelines or existing visual identity
+- Team's design expertise
+- Long-term maintenance considerations
+- Integration requirements with existing systems"
+
+### 3. Explore Specific Design System Options
+
+"**Recommended Options Based on Your Needs:**
+
+**For [Your Platform Type]:**
+
+- [Option 1] - [Key benefit] - [Best for scenario]
+- [Option 2] - [Key benefit] - [Best for scenario]
+- [Option 3] - [Key benefit] - [Best for scenario]
+
+**Considerations:**
+
+- Component library size and quality
+- Documentation and community support
+- Customization capabilities
+- Accessibility compliance
+- Performance characteristics
+- Learning curve for your team"
+
+### 4. Facilitate Decision Process
+
+"**Decision Framework:**
+
+1. What's most important: Speed, uniqueness, or balance?
+2. How much design expertise does your team have?
+3. Are there existing brand guidelines to follow?
+4. What's your timeline and budget?
+5. Long-term maintenance needs?
+
+Let's evaluate options based on your answers to these questions."
+
+### 5. Finalize Design System Choice
+
+"Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
+
+**Rationale:**
+
+- [Reason 1 based on project needs]
+- [Reason 2 based on constraints]
+- [Reason 3 based on team considerations]
+
+Does this design system choice feel right to you?"
+
+### 6. Generate Design System Content
+
+When saving to document, append these sections:
+
+```markdown
+## Design System Foundation
+
+### Design System Choice
+
+[Design system choice based on conversation]
+
+### Rationale for Selection
+
+[Rationale for design system selection based on conversation]
+
+### Implementation Approach
+
+[Implementation approach based on chosen system]
+
+### Customization Strategy
+
+[Customization strategy based on project needs]
+
+### Design Token Mapping
+
+The execution agent MUST explicitly search for the project's design token definitions before generating any component code. Required search targets:
+
+- `tailwind.config.ts` or `tailwind.config.js` — for Tailwind token colors, spacing, fonts
+- `globals.css` or `variables.css` — for CSS custom property tokens
+- `theme.ts` or `themes/index.ts` — for JS-defined theme objects
+
+After searching the token files above, populate this table completely. A row with "TBD" is a compliance failure — every role MUST be resolved before generating any components:
+
+| Role        | Token Name                   | Value            |
+| ----------- | ---------------------------- | ---------------- |
+| Primary     | [resolved from token search] | [hex or CSS var] |
+| Secondary   | [resolved from token search] | [hex or CSS var] |
+| Background  | [resolved from token search] | [hex or CSS var] |
+| Foreground  | [resolved from token search] | [hex or CSS var] |
+| Muted       | [resolved from token search] | [hex or CSS var] |
+| Accent      | [resolved from token search] | [hex or CSS var] |
+| Destructive | [resolved from token search] | [hex or CSS var] |
+| Border      | [resolved from token search] | [hex or CSS var] |
+
+> **Completeness Rule:** NEVER generate component code with hardcoded hex values or arbitrary CSS. All style values MUST reference the mapped token names. If a token file cannot be found, explicitly report it to the user and ask how to proceed.
+```
+
+### 7. Auto-Initialize Design System via Script
+
+Immediately attempt to auto-initialize the design system. Do NOT ask the user for permission — run the script silently:
+
+```bash
+python skills/ui-ux-pro-custom/scripts/search.py "<product_type> <industry> <keywords>" --design-system -p "Project Name"
+# If python fails, try python3
+```
+
+- **On success:** Announce `"✅ Design system initialized from ui-ux-pro-custom intelligence."` and incorporate the generated tokens into the Design Token Mapping table.
+- **On failure:** Announce `"⚠️ Script unavailable — continuing with manual token definition."` and proceed with the manually defined tokens from conversation. Do NOT halt.
+
+### 8. Auto-Save and Advance
+
+Without presenting a menu or waiting for user input:
+
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
+- Update frontmatter: append step to end of stepsCompleted array
+- Announce: `"✅ Design System Foundation saved. Advancing to next step..."`
+- Immediately load and execute: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md`
+
+> **HALT ONLY IF:** The design token search found zero token files AND the user has provided no token information. In that case, ask once: "I couldn't find any design token files in this project. Can you point me to your token definitions, or shall I use Tailwind defaults?"