What problem does it solve? Producing a consistent SaaS marketing landing page requires manually coordinating hero, features, social proof, pricing, and CTA sections while respecting an existing design system, which is slow and error-prone. ## Core Features & Use Cases - Structured Section Workflow: Builds hero, features, social proof, pricing, footer CTA, and footer sections in a fixed order with typed inputs like product_name, tagline, has_pricing, and proof_count. - Design System Enforcement: Reads DESIGN.md for color, typography, layout, and component tokens, refusing to invent hex values or add undeclared shadows. - Self-Contained Output: Writes a single index.html with inlined CSS, semantic HTML, no external JS, and data-od-id attributes for comment-mode targeting. - Use Case: Provide a product name and tagline, and receive a responsive landing page that matches your project's declared palette and typography at 1440w, 768w, and 375w breakpoints. ## Quick Start Ask the agent to generate a SaaS landing page for your product using the saas-landing skill with your product name and tagline.
