# Landing page Human Guide

## What This Is For
Use this skill when the user needs to create or improve a landing page, write above-the-fold copy, structure a sales page, or increase landing page conversion rates. It gives the agent a clearer input/output frame for conversion optimization: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Landing page agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for landing page.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Landing page guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- A landing page has ONE goal. Everything serves that goal or gets cut.
- Structure follows the buyer's internal monologue: "What is this?" -> "Is it for me?" -> "How does it work?" -> "Can I trust it?" -> "What do I do next?"
- Above the fold is the most valuable real estate on the internet.
- Long pages can outperform short pages — IF every section earns its place.
- **Headline** — State the outcome, not the product.
- Be specific: "Cut your deploy time from 45 minutes to 45 seconds"
- **Subheadline** — Add the "how" or a second benefit.
- **Primary CTA** — High contrast, specific action text. "Start building free" not "Get started."
- **Visual** — Product screenshot, short demo, or animated illustration. Show the product in action.
- **Social proof bar** — Logo strip or metric: "Trusted by 15,000+ teams"
- **Connect your repo** — Link your GitHub in one click.
- **Configure your pipeline** — Our AI suggests the optimal setup.

## Decision Points And Nuance
The original skill emphasizes: Core Principles, Workflow, Section-by-Section Build, Hero (Above the Fold), How It Works, Feature Sections, Testimonials, FAQ, Final CTA, Full Page Build.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Must answer for any SaaS:
- Testimonials (use placeholders if I don't have real ones yet)

## Copy-And-Paste Prompt
```text
Use the Landing page human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the whawkinsiv/solo-founder-skills skill entry for `landing-page`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Landing Page

A landing page is a sales conversation, not a brochure. You have 5 seconds to communicate what the product does and why it matters. This skill gives you the structure and copy for every section.

## Core Principles

- A landing page has ONE goal. Everything serves that goal or gets cut.
- Structure follows the buyer's internal monologue: "What is this?" -> "Is it for me?" -> "How does it work?" -> "Can I trust it?" -> "What do I do next?"
- Above the fold is the most valuable real estate on the internet.
- Long pages can outperform short pages — IF every section earns its place.

---

## Workflow

```
Landing Page Build:
- [ ] Define the ONE goal (signup, waitlist, demo request)
- [ ] Write the hero section (headline + subheadline + CTA)
- [ ] Plan sections in scroll order
- [ ] Write copy for each section
- [ ] Build the page
- [ ] Test on mobile
- [ ] Add analytics tracking (see analytics skill)
```

---

## Section-by-Section Build

### Hero (Above the Fold)

The hero has 5 elements. Get these right and the rest is easier.

1. **Headline** — State the outcome, not the product.
   - Be specific: "Cut your deploy time from 45 minutes to 45 seconds"
   - Not: "Deploy faster"
2. **Subheadline** — Add the "how" or a second benefit.
3. **Primary CTA** — High contrast, specific action text. "Start building free" not "Get started."
4. **Visual** — Product screenshot, short demo, or animated illustration. Show the product in action.
5. **Social proof bar** — Logo strip or metric: "Trusted by 15,000+ teams"

**Tell AI:**
```
Write the hero section for our landing page:
- Product: [what it does, one sentence]
- Audience: [who it's for]
- Main benefit: [the #1 outcome users get]
- Social proof: [number of users, notable customers, or key metric]

Give me:
- 3 headline options (under 10 words each, outcome-focused)
- Subheadline for each (adds "how" or second benefit)
- Primary CTA button text + anxiety reducer below it
- Social proof line
Pick the strongest option and explain why.
```

### How It Works

Exactly 3 steps. Cognitive simplicity.

Format: [Number/Icon] + [Short title] + [One sentence]

Example:
1. **Connect your repo** — Link your GitHub in one click.
2. **Configure your pipeline** — Our AI suggests the optimal setup.
3. **Ship with confidence** — Deploy automatically on every push.

### Feature Sections

Alternate layout: text-left/image-right, then text-right/image-left.

Each feature: [Eyebrow label] + [Benefit headline] + [2-3 sentence description] + [Screenshot]

Lead with benefit, not feature name:
- BAD: "Advanced Analytics Dashboard"
- GOOD: "Know exactly what's working — and what's not"

### Testimonials