# Landing page Human Guide

## What This Is For
Check for product marketing context first: If .agents/product-marketing.md exists (or .agents/product-marketing-context.md or .claude/product-marketing-context.md in older. 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
- User wants to create a new landing page or homepage
- User needs copy for specific landing page sections
- User mentions "landing page template," "homepage copy," or "page sections"
- **Confirm page type**: Homepage, feature page, or campaign landing page
- **Gather inputs**: Product name, value proposition, target audience, key features, social proof
- **Generate section-by-section copy** following the template structure
- **Include visual/CTA notes** for each section
- **Headline**: Action statement explaining unique value proposition
- **Subheadline**: 1-2 sentences explaining product and how it creates value
- **Bullet Points**: 2 specific claims, 2 objection handles, 3 social proof points
- **Social Proof**: Testimonials, logos, ratings, stats
- **Hero CTA**: Action-focused, value-focused, or objection-handling

## Decision Points And Nuance
The original skill emphasizes: When to Use, Instructions, Section Structure, Hero Section, Problem to Solution Comparison, Features, Capabilities & Benefits, Integrations, How It Works, FAQs, Second CTA Section.

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
- Each section must have Headline, Description, and CTA (where applicable)

## 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 realjaymes/marketingagentskills 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 Assistant

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.agents/product-marketing-context.md` or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Generate structured, conversion-focused landing page copy using the modular section framework.

## When to Use

- User wants to create a new landing page or homepage
- User needs copy for specific landing page sections
- User mentions "landing page template," "homepage copy," or "page sections"

## Instructions

1. **Confirm page type**: Homepage, feature page, or campaign landing page
2. **Gather inputs**: Product name, value proposition, target audience, key features, social proof
3. **Generate section-by-section copy** following the template structure
4. **Include visual/CTA notes** for each section

## Section Structure

Generate copy for each section in order:

### Hero Section
- **Headline**: Action statement explaining unique value proposition
- **Subheadline**: 1-2 sentences explaining product and how it creates value
- **Bullet Points**: 2 specific claims, 2 objection handles, 3 social proof points
- **Social Proof**: Testimonials, logos, ratings, stats
- **Hero CTA**: Action-focused, value-focused, or objection-handling

### Problem to Solution Comparison
- **Before vs After**: Pain points vs solution benefits
- **Old Way vs New Way**: Limitations vs capabilities
- **CTA**: Reinforce action

### Features, Capabilities & Benefits
For each feature (3-6 features):
- **Heading**: Feature name
- **Description**: Capability + Benefit
- **Visual note**: Image suggestion
- **CTA**: Feature-specific action

### Integrations
For each integration (2-4):
- **Heading**: Integration name
- **Description**: Capability + Benefit
- **Visual**: Logo placement

### How It Works
For each step (3-5 steps):
- **Heading**: Step title
- **Description**: What user does/gets
- **Visual note**: Screenshot suggestion

### FAQs
- **Feature FAQs**: 2-3 questions about features
- **Objection FAQs**: 2-3 questions addressing concerns

### Second CTA Section
- **Heading**: Switch/upgrade focused
- **Description**: Value outcome statement
- **Bullet Points**: Objection handles + ease of start
- **CTA**: Clear next action

### Founder's Note (Optional)
- Put yourself in their shoes
- Explain their problem
- Take ownership
- Show the happy ending

## Output Format

```markdown
## [Section Name]

**Headline**: [Copy]

**Subheadline**: [Copy]