
SaaS Landing
FreeCreate a tailored single-page SaaS landing page.
Free · Opens the source repo
What SaaS Landing does
The SaaS Landing skill is designed to help developers and designers generate a complete single-page landing page specifically for Software as a Service (SaaS) products. This skill follows a structured workflow that ensures the output is not only visually appealing but also adheres to the design specifications provided in the accompanying DESIGN.md file. By reading the design tokens for colors, typography, and layout principles, the skill guarantees that the resulting page is consistent with the brand's identity.
The workflow begins with a thorough reading of the DESIGN.md file to extract essential design elements. It then outlines the required sections of the landing page, including a hero section, features, social proof, pricing tiers, and a footer. Each section is carefully crafted to include specific components such as icons, titles, and calls to action, ensuring that the page is both functional and engaging. The skill also emphasizes the importance of semantic HTML and responsive design, making it suitable for various devices.
This skill is particularly useful for startups and product teams looking to quickly prototype and deploy landing pages without the overhead of manual coding. By automating the generation of HTML and CSS, it allows users to focus on content and strategy rather than technical implementation. The inclusion of data-od-id attributes facilitates easy editing and collaboration within comment mode, enhancing the overall workflow for teams.
Overall, the SaaS Landing skill streamlines the process of creating effective marketing pages, making it an essential tool for anyone involved in SaaS product development or marketing.
When to use it
Use this skill when you need to generate a landing page for a SaaS product quickly and efficiently, while maintaining design consistency.
When not to use it
This skill may not be suitable for highly customized landing pages that require unique design elements outside the provided design tokens.
What you can build with it
Startup Launch
Quickly generate a landing page for your new SaaS product launch, ensuring it aligns with your brand's design.
Marketing Campaign
Create a targeted landing page for a marketing campaign, complete with features and pricing information.
Product Showcase
Develop a single-page showcase for your software features and social proof to attract potential customers.
How to install SaaS Landing
View source1. Install with the skills CLI
npx skills add nexu-io/open-design/saas-landing --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by nexu-ioSaaS Landing Skill
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.
Frequently asked questions about SaaS Landing
Similar skills
Penpot UI/UX Design
Create professional UI/UX designs in Penpot with ease.
UX Theming
Streamline your VS Code theming process with best practices.
Wireframe
Create low-fidelity UI wireframes in SVG format.
Waitlist Page
Create a clean, focused pre-launch landing page.
Hallmark
Design skill for creating unique, structured UIs.
UI Styling
Create beautiful, accessible user interfaces effortlessly.
