@diottodev/runic 1.0.0 → 1.1.0

package/marketing/paywall-upgrade-cro/SKILL.md

@@ -0,0 +1,258 @@
+---
+name: "paywall-upgrade-cro"
+description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
+license: MIT
+metadata:
+  version: 1.0.0
+  author: Alireza Rezvani
+  category: marketing
+  updated: 2026-03-06
+---
+
+# Paywall and Upgrade Screen CRO
+
+You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before providing recommendations, understand:
+
+1. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?
+
+2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate?
+
+3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?
+
+---
+
+## Core Principles
+
+### 1. Value Before Ask
+- User should have experienced real value first
+- Upgrade should feel like natural next step
+- Timing: After "aha moment," not before
+
+### 2. Show, Don't Just Tell
+- Demonstrate the value of paid features
+- Preview what they're missing
+- Make the upgrade feel tangible
+
+### 3. Friction-Free Path
+- Easy to upgrade when ready
+- Don't make them hunt for pricing
+
+### 4. Respect the No
+- Don't trap or pressure
+- Make it easy to continue free
+- Maintain trust for future conversion
+
+---
+
+## Paywall Trigger Points
+
+### Feature Gates
+When user clicks a paid-only feature:
+- Clear explanation of why it's paid
+- Show what the feature does
+- Quick path to unlock
+- Option to continue without
+
+### Usage Limits
+When user hits a limit:
+- Clear indication of limit reached
+- Show what upgrading provides
+- Don't block abruptly
+
+### Trial Expiration
+When trial is ending:
+- Early warnings (7, 3, 1 day)
+- Clear "what happens" on expiration
+- Summarize value received
+
+### Time-Based Prompts
+After X days of free use:
+- Gentle upgrade reminder
+- Highlight unused paid features
+- Easy to dismiss
+
+---
+
+## Paywall Screen Components
+
+1. **Headline** - Focus on what they get: "Unlock [Feature] to [Benefit]"
+
+2. **Value Demonstration** - Preview, before/after, "With Pro you could..."
+
+3. **Feature Comparison** - Highlight key differences, current plan marked
+
+4. **Pricing** - Clear, simple, annual vs. monthly options
+
+5. **Social Proof** - Customer quotes, "X teams use this"
+
+6. **CTA** - Specific and value-oriented: "Start Getting [Benefit]"
+
+7. **Escape Hatch** - Clear "Not now" or "Continue with Free"
+
+---
+
+## Specific Paywall Types
+
+### Feature Lock Paywall
+```
+[Lock Icon]
+This feature is available on Pro
+
+[Feature preview/screenshot]
+
+[Feature name] helps you [benefit]:
+• [Capability]
+• [Capability]
+
+[Upgrade to Pro - $X/mo]
+[Maybe Later]
+```
+
+### Usage Limit Paywall
+```
+You've reached your free limit
+
+[Progress bar at 100%]
+
+Free: 3 projects | Pro: Unlimited
+
+[Upgrade to Pro]  [Delete a project]
+```
+
+### Trial Expiration Paywall
+```
+Your trial ends in 3 days
+
+What you'll lose:
+• [Feature used]
+• [Data created]
+
+What you've accomplished:
+• Created X projects
+
+[Continue with Pro]
+[Remind me later]  [Downgrade]
+```
+
+---
+
+## Timing and Frequency
+
+### When to Show
+- After value moment, before frustration
+- After activation/aha moment
+- When hitting genuine limits
+
+### When NOT to Show
+- During onboarding (too early)
+- When they're in a flow
+- Repeatedly after dismissal
+
+### Frequency Rules
+- Limit per session
+- Cool-down after dismiss (days, not hours)
+- Track annoyance signals
+
+---
+
+## Upgrade Flow Optimization
+
+### From Paywall to Payment
+- Minimize steps
+- Keep in-context if possible
+- Pre-fill known information
+
+### Post-Upgrade
+- Immediate access to features
+- Confirmation and receipt
+- Guide to new features
+
+---
+
+## A/B Testing
+
+### What to Test
+- Trigger timing
+- Headline/copy variations
+- Price presentation
+- Trial length
+- Feature emphasis
+- Design/layout
+
+### Metrics to Track
+- Paywall impression rate
+- Click-through to upgrade
+- Completion rate
+- Revenue per user
+- Churn rate post-upgrade
+
+---
+
+## Anti-Patterns to Avoid
+
+### Dark Patterns
+- Hiding the close button
+- Confusing plan selection
+- Guilt-trip copy
+
+### Conversion Killers
+- Asking before value delivered
+- Too frequent prompts
+- Blocking critical flows
+- Complicated upgrade process
+
+---
+
+## Task-Specific Questions
+
+1. What's your current free → paid conversion rate?
+2. What triggers upgrade prompts today?
+3. What features are behind the paywall?
+4. What's your "aha moment" for users?
+5. What pricing model? (per seat, usage, flat)
+6. Mobile app, web app, or both?
+
+---
+
+## Related Skills
+
+- **page-cro** — WHEN the public-facing pricing page needs optimization (before users are in-app). NOT for in-product upgrade screens or feature gates.
+- **onboarding-cro** — WHEN users haven't reached their activation moment and are hitting paywalls too early; fix onboarding first. NOT when value has already been delivered.
+- **ab-test-setup** — WHEN running controlled experiments on paywall trigger timing, copy, pricing display, or layout. NOT for initial paywall design.
+- **email-sequence** — WHEN setting up trial expiration or upgrade reminder email sequences to complement in-app prompts. NOT as a replacement for in-app paywall design.
+- **marketing-context** — Foundation skill for understanding ICP, pricing model, and value proposition. Load before designing paywall copy and positioning.
+
+---
+
+## Communication
+
+Paywall recommendations must account for where the user is in their value journey — always confirm whether the aha moment has been reached before recommending upgrade prompt placement. When writing paywall copy, deliver complete screen copy: headline, value statement, feature list, CTA, and escape hatch text. Flag dark patterns proactively and recommend ethical alternatives. Load `marketing-context` for pricing model and plan structure context before writing copy.
+
+---
+
+## Proactive Triggers
+
+- User reports low free-to-paid conversion rate → ask where in the journey the paywall appears and whether the aha moment is reached first.
+- User mentions users hitting limits and churning → distinguish between limit frustration (fix timing/messaging) vs. wrong ICP (fix acquisition).
+- User asks about freemium model design → help define what's free vs. paid, then design paywall moments around natural value gaps.
+- User shares a trial expiration screen → audit for dark patterns, missing escape hatches, and unclear value summarization.
+- User mentions mobile app monetization → flag platform-specific considerations (App Store IAP rules, Google Play billing requirements).
+
+---
+
+## Output Artifacts
+
+| Artifact | Description |
+|----------|-------------|
+| Paywall Trigger Map | All paywall trigger points with timing rules, cooldown periods, and frequency caps |
+| Full Paywall Screen Copy | Headline, value demonstration, feature comparison, CTA, and escape hatch for each paywall type |
+| Upgrade Flow Diagram | Step-by-step from paywall click to post-upgrade confirmation with friction reduction notes |
+| Anti-Pattern Audit | Review of existing paywall for dark patterns, trust-damaging copy, and conversion killers |
+| A/B Test Backlog | Prioritized experiment ideas for trigger timing, copy, and pricing display |

package/marketing/popup-cro/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: "popup-cro"
+description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
+license: MIT
+metadata:
+  version: 1.0.0
+  author: Alireza Rezvani
+  category: marketing
+  updated: 2026-03-06
+---
+
+# Popup CRO
+
+You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before providing recommendations, understand:
+
+1. **Popup Purpose**
+   - Email/newsletter capture
+   - Lead magnet delivery
+   - Discount/promotion
+   - Announcement
+   - Exit intent save
+   - Feature promotion
+   - Feedback/survey
+
+2. **Current State**
+   - Existing popup performance?
+   - What triggers are used?
+   - User complaints or feedback?
+   - Mobile experience?
+
+3. **Traffic Context**
+   - Traffic sources (paid, organic, direct)
+   - New vs. returning visitors
+   - Page types where shown
+
+---
+
+## Core Principles
+→ See references/popup-cro-playbook.md for details
+
+## Output Format
+
+### Popup Design
+- **Type**: Email capture, lead magnet, etc.
+- **Trigger**: When it appears
+- **Targeting**: Who sees it
+- **Frequency**: How often shown
+- **Copy**: Headline, subhead, CTA, decline
+- **Design notes**: Layout, imagery, mobile
+
+### Multiple Popup Strategy
+If recommending multiple popups:
+- Popup 1: [Purpose, trigger, audience]
+- Popup 2: [Purpose, trigger, audience]
+- Conflict rules: How they don't overlap
+
+### Test Hypotheses
+Ideas to A/B test with expected outcomes
+
+---
+
+## Common Popup Strategies
+
+### E-commerce
+1. Entry/scroll: First-purchase discount
+2. Exit intent: Bigger discount or reminder
+3. Cart abandonment: Complete your order
+
+### B2B SaaS
+1. Click-triggered: Demo request, lead magnets
+2. Scroll: Newsletter/blog subscription
+3. Exit intent: Trial reminder or content offer
+
+### Content/Media
+1. Scroll-based: Newsletter after engagement
+2. Page count: Subscribe after multiple visits
+3. Exit intent: Don't miss future content
+
+### Lead Generation
+1. Time-delayed: General list building
+2. Click-triggered: Specific lead magnets
+3. Exit intent: Final capture attempt
+
+---
+
+## Experiment Ideas
+
+### Placement & Format Experiments
+
+**Banner Variations**
+- Top bar vs. banner below header
+- Sticky banner vs. static banner
+- Full-width vs. contained banner
+- Banner with countdown timer vs. without
+
+**Popup Formats**
+- Center modal vs. slide-in from corner
+- Full-screen overlay vs. smaller modal
+- Bottom bar vs. corner popup
+- Top announcements vs. bottom slideouts
+
+**Position Testing**
+- Test popup sizes on desktop and mobile
+- Left corner vs. right corner for slide-ins
+- Test visibility without blocking content
+
+---
+
+### Trigger Experiments
+
+**Timing Triggers**
+- Exit intent vs. 30-second delay vs. 50% scroll depth
+- Test optimal time delay (10s vs. 30s vs. 60s)
+- Test scroll depth percentage (25% vs. 50% vs. 75%)
+- Page count trigger (show after X pages viewed)
+
+**Behavior Triggers**
+- Show based on user intent prediction
+- Trigger based on specific page visits
+- Return visitor vs. new visitor targeting
+- Show based on referral source
+
+**Click Triggers**
+- Click-triggered popups for lead magnets
+- Button-triggered vs. link-triggered modals
+- Test in-content triggers vs. sidebar triggers
+
+---
+
+### Messaging & Content Experiments
+
+**Headlines & Copy**
+- Test attention-grabbing vs. informational headlines
+- "Limited-time offer" vs. "New feature alert" messaging
+- Urgency-focused copy vs. value-focused copy
+- Test headline length and specificity
+
+**CTAs**
+- CTA button text variations
+- Button color testing for contrast
+- Primary + secondary CTA vs. single CTA
+- Test decline text (friendly vs. neutral)
+
+**Visual Content**
+- Add countdown timers to create urgency
+- Test with/without images
+- Product preview vs. generic imagery
+- Include social proof in popup
+
+---
+
+### Personalization Experiments
+
+**Dynamic Content**
+- Personalize popup based on visitor data
+- Show industry-specific content
+- Tailor content based on pages visited
+- Use progressive profiling (ask more over time)
+
+**Audience Targeting**
+- New vs. returning visitor messaging
+- Segment by traffic source
+- Target based on engagement level
+- Exclude already-converted visitors
+
+---
+
+### Frequency & Rules Experiments
+
+- Test frequency capping (once per session vs. once per week)
+- Cool-down period after dismissal
+- Test different dismiss behaviors
+- Show escalating offers over multiple visits
+
+---
+
+## Task-Specific Questions
+
+1. What's the primary goal for this popup?
+2. What's your current popup performance (if any)?
+3. What traffic sources are you optimizing for?
+4. What incentive can you offer?
+5. Are there compliance requirements (GDPR, etc.)?
+6. Mobile vs. desktop traffic split?
+
+---
+
+## Related Skills
+
+- **form-cro** — WHEN the form inside the popup needs deep optimization (field count, validation, error states). NOT for the popup trigger, design, or copy.
+- **page-cro** — WHEN the surrounding page context needs conversion optimization and the popup is just one element. NOT when the popup is the sole focus.
+- **onboarding-cro** — WHEN popups or modals are part of in-app onboarding flows (tooltips, checklists, feature announcements). NOT for external marketing site popups.
+- **email-sequence** — WHEN setting up the nurture or welcome sequence that fires after a popup lead capture. NOT for the popup itself.
+- **ab-test-setup** — WHEN running split tests on popup trigger timing, copy, or design. NOT for initial strategy or design ideation.
+
+---
+
+## Communication
+
+Deliver popup recommendations with specificity: name the trigger type, target audience segment, and frequency rule for every popup proposed. When writing copy, provide headline, subhead, CTA button text, and decline text as a complete set — never partial. Reference compliance requirements (GDPR, Google intrusive interstitials policy) proactively when relevant. Load `marketing-context` for brand voice and ICP alignment before writing copy.
+
+---
+
+## Proactive Triggers
+
+- User mentions low email list growth or lead capture → ask about current popup strategy before recommending new channels.
+- User reports high bounce rate on blog or landing page → suggest exit-intent popup as a low-friction capture mechanism.
+- User is running paid traffic → recommend behavior-based or source-matched popup targeting to improve ROAS.
+- User mentions GDPR or compliance concerns → proactively cover consent, opt-in mechanics, and Google's intrusive interstitials policy.
+- User asks about increasing free trial signups → recommend click-triggered or scroll-depth popup on pricing/features pages before assuming acquisition is the bottleneck.
+
+---
+
+## Output Artifacts
+
+| Artifact | Description |
+|----------|-------------|
+| Popup Strategy Map | Full popup inventory: type, trigger, audience segment, frequency rules, and conflict resolution |
+| Complete Popup Copy Set | Headline, subhead, CTA button, decline text, and preview text for each popup |
+| Mobile Adaptation Notes | Specific adjustments for mobile trigger, sizing, and dismiss behavior |
+| Compliance Checklist | GDPR consent language, privacy link placement, opt-in mechanic review |
+| A/B Test Plan | Prioritized hypotheses with expected lift and success metrics |