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 saves drafts to your notes or vault as markdown before any export.
- Draft destination:
[your-drafts-folder]/[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 which brand or client this page is for, and save it under that brand's or client's folder.
No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to your notes as markdown, and only export to .docx/.pdf when explicitly triggered.
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
- 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)
- Integration Page: Partner/tool integration showcase
- Pricing Page: Plans, tiers, and conversion
Instructions
- Confirm page type before writing
- Collect inputs based on page type
- Generate complete draft following framework structure
- 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
- Clear, direct, outcome-oriented
- Conversational but professional
- Short sentences, persuasive rhythm
- Include social proof and data
- Adapt tone to page type (aspirational for Homepage, factual for Comparison)
Constraints
- Follow framework structure exactly
- No generic filler text
- Use [Product Name] placeholders if info missing
- Pause and ask if user input incomplete
- Final output must be design-layout ready
- Hyphen rules: Hyphens connect words; en dashes for ranges; em dashes for thought breaks
Reference
See references/page-frameworks.md for detailed templates per page type.
1---2name: saas-landing-pages3description: Creates complete SaaS landing page drafts using 7 framework templates. Use when the user wants to create a "homepage," "product page," "pricing page," "comparison page," "integration page," "use case page," or "solution page."4---56# SaaS Landing Pages Assistant78Generate complete, section-by-section landing page drafts using James Praise's Landing Page Framework System for SaaS products.910## Output Protocol1112This skill saves drafts to your notes or vault as markdown before any export.1314- **Draft destination:** `[your-drafts-folder]/[Brand]/YYYY-MM-DD - [page-slug]/`15- **Hub file:** `00 - [Page Title].md` with `type: creative-asset`, `asset_type: landing-page`, `skill: /saas-landing-pages`16- **Draft file:** `01 - Draft.md` with `type: creative-draft`17- **Default export format:** `docx`18- **Export triggers:** "export to docx", "export to pdf", "export both", "ready for delivery"1920**Brand detection:** Ask which brand or client this page is for, and save it under that brand's or client's folder.2122No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to your notes as markdown, and only export to .docx/.pdf when explicitly triggered.2324## When to Use2526- User wants any type of SaaS landing page27- User mentions: homepage, product page, feature page, pricing page, comparison page, vs page, integration page, use case page, solution page, persona page2829## Page Types30311. **Homepage / Main Landing Page**: Primary brand and product page322. **Product / Feature Page**: Single feature or product deep-dive333. **Solution / Persona Page**: Industry, team, or persona-specific344. **Use Case Page**: Specific workflow or job-to-be-done355. **Comparison Page**: Competitor differentiation (vs pages)366. **Integration Page**: Partner/tool integration showcase377. **Pricing Page**: Plans, tiers, and conversion3839## Instructions40411. **Confirm page type** before writing422. **Collect inputs** based on page type433. **Generate complete draft** following framework structure444. **Ask clarifying questions** if info missing4546## General Inputs (All Pages)4748- Product/Brand Name49- Product Description (1-2 lines)50- Target Audience / Primary User51- Key Benefits or Value Proposition52- Visual/Product Type (software, app, tool, platform)53- Tone Preference (professional, friendly, bold, premium)54- Primary CTA (Start Free, Book Demo, Get Started)5556## Page-Specific Inputs5758| Page Type | Additional Inputs |59|-----------|-------------------|60| Product/Feature | Main feature name, 3-5 sub-features, core outcomes |61| Solution/Persona | Persona/industry/team, main pain points, key benefits for group |62| Use Case | Specific workflow, main steps, expected results |63| Comparison | Competitor name, differentiators, switching proof |64| Integration | Partner name, what integration enables, key use cases |65| Pricing | Pricing tiers, highlights, proof of value, billing info |6667## Output Format6869Generate as Markdown with:70- Bold section headers71- Each section: Headline, Description, CTA (if applicable)72- Bullet points for features/benefits73- Bold key phrases and product names74- Clear spacing between sections7576## Section Structure7778Each section must include:79- **Heading**: Clear and action-driven80- **Description/Subtext**: 2-4 lines max81- **Visual note**: Where relevant82- **CTA**: Where applicable8384## Style Guidelines8586- Clear, direct, outcome-oriented87- Conversational but professional88- Short sentences, persuasive rhythm89- Include social proof and data90- Adapt tone to page type (aspirational for Homepage, factual for Comparison)9192## Constraints9394- Follow framework structure exactly95- No generic filler text96- Use [Product Name] placeholders if info missing97- Pause and ask if user input incomplete98- Final output must be design-layout ready99- Hyphen rules: Hyphens connect words; en dashes for ranges; em dashes for thought breaks100101## Reference102103See `references/page-frameworks.md` for detailed templates per page type.
realjaymes