Beyond pages
Pages are where most tools stop. Blog posts, shop pages and the Theme Builder are the rest of the site, and Claude builds those too.
Posts and shops
Gutenberg blog posts and WooCommerce shop pages, built against the same design system as everything else — so the shop does not look like it came from a different site than the homepage.
Theme Builder and Library
Headers, footers and templates. Autopilot reads and writes the whole Theme Builder and the Divi Library, so a change to a footer link is one edit in one template rather than forty edits across forty pages.
A way back everywhere
One step back before every Theme Builder or Library write — a WordPress revision, or a saved copy of the previous content where revisions are switched off. One bad header write is every page on the site, so a template gets exactly the same guarantee as a page.
What’s covered
Plain WordPress posts — this site’s own blog is written that way, because prose belongs in the editor and layout belongs in Divi — WooCommerce pages built with your store’s real context, and Theme Builder headers, footers and templates, with a guard that warns before a new template would clobber one matching the same pages.
Plans
These writers are included in every paid plan — the plans differ by seats, not features: Solo covers one site, Pro five, Agency twenty, from $99/year. The free tier still audits every page they produce, so you can hold the output to the same standard as the rest of the site.
The common thread is context: the plugin hands Claude your store’s products, your templates’ display conditions and your posts’ structure before anything is written, so the output fits the site it lands on instead of arriving generic. And because every write is journaled, the same undo and snapshot guarantees that protect pages apply out here too — a template change is as reversible as a heading fix.