{"id":"aa7428ab-dda2-4615-b072-aac63585b6ee","shortId":"Vs8uSZ","kind":"skill","title":"saas-landing","tagline":"Single-page SaaS landing with hero, features, social proof, pricing, and CTA.\nRespects the active DESIGN.md color/typography/layout tokens.\nTrigger keywords: \"saas landing\", \"marketing page\", \"product landing\".","description":"# SaaS Landing Skill\n\nProduce a single-page SaaS landing. Agent, follow this workflow exactly.\n\n## 1. Read context\n\nBefore writing anything:\n- Read `DESIGN.md` in the current working directory. If missing, stop and ask for one.\n- Identify the color palette, typography tokens, and layout principles.\n- Note the \"Agent Prompt Guide\" section — it overrides any instruction here if they conflict.\n\n## 2. Plan sections\n\nRequired sections, in order:\n1. **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.\n2. **Features** — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.\n3. **Social proof** — `proof_count` logos or testimonials. If 0, skip this section.\n4. **Pricing** — 2–3 tiers. Include only if `has_pricing` is true.\n5. **Footer CTA** — large accent-colored band with one-button call to action.\n6. **Footer** — minimal: links + copyright.\n\n## 3. Apply design system\n\n- All colors must come from DESIGN.md tokens. Do not invent hex values.\n- Typography: use the declared display font for headlines, body font for everything else.\n- Layout: respect the grid, max-width, and section spacing rules.\n- Components: use declared button/card/input patterns. Do not add shadows if DESIGN.md's Depth & Elevation says minimal.\n- Accent: use the accent color only once in the hero, once in the footer CTA, and for all links. Do not flood the page.\n\n## 4. Write the file\n\nOutput a single self-contained `index.html` with:\n- All CSS inlined in a `