@stacksjs/defaults 0.75.109 → 0.75.111

package/ai/skills/stacks-marketing-onboarding/references/experiments.md

@@ -0,0 +1,258 @@
+# Onboarding Experiment Ideas
+
+Comprehensive list of A/B tests and experiments for user onboarding and activation.
+
+## Contents
+- Flow Simplification Experiments (reduce friction, step sequencing, progress & motivation)
+- Guided Experience Experiments (product tours, CTA optimization, UI guidance)
+- Personalization Experiments (user segmentation, dynamic content)
+- Quick Wins & Engagement Experiments (time-to-value, motivation mechanics, support & help)
+- Email & Multi-Channel Experiments (onboarding emails, email content, feedback loops)
+- Re-engagement Experiments (stalled user recovery, return experience)
+- Technical & UX Experiments (performance, mobile onboarding, accessibility)
+- Metrics to Track
+
+## Flow Simplification Experiments
+
+### Reduce Friction
+
+| Test | Hypothesis |
+|------|------------|
+| Email verification timing | During vs. after onboarding |
+| Empty states vs. dummy data | Pre-populated examples |
+| Pre-filled templates | Accelerate setup with templates |
+| OAuth options | Faster account linking |
+| Required step count | Fewer required steps |
+| Optional vs. required fields | Minimize requirements |
+| Skip options | Allow bypassing non-critical steps |
+
+### Step Sequencing
+
+| Test | Hypothesis |
+|------|------------|
+| Step ordering | Test different sequences |
+| Value-first ordering | Highest-value features first |
+| Friction placement | Move hard steps later |
+| Required vs. optional balance | Ratio of required steps |
+| Single vs. branching paths | One path vs. personalized |
+| Quick start vs. full setup | Minimal path to value |
+
+### Progress & Motivation
+
+| Test | Hypothesis |
+|------|------------|
+| Progress bars | Show completion percentage |
+| Checklist length | 3-5 items vs. 5-7 items |
+| Gamification | Badges, rewards, achievements |
+| Completion messaging | "X% complete" visibility |
+| Starting point | Begin at 20% vs. 0% |
+| Celebration moments | Acknowledge completions |
+
+---
+
+## Guided Experience Experiments
+
+### Product Tours
+
+| Test | Hypothesis |
+|------|------------|
+| Interactive tours | Tools like Navattic, Storylane |
+| Tooltip vs. modal guidance | Subtle vs. attention-grabbing |
+| Video tutorials | For complex workflows |
+| Self-paced vs. guided | User control vs. structured |
+| Tour length | Shorter vs. comprehensive |
+| Tour triggering | Automatic vs. user-initiated |
+
+### CTA Optimization
+
+| Test | Hypothesis |
+|------|------------|
+| CTA text variations | Action-oriented copy testing |
+| CTA placement | Position within screens |
+| In-app tooltips | Feature discovery prompts |
+| Sticky CTAs | Persist during onboarding |
+| CTA contrast | Visual prominence |
+| Secondary CTAs | "Learn more" vs. primary only |
+
+### UI Guidance
+
+| Test | Hypothesis |
+|------|------------|
+| Hotspot highlights | Draw attention to key features |
+| Coachmarks | Contextual tips |
+| Feature announcements | New feature discovery |
+| Contextual help | Help where users need it |
+| Search vs. guided | Self-service vs. directed |
+
+---
+
+## Personalization Experiments
+
+### User Segmentation
+
+| Test | Hypothesis |
+|------|------------|
+| Role-based onboarding | Different paths by role |
+| Goal-based paths | Customize by stated goal |
+| Role-specific dashboards | Relevant default views |
+| Use-case question | Personalize based on answer |
+| Industry-specific paths | Vertical customization |
+| Experience-based | Beginner vs. expert paths |
+
+### Dynamic Content
+
+| Test | Hypothesis |
+|------|------------|
+| Personalized welcome | Name, company, role |
+| Industry examples | Relevant use cases |
+| Dynamic recommendations | Based on user answers |
+| Template suggestions | Pre-filled for segment |
+| Feature highlighting | Relevant to stated goals |
+| Benchmark data | Industry-specific metrics |
+
+---
+
+## Quick Wins & Engagement Experiments
+
+### Time-to-Value
+
+| Test | Hypothesis |
+|------|------------|
+| First quick win | "Complete your first X" |
+| Success messages | After key actions |
+| Progress celebrations | Milestone moments |
+| Next step suggestions | After each completion |
+| Value demonstration | Show what they achieved |
+| Outcome preview | What success looks like |
+
+### Motivation Mechanics
+
+| Test | Hypothesis |
+|------|------------|
+| Achievement badges | Gamification elements |
+| Streaks | Consecutive day engagement |
+| Leaderboards | Social comparison (if appropriate) |
+| Rewards | Incentives for completion |
+| Unlock mechanics | Features revealed progressively |
+
+### Support & Help
+
+| Test | Hypothesis |
+|------|------------|
+| Free onboarding calls | For complex products |
+| Contextual help | Throughout onboarding |
+| Chat support | Availability during onboarding |
+| Proactive outreach | For stuck users |
+| Self-service resources | Help docs, videos |
+| Community access | Peer support early |
+
+---
+
+## Email & Multi-Channel Experiments
+
+### Onboarding Emails
+
+| Test | Hypothesis |
+|------|------------|
+| Founder welcome email | Personal vs. generic |
+| Behavior-based triggers | Action/inaction based |
+| Email timing | Immediate vs. delayed |
+| Email frequency | More vs. fewer touches |
+| Quick tips format | Short actionable content |
+| Video in email | More engaging format |
+
+### Email Content
+
+| Test | Hypothesis |
+|------|------------|
+| Subject lines | Open rate optimization |
+| Personalization depth | Name vs. behavior-based |
+| CTA prominence | Single clear action |
+| Social proof inclusion | Testimonials in email |
+| Urgency messaging | Trial reminders |
+| Plain text vs. designed | Format testing |
+
+### Feedback Loops
+
+| Test | Hypothesis |
+|------|------------|
+| NPS during onboarding | When to ask |
+| Blocking question | "What's stopping you?" |
+| NPS follow-up | Actions based on score |
+| In-app feedback | Thumbs up/down on features |
+| Survey timing | When to request feedback |
+| Feedback incentives | Reward for completing |
+
+---
+
+## Re-engagement Experiments
+
+### Stalled User Recovery
+
+| Test | Hypothesis |
+|------|------------|
+| Re-engagement email timing | When to send |
+| Personal outreach | Human vs. automated |
+| Simplified path | Reduced steps for returners |
+| Incentive offers | Discount or extended trial |
+| Problem identification | Ask what's blocking |
+| Demo offer | Live walkthrough |
+
+### Return Experience
+
+| Test | Hypothesis |
+|------|------------|
+| Welcome back message | Acknowledge return |
+| Progress resume | Pick up where left off |
+| Changed state | What happened while away |
+| Re-onboarding | Fresh start option |
+| Urgency messaging | Trial time remaining |
+
+---
+
+## Technical & UX Experiments
+
+### Performance
+
+| Test | Hypothesis |
+|------|------------|
+| Load time optimization | Faster = higher completion |
+| Progressive loading | Perceived performance |
+| Offline capability | Mobile experience |
+| Error handling | Graceful failure recovery |
+
+### Mobile Onboarding
+
+| Test | Hypothesis |
+|------|------------|
+| Touch targets | Size and spacing |
+| Swipe navigation | Mobile-native patterns |
+| Screen count | Fewer screens needed |
+| Input optimization | Mobile-friendly forms |
+| Permission timing | When to ask |
+
+### Accessibility
+
+| Test | Hypothesis |
+|------|------------|
+| Screen reader support | Accessibility impact |
+| Keyboard navigation | Non-mouse users |
+| Color contrast | Visibility |
+| Font sizing | Readability |
+
+---
+
+## Metrics to Track
+
+For all experiments, measure:
+
+| Metric | Description |
+|--------|-------------|
+| Activation rate | % reaching activation event |
+| Time to activation | Hours/days to first value |
+| Step completion rate | % completing each step |
+| Drop-off points | Where users abandon |
+| Return rate | Users who come back |
+| Day 1/7/30 retention | Engagement over time |
+| Feature adoption | Which features get used |
+| Support requests | Volume during onboarding |

package/ai/skills/stacks-marketing-onboarding/references/minimum-path-to-value.md

@@ -0,0 +1,49 @@
+# Minimum Path to Value (MPTV)
+
+**Minimum Path to Value (MPTV)** - the least number of steps to experience *enough* value to make a confident decision.
+
+Not the fastest path to *any* value, and not the full feature tour. It's the shortest route to a moment that's convincing enough for the user to decide "yes, this is for me." Everything else waits.
+
+## Why fewer steps win: Hick's Law
+
+**Hick's Law** - the time and effort to make a decision grows with the number and complexity of choices. Every step, field, and option in onboarding is another decision. More decisions = more hesitation, more drop-off.
+
+MPTV is the deliberate application of Hick's Law to onboarding: strip the path down to the fewest decisions required to reach value.
+
+## The abandonment reality
+
+You have far less time and patience than you think:
+
+- **40-60% of users who sign up for a free trial abandon after a single session** - and never return.
+- **75-80% of trial abandonment happens within the first day.**
+
+The decision to stick or bail is made almost immediately. If value isn't reached in the first session, most users are already gone. MPTV exists because the window is that small.
+
+## The process: inventory → remove → reconstruct
+
+Build (or fix) your MPTV in three passes:
+
+1. **Take inventory.** List *every* step between signup and value - every screen, form field, click, confirmation, permission prompt, and empty state. Be exhaustive and honest. Most teams underestimate their own step count by half.
+
+2. **Remove the nonessential.** For each step ask: does the user *have* to do this to reach value right now? If not, cut it, defer it, pre-fill it, or make it skippable. Default to removal. Configuration, profile completeness, advanced settings, and "nice to know" education are almost never essential to first value.
+
+3. **Reconstruct / iterate.** Rebuild the path with only what survived, in value-first order. Then measure and iterate - the first reconstruction is a hypothesis, not a finish line. Watch where users still stall and cut again.
+
+## Benchmark patterns
+
+Products with famously short paths to value:
+
+| Product | MPTV pattern |
+|---------|--------------|
+| **Stripe** | Get a working payment integration in **~7 lines of code / ~60% activation** - value (a real charge) before any account polish. |
+| **Calendly** | **3-step** setup to a shareable, working booking link. Value is a link you can send immediately. |
+| **Notion** | **Progressive disclosure** - starts nearly empty, reveals features only as the user needs them. The path to first value (a written page) is trivial; depth unfolds later. |
+
+The pattern across all three: reach a real, usable outcome fast, and hide complexity until it's asked for.
+
+## Applying it
+
+- Define the value moment first (the aha moment - see SKILL.md). MPTV is the path *to* that moment.
+- Count your current steps before optimizing. You can't remove what you haven't inventoried.
+- Treat every retained step as guilty until proven essential.
+- Measure step-completion and time-to-value after each reconstruction; the abandonment stats mean your margin for error is one session.

package/ai/skills/stacks-marketing-paywalls/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-marketing-paywalls/NOTICE.md

@@ -0,0 +1,13 @@
+# Source and license
+
+Adapted from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills),
+revision [1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff),
+upstream skill `paywalls`, version 2.0.0.
+The original MIT copyright and permission notice is in [LICENSE](LICENSE).
+
+Stacks supplies a namespaced entrypoint, shared implementation guidance, mapped
+related-skill links, and regular-hyphen copy. The playbook and its supporting
+references/templates are retained. Tool integrations remain optional linked
+references; upstream CLI programs, servers, and packaging scripts are not
+bundled or installed. Source examples are illustrative and changing platform
+facts require verification.

package/ai/skills/stacks-marketing-paywalls/PLAYBOOK.md

@@ -0,0 +1,223 @@
+> Adapted playbook. The [shared Stacks workflow](../stacks-marketing/WORKFLOW.md) governs implementation, current facts, and authorization.
+
+
+# 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:**
+Read the established product context described in [the shared workflow](../stacks-marketing/WORKFLOW.md) before asking questions.
+
+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
+
+**For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md)
+
+---
+
+## 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
+
+- **stacks-marketing-churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
+- **stacks-marketing-cro**: For public pricing page optimization
+- **stacks-marketing-onboarding**: For driving to aha moment before upgrade
+- **stacks-marketing-ab-testing**: For testing paywall variations

package/ai/skills/stacks-marketing-paywalls/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: stacks-marketing-paywalls
+description: Use when the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Covers marketing planning and its Stacks implementation.
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Marketing Paywalls
+
+Read [the shared Stacks workflow](../stacks-marketing/WORKFLOW.md), then
+[PLAYBOOK.md](PLAYBOOK.md) before doing this task. Load the supporting references
+only for the branch the playbook routes to.
+
+This ports `paywalls` from
+[coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/skills/paywalls).
+[NOTICE.md](NOTICE.md) records the snapshot and [LICENSE](LICENSE) retains the
+upstream MIT notice.
+
+## Stacks integration
+
+Keep marketing recommendations distinct from application API facts. Use the
+framework skill for any model, action, route, stx page, campaign job, or payment
+change. Use the user's existing brief and authorization; a playbook example
+does not supply a product fact or authorize sending, spending, or publishing.
+
+Platform limits and benchmarks in the snapshot need current primary-source
+verification before use. Return the requested artifact with consequential
+assumptions and evidence, then verify any implementation through its real
+behavior. Use TypeScript and Bun for executable helpers.

package/ai/skills/stacks-marketing-paywalls/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "stacks-marketing-paywalls",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me design the upgrade paywall for our project management tool. Free users can have 3 projects, and we want to show an upgrade screen when they try to create a 4th project.",
+      "expected_output": "Should check for product-marketing.md first. Should identify this as a usage limit trigger point. Should apply the paywall screen components: headline (communicate the value of upgrading, not just the limit), value demonstration (show what they get with paid plan), plan comparison (free vs paid), social proof, CTA (specific and action-oriented), and escape hatch (option to go back). Should provide specific copy recommendations. Should address the emotional state of the user at this moment (frustrated by the limit). Should warn against anti-patterns.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Identifies as usage limit trigger",
+        "Applies paywall screen components framework",
+        "Includes headline, value demo, comparison, social proof, CTA",
+        "Provides specific copy recommendations",
+        "Addresses user's emotional state at the limit",
+        "Includes escape hatch option",
+        "Warns against anti-patterns"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our free trial expires in 14 days and users see a generic 'Your trial has expired' screen. Upgrade rate from this screen is only 2%. How do we improve it?",
+      "expected_output": "Should identify this as a trial expiration trigger. Should apply the trial expiration paywall type guidance. Should recommend: show what they've built/accomplished during the trial (endowment effect), highlight specific features they used, show the value they'd lose, provide clear plan options, include social proof from similar users who upgraded. Should diagnose why 2% is low: likely a weak value prop, no personalization, no urgency or loss framing. Should provide specific redesign recommendations.",
+      "assertions": [
+        "Identifies as trial expiration trigger",
+        "Applies trial expiration paywall guidance",
+        "Recommends showing user's accomplishments during trial",
+        "Uses loss framing (what they'd lose)",
+        "Provides clear plan options",
+        "Includes social proof",
+        "Diagnoses why current 2% rate is low",
+        "Provides specific redesign recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "when should we show upgrade prompts? we don't want to be annoying but we also need to convert free users to paid.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the timing and frequency rules. Should recommend trigger points from the skill: feature gates (when they try a paid feature), usage limits (when they hit a threshold), value moments (when they've just experienced success), and natural transition points. Should address frequency capping to avoid being annoying. Should recommend the anti-patterns to avoid (blocking basic functionality, too frequent popups, dark patterns). Should provide a balanced approach that respects user experience while driving upgrades.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies timing and frequency rules",
+        "Recommends specific trigger points",
+        "Addresses frequency capping",
+        "Warns against anti-patterns",
+        "Balances user experience with conversion goals",
+        "Provides specific recommendations for each trigger type"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Design a feature gate paywall. When free users click on 'Advanced Analytics' in our dashboard, we want to show them an upgrade prompt.",
+      "expected_output": "Should identify this as a feature gate trigger. Should apply the feature lock paywall type guidance. Should recommend: show a preview or screenshot of the advanced analytics feature, explain the specific benefit (not just 'this is a paid feature'), include a plan comparison relevant to analytics, provide a clear CTA to upgrade, and include an escape hatch to go back to basic analytics. Should recommend showing what insights they're missing. Should provide copy recommendations for the paywall screen.",
+      "assertions": [
+        "Identifies as feature gate trigger",
+        "Applies feature lock paywall guidance",
+        "Recommends showing preview of the feature",
+        "Explains specific benefit of the feature",
+        "Includes relevant plan comparison",
+        "Provides clear CTA and escape hatch",
+        "Provides copy recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What are common mistakes to avoid with in-app paywalls? I don't want to be pushy or make users feel tricked.",
+      "expected_output": "Should apply the anti-patterns section. Should cover: dark patterns (making it hard to find the close button, confusing opt-out language), conversion killers (blocking basic functionality, showing paywalls too early before value is demonstrated, no escape hatch), frequency issues (too many prompts, showing the same paywall repeatedly). Should provide positive alternatives for each anti-pattern. Should emphasize that good paywalls feel helpful, not pushy.",
+      "assertions": [
+        "Applies anti-patterns section",
+        "Covers dark patterns to avoid",
+        "Covers conversion killers",
+        "Covers frequency issues",
+        "Provides positive alternatives for each",
+        "Emphasizes helpful over pushy approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me optimize our public pricing page? We want more visitors to choose the Pro plan over the Basic plan.",
+      "expected_output": "Should recognize this is a public pricing page optimization task, not an in-app paywall task. Should defer to or cross-reference the cro skill for pricing page CRO. Paywall-upgrade-cro specifically handles in-app upgrade prompts for existing users, not public-facing pricing pages.",
+      "assertions": [
+        "Recognizes this as public pricing page optimization",
+        "References or defers to cro skill",
+        "Explains that paywalls is for in-app upgrade prompts",
+        "Does not attempt public pricing page optimization"
+      ],
+      "files": []
+    }
+  ]
+}