Server prompt: create a POM archive template

Request create_archive_template_pom with prompts/get. It has no arguments.

The returned instruction requires the client to:

1. call pom_get_template_schema for archive;
2. call pom_get_available_mergetags for the archive context;
3. read pom://theme/templates/archive when detailed examples are needed;
4. generate HTML with documented merge tags only;
5. use %%...%% for complex literal attribute values;
6. validate the markup and repair every error;
7. save with pom_theme_upsert_html_template only after validation.

Add the archive’s purpose, audience, target post type or taxonomy, desired sections, and visual constraints in a separate client message. The server prompt intentionally does not guess those business requirements.

The archive shell should normally contain one {{archive_results}} insertion. The item card belongs in a feed template, so avoid duplicating product or post card markup around the loop.

Before the save, ask the client to show the full HTML, validator response, final template key, and dry-run result. Assignment is a separate consequential write and should name the exact target.

Related guides: archive template resource, archive merge tags, and upsert template tool.