Server prompt: design and create a POM content model

Call prompts/get with create_pom_content_model. Its optional model_description argument should explain the records, classifications, fields, and public views the site needs.

The returned instruction treats the model as a coordinated system. It reads the content-model guide plus archive, single, and feed resources; inspects schemas; designs and validates all templates; runs pom_theme_configure_content_model as a dry run; applies it only after review; and creates draft test content, terms, metadata, and media.

Example:

{
  "name": "create_pom_content_model",
  "arguments": {
    "model_description": "A public course catalog grouped by subject, with duration, level, hero image, archive shell, single view, and listing card"
  }
}

Before proceeding, supply exact singular/plural labels, desired slugs, required and optional fields, taxonomy relationships, archive behavior, and representative empty states. The client should not infer these from a vague noun.

The coordinated write is not atomic. Require a full dry-run report and a current-state inspection if any applied step fails. Keep test records in draft and verify archive, feed, and single output separately.

Related guides: content-model resource, configure an existing design, and content-model tool.