whiteport-design-studio 0.2.2 → 0.3.0

package/docs/{learn-wds/module-05-trigger-mapping/tutorial-05.md → learn/module-06-trigger-mapping/tutorial-06.md}

@@ -1,4 +1,4 @@
-# Tutorial 05: Create Your Trigger Map
+# Tutorial 06: Create Your Trigger Map
 
 **Hands-on guide to mapping business goals to user psychology**
 
@@ -94,7 +94,7 @@ Business goals work on two levels:
 - Ask yourself: "What will we see when this is realized?"
 - Transform vision into observable evidence
 
-**3. Create 3-5 SMART objectives:**
+**3. Create 3-5 strategic objectives using the SMART model:**
 - Specific (not vague)
 - Measurable (with numbers)
 - Achievable (realistic)
@@ -113,7 +113,7 @@ See [SMART Method Reference](../../models/smart-goals-model.md) for detailed gui
 
 **You:** "We'd see teams using our tool daily, staying with us long-term, and growing their usage. We'd see revenue that proves the business model works."
 
-**Saga:** "Excellent. Let's turn those observations into SMART objectives. What specific numbers would prove daily usage?"
+**Saga:** "Excellent. Let's express those observations as strategic objectives using the SMART model. What specific numbers would prove daily usage?"
 
 **You:** "We need to achieve 5,000 active teams by Q4 2024, with at least 70% weekly retention and $50K monthly recurring revenue."
 
@@ -179,11 +179,13 @@ This workshop identifies real people whose product usage drives your business su
 - Specific enough to design for
 - Focus on who will use the product in ways that achieve your goals
 
-**Create persona for each:**
+**Create persona profile for each (WHO they are):**
 - Name and context (their real-world situation)
-- Goals and motivations
-- Frustrations and fears
-- Behavioral patterns
+- Behavioral patterns (how they act)
+
+**Then define usage goals (when they face your problem space):**
+- Positive drivers (what they want to achieve)
+- Negative drivers (what they want to avoid)
 - How their product use connects to your business goals
 
 **Rank by priority:**
@@ -430,7 +432,7 @@ Business Goals → Product/Solution → Target Groups → Usage Goals
                                                      (Positive + Negative)
 ```
 
-1. **Business Goals** (Left, Blue) - Your vision and SMART objectives
+1. **Business Goals** (Left, Blue) - Your vision and strategic objectives
 2. **Product/Solution** (Center, Yellow) - What you're building
 3. **Target Groups** (Middle-Right, Orange) - Prioritized personas (👥 primary, 👤 secondary)
 4. **Usage Goals** (Right, Green/Red) - Positive drivers (✅) and negative drivers (❌) separated
@@ -470,7 +472,7 @@ Business Goals → Product/Solution → Target Groups → Usage Goals
 
 ## What You've Accomplished
 
-✅ **Business Goals** - Clear vision and SMART objectives  
+✅ **Business Goals** - Clear vision and strategic objectives  
 ✅ **Target Groups** - 3-5 prioritized personas with deep context  
 ✅ **Driving Forces** - Positive and negative psychology mapped  
 ✅ **Prioritization** - Ranked groups and drivers by strategic value  
@@ -565,7 +567,7 @@ A: Show them the Trigger Map and scoring matrix. Walk through the strategic reas
 - Use scores to guide sprint planning
 
 **Next Module:**
-- [Module 06: Scenarios](../module-06-scenarios/module-06-overview.md)
+- [Module 06: Scenarios](../module-08-outline-scenarios/module-08-outline-scenarios-overview.md)
 - Transform your Trigger Map into detailed user scenarios
 
 ---
@@ -590,6 +592,6 @@ A: Show them the Trigger Map and scoring matrix. Walk through the strategic reas
 
 **Your Trigger Map is the strategic foundation that guides every design decision. Use it well!**
 
-[← Back to Lesson 6](lesson-06-feature-impact-scoring.md) | [Back to Module Overview](module-05-overview.md)
+[← Back to Lesson 11](lesson-11-feature-impact-scoring.md) | [Back to Module Overview](module-06-overview.md)
 
-*Part of Module 05: Trigger Mapping*
+*Part of Module 06: Trigger Mapping*

package/docs/{learn-wds/module-05-trigger-mapping/tutorial-05c-documentation-synthesis.md → learn/module-06-trigger-mapping/tutorial-06c-documentation-synthesis.md}

@@ -1,4 +1,4 @@
-# Tutorial 05C: Synthesize from Documentation
+# Tutorial 06C: Synthesize from Documentation
 
 **Transform existing research into an actionable Trigger Map**
 
@@ -26,12 +26,9 @@ This tutorial walks you through synthesizing your existing documentation into a
 **Use Full Trigger Mapping instead if:**
 - ❌ Starting from scratch with no documentation
 - ❌ Documentation is minimal or non-existent
+- ❌ Need quick validation (use Suggest or Dream mode)
 
-**Use Value Trigger Chain instead if:**
-- ❌ Need quick validation (under 20 minutes)
-- ❌ Single user journey focus
-
-**Not sure which to use?** See [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md#three-approaches-choose-your-path)
+**Not sure which to use?** See [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md#two-approaches-choose-your-path)
 
 ---
 
@@ -466,10 +463,15 @@ A: Trigger Map organizes research into actionable structure, identifies gaps, va
 ## Related Resources
 
 - [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md) - Understanding the three approaches
-- [Tutorial 05: Full Trigger Mapping](tutorial-05.md) - Starting from scratch
-- [Tutorial 05B: Value Trigger Chain](tutorial-05b-value-trigger-chain.md) - Quick validation
-- [Module 05 Overview](module-05-overview.md) - Complete module guide
+- [Tutorial 06: Full Trigger Mapping](tutorial-06.md) - Starting from scratch
+- [Module 06 Overview](module-06-overview.md) - Complete module guide
 
 ---
 
 **Ready to transform your documentation into an actionable Trigger Map?** Activate Saga and begin! 🎯
+
+---
+
+[← Back to Tutorial 06](tutorial-06.md) | [Module Overview](module-06-overview.md) | [Next Module →](../module-07-design-phase/module-07-design-phase-overview.md)
+
+*Part of Module 06: Trigger Mapping*

package/docs/learn/module-07-design-phase/lesson-01-entering-design.md

@@ -0,0 +1,251 @@
+# Module 07: The Design Phase
+
+## Lesson 1: Entering Design Mode
+
+**The transition from strategy to creation**
+
+---
+
+## You've Built the Foundation
+
+Take a moment to appreciate what you've accomplished:
+
+**Module 04: Product Brief** — Your North Star
+- Vision and positioning
+- Target users and stakeholders
+- Success criteria and constraints
+
+**Module 05: Platform Requirements** — Your Boundaries
+- Platforms you're targeting
+- Integrations required
+- Constraints and knowledge gaps
+
+**Module 06: Trigger Map** — User Psychology Mapped
+- Personas with driving forces
+- Business goals connected to features
+- The "why" behind every decision
+
+This is your strategic foundation. Every design decision you make from here forward references these documents.
+
+---
+
+## The Mindset Shift
+
+Strategy is about **discovering and documenting**.
+Design is about **visualizing and specifying**.
+
+You're moving from:
+
+| Strategy Mode | Design Mode |
+|---------------|-------------|
+| What should we build? | How should it work? |
+| Why does this matter? | What does the user see? |
+| Who is this for? | How do they accomplish their goal? |
+| What's possible? | What exactly happens? |
+
+Both matter. But they require different thinking.
+
+---
+
+## Before We Begin: Why Specifications Matter
+
+Before diving into the design workflow, you need to understand a critical question:
+
+**"Why can't we just skip to code?"**
+
+**Short answer:** Because code is 10-20% of the value. Specifications are 80-90%.
+
+**Your app exists in specifications.** The code is just one possible projection—like compiled output.
+
+This isn't about "doing things the hard way." This is about **doing things the professional way** with AI-assisted development.
+
+**→ [Read Lesson 2: Why Specifications Matter](lesson-02-why-specifications-matter.md)** for the complete philosophy behind WDS.
+
+Key insights you'll learn:
+- Code is a lossy projection from specifications
+- Specifications align humans on shared goals
+- Specs are meta-prompts that enable autonomous AI work
+- Professional approach: Prompt → Spec → Code (not Prompt → Code → Debug hell)
+- Why this represents "the spirit of BMad v6 through the lens of a designer"
+
+**This foundation is critical.** Read Lesson 2 before continuing.
+
+---
+
+## Meet Freya
+
+Freya is your design partner for this phase.
+
+**What Freya does:**
+
+- Thinks WITH you, not FOR you
+- Asks "WHY?" before "WHAT?"
+- Connects every decision to your Trigger Map
+- Won't let you skip the hard thinking
+
+**What Freya doesn't do:**
+
+- Create pretty pictures without substance
+- Make decisions for you
+- Let you design in isolation from strategy
+- Accept "I don't know" as a final answer
+
+She's not a pixel pusher. She's a thinking partner who happens to work with visuals.
+
+---
+
+## The Freya Approach
+
+Freya's first question is always strategic:
+
+> "Looking at your Trigger Map, which persona's journey should we design first?"
+
+Not: "What color should the button be?"
+
+Every design decision connects back to your strategic foundation. If it doesn't connect, it gets questioned.
+
+---
+
+## The Design Workflow
+
+Nine modules. Eight steps. One coherent journey.
+
+```
+Outline → Sketch → Storyboard → Specify → Components → Visual → System → Deliver
+```
+
+| Step | What You Do | What You Create |
+|------|-------------|-----------------|
+| **Outline Scenarios** | Define user journeys | Scenario outlines |
+| **Conceptual Sketching** | Visualize default states | Rough sketches |
+| **Storyboarding** | Show transformations | Keyframe sequences |
+| **Specifications** | Document every detail | Complete specs |
+| **Components** | Define reusable patterns | Component definitions |
+| **Visual Design** | Apply visual language | Polished designs |
+| **Design System** | Organize for reuse | System documentation |
+| **Delivery** | Package for implementation | Delivery package |
+
+---
+
+## Not Strictly Linear
+
+You'll loop back. That's expected.
+
+- Sketching reveals gaps in your scenario outline
+- Storyboarding exposes missing states
+- Specifications surface component needs
+- Visual design raises consistency questions
+
+**The loop is the process.** Don't fight it.
+
+---
+
+## Multiple Entry Points
+
+Every step offers choices for how you start:
+
+| Entry Point | How It Works |
+|-------------|--------------|
+| **I have a sketch** | You provide, AI refines |
+| **I have inspiration** | You share, AI extracts patterns |
+| **Dream it up** | AI creates options, you pick |
+| **Let's discuss** | Conversation shapes the concept |
+
+Same step. Same output. Different starting points.
+
+You're not forced into one way of working. Use what feels natural for each situation.
+
+---
+
+## Creative Discipline
+
+> "Creative discipline enables creativity, not constrains it."
+
+This phrase captures the WDS approach to design.
+
+**Without discipline:**
+- Endless exploration with no conclusion
+- Beautiful mockups that solve wrong problems
+- Scattered work that can't be implemented
+- Decisions without rationale
+
+**With discipline:**
+- Focused exploration with clear outcomes
+- Beautiful mockups grounded in strategy
+- Coherent work ready for implementation
+- Every decision documented with WHY
+
+Structure doesn't limit creativity. It channels it.
+
+---
+
+## What You'll Create
+
+By the end of this phase:
+
+| Artifact | Purpose |
+|----------|---------|
+| **Scenario outlines** | The journeys you're designing |
+| **Conceptual sketches** | Visual explorations of each view |
+| **Storyboards** | How elements transform |
+| **Detailed specifications** | Every decision documented |
+| **Component definitions** | Reusable patterns identified |
+| **Visual designs** | Final look and feel |
+| **Design system** | Your component library |
+| **Delivery package** | Ready for implementation |
+
+---
+
+## Design System
+
+Remember the choice from setup:
+
+| Mode | What Happens |
+|------|--------------|
+| **1. None** | Ad-hoc styling, no extraction |
+| **2. Building** | System grows from your work |
+| **3. Library** | Use external + your branding |
+| **4. Existing** | Import from previous projects |
+
+This affects how Freya works with you throughout the phase.
+
+**Mode 1-2:** You're creating the design language as you go
+**Mode 3-4:** You're working within established patterns
+
+Neither is better. Just different workflows.
+
+---
+
+## The Core Principle
+
+Every pixel has a reason.
+Every interaction traces back to user psychology.
+Every component connects to a business goal.
+
+**Nothing is decoration. Everything is decision.**
+
+When you can explain WHY something exists, you've designed well.
+
+When you can't explain it, something's missing.
+
+---
+
+## Ready to Design
+
+You have:
+- Strategic foundation (Product Brief, Trigger Map, Platform Requirements)
+- A thinking partner (Freya)
+- A clear workflow (8 steps)
+- Flexible entry points (multiple ways to start each step)
+
+Let's begin.
+
+---
+
+**[Continue to Module 08: Outline Scenarios →](../module-08-outline-scenarios/module-08-outline-scenarios-overview.md)**
+
+---
+
+[← Back to Module Overview](module-07-design-phase-overview.md)
+
+*Part of Module 07: Design Phase*