Give the agent the site, page, CMS model, or component you need.
Stop building WordPress by hand.
Bring your own agents. Keep your work in Git. Build real Etch sites from the IDE instead of clicking through another magic box.
Bring your own agents
Use the tools you already pay for.
Oh My IDEtch is not another closed workspace. It gives Codex, Claude Code, Cursor, Copilot, OpenCode, and whatever comes next the same thing they need: project rails.
CodexClaude CodeCursorCopilotOpenCodeWhatever comes next
It writes PHP builders, CMS JSON, styles, and project files inside the repo.
You inspect the diff, run checks, preview locally, and keep the good code.
Commit the work and deploy like a normal WordPress project.
What the starter owns
Rails for agents. Ownership for you.
The system is deliberately boring in the right places: real files, real PHP, real Git history, and local WordPress preview.
Code-owned site structure
Pages, templates, patterns, and components live in src/Site/**. The WordPress database is the local preview target, not the source of truth.
Strict PHP builders
The agent writes against real Etch builders for blocks, loops, conditions, dynamic content, styles, JavaScript, and component slots.
CMS in version control
CPTs, taxonomies, ACF/SCF fields, seed content, and media workflows stay explicit, repeatable, and reviewable.
Git-first workflow
Branch it, diff it, review it, revert it. The output is a WordPress site your team can own like normal software.
First run
Seamless, super-easy onboarding.
Type the slash command or ask the agent to run before-we-start. It checks Bun, Docker, Etch zips, license keys, and wp-env ports – then a what onboarding pass captures your brief into AGENTS.md before bun run dev.
before-we-startONBOARDING
agent ›
/before-we-start- Bun + Node.js 20+ on the host
- Docker available for wp-env
- Etch plugin + theme zips in prerequisites/
- License keys present in .env
- localhost:6767 port free
What onboarding – AGENTS.md
you ›I am building my agency site from this Figma design /path-to-figma/agency-home.fig
You're ready to go
Skills included
The agent gets the manual, not a blank prompt.
Repo-local skills route work into focused builders. Scroll the list on the left – the routing pyramid stays pinned while you hover or tap a skill.
Scroll the skill list – hover or tap to trace its route.
build-skills – pyramidROUTING
build-etch-sitebuild-cms
use-etch-builders
Build what
create pagescreate templatescreate patternscreate components
Build how
write etch csswrite vanilla jsbuild with acssuse-ome
ome-facetsome-wooome-components
ACSS + OME ready
Use the stack you already chose.
- Automatic CSS becomes the default styling path when ACSS is active.
- Oh My Etch UI, facet, and Woo atoms can be composed when OME is active.
- Cursor-style visual iteration can still land as clean project code.
- Etch API surfaces stay covered through explicit PHP builders and checks.
No fake magic
No more magic areas. Your favorite agent is enough.
Work in the IDE you already like. Let the agent write against real Etch builders, review the diff in Git, and keep the whole WordPress build as project code your team actually owns.
No locked AI editorNo hidden export stepNo hand-wavy builder outputNo Git history sacrificed
After deploy
Shipped the repo? Keep the agent on the live builder.
Etch Agent Bridge is the second half of Oh My IDEtch: a local MCP server and Chrome extension that connect your harness to the Etch builder on staging or production.
Local MCP serverChrome extension?etch=magic opt-in~40 Etch tools
Full setup
Get Full + IDEtchBring your agent. Keep the repo.
Oh My IDEtch plus OME Full gives you the complete Etch build setup: IDE workflow, components, patterns, facets, Woo, CMS workflows, and versioned project code.