Refactor remaining skills for progressive disclosure
Phase 2 refactoring of skills >500 lines and medium-sized skills: - paid-ads: 553 → 297 lines - Extract ad-copy-templates.md, audience-targeting.md, platform-setup-checklists.md - analytics-tracking: 541 → 292 lines - Extract ga4-implementation.md, gtm-implementation.md, event-library.md - ab-test-setup: 510 → 264 lines - Extract test-templates.md, sample-size-guide.md - copywriting: 458 → 248 lines - Extract copy-frameworks.md (headline formulas, section types) - page-cro: 336 → 180 lines - Extract experiments.md (experiment ideas by page type) - onboarding-cro: 435 → 218 lines - Extract experiments.md (onboarding experiment ideas) All skills now use progressive disclosure with references/ folders, keeping SKILL.md files focused on core workflow while detailed content is available when needed. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -14,31 +14,11 @@ If `.claude/product-marketing-context.md` exists, read it before asking question
|
||||
|
||||
Before providing recommendations, identify:
|
||||
|
||||
1. **Page Type**: What kind of page is this?
|
||||
- Homepage
|
||||
- Landing page (paid traffic, specific campaign)
|
||||
- Pricing page
|
||||
- Feature/product page
|
||||
- Blog post with CTA
|
||||
- About page
|
||||
- Other
|
||||
1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
|
||||
2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
|
||||
3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
|
||||
|
||||
2. **Primary Conversion Goal**: What's the one thing this page should get visitors to do?
|
||||
- Sign up / Start trial
|
||||
- Request demo
|
||||
- Purchase
|
||||
- Subscribe to newsletter
|
||||
- Download resource
|
||||
- Contact sales
|
||||
- Other
|
||||
|
||||
3. **Traffic Context**: If known, where are visitors coming from?
|
||||
- Organic search (what intent?)
|
||||
- Paid ads (what messaging?)
|
||||
- Social media
|
||||
- Email
|
||||
- Referral
|
||||
- Direct
|
||||
---
|
||||
|
||||
## CRO Analysis Framework
|
||||
|
||||
@@ -49,59 +29,46 @@ Analyze the page across these dimensions, in order of impact:
|
||||
**Check for:**
|
||||
- Can a visitor understand what this is and why they should care within 5 seconds?
|
||||
- Is the primary benefit clear, specific, and differentiated?
|
||||
- Does it address a real pain point or desire?
|
||||
- Is it written in the customer's language (not company jargon)?
|
||||
|
||||
**Common issues:**
|
||||
- Feature-focused instead of benefit-focused
|
||||
- Too vague ("The best solution for your needs")
|
||||
- Too clever (sacrificing clarity for creativity)
|
||||
- Trying to say everything instead of the one most important thing
|
||||
- Too vague or too clever (sacrificing clarity)
|
||||
- Trying to say everything instead of the most important thing
|
||||
|
||||
### 2. Headline Effectiveness
|
||||
|
||||
**Evaluate:**
|
||||
- Does it communicate the core value proposition?
|
||||
- Is it specific enough to be meaningful?
|
||||
- Does it create curiosity or urgency without being clickbait?
|
||||
- Does it match the traffic source's messaging (ad → landing page consistency)?
|
||||
- Does it match the traffic source's messaging?
|
||||
|
||||
**Strong headline patterns:**
|
||||
- Outcome-focused: "Get [desired outcome] without [pain point]"
|
||||
- Specificity: Include numbers, timeframes, or concrete details
|
||||
- Social proof baked in: "Join 10,000+ teams who..."
|
||||
- Direct address of pain: "Tired of [specific problem]?"
|
||||
- Social proof: "Join 10,000+ teams who..."
|
||||
|
||||
### 3. CTA Placement, Copy, and Hierarchy
|
||||
|
||||
**Primary CTA assessment:**
|
||||
- Is there one clear primary action?
|
||||
- Is it visible without scrolling (above the fold)?
|
||||
- Is it visible without scrolling?
|
||||
- Does the button copy communicate value, not just action?
|
||||
- Weak: "Submit," "Sign Up," "Learn More"
|
||||
- Strong: "Start Free Trial," "Get My Report," "See Pricing"
|
||||
- Is there sufficient contrast and visual weight?
|
||||
|
||||
**CTA hierarchy:**
|
||||
- Is there a logical primary vs. secondary CTA structure?
|
||||
- Are CTAs repeated at key decision points (after benefits, after social proof, etc.)?
|
||||
- Is the commitment level appropriate for the page stage?
|
||||
- Are CTAs repeated at key decision points?
|
||||
|
||||
### 4. Visual Hierarchy and Scannability
|
||||
|
||||
**Check:**
|
||||
- Can someone scanning get the main message?
|
||||
- Are the most important elements visually prominent?
|
||||
- Is there clear information hierarchy (H1 → H2 → body)?
|
||||
- Is there enough white space to let elements breathe?
|
||||
- Is there enough white space?
|
||||
- Do images support or distract from the message?
|
||||
|
||||
**Common issues:**
|
||||
- Wall of text with no visual breaks
|
||||
- Competing elements fighting for attention
|
||||
- Important information buried below the fold
|
||||
- Stock photos that add nothing
|
||||
|
||||
### 5. Trust Signals and Social Proof
|
||||
|
||||
**Types to look for:**
|
||||
@@ -110,49 +77,37 @@ Analyze the page across these dimensions, in order of impact:
|
||||
- Case study snippets with real numbers
|
||||
- Review scores and counts
|
||||
- Security badges (where relevant)
|
||||
- "As seen in" media mentions
|
||||
- Team/founder credibility
|
||||
|
||||
**Placement:**
|
||||
- Near CTAs (to reduce friction at decision point)
|
||||
- After benefit claims (to validate them)
|
||||
- Throughout the page at natural break points
|
||||
**Placement:** Near CTAs and after benefit claims
|
||||
|
||||
### 6. Objection Handling
|
||||
|
||||
**Identify likely objections for this page type:**
|
||||
**Common objections to address:**
|
||||
- Price/value concerns
|
||||
- "Will this work for my situation?"
|
||||
- Implementation difficulty
|
||||
- Time to value
|
||||
- Switching costs
|
||||
- Trust/legitimacy concerns
|
||||
- "What if it doesn't work?"
|
||||
|
||||
**Check if the page addresses these through:**
|
||||
- FAQ sections
|
||||
- Guarantee/refund policies
|
||||
- Comparison content
|
||||
- Feature explanations
|
||||
- Process transparency
|
||||
**Address through:** FAQ sections, guarantees, comparison content, process transparency
|
||||
|
||||
### 7. Friction Points
|
||||
|
||||
**Look for unnecessary friction:**
|
||||
**Look for:**
|
||||
- Too many form fields
|
||||
- Unclear next steps
|
||||
- Confusing navigation
|
||||
- Required information that shouldn't be required
|
||||
- Broken or slow elements
|
||||
- Mobile experience issues
|
||||
- Long load times
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
Structure your recommendations as:
|
||||
|
||||
### Quick Wins (Implement Now)
|
||||
Changes that are easy to make and likely to have immediate impact.
|
||||
Easy changes with likely immediate impact.
|
||||
|
||||
### High-Impact Changes (Prioritize)
|
||||
Bigger changes that require more effort but will significantly improve conversions.
|
||||
@@ -161,176 +116,65 @@ Bigger changes that require more effort but will significantly improve conversio
|
||||
Hypotheses worth A/B testing rather than assuming.
|
||||
|
||||
### Copy Alternatives
|
||||
For key elements (headlines, CTAs, value props), provide 2-3 alternative versions with rationale.
|
||||
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
|
||||
|
||||
---
|
||||
|
||||
## Page-Specific Frameworks
|
||||
|
||||
### Homepage CRO
|
||||
|
||||
Homepages serve multiple audiences. Focus on:
|
||||
- Clear positioning statement that works for cold visitors
|
||||
- Quick path to most common conversion action
|
||||
- Navigation that helps visitors self-select
|
||||
- Handling both "ready to buy" and "still researching" visitors
|
||||
- Clear positioning for cold visitors
|
||||
- Quick path to most common conversion
|
||||
- Handle both "ready to buy" and "still researching"
|
||||
|
||||
### Landing Page CRO
|
||||
|
||||
Single-purpose pages. Focus on:
|
||||
- Message match with traffic source
|
||||
- Single CTA (remove navigation if possible)
|
||||
- Complete argument on one page (minimize clicks to convert)
|
||||
- Urgency/scarcity if genuine
|
||||
- Complete argument on one page
|
||||
|
||||
### Pricing Page CRO
|
||||
|
||||
High-intent visitors. Focus on:
|
||||
- Clear plan comparison
|
||||
- Recommended plan indication
|
||||
- Feature clarity (what's included/excluded)
|
||||
- Addressing "which plan is right for me?" anxiety
|
||||
- Easy path from pricing to checkout
|
||||
- Address "which plan is right for me?" anxiety
|
||||
|
||||
### Feature Page CRO
|
||||
|
||||
Visitors researching specifics. Focus on:
|
||||
- Connecting feature to benefit
|
||||
- Connect feature to benefit
|
||||
- Use cases and examples
|
||||
- Comparison to alternatives
|
||||
- Clear CTA to try/buy
|
||||
- Clear path to try/buy
|
||||
|
||||
### Blog Post CRO
|
||||
|
||||
Content-to-conversion. Focus on:
|
||||
- Contextual CTAs that match content topic
|
||||
- Lead magnets related to article subject
|
||||
- Contextual CTAs matching content topic
|
||||
- Inline CTAs at natural stopping points
|
||||
- Exit-intent as backup
|
||||
|
||||
---
|
||||
|
||||
## Experiment Ideas by Page Type
|
||||
## Experiment Ideas
|
||||
|
||||
### Homepage Experiments
|
||||
When recommending experiments, consider tests for:
|
||||
- Hero section (headline, visual, CTA)
|
||||
- Trust signals and social proof placement
|
||||
- Pricing presentation
|
||||
- Form optimization
|
||||
- Navigation and UX
|
||||
|
||||
**Hero Section**
|
||||
- Test headline variations (specific vs. abstract, benefit vs. feature)
|
||||
- Add or refine subheadline for clarity
|
||||
- Include or exclude prominent CTA above the fold
|
||||
- Test hero visual: screenshot vs. GIF vs. illustration vs. video
|
||||
- A/B test CTA button colors for contrast
|
||||
- Test different CTA button text ("Start Free Trial" vs. "Get Started" vs. "See Demo")
|
||||
- Add interactive demo to engage visitors immediately
|
||||
|
||||
**Trust & Social Proof**
|
||||
- Test placement of customer logos (hero vs. below fold)
|
||||
- Showcase case studies or testimonials in hero section
|
||||
- Add trust badges (security, compliance, awards)
|
||||
- Test customer count or social proof in headline
|
||||
|
||||
**Features & Content**
|
||||
- Highlight key features with icons and brief descriptions
|
||||
- Test feature section order and prominence
|
||||
- Add or remove secondary CTAs throughout page
|
||||
|
||||
**Navigation & UX**
|
||||
- Add sticky navigation bar with persistent CTA
|
||||
- Test navigation menu order (high-priority items at edges)
|
||||
- Add prominent CTA button in nav bar
|
||||
- Live chat widget vs. AI chatbot for instant support
|
||||
- Optimize footer for clarity and secondary conversions
|
||||
|
||||
---
|
||||
|
||||
### Pricing Page Experiments
|
||||
|
||||
**Price Presentation**
|
||||
- Highlight annual billing discounts vs. show monthly only vs. show both
|
||||
- Test different pricing points ($99 vs. $100 vs. $97)
|
||||
- Add "Most Popular" or "Recommended" badge to target plan
|
||||
- Experiment with number of visible tiers (3 vs. 4 vs. 2)
|
||||
- Use price anchoring strategically
|
||||
|
||||
**Pricing UX**
|
||||
- Add pricing calculator for complex/usage-based pricing
|
||||
- Turn complex pricing table into guided multistep form
|
||||
- Test feature comparison table formats
|
||||
- Add toggle for monthly/annual with savings highlighted
|
||||
- Test "Contact Sales" vs. showing enterprise pricing
|
||||
|
||||
**Objection Handling**
|
||||
- Add FAQ section addressing common pricing objections
|
||||
- Include ROI calculator or value demonstration
|
||||
- Add money-back guarantee prominently
|
||||
- Show price-per-user breakdowns for team plans
|
||||
- Include "What's included" clarity for each tier
|
||||
|
||||
**Trust Signals**
|
||||
- Add testimonials specific to pricing/value
|
||||
- Show customer logos near pricing
|
||||
- Display review scores from G2/Capterra
|
||||
|
||||
---
|
||||
|
||||
### Demo Request Page Experiments
|
||||
|
||||
**Form Optimization**
|
||||
- Simplify demo request form (fewer fields)
|
||||
- Test multi-step form with progress bar vs. single-step
|
||||
- Test form placement: above fold vs. after content
|
||||
- Add or remove phone number field
|
||||
- Use field enrichment to hide known fields
|
||||
|
||||
**Page Content**
|
||||
- Optimize demo page content with benefits above form
|
||||
- Add product video or GIF showing demo experience
|
||||
- Include "What You'll Learn" section
|
||||
- Add customer testimonials near form
|
||||
- Address common objections in FAQ
|
||||
|
||||
**CTA & Routing**
|
||||
- Test demo button CTAs ("Book Your Demo" vs. "Schedule 15-Min Call")
|
||||
- Offer on-demand demo alongside live option
|
||||
- Personalize demo page messaging based on visitor data
|
||||
- Remove navigation to reduce distractions
|
||||
- Optimize routing: calendar link for qualified, self-serve for others
|
||||
|
||||
---
|
||||
|
||||
### Resource/Blog Page Experiments
|
||||
|
||||
**Content CTAs**
|
||||
- Add floating or sticky CTAs on blog posts
|
||||
- Test inline CTAs within content vs. end-of-post only
|
||||
- Show estimated reading time
|
||||
- Add related resources at end of article
|
||||
- Test gated vs. free content strategies
|
||||
|
||||
**Resource Section**
|
||||
- Optimize resource section navigation and filtering
|
||||
- Add search functionality
|
||||
- Highlight featured or popular resources
|
||||
- Test grid vs. list view layouts
|
||||
- Create resource bundles by topic
|
||||
**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)
|
||||
|
||||
---
|
||||
|
||||
## Task-Specific Questions
|
||||
|
||||
|
||||
1. What's your current conversion rate and goal?
|
||||
2. Where is traffic coming from?
|
||||
3. What does your signup/purchase flow look like after this page?
|
||||
4. Do you have any user research, heatmaps, or session recordings?
|
||||
4. Do you have user research, heatmaps, or session recordings?
|
||||
5. What have you already tried?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **signup-flow-cro**: If the issue is in the signup process itself, not the page leading to it
|
||||
- **signup-flow-cro**: If the issue is in the signup process itself
|
||||
- **form-cro**: If forms on the page need optimization
|
||||
- **popup-cro**: If considering popups as part of the conversion strategy
|
||||
- **copywriting**: If the page needs a complete copy rewrite rather than CRO tweaks
|
||||
- **popup-cro**: If considering popups as part of the strategy
|
||||
- **copywriting**: If the page needs a complete copy rewrite
|
||||
- **ab-test-setup**: To properly test recommended changes
|
||||
|
||||
Reference in New Issue
Block a user