SaaS Landing Skill
Produce a single-page SaaS landing. Agent, follow this workflow exactly.
1. Read context
Before writing anything:
- Read
DESIGN.md in the current working directory. If missing, stop and ask for one.
- Identify the color palette, typography tokens, and layout principles.
- Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.
2. Plan sections
Required sections, in order:
- Hero — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the hero_density parameter as vertical padding in px.
- Features — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.
- Social proof —
proof_count logos or testimonials. If 0, skip this section.
- Pricing — 2–3 tiers. Include only if
has_pricing is true.
- Footer CTA — large accent-colored band with one-button call to action.
- Footer — minimal: links + copyright.
3. Apply design system
- All colors must come from DESIGN.md tokens. Do not invent hex values.
- Typography: use the declared display font for headlines, body font for everything else.
- Layout: respect the grid, max-width, and section spacing rules.
- Components: use declared button/card/input patterns. Do not add shadows if DESIGN.md's Depth & Elevation says minimal.
- Accent: use the accent color only once in the hero, once in the footer CTA, and for all links. Do not flood the page.
4. Write the file
Output a single self-contained index.html with:
- All CSS inlined in a
<style> block in <head>.
- System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc.
- No external JS.
- Semantic HTML (
<header>, <main>, <section>, <footer>).
- Each editable element tagged with
data-od-id="<unique-slug>" so the host app's comment mode can target it.
5. Self-check
Before finishing, verify:
6. Done
Write only index.html. Do not generate a separate CSS file, JS file, or README.
For skill authors reading this as a reference
This is a minimal but complete skill. Structure:
saas-landing-skill/
├── SKILL.md ← you are here
└── assets/
└── base.html (optional starter template; this skill doesn't use one)
Things to notice:
- The
od: front-matter block is optional for Claude-Code-only compatibility, but adding it lights up OD's typed inputs, sliders, preview metadata, and capability gating.
- The workflow below the front-matter is plain Markdown that the agent reads as its system prompt.
- DESIGN.md is treated as a collaborator, not an override. The skill gives the agent authority to override when the brief conflicts, but never to invent new tokens.
data-od-id tagging is how we wire elements to comment mode. Skills that want comment-mode compatibility must annotate their output.
See ../../skills-protocol.md for the full protocol.
1---2name: saas-landing-skill3description: Single-page SaaS landing with hero, features, social proof, pricing, and CTA. Respects the active DESIGN.md color/typography/layout tokens. Trigger keywords: "saas landing", "marketing page", "product landing".4---56# SaaS Landing Skill78Produce a single-page SaaS landing. Agent, follow this workflow exactly.910## 1. Read context1112Before writing anything:13- Read `DESIGN.md` in the current working directory. If missing, stop and ask for one.14- Identify the color palette, typography tokens, and layout principles.15- Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.1617## 2. Plan sections1819Required sections, in order:201. **Hero** — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the hero_density parameter as vertical padding in px.212. **Features** — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.223. **Social proof** — `proof_count` logos or testimonials. If 0, skip this section.234. **Pricing** — 2–3 tiers. Include only if `has_pricing` is true.245. **Footer CTA** — large accent-colored band with one-button call to action.256. **Footer** — minimal: links + copyright.2627## 3. Apply design system2829- All colors must come from DESIGN.md tokens. Do not invent hex values.30- Typography: use the declared display font for headlines, body font for everything else.31- Layout: respect the grid, max-width, and section spacing rules.32- Components: use declared button/card/input patterns. Do not add shadows if DESIGN.md's Depth & Elevation says minimal.33- Accent: use the accent color only once in the hero, once in the footer CTA, and for all links. Do not flood the page.3435## 4. Write the file3637Output a single self-contained `index.html` with:38- All CSS inlined in a `<style>` block in `<head>`.39- System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc.40- No external JS.41- Semantic HTML (`<header>`, `<main>`, `<section>`, `<footer>`).42- Each editable element tagged with `data-od-id="<unique-slug>"` so the host app's comment mode can target it.4344## 5. Self-check4546Before finishing, verify:47- [ ] All text is content-meaningful, not lorem ipsum (use product_name and tagline inputs; generate plausible specific copy for the rest).48- [ ] No broken color references (every CSS color value is in DESIGN.md's palette or a valid alpha/fallback variant).49- [ ] Responsive breakpoints match DESIGN.md's Responsive Behavior section.50- [ ] The page looks good at 1440w, 768w, and 375w (mentally simulate).51- [ ] Accent used no more than twice total.5253## 6. Done5455Write only `index.html`. Do not generate a separate CSS file, JS file, or README.5657---5859## For skill authors reading this as a reference6061This is a minimal but complete skill. Structure:6263```64saas-landing-skill/65├── SKILL.md ← you are here66└── assets/67 └── base.html (optional starter template; this skill doesn't use one)68```6970Things to notice:71- The `od:` front-matter block is optional for Claude-Code-only compatibility, but adding it lights up OD's typed inputs, sliders, preview metadata, and capability gating.72- The workflow below the front-matter is plain Markdown that the agent reads as its system prompt.73- DESIGN.md is treated as a collaborator, not an override. The skill gives the agent authority to override when the brief conflicts, but never to invent new tokens.74- `data-od-id` tagging is how we wire elements to comment mode. Skills that want comment-mode compatibility must annotate their output.7576See [`../../skills-protocol.md`](../../skills-protocol.md) for the full protocol.
onfire7777