conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.
What this skill does
# Strategies: Conversion Optimization Guides conversion rate optimization (CRO): increasing the percentage of visitors who complete desired actions. Higher conversion rates mean increased revenue, reduced CAC, and better ROI. Use this skill when optimizing funnels, running experiments, or reducing friction on high-traffic pages. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 4 (Audience), 5 (Website), 6 (Keywords). Identify: 1. **Funnel stage**: Awareness, consideration, decision, post-purchase 2. **Conversion goal**: Signup, purchase, download, demo request 3. **Traffic**: Volume; mobile vs desktop split 4. **Current conversion rate**: Baseline for improvement ## CRO Process | Step | Action | |------|--------| | **1. Research** | Map funnel; identify high-traffic, low-conversion pages | | **2. Hypothesize** | Form testable hypothesis (if X, then Y because Z) | | **3. Prioritize** | Score by Potential, Importance, Ease (PIE) | | **4. Test** | A/B or multivariate; adequate sample size | | **5. Analyze** | Statistical significance; implement winner | ## PIE Prioritization Framework Score each test idea 1–10: | Factor | Question | |--------|----------| | **Potential** | How much improvement is possible? | | **Importance** | How much traffic does this page get? | | **Ease** | How easy to implement? | Rank backlog by total score; run highest-impact tests first. ## A/B Testing Best Practices | Practice | Guideline | |----------|-----------| | **Sample size** | Calculate minimum before launch; 95% significance without adequate sample = false positives | | **Duration** | Run full week cycles; account for day-of-week effects | | **One variable** | Test one element per experiment (or use MVT for multiple) | | **Mobile separate** | Mobile converts ~50% of desktop; test mobile independently—thumb reach, form complexity differ | | **Low traffic** | Use Bayesian testing for faster, actionable results | ## Key Testing Areas | Page Type | Test Ideas | |-----------|------------| | **Homepage** | Search bar prominence; personalized content; hero CTA; social proof placement | | **Landing page** | Headline; form length; CTA copy; above-fold layout | | **Product/Category** | Quick view; descriptions; add-to-cart placement | | **Checkout** | Form fields; progress indicator; trust badges; guest checkout | | **Pricing** | Plan order; anchoring; CTA per tier | **Personalization**: Personalized experiences generate ~41% more impact than generic ones. ## Commercialization Infrastructure | Module | Purpose | |--------|---------| | **Data & BI** | Data warehouse; user behavior events; agile surveys | | **A/B testing** | Experiment platform; statistical significance; backend-controlled variants | | **User education** | Help docs (multi-language); update notifications; EDM | | **Attribution** | Ad pixels; attribution model; impression-to-click-to-sale tracking | **Avoid**: Intrusive interstitials; popups that block content. Prefer non-intrusive ad formats. ## Foundational Requirements - **Analytics**: Map funnels; identify drop-off points (analytics-tracking, traffic-analysis) - **Qualitative**: Heatmaps, session recordings, user tests—understand *why* drop-off occurs - **Technical**: Dedicated resources for 2–4 tests/month; maintain momentum ## Output Format - **Funnel map** (stages, conversion rates, drop-off) - **Hypothesis** (if X, then Y because Z) - **Test plan** (variant, metric, sample size, duration) - **Implementation** checklist ## Related Skills - **landing-page-generator**: Landing page structure and copy - **cta-generator**: CTA design and placement - **analytics-tracking**: GA4, events, conversion tracking - **traffic-analysis**: Attribution, funnel analysis - **copywriting**: Headline, CTA copy for tests
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".