adapto-schema-design

# adapto:schema-design Derives a **content schema** from your project context: the **custom collections** (and their fields) the site needs, the **Article categories** worth setting up, and an **advisory map** of which built-in types cover everything else. Its output is a reviewable, hand-editable **`.adapto/schema-plan.json`** that `adapto:schema-apply` reads to do the actual writing. This skill makes **no CMS writes** — it's safe and re-runnable. ## When to use - "Design my content schema", "what collections do I need", "model my content". - Right after `adapto:project-define`, and before `adapto:content-seed`. ## When not to use - To actually create the collections/categories in Adapto → `adapto:schema-apply`. - To seed content rows → `adapto:content-seed`. - Just checking the environment → `adapto:doctor`. ## Inputs - **Project context, if available** — read from the `.adapto/project.md` cache, or (when authenticated) `adapto collections get-by-slug _adapto_project_config --json`. - **Existing collections, when authenticated** — `adapto collections list --json`, so the proposal reuses or skips what already exists instead of duplicating it. - **If there's no project context** — ask for a **1–2 line site description** (a single, skippable question). ## Outputs - **`.adapto/schema-plan.json`** — the reviewable proposal that `adapto:schema-apply` consumes. Shape: ```json { "version": 1, "language": "en-US", "collections": [ { "name": "Team", "slug": "team"...