whiteport-design-studio 0.1.0 → 0.2.0

package/src/workflows/shared/content-creation-workshop/steps-c/OPTIMIZATION-COMPLETE.md

@@ -1,143 +0,0 @@
-# Content Creation Workshop - Optimization Complete ✅
-
-**Date:** 2026-01-22
-**Status:** All files now compliant with BMAD v6 standards
-
----
-
-## Final Line Counts
-
-| File | Original | Final | Reduction | Status |
-|------|----------|-------|-----------|--------|
-| step-00-define-purpose.md | 291 | 196 | -95 (-33%) | ✅ Under 250 |
-| step-01-load-vtc-context.md | 126 | 126 | 0 | ✅ Already compliant |
-| step-02-awareness-strategy.md | 245 | 245 | 0 | ✅ Already compliant |
-| step-03-action-filter.md | 265 | 230 | -35 (-13%) | ✅ Under 250 |
-| step-04-empowerment-frame.md | 322 | 248 | -74 (-23%) | ✅ Under 250 |
-| step-05-structural-order.md | 341 | 227 | -114 (-33%) | ✅ Under 250 |
-| step-06-generate-content.md | 430 | 247 | -183 (-43%) | ✅ Under 250 |
-| **TOTALS** | **2,020** | **1,519** | **-501 (-25%)** | **7/7 Compliant** |
-
----
-
-## Optimization Strategy Applied
-
-### 1. Primary Focus: One Task Per Step ⭐
-
-**Key Principle:** "Let's make sure the characters is not the benchmark. Let's instead focus on one task per step."
-
-Each step now has ONE clear, focused task:
-- **Step 0:** Define content purpose
-- **Step 1:** Load VTC context
-- **Step 2:** Apply Customer Awareness strategy
-- **Step 3:** Apply Action Mapping to filter content
-- **Step 4:** Apply Badass Users framework for empowerment
-- **Step 5:** Apply Golden Circle for structural order
-- **Step 6:** Generate strategically grounded content variations
-
-### 2. Substep Extraction Pattern
-
-Created **9 substep files** to house detailed examples and frameworks:
-
-**Step 0 Substeps:**
-- `00-purpose-examples.md` (132 lines) - Three complete purpose definition examples
-
-**Step 3 Substeps:**
-- `03-action-filter-example.md` (98 lines) - Complete hairdresser newsletter action filter
-
-**Step 4 Substeps:**
-- `04-badass-users-principles.md` (121 lines) - Kathy Sierra framework details
-- `04-example-empowerment-frame.md` (95 lines) - Complete empowerment frame example
-
-**Step 5 Substeps:**
-- `05-golden-circle-guide.md` (161 lines) - WHY→HOW→WHAT framework guide
-- `05-example-golden-circle.md` (97 lines) - Complete Golden Circle application
-
-**Step 6 Substeps:**
-- `06-generation-instructions.md` (83 lines) - Detailed generation process
-- `06-example-hairdresser-newsletter.md` (150 lines) - Complete generation example
-- `06-content-output-template.md` (126 lines) - Output template
-
-**Total substeps content:** 1,063 lines (preserved, not lost)
-
-### 3. Reference Pattern Used
-
-Main step files now reference substeps using consistent pattern:
-
-```markdown
-## Example
-
-**See:** [substeps/03-action-filter-example.md](substeps/03-action-filter-example.md)
-
-This shows complete Action Mapping for hairdresser newsletter signup...
-```
-
----
-
-## Quality Validation
-
-### ✅ BMAD v6 Compliance
-- All 7 step files under 250-line limit
-- Micro-file design maintained
-- Just-in-time loading enabled
-
-### ✅ Task Focus
-- Each step has ONE clear task
-- No vague or multi-part tasks
-- Strategic flow maintained
-
-### ✅ Content Preserved
-- All examples moved to substeps (not deleted)
-- All frameworks accessible via references
-- Educational value retained
-
-### ✅ Workshop Integrity
-- 6-step strategic flow intact
-- Multi-model integration preserved
-- Complete traceability maintained
-
----
-
-## Files Created
-
-**Substep Files (9):**
-1. substeps/00-purpose-examples.md
-2. substeps/03-action-filter-example.md
-3. substeps/04-badass-users-principles.md
-4. substeps/04-example-empowerment-frame.md
-5. substeps/05-golden-circle-guide.md
-6. substeps/05-example-golden-circle.md
-7. substeps/06-generation-instructions.md
-8. substeps/06-example-hairdresser-newsletter.md
-9. substeps/06-content-output-template.md
-
-**Documentation:**
-- This validation report
-
----
-
-## Impact Summary
-
-**Before Optimization:**
-- 5 files over 250-line limit
-- Examples inline bloating main files
-- Harder to scan and understand each step
-
-**After Optimization:**
-- 0 files over limit (7/7 compliant)
-- Examples in dedicated substeps
-- Clear one-task-per-step structure
-- 25% reduction in main step files
-- Educational content fully preserved
-
----
-
-## Next Steps
-
-1. ✅ Content Creation Workshop - **COMPLETE**
-2. ⏭️ Move to next workflow validation
-3. Apply same optimization pattern where needed
-
----
-
-**Optimization completed successfully. All content-creation-workshop files now meet BMAD v6 standards while maintaining educational quality and one-task-per-step focus.**

package/src/workflows/shared/content-creation-workshop/steps-c/step-00-define-purpose.md

@@ -1,196 +0,0 @@
-# Step 0: Define Content Purpose
-
-**What job must this content do?**
-
----
-
-## Purpose
-
-Before generating any content, we must define its **measurable job**. Content purpose determines which strategic models to emphasize and enables objective review.
-
----
-
-## Duration
-
-⏱️ **3-5 minutes**
-
----
-
-## What You're Doing
-
-Defining a clear, testable purpose statement that answers:
-- What must this content accomplish?
-- For whom? (audience/user state)
-- How will we know it succeeded?
-
----
-
-## Questions for the User
-
-### 1. Content Context
-
-**"What content are we creating?"**
-
-Examples:
-- Landing page hero section
-- Product comparison table
-- Error message for invalid email
-- CTA button on pricing page
-- About page mission statement
-
-### 2. The Job To Do
-
-**"What must this content accomplish?"**
-
-Not "what it says" but "what it does":
-
-**Good (outcome-focused):**
-- "Convince Problem Aware users that shelf life matters"
-- "Enable confident product selection between us and competitors"
-- "Help user fix validation error while maintaining confidence"
-- "Remove final purchase barrier with risk reversal"
-
-**Bad (vague):**
-- "Describe the product"
-- "Explain benefits"
-- "Add social proof"
-- "Make it sound good"
-
-**"Can you describe the specific outcome this content needs to achieve?"**
-
-### 3. Target Audience/State
-
-**"Who will read this? What state are they in?"**
-
-Be specific:
-- "Problem Aware hairdressers feeling behind on trends"
-- "Product Aware B2B buyers comparing options"
-- "New users who just made a validation error"
-- "Most Aware users at checkout with last-minute doubts"
-
-**"What's their mental/emotional state when they encounter this?"**
-
-### 4. Success Criteria
-
-**"How will we know this content succeeded?"**
-
-Define measurable or observable outcomes:
-- "User recognizes themselves and continues reading"
-- "User can choose the right tier in < 30 seconds"
-- "User knows what happened and how to fix it"
-- "User clicks CTA feeling confident, not anxious"
-
-**"What would 'working perfectly' look like?"**
-
-### 5. Model Priority Emphasis
-
-**"Which strategic models matter most for THIS job?"**
-
-Based on content type and purpose, some models are more critical:
-
-Present the **Model Priority Matrix** from Content Purpose Guide and discuss:
-
-**Example: Error Message**
-- Badass Users ⭐⭐⭐ (maintain confidence)
-- Action Mapping ⭐⭐⭐ (enable recovery)
-- Customer Awareness ⭐ (keep simple)
-- Golden Circle ⭐ (not needed)
-- VTC ⭐ (context only)
-
-**Example: Landing Page Hero**
-- Customer Awareness ⭐⭐⭐ (hook at their level)
-- Golden Circle ⭐⭐⭐ (WHY-first)
-- Badass Users ⭐⭐ (transformation promise)
-- VTC ⭐⭐ (targeting/motivation)
-- Action Mapping ⭐ (CTA comes later)
-
-**"Which models should we emphasize for this content's purpose?"**
-
----
-
-## Agent Actions
-
-1. **Understand the content context** - What type of content is this?
-2. **Define the purpose collaboratively** - What job must it do?
-3. **Identify the audience/state** - Who will read it? When?
-4. **Establish success criteria** - How will we know it worked?
-5. **Select model priorities** - Which frameworks matter most?
-6. **Document the purpose** - Clear statement for traceability and review
-
----
-
-## Validation
-
-Before proceeding to Step 1:
-
-- [ ] Content type/context is clear
-- [ ] Purpose is specific and outcome-focused (not vague)
-- [ ] Audience and their state are defined
-- [ ] Success criteria are measurable or observable
-- [ ] Model priorities are selected based on purpose
-- [ ] Purpose statement is documented
-
----
-
-## Output
-
-**Purpose Definition:**
-
-```yaml
-content_purpose:
-  content_type: "[e.g., Landing page hero, Error message, CTA button]"
-  
-  purpose_statement: "[Action verb] + [specific audience/state] + [desired outcome]"
-  
-  audience:
-    who: "[User persona or type]"
-    state: "[Mental/emotional state, awareness level]"
-    context: "[When/where they encounter this content]"
-  
-  success_criteria:
-    - "[Observable outcome 1]"
-    - "[Observable outcome 2]"
-  
-  model_priorities:
-    primary: ["[Model 1 ⭐⭐⭐]", "[Model 2 ⭐⭐⭐]"]
-    secondary: ["[Model 3 ⭐⭐]"]
-    tertiary: ["[Model 4 ⭐]"]
-  
-  review_question: "[How will we know this achieved its purpose?]"
-```
-
----
-
-## Next Step
-
-Once purpose is defined:
-
-**→ Proceed to [Step 1: Load VTC Context](step-01-load-vtc-context.md)**
-
----
-
-## Examples & Templates
-
-**See:** [substeps/00-purpose-examples.md](substeps/00-purpose-examples.md)
-
-This shows three complete examples:
-- Landing page hero (Problem Aware targeting)
-- Error message (functional content with empowerment focus)
-- Product comparison feature (competitive differentiation)
-
-Plus purpose templates for persuasion, education, functional, and brand content.
-
----
-
-## Notes
-
-- **Purpose comes first** - Everything else flows from this
-- **Be specific** - Vague purposes lead to vague content
-- **Make it testable** - "I like it" isn't a success criterion
-- **Different purposes emphasize different models** - One size doesn't fit all
-- **Purpose enables review** - Objective evaluation, not subjective preference
-
----
-
-**⚠️ ALPHA:** If this step felt unnecessary or too structured, please note feedback. Is purpose definition too formal for Quick Mode?
-

package/src/workflows/shared/content-creation-workshop/steps-c/step-01-load-vtc-context.md

@@ -1,126 +0,0 @@
-# Step 1: Load VTC Context
-
-**Establish the strategic foundation for content creation**
-
----
-
-## Purpose
-
-Before writing any content, we must understand the strategic context: WHO we're serving, WHAT motivates them, and WHERE they are in their awareness journey.
-
----
-
-## Duration
-
-⏱️ **5 minutes**
-
----
-
-## What You're Doing
-
-Loading the Value Trigger Chain (VTC) that defines the strategic context for this content section.
-
----
-
-## Questions for the User
-
-### 1. VTC Identification
-
-**"Which VTC applies to this content section?"**
-
-- Is there an existing VTC for this page/scenario?
-- If multiple VTCs exist, which one is active here?
-- If no VTC exists, should we create one? (Route to VTC Workshop if needed)
-
-### 2. VTC Review
-
-Present the selected VTC and confirm:
-
-```
-Business Goal: [goal]
-Solution: [solution being designed]
-User: [persona name and description]
-Driving Forces:
-  • Wish: [positive motivator]
-  • Fear: [negative motivator]
-Customer Awareness: [START level] → [END level]
-```
-
-**"Is this the correct VTC for this content? Any adjustments needed?"**
-
----
-
-## Agent Actions
-
-1. **Check for existing VTCs** in project context
-   - Look in project documentation
-   - Check scenario definitions
-   - Review page specifications
-
-2. **If VTC exists:**
-   - Load and display it
-   - Confirm with user
-   - Note any adjustments
-
-3. **If NO VTC exists:**
-   - Explain that VTC is needed for strategic content
-   - Ask: "Should we create a VTC now?"
-   - If YES → Route to VTC Workshop
-   - If NO → Flag risk and continue with limited context
-
-4. **Document the VTC** for this content section
-   - Save reference to output file
-   - Ensure traceability
-
----
-
-## Validation
-
-Before proceeding to Step 2:
-
-- [ ] VTC is identified and loaded
-- [ ] All VTC fields are populated (goal, solution, user, driving forces, awareness)
-- [ ] User confirms this is the correct VTC for this content
-- [ ] VTC is documented for traceability
-
----
-
-## Output
-
-**VTC Context Document** - Saved for this content section:
-
-```yaml
-vtc_reference:
-  business_goal: "[goal text]"
-  solution: "[solution name/description]"
-  user:
-    name: "[persona name]"
-    description: "[brief persona description]"
-  driving_forces:
-    positive: "[wish/aspiration]"
-    negative: "[fear/frustration]"
-  customer_awareness:
-    start: "[awareness level where user begins]"
-    end: "[awareness level we want them to reach]"
-```
-
----
-
-## Next Step
-
-Once VTC is loaded and validated:
-
-**→ Proceed to [Step 2: Apply Customer Awareness Strategy](step-02-awareness-strategy.md)**
-
----
-
-## Notes
-
-- If project has multiple VTCs, it's normal - different pages/scenarios serve different goals/users
-- If VTC seems wrong for this content, it's better to pause and fix it than to continue
-- VTC is not bureaucracy - it's the strategic lens that makes content effective vs. guesswork
-
----
-
-**⚠️ ALPHA:** If this step felt unclear or unnecessary, please note feedback for improvement.
-

package/src/workflows/shared/content-creation-workshop/steps-c/step-02-awareness-strategy.md

@@ -1,245 +0,0 @@
-# Step 2: Apply Customer Awareness Strategy
-
-**Determine the right language, information, and proof for the user's awareness level**
-
----
-
-## Purpose
-
-The Customer Awareness Cycle determines WHAT you can say and HOW you say it. A user who is "Problem Aware" needs completely different language than one who is "Product Aware." This step translates the VTC's awareness positioning into concrete content strategy.
-
----
-
-## Duration
-
-⏱️ **5-7 minutes**
-
----
-
-## What You're Doing
-
-Using the Customer Awareness Cycle model to determine:
-- What language the user can understand
-- What information they need at this stage
-- What proof/credibility is required
-- What emotional journey we're facilitating
-
----
-
-## Context from Previous Step
-
-**VTC loaded in Step 1:**
-- Customer Awareness: **[START] → [END]**
-
----
-
-## The Customer Awareness Cycle (Quick Reference)
-
-**5 Levels (Eugene Schwartz):**
-
-1. **Unaware** - Don't know they have a problem
-2. **Problem Aware** - Know the problem, don't know solutions exist
-3. **Solution Aware** - Know solutions exist, exploring options
-4. **Product Aware** - Know your product, evaluating it
-5. **Most Aware** - Ready to buy/use, need final push
-
----
-
-## Questions for the User
-
-### 1. Validate Starting Awareness Level
-
-**"Let's confirm where the user is when they encounter this content:"**
-
-Present the START level from VTC and describe what it means:
-
-**Example:** *"The VTC says users are 'Problem Aware' - meaning they know they're struggling with [problem], but might not know that solutions like [your solution type] exist. Does this match your understanding of where users are when they encounter this [page/section]?"*
-
-- If YES → Continue
-- If NO → Discuss and adjust VTC
-
-### 2. Clarify Target Awareness Level
-
-**"And where do we want them after reading this content?"**
-
-Present the END level from VTC and describe the shift:
-
-**Example:** *"We want to move them to 'Solution Aware' - meaning after this section, they should understand that [solution category] exists and can solve their [problem]. Is that the right goal for this content?"*
-
-- If YES → Continue
-- If NO → Discuss and adjust VTC
-
-### 3. Awareness-Appropriate Language
-
-**"What can they understand at their STARTING level?"**
-
-Explore together:
-
-- **If Problem Aware:** Can we use your product name? Or should we speak in problem language first?
-- **If Solution Aware:** Do they understand the solution category terminology? Or do we need to explain it?
-- **If Product Aware:** What specific features matter to them? What comparisons are they making?
-
-**"What words will resonate vs. confuse?"**
-
-### 4. Information Priorities
-
-**"What do they NEED to know at this stage?"**
-
-Different awareness levels need different information:
-
-- **Problem Aware needs:** Problem validation, emotional recognition, hint that solutions exist
-- **Solution Aware needs:** How this type of solution works, why it's effective, what makes solutions good/bad
-- **Product Aware needs:** Specific features, proof it works, why choose you vs. competitors
-
-**"What's essential vs. overwhelming at their starting point?"**
-
-### 5. Credibility Requirements
-
-**"What proof do they need to believe us?"**
-
-Different awareness levels trust different things:
-
-- **Problem Aware:** Personal stories, emotional validation ("You're not alone")
-- **Solution Aware:** Expert credentials, how it works explanations, logic
-- **Product Aware:** Social proof, testimonials, data, comparisons
-
-**"What will make this credible to them?"**
-
-### 6. Emotional Journey
-
-**"What emotional shift happens from START → END?"**
-
-Explore the transformation:
-
-- **Starting emotion:** How do they FEEL at START level? (frustrated, confused, overwhelmed, cautious?)
-- **Ending emotion:** How should they FEEL at END level? (hopeful, informed, confident, excited?)
-
-**"What's the emotional bridge we're building?"**
-
----
-
-## Agent Actions
-
-1. **Present awareness level analysis** based on VTC
-2. **Explore each question** with the user
-3. **Document the answers** in structured format
-4. **Validate strategy** before moving forward
-
----
-
-## Validation
-
-Before proceeding to Step 3:
-
-- [ ] Start awareness level is confirmed and understood
-- [ ] End awareness level is confirmed and understood
-- [ ] Appropriate language identified (what words to use/avoid)
-- [ ] Information priorities clear (what to include/exclude)
-- [ ] Credibility requirements identified (what proof is needed)
-- [ ] Emotional journey mapped (start feeling → end feeling)
-
----
-
-## Output
-
-**Awareness Strategy Document:**
-
-```yaml
-awareness_strategy:
-  start_level: "[awareness level]"
-  start_characteristics:
-    - "[what they know]"
-    - "[what they don't know]"
-    - "[how they feel]"
-  
-  end_level: "[awareness level]"
-  end_characteristics:
-    - "[what they'll know]"
-    - "[what they'll understand]"
-    - "[how they'll feel]"
-  
-  language_guidelines:
-    use: ["[appropriate terms]"]
-    avoid: ["[confusing jargon]"]
-    tone: "[conversational, authoritative, empathetic, etc.]"
-  
-  information_priorities:
-    essential: ["[must include]"]
-    helpful: ["[nice to include if space]"]
-    avoid: ["[too advanced, confusing, or premature]"]
-  
-  credibility_required:
-    type: "[personal story, expert credentials, data, social proof]"
-    examples: ["[specific proof elements]"]
-  
-  emotional_journey:
-    starting_emotion: "[frustrated, confused, etc.]"
-    bridge: "[how we facilitate the shift]"
-    ending_emotion: "[hopeful, confident, etc.]"
-```
-
----
-
-## Next Step
-
-Once awareness strategy is defined:
-
-**→ Proceed to [Step 3: Define Required Action](step-03-action-filter.md)**
-
----
-
-## Example
-
-**VTC Context:** Hairdresser newsletter signup
-- Start: Problem Aware ("I feel behind on trends")
-- End: Product Aware ("This newsletter will keep me current")
-
-**Awareness Strategy:**
-
-```yaml
-awareness_strategy:
-  start_level: "Problem Aware"
-  start_characteristics:
-    - "Knows she's missing trends"
-    - "Doesn't know trend newsletters exist"
-    - "Feels frustrated and behind"
-  
-  end_level: "Product Aware"
-  end_characteristics:
-    - "Knows trend newsletters exist"
-    - "Understands how TrendWeek works"
-    - "Feels hopeful about staying current"
-  
-  language_guidelines:
-    use: ["missing trends", "falling behind", "your clients ask", "stay current"]
-    avoid: ["TrendWeek" in headline, technical jargon, assuming knowledge]
-    tone: "Empathetic and empowering"
-  
-  information_priorities:
-    essential: 
-      - "Validate the problem (you're not alone)"
-      - "Introduce solution category (trend newsletters)"
-      - "Show how it works (weekly digest)"
-    helpful:
-      - "Social proof (2,000 stylists)"
-      - "Time commitment (60 seconds per trend)"
-    avoid:
-      - "Company history"
-      - "Technical newsletter infrastructure"
-  
-  credibility_required:
-    type: "Social proof + Practical value"
-    examples: 
-      - "Testimonial: 'My clients always ask how I stay so current'"
-      - "Specific: 'Top 5 trends every Monday'"
-  
-  emotional_journey:
-    starting_emotion: "Frustrated and behind"
-    bridge: "Recognition → Hope → Confidence"
-    ending_emotion: "Empowered and excited to try"
-```
-
----
-
-**⚠️ ALPHA:** If this step felt too long or certain questions were unhelpful, please note feedback.
-