Recipe: orient the client on an unfamiliar site

This read-only recipe gathers enough context to choose the next workflow without dumping the entire site.

Inspect the connected WordPress site without making changes. Read site info
and pom://site/authoring-context. List public post types and taxonomies, then
summarize only the objects relevant to [TASK]. If POM Theme, WooCommerce, or
POM Cache is available and relevant, call its status or summary read tool.
Report the site URL, target site in multisite, editor/builder model, relevant
content types, dependencies, permissions encountered, and recommended next
read. Do not call any write tool.

The authoring context reports POM Theme and builder guidance; it is not a plugin/theme inventory. Store status tools expose the product surface they own, not arbitrary installed software.

Good output

An inspection should answer:

• Which exact site is connected?
• What type of object is the user asking about?
• Which editor or POM content format applies?
• Are the relevant integration tools present?
• Which read should happen next?
• Which boundary prevents an unsupported request?

Avoid listing hundreds of posts or loading all shortcode schemas. Narrow discovery to the stated task and use pagination.

Related guides: site authoring context, site information tool, and plugin inventory boundary.