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.
You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
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:
Popup Purpose
Current State
Traffic Context
→ See references/popup-cro-playbook.md for details
If recommending multiple popups:
Ideas to A/B test with expected outcomes
Banner Variations
Popup Formats
Position Testing
Timing Triggers
Behavior Triggers
Click Triggers
Headlines & Copy
CTAs
Visual Content
Dynamic Content
Audience Targeting
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.
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/popup-cro · pinned to the source commit
# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/popup-cro" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/popup-cro" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/popup-cro
Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.