You can build a WordPress theme with Claude by letting it inspect your current site, agree a written plan with you, and then create or edit files only inside a theme folder you have approved — on a staging copy, with a checkpoint before each larger step. Claude writes and reads back the code; you preview it, test it on real devices and decide when to activate and deploy. Meikero provides the file access and safety rails, but it does not activate themes, deploy sites or test designs visually.
What Claude can do, and what needs a person
| Claude can help with | A person still needs to |
|---|---|
| Reading the current theme, active plugins and page structure | Decide the design direction and approve the brief |
| Proposing a file structure and template plan | Approve which folder Claude may write to |
| Writing templates, styles and small functions in approved files | Preview every page type in a browser |
| Reading files back and checking them against the plan | Test on phones, with a keyboard and with real content |
| Explaining what changed and why | Activate the theme and deploy it |
Meikero refuses PHP files that would not parse, which catches syntax mistakes. It cannot catch runtime errors, layout problems or plugin conflicts — that is what testing is for.
Step 1: Inspect what you already have
Start read-only. With Claude connected to your WordPress site, ask it to report the active theme, installed plugins, published pages and, if you approve the current theme’s folder for reading, its templates and how styles are loaded. Pay attention to integrations: WooCommerce, an SEO plugin, forms or a page builder each have expectations a new theme must meet.
One distinction matters a lot with block themes. As the WordPress Theme Handbook’s child themes chapter explains, customisations made in the Site Editor are stored in the database, not in theme files. Meikero’s file tools see and change files in approved folders; they do not see or edit those database-stored template changes.
Step 2: New custom theme or child theme?
| Child theme | New custom theme | |
|---|---|---|
| Best for | Small to moderate changes on top of a theme you like | A new design or a site that has outgrown its theme |
| Parent updates | Still received; your changes stay separate | Not applicable — you own all the code |
| Maintenance | Can become messy if overrides pile up | Everything is yours to maintain |
The Handbook recommends child themes for modifying a theme without touching its code, and suggests a full theme of your own once customisations become extensive. What you should avoid is editing a third-party theme that receives updates: the next update replaces its files and your changes disappear. Both routes are explained in the WordPress Theme Handbook.
Step 3: Agree a design brief before any files exist
Ask Claude to turn the inspection into a short brief you can edit: block or classic theme, page types and templates, header and footer contents, colours and typography, components such as cards or forms, integration requirements and what is explicitly out of scope. Changing a brief costs a minute; changing twenty files costs much more.
Step 4: Staging, backups and one approved folder
- Work on staging. Build and test on a copy of the site, not the live store.
- Keep regular backups of files and database from your host or backup plugin.
- Scope access tightly. In Meikero, approve write access only for the new theme folder. Leave other themes and plugins read-only or off.
Before each larger step, ask Claude to save a project checkpoint of the theme folder. A checkpoint captures the supported text files in that one approved folder — templates, PHP, CSS, JavaScript, JSON — and can be restored later. It does not include images or other binary files, the database, media or Site Editor customisations. Individual file writes also keep automatic backups.
Step 5: Work in small, verifiable steps
- Inspect the files involved in the next step.
- Plan the change in a sentence or two and confirm it.
- Create or edit approved files. New files are created explicitly; existing files are edited against their current hash, so an outdated read cannot overwrite newer work.
- Read back the result and compare it with the plan.
- Preview and test it yourself before moving on.
A sensible order is: base files and global styles, header and footer, the main page template, posts and archives, then integrations such as WooCommerce.
Step 6: Check quality, not just appearance
- Responsive layout: test narrow phones, tablets and wide screens, with long titles and real images.
- Keyboard navigation: every menu, button and form must work with Tab and Enter, with a visible focus state and a skip link.
- Escaping and sanitisation: output should be escaped with functions such as
esc_html(),esc_attr()andesc_url(), and any input sanitised. Ask Claude to point out every place data is printed. - Integrations: check shop, cart, checkout and account pages if WooCommerce is active, and confirm your SEO plugin still controls the
<title>tag.
Step 7: Activate and deploy as separate decisions
Meikero has no tool for switching themes. When staging looks right, you activate the theme yourself under Appearance → Themes, check the site again, and then deploy to production with your normal process. Treat activation on the live site as its own approved step, with a fresh backup taken just before.
After launch, the new templates may output titles differently from the old theme, so it is a good moment to review your Yoast SEO titles and descriptions with Claude.
Related workflows: build a landing page for your next campaign, or add a pricing calculator as a small custom plugin.
A prompt to start with a plan
I want to build a custom WordPress theme for this site. Start with inspection and a plan only.
1. Using the available Meikero tools, read the site information: active theme, installed plugins, post types and the folders you are allowed to access. Read the current theme's main files if that folder is approved for reading.
2. List the page types and templates the site needs, the integrations the new theme must support (for example WooCommerce or an SEO plugin) and anything stored in the Site Editor database that file tools cannot reach.
3. Recommend a child theme or a new custom theme, with reasons.
4. Propose a short design brief and a file plan: folder name, files to create, and the order you would build them in.
5. Do not create, edit or delete any files, and do not activate any theme. Wait until I approve the scope and confirm which folder you may write to.FAQ
Do I need Meikero Pro?
Inspection and planning work on Free. Writing files and saving checkpoints need Pro plus write permission for the approved folder. See Meikero Free and Pro.
Can Claude convert my page-builder layouts automatically?
Not automatically. Claude can read page content and propose templates that replace builder layouts, but the content of each page still has to be reviewed and, often, rebuilt deliberately.
What happens if a change breaks something?
On staging, restore the file backup or the last checkpoint, then fix the cause. If the problem involves the database or media, restore from your regular backup — checkpoints do not cover those.
Begin with the inspection
Run the planning prompt on a staging copy and edit the brief until it describes the site you actually want. The setup guide covers folder permissions, and the theme and plugin file tools list exactly what Claude can read and write.