build-website

Build a complete, publishable SanityPress website for [BUSINESS NAME] using only the Sanity MCP connector. You write and publish all content; you do not edit, scaffold, or add any code files (no new modules, no schema changes). Compose everything from the existing module types.

This skill assumes the SanityPress schema (page, site, navigation, global-module, the module objects) is already deployed and the Sanity MCP connector is connected. If it is not connected, stop and ask the user to connect it.

Phase 0 — Connect & load the schema

1. Confirm the Sanity MCP connector is available (list_projects / whoami). If multiple projects exist and the target is ambiguous, ask which project id and dataset to use. Default dataset: production.
2. Always call get_schema first. Do not write any document until you have read the live schema — field names, code-typed fields, and module _types must match exactly.
3. If unsure about any field shape, call search_docs / read_docs before guessing.
4. Check for relevant per-instance skill documents before drafting any copy — see the check-studio-skills skill (query _type == "skill", surface/confirm anything relevant, e.g. a content-guidelines doc, before Phase 1 copywriting).

Phase 1 — Discovery (ask in this order, before building)

Discovery is sequential on purpose: understand the business first, because the answers shape every later question and all the page copy. Do not jump ahead to colors/fonts before you understand what the site is for. Skip any question the user has already answered, and infer sensible defaults rather than asking about things the earlier answers already make obvious.