What POM Site Authoring can do and how to ask
POM Site Authoring helps you design, build, improve and review WordPress websites made with POM Theme and POM AI. It guides the agent toward the site's native builder, settings and reusable templates so the result remains editable in WordPress.
This guide is for site owners, designers and content editors who want to describe an outcome in ordinary language. You do not need to write JSON or choose individual MCP tools. The skill supplies the working instructions; the connected MCP, authorized browser access or an authorized local installation supplies the ability to act.
Before you start
Follow Install the POM Site Authoring skill to connect your client and install the skill, or load it for the current conversation. On the website, enable POM AI MCP under Settings → POM AI → AI Tools and use the permissions and write controls appropriate to your task.
Name the destination website, especially when your connection can reach several sites. Ask the agent to inspect its capabilities first: the available operations depend on the destination's installed products, enabled features, connection and permissions. Being able to list a site does not establish permission to edit everything on it.
Browser access is needed to inspect the rendered result and, for some tasks, use the installed editor. Supply your brand assets and real business facts before asking for finished content.
Capabilities and example requests
Each example assumes that you have selected the intended website. The agent should inspect and reuse existing content, styles and settings before adding replacements.
| What you can ask for | What the skill covers | Example request |
|---|---|---|
| Inspect a website | Identify its editor, pages, POM modules, settings and available authoring actions. | “Inspect this site and explain what you can edit through this connection. Do not change anything.” |
| Design a website or page | Connect the visitor's goal to page structure, typography, color, imagery and a clear next action. | “Prepare a draft website for our architecture studio using the supplied identity. Include Home, Projects, Services and Contact.” |
| Create or edit content | Work with pages, posts, supported custom content types and reusable blocks while preserving the installed editing format. | “Create a draft Services page with editable POM modules. Reuse the existing service descriptions.” |
| Refine an existing design | Improve hierarchy, spacing, alignment, image treatment, copy and calls to action within the agreed scope. | “Polish this landing page while preserving its identity, URL and factual content.” |
| Improve mobile layouts | Review column order, type sizes, spacing, image crops and control usability at relevant viewport sizes. | “Improve the mobile layout of this page, including its header and contact action. Preserve the desktop design.” |
| Prepare images and media | Reuse library assets, upload supplied files and set supported titles, captions, alternative text and featured images. Image generation requires a separate available and authorized tool. | “Choose suitable images from the media library for these sections and write descriptive alternative text.” |
| Configure navigation and shared areas | Work with native header choices, desktop and mobile menus, reusable footer content and supported homepage, posts-page or privacy-page assignments. | “Simplify the main menu and build a footer with our supplied contact details and legal links.” |
| Structure reusable content | Use supported custom content types, taxonomies and fields, reusing the site's existing model where possible. | “Organize our projects by category and add fields for location and floor area. Inspect the existing structure first.” |
| Build content templates | Define an archive for the listing page, a feed template for each result card and a single template for each detail page. | “Give Projects a consistent listing, result card and project detail layout.” |
| Create filterable listings | Combine native queries, search, filters, sorting, counts, reset controls and pagination, with the required indexing configuration. | “Build a project catalogue with category filters, keyword search, result counts and a clear empty state.” |
| Build native forms | Configure supported fields, columns, steps, validation messages, buttons, consent text and recipient settings. | “Create a quote request form using these fields, this consent text and this approved recipient. Do not submit it.” |
| Adjust theme settings | Apply supported typography, colors, buttons, header settings and optional POM features through the site's settings. | “Apply our supplied palette and typography consistently to headings, links and buttons.” |
| Configure contact and cookie controls | Set up native phone, WhatsApp or email actions and available cookie controls using the site's actual services and supplied privacy information. | “Add our phone and WhatsApp contact actions using the numbers provided. Review cookie settings against the services we actually use.” |
| Refine CSS and asset assignments | Prefer native controls, then use scoped CSS, component styles or named stylesheets where supported. Assign scripts already present in the theme catalog. | “Adjust this card's spacing with the smallest suitable style change and preserve the existing rules.” |
| Review the visitor experience | Inspect complete pages, desktop and mobile layouts, reading order, legibility, keyboard focus, links and relevant form or filter states. | “Audit the complete enquiry journey without editing it. Show the most useful improvements with evidence.” |
| Resume a larger project | Use saved site plans to track supported steps, inspect progress and continue without blindly repeating completed operations. | “Resume the saved site plan, check what has already been applied and continue from the next incomplete step.” |
The skill works with the installed POM Page Builder and native interactions. Existing menus, sticky headers, galleries, forms and filters should use their supported behavior. It does not add a separate frontend framework or custom filtering script.
For new footers, it normally uses one enabled footer row containing a reusable block whose internal layout remains editable in the builder. An existing footer is preserved unless its replacement is part of your request.
Make a useful request
- Select the skill and destination. In Codex, mention
$pom-site-authoring; in Claude Code, use/pom-site-authoring. You can also explicitly ask the agent to use POM Site Authoring. Include the website's domain and the page or area to change. - Explain the outcome. Describe your business, audience and the action visitors should take, such as requesting a quote or finding a project.
- Provide the source material. Supply approved copy, factual details, brand assets and useful visual references. Identify anything the agent must preserve.
- Set the scope and publication state. Say whether you want a review, a draft, an edit to an existing live page or publication. Name any shared settings or templates that may be changed.
- Specify verification. Ask for the relevant desktop and mobile checks, links and interaction states. Complete any write review required by your site's connection.
For example:
Use POM Site Authoring on [website domain]. Create a Services page for [business] aimed at [audience], with the goal of [visitor action]. Use the supplied copy and images from our media library. Preserve the logo, palette and existing URLs. Edit only this page and leave shared settings unchanged. Keep it in draft, verify the complete layout on desktop and mobile, and report anything you could not check.
You can then refine the result with a focused follow-up:
Keep the current structure. Shorten the introduction, give the primary contact button more emphasis and reduce the spacing between service cards on mobile.
Choose how much the agent may change
Clear scope helps separate a useful proposal from an instruction to apply it. These phrases can be added to any brief:
| Intended scope | Phrase to use |
|---|---|
| Review only | “Inspect and recommend improvements. Do not change the site.” |
| One page | “Apply the changes only to this page. Preserve shared templates, menus and global settings.” |
| New draft | “Create this as a draft and do not publish or add it to navigation.” |
| Shared design changes | “Update the shared header and footer across the site, using the supplied design and contact details.” |
| Publication | “Publish this page after the agreed checks pass and add it to the specified menu.” |
| Form delivery check | “Send one test submission using these test values to this approved recipient, then report the observed result.” |
New content should remain in draft unless publication is authorized. Changes to existing published pages, active templates, menus or global settings can affect the live site immediately. A reusable block's draft status does not make it a safe preview if a live footer or template already renders that block.
Your request defines the work, while the website's capabilities, scopes and write controls determine what can be executed. An instruction to publish does not bypass a review required by the server.
Check the result
The expected result is editable POM content and a clear account of what changed. Ask the agent to provide the affected pages or templates, their publication state and the checks it actually completed.
Review the full visitor path, including the header, page body, footer and any linked detail page. Relevant checks include:
- Reopen saved content in its intended editor and confirm that its structure remains editable.
- Inspect desktop and mobile layouts for reading order, overflow, spacing, image crops and legibility.
- Follow navigation and contact links; check keyboard focus and the controls used in the requested journey.
- For listings, try search, filters, sorting, reset, pagination and empty results where applicable.
- For forms, inspect required-field feedback. Treat delivery as a separate check that needs an authorized submission and evidence of its outcome.
The report should distinguish observed results from unverified behavior. Browser viewport emulation is not a test on a real phone, and a successful save is not proof that every visitor interaction works.
Important boundaries
- Access comes from the connection. Installing the skill does not grant website access, activate a product license or enable every operation. Unsupported actions must be reported rather than bypassed.
- Native editor compatibility matters. Creating static block markup can require the actual installed block editor to serialize and verify it. MCP-only access may be insufficient to finish that task reliably.
- JavaScript authoring is excluded. The skill can assign existing catalog scripts where supported, but does not create or modify JavaScript or install new script libraries.
- Website authoring has a defined scope. User accounts, passwords, roles and permission administration are excluded. The skill does not deploy replacement plugin or theme code.
- Business and legal facts must come from you. The agent should identify missing details instead of inventing claims, contact information or finished legal text. Configuring a cookie banner does not establish legal compliance.
- Public listings need suitable content. A listing based on published content cannot be fully verified using draft-only records. Any publication needed for verification must be within the agreed scope.
- Plans record progress. A saved plan is not a backup or automatic rollback. Discarding a plan does not undo changes already applied to the website.
Troubleshooting
The agent sees several sites or selects the wrong one. Provide the exact destination domain and ask it to confirm the target before continuing. Refresh discovery for that destination; a network or account connection may expose a different set of operations from a direct site connection.
A requested feature is unavailable. Ask the agent to identify the missing POM feature, tool or permission. An authorized administrator may need to enable the relevant feature, grant the appropriate access or complete the step in the native interface. Do not assume installing the skill enables it.
A write is refused or needs review. Follow Enabling writes and the connection's reported requirements. Refresh the current state before retrying a conflicting change.
The agent cannot inspect the page visually. Provide authorized browser access or request a clearly labeled partial result. The report should say which layouts and interactions remain unchecked.
A long task was interrupted. Ask the agent to read the saved plan and inspect the current website before resuming. This is especially important when the outcome of the last operation is uncertain.