One link for your assistant. A check before every build.
Claude, Cursor, ChatGPT or your own agent can mark up a site for ThemeForge with very little manual work: the rules are plain text, the check is a free request, and the build takes an archive.
Give your assistant the link themeforge.pro/ai. It reads where the attributes go, marks up the HTML, sends every page to POST /api/validate-markup and fixes what comes back until the answer is "ok": true. Then you build the theme in a project, or the agent sends the archive itself.
What an agent can use
Rules in plain text
A 2 KB entry page that names the modules: core rules, generating a site from scratch, pages, blog, custom types, WooCommerce, handover. The agent pulls only what the site needs, such as /ai?m=core.
Markup check
Runs the real generator’s parser on the whole set of pages and lists what it would object to, most severe first. Free, no account, nothing stored; limited per address.
Attribute dictionary
Every attribute with its type and scope, in JSON, for tools that suggest or check markup.
Build from an archive
Send the source as a ZIP with the project’s token and get the theme back. Needs an active subscription; the token is in tf-update-key.php of any theme downloaded from the project.
Abilities in the theme
On the client’s site, an assistant connected over MCP can read the site’s source and the markup rules. Changes from outside are off until the owner allows them in wp-admin; every change is logged and can be undone.
The same rules for people
The guide a person reads to check what the assistant did, with examples for every kind of block.
Open the guide →Agent kit
A Claude Code skill, a Cursor rule, AGENTS.md and a script that checks a folder of pages — an open repository under the MIT license. The kit does not copy the rules: it fetches them from themeforge.pro/ai every time.
A prompt and a request are enough
Give Claude, Cursor or ChatGPT one link. It reads where the attributes go, marks up the site and checks its own work against the same rules the builder uses.
- 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":"…"}]}'
How an agent works with ThemeForge
- Step 1
Agree the site map
Page files decide WordPress templates, so the agent first lists the pages, content types, site-wide values and languages, and waits for your yes.
- Step 2
Mark up and check
It adds
fld-,opt-andtax-attributes and sends the pages to the check until nothing is left to fix. - Step 3
Build and update
You build the theme in your project and preview its admin free. With a subscription, the same source updates the client’s site after every change.
Good to know
The check is rate-limited
Send the whole set of pages in one request instead of page by page; a 429 answer says when to try again.
Building needs a project
Builds belong to a project in your account. A free account builds and previews the admin; downloading and updating need the subscription.
React apps do not move as they are
The rules expect HTML pages. A site whose content is assembled by React in the browser needs to be exported to static HTML first.