wizz-method 1.4.1 → 1.5.0

package/src/skills-lib/popup-cro/references/triggers-and-popup-types.md

@@ -0,0 +1,108 @@
+# Trigger Strategies and Popup Types
+
+Load this file when deciding which trigger mechanism and which popup format/type fits the goal (email capture, lead magnet, discount, exit intent, announcement, slide-in).
+
+## Trigger Strategies
+
+### Time-Based
+- **Not recommended**: "Show after 5 seconds"
+- **Better**: "Show after 30-60 seconds" (proven engagement)
+- Best for: General site visitors
+
+### Scroll-Based
+- **Typical**: 25-50% scroll depth
+- Indicates: Content engagement
+- Best for: Blog posts, long-form content
+- Example: "You're halfway through—get more like this"
+
+### Exit Intent
+- Detects cursor moving to close/leave
+- Last chance to capture value
+- Best for: E-commerce, lead gen
+- Mobile alternative: Back button or scroll up
+
+### Click-Triggered
+- User initiates (clicks button/link)
+- Zero annoyance factor
+- Best for: Lead magnets, gated content, demos
+- Example: "Download PDF" → Popup form
+
+### Page Count / Session-Based
+- After visiting X pages
+- Indicates research/comparison behavior
+- Best for: Multi-page journeys
+- Example: "Been comparing? Here's a summary..."
+
+### Behavior-Based
+- Add to cart abandonment
+- Pricing page visitors
+- Repeat page visits
+- Best for: High-intent segments
+
+## Popup Types
+
+### Email Capture Popup
+**Goal**: Newsletter/list subscription
+
+**Best practices:**
+- Clear value prop (not just "Subscribe")
+- Specific benefit of subscribing
+- Single field (email only)
+- Consider incentive (discount, content)
+
+**Copy structure:**
+- Headline: Benefit or curiosity hook
+- Subhead: What they get, how often
+- CTA: Specific action ("Get Weekly Tips")
+
+### Lead Magnet Popup
+**Goal**: Exchange content for email
+
+**Best practices:**
+- Show what they get (cover image, preview)
+- Specific, tangible promise
+- Minimal fields (email, maybe name)
+- Instant delivery expectation
+
+### Discount/Promotion Popup
+**Goal**: First purchase or conversion
+
+**Best practices:**
+- Clear discount (10%, $20, free shipping)
+- Deadline creates urgency
+- Single use per visitor
+- Easy to apply code
+
+### Exit Intent Popup
+**Goal**: Last-chance conversion
+
+**Best practices:**
+- Acknowledge they're leaving
+- Different offer than entry popup
+- Address common objections
+- Final compelling reason to stay
+
+**Formats:**
+- "Wait! Before you go..."
+- "Forget something?"
+- "Get 10% off your first order"
+- "Questions? Chat with us"
+
+### Announcement Banner
+**Goal**: Site-wide communication
+
+**Best practices:**
+- Top of page (sticky or static)
+- Single, clear message
+- Dismissable
+- Links to more info
+- Time-limited (don't leave forever)
+
+### Slide-In
+**Goal**: Less intrusive engagement
+
+**Best practices:**
+- Enters from corner/bottom
+- Doesn't block content
+- Easy to dismiss or minimize
+- Good for chat, support, secondary CTAs

package/src/skills-lib/signup-flow-cro/SKILL.md

@@ -16,330 +16,24 @@ If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-
 
 Before providing recommendations, understand:
 
-1. **Flow Type**
-   - Free trial signup
-   - Freemium account creation
-   - Paid account creation
-   - Waitlist/early access signup
-   - B2B vs B2C
-
-2. **Current State**
-   - How many steps/screens?
-   - What fields are required?
-   - What's the current completion rate?
-   - Where do users drop off?
-
-3. **Business Constraints**
-   - What data is genuinely needed at signup?
-   - Are there compliance requirements?
-   - What happens immediately after signup?
-
----
+1. **Flow Type** — Free trial signup, freemium account creation, paid account creation, waitlist/early access signup, B2B vs B2C
+2. **Current State** — How many steps/screens? What fields are required? What's the current completion rate? Where do users drop off?
+3. **Business Constraints** — What data is genuinely needed at signup? Are there compliance requirements? What happens immediately after signup?
 
 ## Core Principles
 
-### 1. Minimize Required Fields
-Every field reduces conversion. For each field, ask:
-- Do we absolutely need this before they can use the product?
-- Can we collect this later through progressive profiling?
-- Can we infer this from other data?
-
-**Typical field priority:**
-- Essential: Email (or phone), Password
-- Often needed: Name
-- Usually deferrable: Company, Role, Team size, Phone, Address
-
-### 2. Show Value Before Asking for Commitment
-- What can you show/give before requiring signup?
-- Can they experience the product before creating an account?
-- Reverse the order: value first, signup second
-
-### 3. Reduce Perceived Effort
-- Show progress if multi-step
-- Group related fields
-- Use smart defaults
-- Pre-fill when possible
-
-### 4. Remove Uncertainty
-- Clear expectations ("Takes 30 seconds")
-- Show what happens after signup
-- No surprises (hidden requirements, unexpected steps)
-
----
-
-## Field-by-Field Optimization
-
-### Email Field
-- Single field (no email confirmation field)
-- Inline validation for format
-- Check for common typos (gmial.com → gmail.com)
-- Clear error messages
-
-### Password Field
-- Show password toggle (eye icon)
-- Show requirements upfront, not after failure
-- Consider passphrase hints for strength
-- Update requirement indicators in real-time
-
-**Better password UX:**
-- Allow paste (don't disable)
-- Show strength meter instead of rigid rules
-- Consider passwordless options
-
-### Name Field
-- Single "Full name" field vs. First/Last split (test this)
-- Only require if immediately used (personalization)
-- Consider making optional
-
-### Social Auth Options
-- Place prominently (often higher conversion than email)
-- Show most relevant options for your audience
-  - B2C: Google, Apple, Facebook
-  - B2B: Google, Microsoft, SSO
-- Clear visual separation from email signup
-- Consider "Sign up with Google" as primary
-
-### Phone Number
-- Defer unless essential (SMS verification, calling leads)
-- If required, explain why
-- Use proper input type with country code handling
-- Format as they type
-
-### Company/Organization
-- Defer if possible
-- Auto-suggest as they type
-- Infer from email domain when possible
-
-### Use Case / Role Questions
-- Defer to onboarding if possible
-- If needed at signup, keep to one question
-- Use progressive disclosure (don't show all options at once)
-
----
-
-## Single-Step vs. Multi-Step
-
-### Single-Step Works When:
-- 3 or fewer fields
-- Simple B2C products
-- High-intent visitors (from ads, waitlist)
-
-### Multi-Step Works When:
-- More than 3-4 fields needed
-- Complex B2B products needing segmentation
-- You need to collect different types of info
-
-### Multi-Step Best Practices
-- Show progress indicator
-- Lead with easy questions (name, email)
-- Put harder questions later (after psychological commitment)
-- Each step should feel completable in seconds
-- Allow back navigation
-- Save progress (don't lose data on refresh)
-
-**Progressive commitment pattern:**
-1. Email only (lowest barrier)
-2. Password + name
-3. Customization questions (optional)
-
----
-
-## Trust and Friction Reduction
-
-### At the Form Level
-- "No credit card required" (if true)
-- "Free forever" or "14-day free trial"
-- Privacy note: "We'll never share your email"
-- Security badges if relevant
-- Testimonial near signup form
-
-### Error Handling
-- Inline validation (not just on submit)
-- Specific error messages ("Email already registered" + recovery path)
-- Don't clear the form on error
-- Focus on the problem field
-
-### Microcopy
-- Placeholder text: Use for examples, not labels
-- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
-- Help text: Only when needed, placed close to field
-
----
-
-## Mobile Signup Optimization
-
-- Larger touch targets (44px+ height)
-- Appropriate keyboard types (email, tel, etc.)
-- Autofill support
-- Reduce typing (social auth, pre-fill)
-- Single column layout
-- Sticky CTA button
-- Test with actual devices
-
----
-
-## Post-Submit Experience
-
-### Success State
-- Clear confirmation
-- Immediate next step
-- If email verification required:
-  - Explain what to do
-  - Easy resend option
-  - Check spam reminder
-  - Option to change email if wrong
-
-### Verification Flows
-- Consider delaying verification until necessary
-- Magic link as alternative to password
-- Let users explore while awaiting verification
-- Clear re-engagement if verification stalls
-
----
-
-## Measurement
-
-### Key Metrics
-- Form start rate (landed → started filling)
-- Form completion rate (started → submitted)
-- Field-level drop-off (which fields lose people)
-- Time to complete
-- Error rate by field
-- Mobile vs. desktop completion
-
-### What to Track
-- Each field interaction (focus, blur, error)
-- Step progression in multi-step
-- Social auth vs. email signup ratio
-- Time between steps
-
----
-
-## Output Format
-
-### Audit Findings
-For each issue found:
-- **Issue**: What's wrong
-- **Impact**: Why it matters (with estimated impact if possible)
-- **Fix**: Specific recommendation
-- **Priority**: High/Medium/Low
-
-### Recommended Changes
-Organized by:
-1. Quick wins (same-day fixes)
-2. High-impact changes (week-level effort)
-3. Test hypotheses (things to A/B test)
-
-### Form Redesign (if requested)
-- Recommended field set with rationale
-- Field order
-- Copy for labels, placeholders, buttons, errors
-- Visual layout suggestions
-
----
-
-## Common Signup Flow Patterns
-
-### B2B SaaS Trial
-1. Email + Password (or Google auth)
-2. Name + Company (optional: role)
-3. → Onboarding flow
-
-### B2C App
-1. Google/Apple auth OR Email
-2. → Product experience
-3. Profile completion later
-
-### Waitlist/Early Access
-1. Email only
-2. Optional: Role/use case question
-3. → Waitlist confirmation
-
-### E-commerce Account
-1. Guest checkout as default
-2. Account creation optional post-purchase
-3. OR Social auth with single click
-
----
-
-## Experiment Ideas
-
-### Form Design Experiments
+1. **Minimize Required Fields** — every field reduces conversion. Essential: email (or phone), password. Often needed: name. Usually deferrable: company, role, team size, phone, address.
+2. **Show Value Before Asking for Commitment** — show/give value before requiring signup where possible; reverse the order (value first, signup second).
+3. **Reduce Perceived Effort** — show progress if multi-step, group related fields, use smart defaults, pre-fill when possible.
+4. **Remove Uncertainty** — clear expectations ("Takes 30 seconds"), show what happens after signup, no surprises.
 
-**Layout & Structure**
-- Single-step vs. multi-step signup flow
-- Multi-step with progress bar vs. without
-- 1-column vs. 2-column field layout
-- Form embedded on page vs. separate signup page
-- Horizontal vs. vertical field alignment
+## References (load on demand)
 
-**Field Optimization**
-- Reduce to minimum fields (email + password only)
-- Add or remove phone number field
-- Single "Name" field vs. "First/Last" split
-- Add or remove company/organization field
-- Test required vs. optional field balance
-
-**Authentication Options**
-- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
-- SSO prominent vs. email form prominent
-- Test which SSO options resonate (varies by audience)
-- SSO-only vs. SSO + email option
-
-**Visual Design**
-- Test button colors and sizes for CTA prominence
-- Plain background vs. product-related visuals
-- Test form container styling (card vs. minimal)
-- Mobile-optimized layout testing
-
----
-
-### Copy & Messaging Experiments
-
-**Headlines & CTAs**
-- Test headline variations above signup form
-- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
-- Add clarity around trial length in CTA
-- Test value proposition emphasis in form header
-
-**Microcopy**
-- Field labels: minimal vs. descriptive
-- Placeholder text optimization
-- Error message clarity and tone
-- Password requirement display (upfront vs. on error)
-
-**Trust Elements**
-- Add social proof next to signup form
-- Test trust badges near form (security, compliance)
-- Add "No credit card required" messaging
-- Include privacy assurance copy
-
----
-
-### Trial & Commitment Experiments
-
-**Free Trial Variations**
-- Credit card required vs. not required for trial
-- Test trial length impact (7 vs. 14 vs. 30 days)
-- Freemium vs. free trial model
-- Trial with limited features vs. full access
-
-**Friction Points**
-- Email verification required vs. delayed vs. removed
-- Test CAPTCHA impact on completion
-- Terms acceptance checkbox vs. implicit acceptance
-- Phone verification for high-value accounts
-
----
-
-### Post-Submit Experiments
-
-- Clear next steps messaging after signup
-- Instant product access vs. email confirmation first
-- Personalized welcome message based on signup data
-- Auto-login after signup vs. require login
-
----
+- `references/field-optimization.md` — field-by-field guidance (email, password, name, social auth, phone, company, use case/role). Load when deciding which fields to keep, defer, or cut.
+- `references/flow-structure.md` — single-step vs. multi-step decision criteria, the progressive commitment pattern, and mobile signup optimization. Load when deciding how many steps the flow needs.
+- `references/trust-and-post-submit.md` — trust copy near the form, error handling, microcopy, and the post-submit experience (success state, verification flows). Load when writing form-adjacent copy or designing what happens right after submit.
+- `references/measurement-output-patterns.md` — key metrics to track, the output format for an audit/redesign deliverable, and proven signup patterns by product type (B2B SaaS, B2C, waitlist, e-commerce). Load when instrumenting the flow, formatting a deliverable, or looking for a reference pattern.
+- `references/experiments.md` — a full experiment backlog (form design, copy/messaging, trial/commitment, post-submit) for A/B testing. Load when the deliverable needs a test plan.
 
 ## Task-Specific Questions
 
@@ -349,8 +43,6 @@ Organized by:
 4. Are there compliance or verification requirements?
 5. What happens immediately after signup?
 
----
-
 ## Related Skills
 
 - **onboarding-cro**: For optimizing what happens after signup

package/src/skills-lib/signup-flow-cro/references/experiments.md

@@ -0,0 +1,72 @@
+# Experiment Ideas
+
+Load this file when the deliverable includes a test plan / A/B test backlog for a signup flow.
+
+## Form Design Experiments
+
+**Layout & Structure**
+- Single-step vs. multi-step signup flow
+- Multi-step with progress bar vs. without
+- 1-column vs. 2-column field layout
+- Form embedded on page vs. separate signup page
+- Horizontal vs. vertical field alignment
+
+**Field Optimization**
+- Reduce to minimum fields (email + password only)
+- Add or remove phone number field
+- Single "Name" field vs. "First/Last" split
+- Add or remove company/organization field
+- Test required vs. optional field balance
+
+**Authentication Options**
+- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
+- SSO prominent vs. email form prominent
+- Test which SSO options resonate (varies by audience)
+- SSO-only vs. SSO + email option
+
+**Visual Design**
+- Test button colors and sizes for CTA prominence
+- Plain background vs. product-related visuals
+- Test form container styling (card vs. minimal)
+- Mobile-optimized layout testing
+
+## Copy & Messaging Experiments
+
+**Headlines & CTAs**
+- Test headline variations above signup form
+- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
+- Add clarity around trial length in CTA
+- Test value proposition emphasis in form header
+
+**Microcopy**
+- Field labels: minimal vs. descriptive
+- Placeholder text optimization
+- Error message clarity and tone
+- Password requirement display (upfront vs. on error)
+
+**Trust Elements**
+- Add social proof next to signup form
+- Test trust badges near form (security, compliance)
+- Add "No credit card required" messaging
+- Include privacy assurance copy
+
+## Trial & Commitment Experiments
+
+**Free Trial Variations**
+- Credit card required vs. not required for trial
+- Test trial length impact (7 vs. 14 vs. 30 days)
+- Freemium vs. free trial model
+- Trial with limited features vs. full access
+
+**Friction Points**
+- Email verification required vs. delayed vs. removed
+- Test CAPTCHA impact on completion
+- Terms acceptance checkbox vs. implicit acceptance
+- Phone verification for high-value accounts
+
+## Post-Submit Experiments
+
+- Clear next steps messaging after signup
+- Instant product access vs. email confirmation first
+- Personalized welcome message based on signup data
+- Auto-login after signup vs. require login

package/src/skills-lib/signup-flow-cro/references/field-optimization.md

@@ -0,0 +1,49 @@
+# Field-by-Field Optimization
+
+Load this file when deciding which signup fields to keep, defer, or cut, and how to design each one.
+
+### Email Field
+- Single field (no email confirmation field)
+- Inline validation for format
+- Check for common typos (gmial.com → gmail.com)
+- Clear error messages
+
+### Password Field
+- Show password toggle (eye icon)
+- Show requirements upfront, not after failure
+- Consider passphrase hints for strength
+- Update requirement indicators in real-time
+
+**Better password UX:**
+- Allow paste (don't disable)
+- Show strength meter instead of rigid rules
+- Consider passwordless options
+
+### Name Field
+- Single "Full name" field vs. First/Last split (test this)
+- Only require if immediately used (personalization)
+- Consider making optional
+
+### Social Auth Options
+- Place prominently (often higher conversion than email)
+- Show most relevant options for your audience
+  - B2C: Google, Apple, Facebook
+  - B2B: Google, Microsoft, SSO
+- Clear visual separation from email signup
+- Consider "Sign up with Google" as primary
+
+### Phone Number
+- Defer unless essential (SMS verification, calling leads)
+- If required, explain why
+- Use proper input type with country code handling
+- Format as they type
+
+### Company/Organization
+- Defer if possible
+- Auto-suggest as they type
+- Infer from email domain when possible
+
+### Use Case / Role Questions
+- Defer to onboarding if possible
+- If needed at signup, keep to one question
+- Use progressive disclosure (don't show all options at once)

package/src/skills-lib/signup-flow-cro/references/flow-structure.md

@@ -0,0 +1,38 @@
+# Single-Step vs. Multi-Step and Mobile Optimization
+
+Load this file when deciding how many steps the signup flow needs and how to adapt it for mobile.
+
+## Single-Step vs. Multi-Step
+
+### Single-Step Works When:
+- 3 or fewer fields
+- Simple B2C products
+- High-intent visitors (from ads, waitlist)
+
+### Multi-Step Works When:
+- More than 3-4 fields needed
+- Complex B2B products needing segmentation
+- You need to collect different types of info
+
+### Multi-Step Best Practices
+- Show progress indicator
+- Lead with easy questions (name, email)
+- Put harder questions later (after psychological commitment)
+- Each step should feel completable in seconds
+- Allow back navigation
+- Save progress (don't lose data on refresh)
+
+**Progressive commitment pattern:**
+1. Email only (lowest barrier)
+2. Password + name
+3. Customization questions (optional)
+
+## Mobile Signup Optimization
+
+- Larger touch targets (44px+ height)
+- Appropriate keyboard types (email, tel, etc.)
+- Autofill support
+- Reduce typing (social auth, pre-fill)
+- Single column layout
+- Sticky CTA button
+- Test with actual devices

package/src/skills-lib/signup-flow-cro/references/measurement-output-patterns.md

@@ -0,0 +1,62 @@
+# Measurement, Output Format, and Common Patterns
+
+Load this file when defining what to measure, formatting the audit/recommendation deliverable, or looking for a proven signup pattern by product type.
+
+## Measurement
+
+### Key Metrics
+- Form start rate (landed → started filling)
+- Form completion rate (started → submitted)
+- Field-level drop-off (which fields lose people)
+- Time to complete
+- Error rate by field
+- Mobile vs. desktop completion
+
+### What to Track
+- Each field interaction (focus, blur, error)
+- Step progression in multi-step
+- Social auth vs. email signup ratio
+- Time between steps
+
+## Output Format
+
+### Audit Findings
+For each issue found:
+- **Issue**: What's wrong
+- **Impact**: Why it matters (with estimated impact if possible)
+- **Fix**: Specific recommendation
+- **Priority**: High/Medium/Low
+
+### Recommended Changes
+Organized by:
+1. Quick wins (same-day fixes)
+2. High-impact changes (week-level effort)
+3. Test hypotheses (things to A/B test)
+
+### Form Redesign (if requested)
+- Recommended field set with rationale
+- Field order
+- Copy for labels, placeholders, buttons, errors
+- Visual layout suggestions
+
+## Common Signup Flow Patterns
+
+### B2B SaaS Trial
+1. Email + Password (or Google auth)
+2. Name + Company (optional: role)
+3. → Onboarding flow
+
+### B2C App
+1. Google/Apple auth OR Email
+2. → Product experience
+3. Profile completion later
+
+### Waitlist/Early Access
+1. Email only
+2. Optional: Role/use case question
+3. → Waitlist confirmation
+
+### E-commerce Account
+1. Guest checkout as default
+2. Account creation optional post-purchase
+3. OR Social auth with single click