whiteport-design-studio 0.1.0

package/src/workflows/shared/content-creation-workshop/steps-c/step-03-action-filter.md

@@ -0,0 +1,230 @@
+# Step 3: Define Required Action
+
+**Apply Action Mapping to filter for relevance and purpose**
+
+---
+
+## Purpose
+
+Action Mapping (Cathy Moore) asks the critical question: **"What action does this content enable?"** 
+
+If content doesn't enable a specific, valuable action, it's likely fluff. This step ensures every word serves a purpose.
+
+---
+
+## Duration
+
+⏱️ **3-5 minutes**
+
+---
+
+## What You're Doing
+
+Identifying the specific action the user must be able to take after reading this content, and using that to filter what information is truly necessary.
+
+---
+
+## Context from Previous Steps
+
+**VTC:** Business goal, user, driving forces, awareness positioning  
+**Awareness Strategy:** Language guidelines, information priorities, emotional journey
+
+---
+
+## The Action Mapping Principle (Quick Reference)
+
+**Cathy Moore's Core Question:**
+> "What does the user need to be able to DO?"
+
+**Not:**
+- "What do they need to know?"
+- "What information should we provide?"
+- "What sounds impressive?"
+
+**But:**
+- "What behavior enables success?"
+- "What action drives the business goal?"
+
+**Then work backward:**
+- What information enables that action?
+- What practice enables that action?
+- What environment enables that action?
+
+---
+
+## Questions for the User
+
+### 1. Identify the Required Action
+
+**"After reading this content, what must the user be able to DO?"**
+
+Be specific. Not "understand" or "know about" - but actual behaviors:
+
+**Good examples:**
+- "Click the signup button with confidence"
+- "Choose the right pricing tier for their needs"
+- "Complete the first step in the onboarding flow"
+- "Recognize if this product is right for them (or not)"
+- "Explain the value to their boss/team"
+
+**Bad examples:**
+- "Understand our features" (too vague)
+- "Learn about our company" (no action)
+- "Be aware of the benefits" (awareness isn't action)
+
+**"What's the ONE action this content must enable?"**
+
+### 2. Connect Action to Business Goal
+
+**"How does this action serve the business goal?"**
+
+Trace the logic:
+- User does [action]
+- Which leads to [outcome]
+- Which drives [business goal from VTC]
+
+**Example:**
+- User clicks signup button (action)
+- Which leads to email capture (outcome)
+- Which drives "500 newsletter signups" goal (business goal)
+
+**"Does this action clearly serve the VTC's business goal?"**
+
+- If YES → Continue
+- If NO → Reconsider if this content is needed, or if the action is defined correctly
+
+### 3. Connect Action to Driving Forces
+
+**"How does this action satisfy the user's driving forces?"**
+
+From VTC, we know:
+- Positive driving force (wish): [from VTC]
+- Negative driving force (fear): [from VTC]
+
+**"By taking this action, how does the user move toward their wish or away from their fear?"**
+
+**Example:**
+- Action: Sign up for newsletter
+- Wish satisfied: "Become local beauty authority" (gets trend info)
+- Fear addressed: "Stop missing industry trends" (regular updates)
+
+### 4. Determine Essential Information
+
+**"What information is REQUIRED to enable this action?"**
+
+Work backward from the action:
+
+- To [do the action], the user must understand [X]
+- To understand [X], they need to know [Y]
+- To know [Y], we must tell them [Z]
+
+**Strip away everything else.**
+
+**"What can we cut without preventing the action?"**
+
+- Nice-to-know company history? → Cut
+- Impressive but irrelevant features? → Cut
+- Background context that doesn't enable action? → Cut
+
+### 5. Identify Action Barriers
+
+**"What might prevent the user from taking this action?"**
+
+Common barriers:
+- **Confusion:** Don't understand what to do
+- **Fear:** Worried about consequences
+- **Effort:** Seems too hard or time-consuming
+- **Distrust:** Don't believe it will work
+- **Irrelevance:** Don't see how it helps them
+
+**"What content is needed to remove these barriers?"**
+
+---
+
+## Agent Actions
+
+1. **Guide user to identify specific action** (not vague understanding)
+2. **Validate action connects** to business goal and driving forces
+3. **Work backward** to determine essential information
+4. **Challenge "nice to know"** content that doesn't enable action
+5. **Document** the required action and supporting information
+
+---
+
+## Validation
+
+Before proceeding to Step 4:
+
+- [ ] Specific action identified (not vague "understanding")
+- [ ] Action connects to VTC business goal
+- [ ] Action satisfies user's driving forces
+- [ ] Essential information determined (what enables the action)
+- [ ] Unnecessary information identified (what doesn't enable action)
+- [ ] Action barriers identified and addressed
+
+---
+
+## Output
+
+**Action Filter Document:**
+
+```yaml
+action_filter:
+  required_action:
+    description: "[Specific action user must be able to take]"
+    success_criteria: "[How we know they can do it]"
+  
+  business_impact:
+    connection: "[How this action drives the VTC business goal]"
+    logic: "[Action → Outcome → Goal]"
+  
+  user_motivation:
+    positive_driver: "[How action satisfies their wish]"
+    negative_driver: "[How action addresses their fear]"
+  
+  essential_information:
+    - "[Information element 1 - WHY needed for action]"
+    - "[Information element 2 - WHY needed for action]"
+    - "[Information element 3 - WHY needed for action]"
+  
+  cut_list:
+    - "[Nice-to-know info that doesn't enable action]"
+    - "[Impressive but irrelevant content]"
+  
+  action_barriers:
+    - barrier: "[e.g., confusion about next steps]"
+      solution: "[Content that removes this barrier]"
+    - barrier: "[e.g., fear of commitment]"
+      solution: "[Content that addresses this fear]"
+```
+
+---
+
+## Next Step
+
+Once the required action is clear and information is filtered:
+
+**→ Proceed to [Step 4: Frame User Empowerment](step-04-empowerment-frame.md)**
+
+---
+
+## Example
+
+**See:** [substeps/03-action-filter-example.md](substeps/03-action-filter-example.md)
+
+This shows complete Action Mapping for hairdresser newsletter signup, demonstrating how to filter essential information through required action, identify barriers, and create a cut list.
+
+---
+
+## Notes
+
+- This step often reveals that pages have too much content that doesn't serve the action
+- It's normal to identify 30-50% of planned content as "cut-able"
+- If you can't identify a clear action, question whether this content section is needed at all
+- Multiple small actions are fine (e.g., "read OR watch video")
+- But vague goals like "learn about us" indicate unfocused content
+
+---
+
+**⚠️ ALPHA:** Was this filtering process helpful or did it feel limiting? Feedback appreciated.
+

package/src/workflows/shared/content-creation-workshop/steps-c/step-04-empowerment-frame.md

@@ -0,0 +1,248 @@
+# Step 4: Frame User Empowerment
+
+**Apply Kathy Sierra's Badass Users principles to tone and framing**
+
+---
+
+## Purpose
+
+Kathy Sierra's core insight: **Don't make a better product. Make a better USER.**
+
+This step frames content to make users feel capable, show their transformation, create "aha moments," and reduce cognitive load. Content isn't about YOU—it's about them becoming badass.
+
+---
+
+## Duration
+
+⏱️ **5-7 minutes**
+
+---
+
+## The Single Task
+
+**Apply Badass Users framework to frame content around user capability and transformation**
+
+---
+
+## Context from Previous Steps
+
+**VTC:** User, driving forces, awareness positioning  
+**Awareness Strategy:** Emotional journey (start emotion → end emotion)  
+**Action Filter:** Required action and essential information
+
+---
+
+## Badass Users Framework
+
+**Quick Reference:** See [substeps/04-badass-users-principles.md](substeps/04-badass-users-principles.md) for detailed framework.
+
+**Core:** "You'll be able to..." not "Our product has..."
+
+**Five Principles:**
+1. Make Them Better (not product better)
+2. Show The Transformation (current → badass)
+3. Create "Aha Moments" (perspective shifts)
+4. Reduce Cognitive Load (simplify ruthlessly)
+5. Focus on Skills (not tools)
+
+---
+
+## Questions for the User
+
+### 1. Define Current vs. Badass State
+
+**"What's the user's CURRENT state?"**
+
+Be specific and empathetic:
+- What are they struggling with?
+- How do they feel? (frustrated, uncertain, overwhelmed, behind?)
+- What can't they do yet?
+
+**"What's their BADASS state after success?"**
+
+Paint the picture:
+- What will they be able to do?
+- How will they feel? (confident, capable, ahead?)
+- What transformation happened?
+
+---
+
+### 2. Identify the "Aha Moment"
+
+**"What insight or realization will make them say 'Oh! I get it!'?"**
+
+The "aha moment" isn't just understanding—it's a perspective shift:
+
+**Examples:**
+- "Oh! I don't need to follow 100 accounts—I just need THIS digest!"
+- "Oh! This is about my CLIENT'S reactions, not just knowing trends!"
+- "Oh! 60 seconds is all I need—I thought it would take hours!"
+
+**"What's the key insight that unlocks confidence?"**
+
+---
+
+### 3. Frame Around Capability
+
+**"How do we frame this content to highlight THEIR capability, not our features?"**
+
+Transform feature-focused language:
+
+**Before (feature-focus):**
+- "Our AI analyzes 10,000 beauty sources"
+- "We send weekly emails with 5 trends"
+
+**After (capability-focus):**
+- "You'll spot trends before your competitors"
+- "You'll always have something new to talk about with clients"
+
+**"How can we reframe essential information to focus on what THEY can do?"**
+
+---
+
+### 4. Show the Transformation Path
+
+**"How do we make the transformation visible and achievable?"**
+
+Users need to see:
+- Where they are (current state)
+- Where they're going (badass state)
+- That the path is real and manageable
+
+**"What makes the transformation feel real and achievable, not aspirational?"**
+
+Examples:
+- Specific numbers: "60 seconds per trend" (concrete)
+- Social proof: "2,000 stylists already there" (others did it)
+- Quick win: "Try it on your next client" (immediate)
+
+---
+
+### 5. Reduce Cognitive Load
+
+**"Where might this content overwhelm or confuse?"**
+
+Look for cognitive load issues:
+- Too many choices? → Reduce options or guide selection
+- Too much jargon? → Use plain language
+- Too many steps? → Break down or simplify
+- Unclear what to do? → Make next step obvious
+
+**"What can we simplify or cut to reduce mental effort?"**
+
+---
+
+### 6. Focus on Skills Over Tools
+
+**"What skill or capability are we helping them develop?"**
+
+Not:
+- "Using our platform"
+- "Receiving emails"
+
+But:
+- "Staying current effortlessly"
+- "Becoming the local authority"
+
+**"Can we frame this around the skill they gain, not the tool they use?"**
+
+---
+
+## Agent Actions
+
+1. **Guide user to articulate** current vs. badass transformation
+2. **Identify the "aha moment"** that shifts perspective
+3. **Reframe essential information** from Step 3 using capability language
+4. **Map the transformation path** to make it visible
+5. **Identify and address** cognitive load issues
+6. **Document the empowerment framing**
+
+---
+
+## Validation
+
+Before proceeding to Step 5:
+
+- [ ] Current state clearly defined (where user is now)
+- [ ] Badass state clearly defined (where they're going)
+- [ ] "Aha moment" identified (key insight that unlocks confidence)
+- [ ] Content framed around user capability (not features)
+- [ ] Transformation path visible and achievable
+- [ ] Cognitive load issues identified and addressed
+- [ ] Focus on skills gained, not tools used
+
+---
+
+## Output
+
+**Empowerment Frame Document:**
+
+```yaml
+empowerment_frame:
+  transformation:
+    current_state:
+      description: "[Where user is now]"
+      feelings: ["frustrated", "uncertain", "behind"]
+      capabilities: "[What they can't do yet]"
+    
+    badass_state:
+      description: "[Where they're going]"
+      feelings: ["confident", "capable", "ahead"]
+      capabilities: "[What they'll be able to do]"
+    
+    visibility: "[How we make the transformation visible and achievable]"
+  
+  aha_moment:
+    insight: "[Key realization that shifts perspective]"
+    why_powerful: "[Why this unlocks confidence]"
+  
+  capability_framing:
+    - feature: "[Product feature]"
+      reframed: "[What USER can do because of it]"
+    - feature: "[Product feature]"
+      reframed: "[What USER can do because of it]"
+  
+  cognitive_load:
+    potential_issues:
+      - issue: "[Where content might overwhelm]"
+        solution: "[How we reduce load]"
+    
+    simplifications:
+      - "[What we simplified or cut]"
+  
+  skill_focus:
+    primary_skill: "[Main capability user develops]"
+    supporting_skills: ["[Related capabilities]"]
+    tools_secondary: "[Tools are means to skill, not the focus]"
+```
+
+---
+
+## Next Step
+
+Once empowerment framing is defined:
+
+**→ Proceed to [Step 5: Determine Structural Order](step-05-structural-order.md)**
+
+---
+
+## Example
+
+**See:** [substeps/04-example-empowerment-frame.md](substeps/04-example-empowerment-frame.md)
+
+This shows complete Badass Users framework application for hairdresser newsletter, demonstrating transformation framing, aha moment, capability reframing, cognitive load reduction, and skill focus
+
+---
+
+## Notes
+
+- This is where content shifts from "us-focused" to "you-focused"
+- The transformation must feel REAL, not aspirational marketing fluff
+- "Aha moments" are specific insights, not vague "understanding"
+- Cognitive load reduction often means cutting 30-40% of planned content
+- If you can't define a clear skill focus, content might be too product-centric
+
+---
+
+**⚠️ ALPHA:** Did this framing process help shift perspective? Or feel too abstract? Feedback welcome.
+

package/src/workflows/shared/content-creation-workshop/steps-c/step-05-structural-order.md

@@ -0,0 +1,227 @@
+# Step 5: Determine Structural Order
+
+**Apply the Golden Circle to create persuasive content flow**
+
+---
+
+## Purpose
+
+Simon Sinek's Golden Circle provides the structural order that makes content persuasive: **WHY → HOW → WHAT**. Most content does it backward (WHAT → HOW → WHY) and fails to inspire action. This step sequences your content for maximum impact.
+
+---
+
+## Duration
+
+⏱️ **3-5 minutes**
+
+---
+
+## The Single Task
+
+**Map all content from previous steps into WHY → HOW → WHAT sequence**
+
+---
+
+## Context from Previous Steps
+
+**VTC:** Business goal, user, driving forces  
+**Awareness Strategy:** Language, information priorities, emotional journey  
+**Action Filter:** Essential information that enables action  
+**Empowerment Frame:** Transformation, capability framing, "aha moment"
+
+---
+
+## The Golden Circle
+
+**Quick Reference:** See [substeps/05-golden-circle-guide.md](substeps/05-golden-circle-guide.md) for detailed framework explanation.
+
+```
+WHY (Emotion) → HOW (Method) → WHAT (Specifics)
+```
+
+**WHY** - Emotional truth, purpose (connects to driving forces)  
+**HOW** - Method, approach (bridges emotion to action)  
+**WHAT** - Specifics, proof (enables action)
+
+---
+
+## Questions for the User
+
+### 1. Identify the WHY
+
+**"What's the emotional opening that connects to their driving forces?"**
+
+- Opens with user's current emotional state (from Empowerment Frame)
+- Connects to driving forces (from VTC)
+- Makes them care before explaining solution
+
+**"What's the opening that makes them say 'that's me'?"**
+
+---
+
+### 2. Identify the HOW
+
+**"What's the method that bridges emotional need to specific solution?"**
+
+- Explains the approach or process
+- Shows how transformation happens
+- Uses capability framing (from Step 4)
+- Contains the "aha moment" insight
+
+**"Which essential information belongs in the HOW section?"**
+
+---
+
+### 3. Identify the WHAT
+
+**"What are the concrete specifics and call to action?"**
+
+- Names the product/offer
+- Provides social proof
+- Clear CTA with capability framing
+- Risk removal
+
+**"Which information belongs in WHAT—the final specifics?"**
+
+---
+
+### 4. Map Content to Structure
+
+**"Let's organize all essential information into WHY-HOW-WHAT:"**
+
+Present all content from Steps 3-4 (Action Filter + Empowerment Frame).
+
+**Work together to assign each piece:**
+- This goes in WHY (emotional opening)
+- This goes in HOW (method/bridge)
+- This goes in WHAT (specifics/proof)
+
+---
+
+### 5. Sequence Within Sections
+
+**"Within each section, what's the most persuasive order?"**
+
+**WHY section:** Problem → Validation → Aspiration  
+**HOW section:** Approach → Differentiator → Transformation  
+**WHAT section:** Naming → Proof → Action → Risk Removal
+
+**"Does the sequence within each section flow smoothly?"**
+
+---
+
+### 6. Validate Persuasive Flow
+
+**"Does WHY → HOW → WHAT create natural emotional → logical → action flow?"**
+
+- Can user understand WHY without knowing WHAT yet?
+- Does HOW bridge the gap naturally?
+- Does WHAT feel like natural conclusion (not premature)?
+
+**"Does anything feel out of order or jarring?"**
+
+---
+
+## Agent Actions
+
+1. **Help user identify** the WHY (emotional truth/purpose)
+2. **Help user identify** the HOW (method/bridge)
+3. **Help user identify** the WHAT (specifics/proof)
+4. **Map all essential information** from previous steps into WHY-HOW-WHAT
+5. **Sequence content within sections** for smooth flow
+6. **Validate persuasive flow** end-to-end
+7. **Document the structure**
+
+---
+
+## Validation
+
+Before proceeding to Step 6:
+
+- [ ] WHY is identified (emotional opening, purpose)
+- [ ] HOW is identified (method, bridge, differentiator)
+- [ ] WHAT is identified (specifics, proof, CTA)
+- [ ] All essential information assigned to WHY, HOW, or WHAT
+- [ ] Content sequenced within each section
+- [ ] Flow feels natural and persuasive (WHY → HOW → WHAT)
+- [ ] Nothing feels out of order or premature
+
+---
+
+## Output
+
+**Structural Order Document:**
+
+```yaml
+structural_order:
+  section_why:
+    purpose: "Emotional truth / Why user should care"
+    content_elements:
+      - order: 1
+        element: "[Opening hook]"
+        rationale: "[Why this opens]"
+      - order: 2
+        element: "[Validation or aspiration]"
+        rationale: "[Why this comes second]"
+  
+  section_how:
+    purpose: "Method / Bridge from emotion to specifics"
+    content_elements:
+      - order: 1
+        element: "[Solution approach]"
+        rationale: "[Why this bridges first]"
+      - order: 2
+        element: "[Key differentiator]"
+        rationale: "[Why this matters here]"
+      - order: 3
+        element: "[Transformation path]"
+        rationale: "[Why this comes last in HOW]"
+  
+  section_what:
+    purpose: "Specifics / Proof / Action"
+    content_elements:
+      - order: 1
+        element: "[Product/offer name]"
+        rationale: "[Why we can name it now]"
+      - order: 2
+        element: "[Social proof]"
+        rationale: "[Why proof comes here]"
+      - order: 3
+        element: "[CTA]"
+        rationale: "[Why action comes last]"
+  
+  flow_validation:
+    feels_natural: "[yes/no + notes]"
+    persuasive_arc: "[Does WHY → HOW → WHAT create emotional → logical → action flow?]"
+```
+
+---
+
+## Next Step
+
+Once structure is determined:
+
+**→ Proceed to [Step 6: Generate & Review Content](step-06-generate-content.md)**
+
+---
+
+## Example
+
+**See:** [substeps/05-example-golden-circle.md](substeps/05-example-golden-circle.md)
+
+This shows complete WHY → HOW → WHAT sequencing for hairdresser newsletter content, with detailed rationale for each element's placement and order
+
+---
+
+## Notes
+
+- The Golden Circle is fractal—you can apply WHY-HOW-WHAT at page level AND within each section
+- If WHAT comes before WHY, content feels salesy and pushy
+- If WHY is missing, content feels cold and transactional
+- The "aha moment" from Step 4 often lives in the HOW section (the insight that bridges emotion to action)
+- This structure works for pages, sections, paragraphs, even sentences
+
+---
+
+**⚠️ ALPHA:** Did this structural sequencing feel helpful? Or was it redundant with previous steps? Feedback appreciated.
+