product-page-optimization
Generates A/B test plans and optimization checklists for your App Store product page — icon, screenshots, and app previews. Use when running Product Page Optimization tests or improving conversion rates.
What this skill does
# Product Page Optimization Generator Create structured A/B test plans for App Store Product Page Optimization (PPO), including test hypotheses, variant designs, success metrics, and iteration strategy. ## When This Skill Activates Use this skill when the user: - Asks to "optimize product page" or "A/B test App Store page" - Mentions "product page optimization" or "PPO" - Wants to improve "App Store conversion rate" - Asks about "screenshot testing" or "icon testing" - Mentions improving download rate or tap-through rate ## How PPO Works - Test up to **3 treatments** against your original (control) - Testable elements: **app icon**, **screenshots**, **app previews** - Traffic split: Evenly distributed among variants - Duration: Apple recommends minimum 7 days (typically run 14-28 days) - Statistical confidence: Apple shows results when statistically significant - Localization: Tests can run in specific localizations ### Important Limitations - Cannot test: app name, subtitle, description, keyword field, or price - One test at a time per localization - Results apply to organic App Store traffic only - Minimum traffic required for statistical significance ### Minimum Traffic Thresholds **PPO requires sufficient impression volume to produce meaningful results.** If the app doesn't meet these thresholds, skip A/B testing and make direct qualitative improvements instead. | Monthly Impressions | Can You PPO? | Recommendation | |--------------------|--------------|----| | **Under 1,000** | No | Don't bother — tests will never reach significance. Apply screenshot best practices directly. | | **1,000-5,000** | Barely | Test ONE element at a time with only 1 variant (A/B, not A/B/C). Expect 4-8 week test cycles. | | **5,000-20,000** | Yes | Standard testing. Run 2 variants per test, 2-4 week cycles. | | **20,000+** | Aggressively | Test 3 variants, rapid iteration. Can test icon + screenshots sequentially. | **If below threshold:** Focus on qualitative improvements (follow the Quick Win Checklist in the output) rather than running inconclusive A/B tests. ## Configuration Questions Ask user via AskUserQuestion: 1. **What do you want to test?** - App icon variants - Screenshot order/design - App preview video - Multiple elements (run sequentially) 2. **What's your current conversion rate concern?** - Low impression-to-page-view rate (need better icon/name) - Low page-view-to-download rate (need better screenshots/description) - Low overall conversion (need comprehensive optimization) - Don't know (need baseline measurement) 3. **Monthly impression volume?** - Under 1,000 (PPO may not reach significance — focus on qualitative improvements) - 1,000-10,000 (test one element at a time, longer test duration) - 10,000-100,000 (can test 2-3 variants, standard duration) - 100,000+ (can test aggressively, quick results) ## Generation Process ### Step 1: Audit Current Page Review the existing product page: - Current screenshot sequence and messaging - Icon design and distinctiveness - App preview presence and quality - Promotional text and description ### Step 2: Generate Test Plan Produce a structured test plan with: - Hypothesis for each test - Variant descriptions - Expected impact - Duration and traffic requirements ### Step 3: Design Variant Specs For each variant, specify: - What changes from control - Design direction and mockup description - Why this variant might outperform ## Output Format ```markdown # Product Page Optimization Plan: [App Name] ## Current State Assessment | Element | Current | Strength | Weakness | |---------|---------|----------|----------| | Icon | [Description] | [What works] | [What doesn't] | | Screenshots | [Description] | [What works] | [What doesn't] | | Preview | [Present/Absent] | [What works] | [What doesn't] | | Promo Text | [Description] | [What works] | [What doesn't] | **Estimated current conversion rate**: [X%] (category average: [Y%]) --- ## Test 1: [Element Being Tested] ### Hypothesis "If we [change], then [metric] will improve because [rationale]." ### Variants | Variant | Description | Key Difference from Control | |---------|-------------|---------------------------| | Control (A) | [Current design] | — | | Treatment B | [Description] | [What's different] | | Treatment C | [Description] | [What's different] | ### Test Configuration - **Element**: [Icon / Screenshots / Preview] - **Localization**: [All / Specific locale] - **Duration**: [14-28 days] - **Traffic requirement**: [~X impressions per variant] - **Success metric**: [Conversion rate improvement > X%] ### Design Specs per Variant [Detailed specs for each variant] --- ## Test 2: [Next Element] [Same format — run after Test 1 concludes] --- ## Testing Roadmap | Order | Test | Element | Duration | Expected Lift | |-------|------|---------|----------|--------------| | 1 | [Name] | [Element] | [Weeks] | [%] | | 2 | [Name] | [Element] | [Weeks] | [%] | | 3 | [Name] | [Element] | [Weeks] | [%] | ## Quick Win Checklist While waiting for PPO results, implement these proven improvements: - [ ] First screenshot shows core value in under 2 seconds - [ ] Screenshots use benefit-focused captions (not feature names) - [ ] App preview starts with the "wow moment" in first 3 seconds - [ ] Icon is distinct and recognizable at small sizes - [ ] Promotional text includes a current hook or seasonal relevance ``` ## Common Test Ideas ### Icon Tests | Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | Color | Current color | Contrasting color | Higher tap-through from search | | Style | 3D/detailed | Flat/minimal | Modernized perception | | Element | Full logo | Key symbol only | Better small-size recognition | | Background | Solid | Gradient | Shelf standout | ### Screenshot Tests | Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | First screenshot | Feature-focused | Benefit-focused | Higher engagement | | Layout | Device frames | Full-bleed | More immersive | | Text | Feature names | User outcomes | Stronger conversion | | Order | Standard flow | Problem→Solution | Better storytelling | | Social proof | None | Reviews/awards | Trust building | ### App Preview Tests | Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | Hook | Slow intro | Immediate action | Higher watch-through | | Length | 30 seconds | 15 seconds | Less drop-off | | Style | Screen recording | Lifestyle + UI | Emotional connection | ## Seasonal Optimization Calendar | Season | Focus | Screenshot Refresh | |--------|-------|-------------------| | Jan | New Year energy, fresh starts | Resolution-themed captions | | Mar-Apr | Spring cleaning, organization | Productivity-focused | | Jun | WWDC, new OS features | "Updated for iOS [X]" | | Aug-Sep | Back to school | Student/education focus | | Nov-Dec | Holiday, gift-giving | Gift-worthy messaging | ## References - Related: `generators/custom-product-pages` — Targeted pages per audience - Related: `app-store/screenshot-planner` — Screenshot design guidance - Related: `app-store/keyword-optimizer` — Text optimization - Related: `app-store/marketing-strategy` — Overall optimization strategy
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".