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:

{
  "version": 1,
  "language": "en-US",
  "collections": [
    { "name": "Team", "slug": "team", "description": "Team members", "status": "draft",
      "fields": [
        { "name": "role", "label": "Role", "type": "text", "required": true },
        { "name": "manager", "label": "Manager", "type": "reference", "related_collection": "team" }
      ] }
  ],
  "categories": [ { "name": "Tutorials", "slug": "tutorials" } ],
  "advisory": { "articles": "blog posts / news", "pages": "static & marketing pages" }
}

• related_collection holds the target collection's slug — adapto:schema-apply resolves it to the real id at write time. fields[] entries are FieldDefinitionModel (keys: name, label, type, required?, multiple?, options? as [{label,value}], related_collection?, default_value?, description?, validation? — see cli-cheatsheet.md §5).
• A compact on-screen summary: N collections, M categories, and the advisory map. No CMS writes.