download-page-generator
When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
Best use case
download-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
Teams using download-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/download/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How download-page-generator Compares
| Feature / Agent | download-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.