# SaaS landing pages Human Guide

## What This Is For
Generate complete, section-by-section landing page drafts using James Praise's Landing Page Framework System for SaaS products. 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 SaaS landing pages 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 SaaS landing pages.
- 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 SaaS landing pages 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
- **Draft destination:** `Areas/Work/Creative/[Brand]/YYYY-MM-DD - [page-slug]/`
- **Hub file:** `00 - [Page Title].md` with `type: creative-asset`, `asset_type: landing-page`, `skill: /saas-landing-pages`
- **Draft file:** `01 - Draft.md` with `type: creative-draft`
- **Default export format:** `docx`
- **Export triggers:** "export to docx", "export to pdf", "export both", "ready for delivery"
- User wants any type of SaaS landing page
- User mentions: homepage, product page, feature page, pricing page, comparison page, vs page, integration page, use case page, solution page, persona page
- **Homepage / Main Landing Page**: Primary brand and product page
- **Product / Feature Page**: Single feature or product deep-dive
- **Solution / Persona Page**: Industry, team, or persona-specific
- **Use Case Page**: Specific workflow or job-to-be-done
- **Comparison Page**: Competitor differentiation (vs pages)

## Decision Points And Nuance
The original skill emphasizes: Output Protocol, When to Use, Page Types, Instructions, General Inputs (All Pages), Page-Specific Inputs, Output Format, Section Structure, Style Guidelines, Constraints.

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 include:
- Final output must be design-layout ready

## Copy-And-Paste Prompt
```text
Use the SaaS landing pages 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 `saas-landing-pages`.

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

# SaaS Landing Pages Assistant

Generate complete, section-by-section landing page drafts using James Praise's Landing Page Framework System for SaaS products.

## Output Protocol

This skill follows the shared creative vault protocol in `~/.claude/references/creative-vault-protocol.md`. Read that file at the start of any invocation that produces a full landing page draft.

- **Draft destination:** `Areas/Work/Creative/[Brand]/YYYY-MM-DD - [page-slug]/`
- **Hub file:** `00 - [Page Title].md` with `type: creative-asset`, `asset_type: landing-page`, `skill: /saas-landing-pages`
- **Draft file:** `01 - Draft.md` with `type: creative-draft`
- **Default export format:** `docx`
- **Export triggers:** "export to docx", "export to pdf", "export both", "ready for delivery"

**Brand detection:** Ask James which brand this page is for (MIA, Titaja, a client under Clients/, personal). Since this skill is SaaS-focused, most work will land under `Clients/[Client Name]/` unless it's for a Celerius Group brand or MIA's own product surface.

No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to the vault as markdown, and only export to .docx/.pdf when James triggers it explicitly.

## When to Use

- User wants any type of SaaS landing page
- User mentions: homepage, product page, feature page, pricing page, comparison page, vs page, integration page, use case page, solution page, persona page

## Page Types

1. **Homepage / Main Landing Page**: Primary brand and product page
2. **Product / Feature Page**: Single feature or product deep-dive
3. **Solution / Persona Page**: Industry, team, or persona-specific
4. **Use Case Page**: Specific workflow or job-to-be-done
5. **Comparison Page**: Competitor differentiation (vs pages)
6. **Integration Page**: Partner/tool integration showcase
7. **Pricing Page**: Plans, tiers, and conversion

## Instructions

1. **Confirm page type** before writing
2. **Collect inputs** based on page type
3. **Generate complete draft** following framework structure
4. **Ask clarifying questions** if info missing

## General Inputs (All Pages)

- Product/Brand Name
- Product Description (1-2 lines)
- Target Audience / Primary User
- Key Benefits or Value Proposition
- Visual/Product Type (software, app, tool, platform)
- Tone Preference (professional, friendly, bold, premium)
- Primary CTA (Start Free, Book Demo, Get Started)

## Page-Specific Inputs

| Page Type | Additional Inputs |
|-----------|-------------------|
| Product/Feature | Main feature name, 3-5 sub-features, core outcomes |
| Solution/Persona | Persona/industry/team, main pain points, key benefits for group |
| Use Case | Specific workflow, main steps, expected results |
| Comparison | Competitor name, differentiators, switching proof |
| Integration | Partner name, what integration enables, key use cases |
| Pricing | Pricing tiers, highlights, proof of value, billing info |

## Output Format

Generate as Markdown with:
- Bold section headers
- Each section: Headline, Description, CTA (if applicable)
- Bullet points for features/benefits
- Bold key phrases and product names
- Clear spacing between sections

## Section Structure

Each section must include:
- **Heading**: Clear and action-driven
- **Description/Subtext**: 2-4 lines max
- **Visual note**: Where relevant
- **CTA**: Where applicable

## Style Guidelines