One devkit · many LocalWP sites

One devkit for every WordPress site you build.

Bring your agents. Keep your work in Git. The LocalWP devkit is one long-lived workspace that builds unlimited Etch sites – no Docker maze, no per-site checkouts, no magic box.

Get Full + IDEtch See the workflow

oh-my-idetch-devkit1 DEVKIT · N SITES

devkit/projects/site-a/site-b/site-c/

one command per site

/new-project
  -> site name -> slug, domain, webroot inferred
  -> bind -> check -> sync -> activate

$ bun run localwp:sync — –project site-aSame devkit. New site in seconds.

One workspace, not many checkouts

One devkit. Unlimited sites.

Each site is a projects/<slug>/ folder – its own source, CMS, and LocalWP binding – all sharing one bun install, one skill set, and one updater. Stop cloning a fresh starter for every client.

Site A

projects/site-a/

src/Site/**
cms/acf-json
project.json

bound to site-a.local

Site B

projects/site-b/

src/Site/**
cms/acf-json
project.json

bound to site-b.local

Site C

projects/site-c/

src/Site/**
cms/acf-json
project.json

bound to site-c.local

Three live projects coexist in one devkit today – each bound to its own LocalWP site, each a separate deployable plugin ZIP.

Bring your own agents

Use the tools you already pay for.

The devkit is not another closed workspace. It gives Codex, Claude Code, Cursor, Copilot, OpenCode, and whatever comes next the same thing they need: one long-lived repo with real Etch rails, and a LocalWP site per project to preview against.

CodexClaude CodeCursorCopilotOpenCodeWhatever comes next

Describe

Give the agent the site, page, CMS model, or component you need.

Build

It writes PHP builders, CMS JSON, styles, and project files inside the repo.

Review

You inspect the diff, run project:check, sync to LocalWP, and keep the good code.

Ship

Commit the work and build a deployable plugin ZIP like normal software.

What the devkit owns

Rails for agents. Ownership for you.

The system is deliberately boring in the right places: real files, real PHP, real Git history, and a real LocalWP site to preview against.

01

Code-owned site structure

Pages, templates, patterns, and components live in projects/<slug>/src/Site/**. The WordPress database is the local preview target, not the source of truth.

02

Strict PHP builders

The agent writes against real Etch builders for blocks, loops, conditions, dynamic content, styles, JavaScript, and component slots.

03

CMS in version control

CPTs, taxonomies, ACF/SCF fields, seed content, and media workflows stay explicit, repeatable, and reviewable.

04

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

Type the site name. The devkit does the rest.

Run /new-project and give the Local site name plus a build brief. The devkit infers the slug, domain, web root, and plugin path – then binds, checks, syncs, and activates. The brief lands in AGENTS.project.md before the first build.

new-projectONBOARDING

agent ›/new-project

LocalWP site exists in Local
Premium plugins licensed in the app
Site Shell opened once
Slug + domain + web root inferred
Plugin activated via WP-CLI

Intake – site name + brief

you ›Site name: "agency website". Build me a five-page marketing site from this Figma /path-to-figma/agency-home.fig

You're ready to go

Updates

Update once. Every project stays untouched.

Run bun run devkit:update to refresh the shared tooling and project template for all future sites. Every existing project – source, CMS, and LocalWP binding – is protected by a manifest, SHA-256 verified, and backed up before anything changes.

Manifest-trackedSHA-256 verifiedTimestamped backupprojects/** never touched

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, sync to a real LocalWP site, review the diff in Git, and keep the whole WordPress build as project code your team actually owns.

No Docker mazeNo per-site checkoutsNo locked AI editorNo hidden export step

After deploy

Shipped the repo? Keep the agent on the live builder.

OhMyIDEtch MCP is the second half of Oh My IDEtch: a local MCP server that connects your harness to the Etch builder through Etch's native AI Connector – on staging, production, or a client site.

See OhMyIDEtch MCP Back to package overview

Local MCP serverEtch AI Connector75+ Etch toolsNo browser extension

One devkit. Every site.

Bring your agent. Build every site from one repo.

Oh My IDEtch plus OME Full gives you the complete Etch build setup: a long-lived LocalWP devkit, agent skills, components, patterns, facets, Woo, CMS workflows, and versioned project code.

Get Full + IDEtch