landing-page-design
Create high-converting, visually distinctive landing pages. Use when building marketing pages, product launches, SaaS homepages, or any single-page conversion-focused website. Guides section-by-section composition with anti-AI-slop principles.
What this skill does
# Landing Page Design ## Overview Build landing pages that convert AND captivate. This skill combines conversion-focused structure with distinctive visual design to create pages that stand out in an AI-saturated world. The goal: pages worth $50-100 that you'd be proud to sell. ## MANDATORY: Vibe Discovery (Do This First) **BEFORE writing any code, you MUST run the Vibe Discovery process.** This isn't a lookup table - it's a creative prompt that generates a UNIQUE aesthetic direction every time. The goal: No two landing pages should look alike, even for similar products. --- ### The Vibe Discovery Process **Ask the user these questions, then SYNTHESIZE a unique direction. Don't just map answers to presets.** #### Step 1: Gather Context (Ask These) **Q1: What's one real-world place or object this brand would be?** > Not "what industry" - an actual specific thing. A Tokyo convenience store at 2am. A grandmother's kitchen. A brutalist parking garage. A coral reef. The cockpit of a 747. A flea market in Marrakech. A 1970s recording studio. **Q2: What's the ONE emotion someone should feel in the first 3 seconds?** > Pick ONE: Calm. Energized. Curious. Trusted. Delighted. Impressed. Rebellious. Nostalgic. Inspired. Amused. Sophisticated. Welcomed. Intrigued. Confident. **Q3: Pick TWO unexpected influences to collide:** > Examples: "medical packaging + skateboard graphics", "spreadsheets + street art", "luxury hotel + punk zine", "NASA mission control + kindergarten", "Japanese convenience store + Victorian library" **Q4: What should this page NEVER be mistaken for?** > Name 2-3 specific things to actively avoid. "A crypto project", "A wellness app", "Something made by a bank", "Anything with purple gradients" #### Step 2: Invent The Aesthetic (Don't Look Up - Create) Based on the answers, CREATE a unique vibe by deciding: **COLOR INVENTION** (Don't use memorized palettes - derive from the place/object) - What colors exist in that real-world place/object from Q1? - Extract 3-4 colors that feel authentic to that reference - Invent specific hex codes fresh - don't reuse codes from previous projects - Name your palette something evocative (not "blue and orange" but "Midnight Bodega" or "Rust Belt Morning") **TYPOGRAPHY INVENTION** (Match the voice to the collision) - What would text sound like in that place? - Find a display font that embodies the collision from Q3 - Don't default to your usual choices - browse Google Fonts with fresh eyes - Consider: weight, width, contrast, quirks **LAYOUT INVENTION** (Derive from the physical space) - How is space organized in that place from Q1? - Is it cramped or expansive? Grid-like or organic? Vertical or horizontal? - What unexpected layout choice would embody the collision from Q3? **MOTION INVENTION** (Match the emotion) - How does the emotion from Q2 move? - Calm = barely perceptible. Energized = kinetic. Sophisticated = slow and deliberate. - What's ONE signature motion that defines this page? #### Step 3: Write Your Vibe Spec Before coding, write this out explicitly: ``` VIBE NAME: [Invent a 2-3 word name] REFERENCE: [The place/object from Q1] EMOTION: [From Q2] COLLISION: [From Q3] ANTI-PATTERNS: [From Q4] COLORS: - Primary: [hex] - [why this color] - Secondary: [hex] - [why] - Background: [hex] - [why] - Accent: [hex] - [why] - Palette name: [evocative name] TYPOGRAPHY: - Display: [specific font name] - [why it fits] - Body: [specific font name] - [why] - Character: [describe the voice] LAYOUT: - Density: [sparse/balanced/dense] - Shapes: [sharp/rounded/organic/mixed] - Signature element: [one unusual layout choice] MOTION: - Level: [still/subtle/moderate/dynamic/chaotic] - Signature animation: [one specific animation that defines this] WILDCARD: - One unexpected detail that doesn't "match" but makes it memorable ``` #### Step 4: The Freshness Check Before proceeding, verify: - [ ] I did NOT reuse hex codes from my last 3 projects - [ ] I did NOT default to my "comfortable" fonts (check: am I using Inter? Nunito? Space Grotesk? If yes, find something else) - [ ] The collision from Q3 is actually visible in my choices - [ ] Someone could NOT mistake this for my previous landing pages - [ ] I included a wildcard that surprises even me --- ### Example Vibe Discovery **Q1 - Place/Object:** "A Japanese train station at rush hour" **Q2 - Emotion:** "Confident" **Q3 - Collision:** "Transit signage + haute couture" **Q4 - Never mistaken for:** "A meditation app, anything whimsical, startup-bro tech" **Generated Vibe Spec:** ``` VIBE NAME: Shinjuku Runway REFERENCE: Japanese train station at rush hour EMOTION: Confident COLLISION: Transit signage + haute couture ANTI-PATTERNS: No soft gradients, no playful illustrations, no rounded friendly shapes COLORS: - Primary: #1a1a1a - the black of train doors - Secondary: #f5f5f0 - platform concrete, worn smooth - Background: #fafaf8 - fluorescent-lit white - Accent: #e60012 - JR line red, commanding attention - Palette name: "Platform Edge" TYPOGRAPHY: - Display: Darker Grotesque - confident, slightly condensed, European edge - Body: Noto Sans JP - clean utility, transit-inspired - Character: Authoritative but not cold. Clear. Directional. LAYOUT: - Density: Rich but organized - like a station map - Shapes: Sharp with intentional rounded exceptions (like train windows) - Signature element: Strong horizontal bands that divide sections like train schedules MOTION: - Level: Subtle but precise - Signature animation: Elements slide in from the side like arriving trains - horizontal, smooth, with exact timing WILDCARD: - One element uses a fabric-like texture overlay - the haute couture collision ``` --- ### Inspiration Starters (When Stuck on Q1) **Spaces:** Night market in Bangkok | Empty museum at closing | Airport lounge at 4am | Vintage record store | Hospital waiting room | Casino floor | Greenhouse in winter | Subway platform | Observatory dome | Abandoned factory | Luxury yacht interior | 24-hour laundromat | Library rare books room | Auto body shop | Space station module **Objects:** 1980s synthesizer | Surgical instruments | Vintage luggage | Racing motorcycle | Antique compass | Industrial loom | Neon sign | Typewriter | Scientific glassware | Leather-bound book | Circuit board | Porcelain dishware **Eras/Movements:** Soviet constructivism | Memphis design | Swiss international | Art nouveau | Bauhaus | De Stijl | Googie architecture | Streamline moderne | Brutalism | Japanese metabolism | Scandinavian modernism | Italian futurism --- ### The Anti-Convergence Rules 1. **No hex code memory** - Generate colors fresh from the reference, don't recall "my usual blue" 2. **Font rotation required** - Cannot use the same display font in consecutive projects 3. **Collision must show** - If someone can't see BOTH influences from Q3, push harder 4. **Wildcard is mandatory** - Every vibe needs one element that doesn't "fit" but makes it unique 5. **Name it** - An unnamed vibe becomes generic. A named vibe has identity. --- ### Quick Context Questions (Minimal Version) If the user just says "make me a landing page" with no context, ask: 1. "What's one place or object that captures this brand's energy?" 2. "What emotion should dominate?" 3. "What should this NEVER look like?" Then synthesize a vibe from those three answers. --- ## The 50% Rule **Spend 50% of your time on the hero section.** It's the cover image for social media, the first impression, the hook. Everything else flows from getting the hero right. ## Section Composition (Top to Bottom) ### 1. Hero Section (Primary Focus) The make-or-break element. Must contain: - **Headline**: Sharp, benefit-driven hook (reference H1 Gallery for inspiration) - **Subheadline**: Supporting context, 1-2 sentences max - **CTA Button(s)**: Primary action + optional secondary - **Social Proof**: Logo marquee, testimonials, or trust badges - **Visual Element**: Product shot, illustration,
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".