build-website

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: build-website
description: Build out a complete SanityPress website — all pages, content, navigation, and CSS — entirely through the Sanity MCP connector, using only existing modules. No code files are edited. Use when the user wants a full site created for a business/brand from a brief.
---

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 `_type`s 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.

**Run the steps one at a time and wait for confirmation at each.** Ask Step 1 and wait, then Step 2 and wait, and so on. Don't batch them or start building before each step is confirmed — each step's answers should visibly inform the next question/proposal. (Step 0 is the Phase 0 prerequisites check; confirm those before Step 1.)

**Thin brief?** If the user gives only a little (e.g. just a name, or "just build it"), don't stall and don't invent silently: infer a likely answer for the current step, present it as a concrete proposal, and move on once they confirm or adjust. Lead with the proposal, not a wall of questions.

### Step 0 — Confirm technical prerequisites
Before any discovery, confirm the Phase 0 prerequisites are met: Sanity MCP connected, target project id + dataset known, `get_schema` loaded. If not, resolve that first.

### Step 1 — Tell me about the business
Lead here so you can write real copy, not lorem ipsum, and so everything downstream follows from substance:

> First, tell me about the business:
> 1. **What is it?** Name + one line on what you do/sell.
> 2. **Who's it for?** Target customer/audience.
> 3. **What makes you different?** Selling points, offerings, or proof (stats, testimonials, clients) I can turn into real content.

### Step 2 — Intent & primary call-to-action
Now pin down what the site is *for* — this drives page priority, hero CTAs, and which `cta` themes/links to use:

> What's the site meant to achieve?
> 1. **Primary goal?** (e.g. get bookings, generate leads, sell products, build credibility, take signups)
> 2. **Main call-to-action?** The single action you most want a visitor to take (e.g. "Book a call", "Request a quote", "Buy now") — and where it should point.
> 3. Any secondary action? (optional)

Make the primary CTA the dominant `cta` (`theme: 'action'`) in the hero and callout modules; secondary actions use `action-outline`/`ghost`/`link`.

### Step 3 — Brand, design direction & tone
Propose a