What problem does it solve? Teams building a software product often ship only a homepage or copy page structures from other SaaS companies, leaving their site missing critical trust, legal, support, and system-state pages. This Skill determines which pages a product site actually needs and what each page should accomplish based on the product type, business model, and audience. ## Core Features & Use Cases - Page Architecture Planning: Selects the right set of marketing, trust/legal, support, authentication, and system-state pages from product characteristics like B2B vs B2C, self-serve vs sales-led, and product maturity. - Per-Page Content Guidance: Defines what the homepage, features, pricing, about, privacy, terms, security, docs, changelog, and status pages should each communicate and answer. - Use Case: You are launching a new developer tool and ask what pages the site needs. The Skill recommends a minimum credible set (Home, Features, About, Contact, Privacy, Terms) plus Documentation and Status, and outlines the homepage section hierarchy from hero to final CTA. ## Quick Start Ask the agent to plan the complete website structure for your SaaS product, including which pages are needed and what each page should contain.
