Build in Cursor. Ship to WordPress after every change.
Your site lives in a Cursor project and keeps changing. ThemeForge turns it into a WordPress theme with admin fields, and every rebuild after the next change keeps what your client typed in.
Static HTML projects · agent-checked markup · $20/month to download and update
Yes, if the project outputs static HTML. Give Cursor’s agent the rules from themeforge.pro/ai and ask it to mark the editable parts; it can run our free markup check from the terminal and fix what it finds. ThemeForge builds the theme from the published site, and the update button in wp-admin pulls each new version.
A Cursor project with a WordPress theme as its output
- Step 1
Teach the agent once
Save the rules from
themeforge.pro/aiinto the project’s rules or docs, so every agent run marks fields the same way. - Step 2
Mark up and check
Ask the agent to mark the pages and to call
POST /api/validate-markupuntil the report is empty. It is free and needs no key. - Step 3
Publish and rebuild
Publish the static output at an address and add it to ThemeForge. After each change, press “Update” in wp-admin: the theme rebuilds and the content stays.
The theme is a build artifact, not a fork
Source stays in Cursor
You never edit PHP templates. Change the HTML in your project, rebuild, and the theme follows.
Content stays in WordPress
Field values live in the database, so a rebuild replaces templates and styles without touching what the client wrote.
Your PHP survives too
Custom code goes into protected theme files, and no update overwrites them.
Failed updates roll back
After an update the theme checks the site; if a page breaks, it restores the previous version by itself.
The agent checks its own markup
The validator answers in JSON with the exact element and rule, so the agent can fix the markup in a loop before you ever build the theme.
- themeforge.pro/ai · plain-text rules for assistants
- Markup check · free, no account, before you build
- Markup guide · the same rules, written for people
# Tell your assistant Read https://themeforge.pro/ai and mark up this site so the client can edit the menu. # Check the result before building curl -X POST https://themeforge.pro/api/validate-markup \ -H "Content-Type: application/json" \ -d '{"pages":[{"name":"index.html","html":"…"}]}'
Know these before you start
Static output only
React, Next.js or Vue apps do not become themes as they are. Build or export static HTML pages first.
Localhost needs one helper file
To build or preview from your local server, start it with tf-cors.php from the guide, and allow access to your local network when the browser asks.
Keep field names stable
Fields are matched by name. If the agent renames one, the rebuilt field starts empty, so tell it to keep existing names.
Shop, languages and forms come with the theme
Not in Cursor?
- Sign up
- Preview your admin
- Subscribe
- Download and update
Cancel any time · 14-day refund · your site keeps working after you cancel
Cursor to WordPress, answered
Do I edit the generated PHP?
No. Treat the theme as a build output. Custom PHP, CSS and JS go into protected files that every update keeps.
How do updates reach the live site?
From wp-admin: one button asks ThemeForge for a fresh build from the published URL and installs it, with a check and an automatic rollback.
Can the agent build the theme by itself?
It can prepare and check the markup on its own. Building and downloading the theme needs your subscription.
What if the agent changes the design completely?
Rebuild as usual. As long as field names stay the same, every field keeps its content in the new design.