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.
What this skill does
# 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 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".