SaaS Landing Skill
SkillMediasaas-landing is an agent skill that builds a single-page SaaS landing site. It reads the project's DESIGN.md, restricts all colors, fonts, and layout choices to the tokens defined there, and writes one self-contained index.html with hero, features, social proof, pricing, and CTA sections.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a DESIGN.md file in the working directory with color, typography, layout, and components sections; the skill stops and asks for one if it is missing.
Then ask your AI: use the SaaS Landing Skill skill
What your AI can do with it
- Builds a single-file index.html with hero, features, social proof, pricing, and footer sec
- Reads DESIGN.md and restricts colors, fonts, and layout to its tokens
- Accepts inputs for product name, tagline, pricing on/off, and proof count (0-6)
- Tunes hero density (48-200px) and accent strength (0.5-1.0) parameters
- Outputs semantic HTML with inline CSS, system font fallbacks, and no external JS
- Tags editable elements with data-od-id slugs
Getting started
- Have a DESIGN.md file in the working directory with color, typography, layout, and components sections; the skill stops and asks for one if it is missing.
- Provide the required inputs: a product name and a tagline.
- Optionally set has_pricing (default true) and proof_count (default 3, range 0-6).
- Ask the agent to build the page using a trigger phrase such as "saas landing", "marketing page", or "product landing".
- Open the generated index.html to preview the result.
What this skill tells your AI
The instructions your AI receives, as published by nexu-io/open-design in design-templates/saas-landing/SKILL.md and read by ahel’s review.
Produce a single-page SaaS landing. Agent, follow this workflow exactly.
1. Read context
Before writing anything:
- Read
DESIGN.mdin 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_countlogos or testimonials. If 0, skip this section. - Pricing — 2–3 tiers. Include only if
has_pricingis 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:
- All text is content-meaningful, not lorem ipsum (use product_name and tagline inputs; generate plausible specific copy for the rest).
- No broken color references (every CSS color value is in DESIGN.md's palette or a valid alpha/fallback variant).
- Responsive breakpoints match DESIGN.md's Responsive Behavior section.
- The page looks good at 1440w, 768w, and 375w (mentally simulate).
- Accent used no more than twice total.
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-idtagging is how we wire elements to comment mode. Skills that want comment-mode compatibility must annotate their output.
See ../../docs/skills-protocol.md for the full protocol.
Signals
- GitHub stars
- 98k
- Forks
- 11k
- Last commit
- Sep 2026
Others that do the same job
Questions
- What happens if DESIGN.md is missing?
- The skill stops and asks for one before writing anything. It requires a DESIGN.md with color, typography, layout, and components sections.
- What does the output look like?
- A single self-contained index.html with all CSS inlined in a style block, semantic HTML, system font fallbacks, and no external JavaScript.
- Can I skip the pricing section?
- Yes. Set the has_pricing input to false; pricing is included by default.
Advanced
- Item type
- skill
- Key
saas-landing-2- Source
- github.com/nexu-io/open-design