SaaS Landing Skill · Single-Page Landing Page Skeleton
Agent, strictly follow this process. No skipping steps.
1. Read Context (Required)
Before starting:
- Read the
DESIGN.mdfile in the current workspace. If it's missing, stop and ask for it; don't proceed blindly. - Extract the color palette, fonts, layout principles, and component style tokens.
- Pay attention to the "Agent Prompt Guide" section in DESIGN.md — if it conflicts with this skill's instructions, DESIGN.md takes precedence.
2. Copy the Skeleton (Required)
- Copy the entire
example.htmlfile from this directory to the workspace, naming it{project-name}.html - Do NOT rewrite from a blank HTML file — the skeleton already includes the 6-section structure, token variables,
data-od-idanchors, and responsive breakpoints. - After copying, keep all CSS in the
<style>block unchanged; first, map the CSS variables in:rootto the DESIGN.md tokens.
3. Section Checklist (In Order)
The skeleton must include the following 6 sections, no fewer allowed:
- Hero — Logo / main headline (tagline input) / 1-2 subtitle sentences / primary CTA / secondary CTA
- Main headline font-size:
clamp(44px, 6vw, 76px), line-height:1.05, letter-spacing:-0.02em - Hero section vertical padding uses the
hero_densityparameter (default 96px)
- Main headline font-size:
- Features — 3-6 feature cards
- Each: number (mono font) / title / 1-2 sentence body
- Must have content variation — no three identical symmetrical cards
- Social Proof —
proof_countnumber of logos or testimonials- Skip this section if
proof_count = 0 - Do not fabricate decorative stats like "10,000+ happy customers"
- Skip this section if
- Pricing — 2-3 tiers (only when
has_pricing = true)- Mark the middle tier as "Recommended" with an accent color border
- Each tier: name / price / 4-6 feature list items
- Footer CTA — Large accent-color background final call-to-action
- Footer — Minimal copyright + links
4. Apply DESIGN.md (Hard Constraint)
- All colors must come from DESIGN.md tokens; do not invent hex values out of nowhere.
- Fonts: Display font for hero / pricing titles; body font for everything else.
- Accent color used ≤ 3 times across the whole page (hero CTA + pricing recommended tier border + footer CTA entire section).
- No stacking shadows — if DESIGN.md doesn't explicitly allow it, omit box-shadow entirely.
5. Run Craft (Hard Constraint)
Based on the 4 craft files pulled via od.craft.requires:
typography— letter-spacing, line-height, widows/orphans, tabular-numscolor— prefer oklch, don't invent colors, contrast ratio ≥ 4.5anti-ai-slop— banned list: Inter / Roboto / Fraunces / purple gradient / Bento grid / left border accent / Lorem ipsum / "John Doe" / fabricated numbers like "100% uptime"laws-of-ux— Fitts / Hick / Miller / error recovery
6. Self-Check (Required, Check Each Box)
Before delivery, confirm:
- All text content is truthful and credible, no lorem ipsum, no "John Doe", no fabricated stats like "10,000+"
- Every hex value can be traced back to a DESIGN.md token
- Responsive: mentally tested at 1440 / 768 / 375 breakpoints
- Accent color used ≤ 3 times across the whole page
- Every core element has a
data-od-id="<slug>"annotation (hero / features / pricing / footer, etc.) - Fonts are not Inter / Roboto / Fraunces / Space Grotesk
- No purple gradients / mesh gradients / left border accent cards
- Each piece of fake data has at least 5 fields (pricing card has at least 4 features)
7. Write the File
Output only a single, self-contained {project-name}.html:
- All CSS inline in
<head>within a<style>block - Fonts via Google Fonts CDN (with system-ui fallback)
- No external JS
- Semantic HTML:
<header>/<main>/<section>/<footer>
Do not generate separate .css / .js / README files.
Notes for Skill Authors
This skill is a minimal but complete paradigm. Structure:
saas-landing/
├── SKILL.md ← This file (instructions)
└── example.html ← Copyable production skeleton (300+ lines)
Key points:
- The
od:frontmatter block declares three-axis dependencies (design-system / craft) + adjustable parameters + required inputs. The agent reads this block and automatically pulls dependent resources. data-od-idannotations allow frontend comment mode to locate elements for partial patches.- DESIGN.md is a collaborator, not an override — this skill gives the agent power to fine-tune based on the brief, but not to invent new tokens out of nowhere.