Native Custom CSS is not writable through MCP
POM AI does not expose WordPress’s native Additional CSS storage or a generic stylesheet editor. The POM builder guidance instead prefers live shortcode attributes for spacing, colors, backgrounds, alignment, and responsive behavior.
Why this matters
Writing CSS without the editor’s contract can create site-wide regressions, bypass sanitization and review, or override the POM Theme design system. It also makes an otherwise editable page depend on hidden global rules.
For a page task:
- read the component’s shortcode schema;
- use supported visual attributes;
- validate the complete shortcode tree;
- preview desktop and mobile output.
For a POM Theme setting, use the live setting schema and dedicated theme tools. If neither surface exposes the required presentation, the client may prepare a reviewed CSS proposal, but a developer or administrator must add it through the site’s supported theme or Custom CSS workflow.
Do not place <style> blocks, script-capable shortcodes, or arbitrary CSS in content merely to avoid this boundary. A request for a deliberate theme code change is a separate development task with its own review and release process.
Related guides: layout resource, shortcode schemas, and generic theme mods.