Recipe: configure an already designed content model

This copyable recipe is for applying a known CPT, taxonomy, field, template, and assignment design. If the model still needs to be invented, use the server prompt create a POM content model first.

Read pom://theme/content-model-guide and inspect the current POM content
model. Compare it with the supplied model specification. Read the archive,
single, and feed template schemas and merge-tag catalogs, validate every
proposed template, then call pom_theme_configure_content_model with dry_run
enabled. Present all planned operations and conflicts. Apply only after my
confirmation. Because the operation is not atomic, stop on an error, inspect
current state, and report which earlier operations were applied.

Include the exact model specification after the prompt: slugs, labels, public behavior, taxonomy relationships, field names and types, template HTML, assignments, and desired draft test content.

Review the dry run

Confirm that:

• no existing post type, taxonomy, or field is unintentionally redefined;
• each template uses only its context’s merge tags;
• the archive template includes archive_results;
• template identifiers and assignments match;
• test content will remain draft;
• the acting user has POM Theme write access and the POM Theme write gate is open.

After application, create one representative record with and without optional values. Verify its single view, archive shell, and feed card independently.

Related guides: content-model resource, configure content-model tool, and non-atomic writes.