download-page-generator
The download-page-generator skill guides creation and optimization of desktop and mobile app download pages. It provides structure for presenting value propositions, platform-specific download options, trust signals, and visual proof to maximize conversion from visitor to installer. Use it when creating a new download page, auditing an existing one, or optimizing for better performance across Windows, macOS, Linux, iOS, and Android platforms.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/download-page-generator && cp -r /tmp/download-page-generator/skills/pages/marketing/download ~/.claude/skills/download-page-generatorSKILL.md
# Pages: Download Page Guides download page structure and optimization for desktop and mobile app downloads. Purpose: convert visitors into installers by clearly presenting value, platform options, and trust signals. **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 it for product, audience, and value proposition. Identify: 1. **App type**: Desktop (Windows, macOS, Linux) or mobile (iOS, Android, both) 2. **Traffic source**: Organic, paid, email, referral 3. **Distribution**: App Store / Play Store only, direct download, or both ## Page Purpose | Purpose | Goal | |---------|------| | **Download** | Guide users to install desktop or mobile app | | **Trust** | Build confidence before download (security, privacy, reviews) | | **Conversion** | Maximize download rate, store visits, install conversion | ## Download Page Structure | Step | Purpose | Elements | |------|---------|----------| | **1. Value proposition** | Why download | Headline, benefit-focused copy, key features | | **2. Platform selection** | Clear path | Desktop: OS detection or manual pick; Mobile: App Store / Play Store buttons | | **3. Trust signals** | Reduce friction | Ratings, download count, security badges, privacy note | | **4. Visual proof** | Show the app | Screenshots, app previews, video | | **5. CTA** | Primary action | Single, prominent download button | ## Platform-Specific Layout ### Desktop App - **OS detection**: Auto-detect OS or show "Download for Windows / macOS / Linux" - **Direct download**: One-click .exe / .dmg / .deb etc. - **Alternatives**: Optional "Other platforms" or "Command line" for power users ### Mobile App - **Dual store**: App Store + Play Store buttons side by side - **Smart redirect**: Detect device and show relevant store first; still show both - **QR code**: Optional for desktop visitors to scan and install on phone ## Optimization Best Practices ### Performance - **Load time**: Under 3 seconds; each extra second can cost ~7% conversion - **Mobile-first**: Most app download traffic is mobile; responsive, thumb-reachable CTAs - **Image optimization**: WebP, lazy loading, compression (e.g. TinyPNG, ImageOptim) ### Conversion - **Single primary CTA**: "Download Free Now," "Get on App Store," "Get for Windows" - **Above the fold**: CTA visible without scrolling - **Repeat CTA**: On longer pages, repeat at logical points - **A/B test**: CTA color, size, copy, placement ### Trust & Social Proof - **Star ratings**: Show App Store / Play Store ratings - **Download count**: "10M+ downloads," "Trusted by X users" - **Testimonials**: User quotes, media logos - **Security**: Security badges if collecting sensitive info ### Content - **Top 3–5 features**: Benefit-focused, scannable bullet points - **Screenshots**: High-quality, show app in action - **Video**: App preview or demo video ### Alignment with Traffic - **Ads**: If from PPC, ensure message matches ad (offer, platform); see **paid-ads-strategy** - **Email**: Match campaign message and CTA ## Output Format - **Headline** and subheadline - **Structure** (5-step flow sections) - **Platform layout** (desktop vs mobile) - **CTA** copy and placement - **Trust signals** placement - **SEO** metadata (if page is indexed) ## Related Skills ### Pages - **landing-page-generator**: Download page is a type of landing page; apply LP principles - **homepage-generator**: Homepage often links to download page - **features-page-generator**: Feature copy for "Explain value" section ### Components - **hero-generator**: Hero section (value proposition) - **cta-generator**: Download button design - **trust-badges-generator**: Social proof, ratings - **testimonials-generator**: User testimonials ### SEO - **title-tag, meta-description, page-metadata**: Download page metadata
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.