Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Alternative popup framework from the Alireza collection. Use Popup Modal Planning for the existing M11 workflow with bundled references; this source variant has no reference package.
--- 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 |
Alternative popup framework from the Alireza collection. Use Popup Modal Planning for the existing M11 workflow with bundled references; this source variant has no reference package.
The complete original guidance with attributed source and declared limitations.
Clarify the task and evidence, then apply relevant source instructions within authorized scope.
Page context, audience, trigger rules, goal and user constraints.
Brief source danger screening: full-text pattern triage and review of flagged passages, not a comprehensive audit or functional test. Preserve accessible dismissal and actual consent; avoid coercive interfaces and unsupported conversion claims. Referenced scripts, templates, integrations and sibling skills are not supplied or installed unless explicitly listed as included. External calls, account changes, messages and file writes require the actual user task and authorization.
Use Popup Conversion Review for [TASK]. Ask for missing inputs: Page context, audience, trigger rules, goal and user constraints. Identify assumptions and missing tools before execution; do not claim results or approvals without evidence.
Claiming runtime installation, certified safety, verified numerical outputs or permission for external actions merely from loading this source.
German routing, task scope and source limitations. Original author attribution: Alireza Rezvani. Brief source danger screening: full-text pattern triage and review of flagged passages, not a comprehensive audit or functional test. Preserve accessible dismissal and actual consent; avoid coercive interfaces and unsupported conversion claims. Referenced scripts, templates, integrations and sibling skills are not supplied or installed unless explicitly listed as included. External calls, account changes, messages and file writes require the actual user task and authorization.
MIT License Copyright (c) 2025 Alireza Rezvani 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.
Copy the text below, then paste it into your chat.