divi5-builderlisted

Build or edit Divi 5 pages on any WordPress site via the WP REST API — using native Divi 5 modules so pages stay editable in the Divi visual builder, with a custom-HTML "code" module fallback. Use whenever the user wants to create, build, edit, redesign, or lay out a page/section/hero/pricing/landing page on a Divi 5 WordPress site, set a page as the homepage, insert sections/rows/columns/modules, upload images to the media library, or "build a page from this design brief". Handles credentials from the shared .web-creds.txt securely. Trigger even if the user just says "add a section to the site", "update the homepage", or names a site + a page change.
doughoseck/divi5-builder · ★ 1 · Web & Frontend · score 77

Install: claude install-skill doughoseck/divi5-builder

# Divi 5 site builder Create and edit Divi 5 pages through the WordPress REST API. Divi 5 stores pages as WordPress block markup (``), so you build a page by writing that markup into `content` and POSTing it. This skill gives you a **spec → markup compiler** (`scripts/divi.js`) and a **secure REST client** (`scripts/wp.js`) so you rarely touch raw markup or credentials directly. Default strategy (agreed with the author): **native modules first** — real `divi/section/row/column/text/heading/button/image/blurb/icon-list` modules that stay fully editable in the visual builder. Fall back to a `divi/code` module only for a section whose layout the native set can't express. ## Styling rules — NON-NEGOTIABLE These come straight from how the author builds; follow them exactly. The point of Divi is that everything is editable in the builder and re-themeable from one place — inline CSS and hard-coded per-module values destroy that. 1. **NEVER use inline CSS.** No `style="..."` attributes in any module's HTML content — ever. It's the hardest thing to find and edit and it defeats the builder. Module content holds clean **semantic HTML only** (`<h1>`, `<h2>`, `<p>`, `<ul>`…). Style through **module settings** (the `decoration.*` objects the compiler emits), never through markup. `scripts/divi.js` enforces this — do not hand-write blocks that reintroduce inline styles. (The one exception is a `code` module, which is intentionally raw HTML/CSS; keep