# The order a build wants to happen in

URL: https://kywi-docs-production.up.railway.app/agent/the-order-a-build-wants-to-happen-in
Type: docPage

The build-order playbook — model, structure, taxonomy, media, templates, then workflow — is a sequence the building-patterns guide and every AGENTS.md repeat.

The building-patterns guide's eleven-step build-order playbook isn't the last thing in the file — a short list of anti-patterns follows it — but the playbook itself is copied into every project's `AGENTS.md` unchanged, and it's the sequence an agent building a new site is expected to follow, not one option among several.

## The sequence

0. Propose the content model, get owner sign-off 1. Model: custom content types for every repeated shape 2. Structure: the site tree — pages, folders per collection 3. Taxonomy: categories/tags the feeds will need 4. Media: upload the brand's assets to the library 5. Templates: saved layouts + reusable components 6. Wire collections: feeds + Feed Display placements 7. Forms: contact/newsletter/etc. 8. Workflow: groups, permissions, review path 9. Ask about: personalization/A-B, comments, webhooks, i18n 10. SEO pass, then hand over

## Step 0 asks for confirmation — nothing enforces it

Nothing else on the list is meant to start before the owner has approved a content model, but nothing in the tool set stops an agent from skipping straight to step 5. The `kywi-content-model` skill's own trigger just asks the agent to confirm the model with the owner before building anything — it's a prompt for the agent to follow, not a check any tool refuses to run past. An agent that jumps to templates or forms before that sign-off is working against a step the playbook, and the skill meant to catch it, both put first for a reason: every later step assumes the shapes from step 1 are settled.

## One tool set seam looks like enforcement, but isn't reliable

Scaffolding a content type and writing it are two separate developer-server calls — `scaffold_content_type` only returns a suggested definition and says so in its own description; `add_content_type` is the call that actually writes it. But whether an agent has both of those tools available depends on how the developer server is configured, not on the playbook: `scaffold_content_type` registers whenever a `baseUrl` is set, in either mode, while `add_content_type` is a config-mutation tool that registers only in filesystem mode with a writable config path. The two exist together only when both conditions are met at once — there's no guarantee an agent that has one also has the other, so this isn't a mechanism that reliably forces a two-step scaffold-then-apply flow. See [the developer server's mode decides your tool list](/agent/the-developer-servers-mode-decides-your-tool-list/) for the full registration rules.

## The suggestion ignores what you described

`scaffold_content_type` always proposes the same six fields — title, slug, body, featured image, meta title, meta description — no matter what you pass as `description`. The text you wrote comes back in the result unchanged, but it never shapes the suggested fields. Read the suggestion before calling `add_content_type`, and edit it yourself if the type you actually want isn't a generic page.

Before you build anything, propose a content type for an "Event" using scaffold_content_type — I need fields for a date, a venue, and a ticket link, not the generic page fields. Show me the suggestion and wait for my sign-off before calling add_content_type.

The agent calls scaffold_content_type and gets back the same generic six fields (title, slug, body, featuredImage, metaTitle, metaDescription) regardless of what was described, shows you that suggestion, and stops there — it does not call add_content_type until you approve, and it should tell you the fields don't match what you asked for rather than applying them as-is.
