# Build anything with Claude & WordPress — Austin Ginder ## 🗂️ Triage — annotated highlights surfaced > [!note]- Cross Reference > - **Direction, not code, is the valuable output** — the talk's one idea; reframes AI-assisted dev value from artifact to steering. #xref > - **The GitHub release is the deployment** — self-hosted `manifest.json` updater maps one-to-one onto Courtney's deployer workflow. #xref > - **Steering the agent keeps responsibility with the human** — the safety thesis, stated after the July 1 live-site-rendering pivot. #xref ## 🧭 Bib capsule Austin Ginder, "Build anything with Claude & WordPress," WordPress Lancaster Meetup slides, 2026 — https://slides.austinginder.com/2026-07-16-build-anything-with-claude-and-wordpress/ ## 🧠 Author's thesis (Adler Q1+Q2) A mostly-solo operator of a few thousand WordPress sites shows that real WordPress software — plugins, DB tables, REST APIs, themes, WP-CLI commands — now ships through conversation with Claude Code, and the valuable, shareable thing has moved from the code to the human's direction of the agent. In detail: a disciplined pipeline (design in Claude Design as a `.dc.html` prototype → translate via DesignSync in Claude Code → run locally on Cove → verify in a real browser with light+dark screenshots → self-hosted GitHub-release-as-deploy) scales across a spectrum from an evening's plugin to a 92-day platform rescue, as long as the human owns what the agent does. ## 🧩 Key arguments - The bottleneck moved from typing to steering; existing WordPress fluency (WP-CLI, PHP, git) is the steering wheel, so the moat is domain skill, not prompt trickery. - "Real WordPress, all the way down" — no lock-in, no new framework; a conversation yields a running site, and self-hosted updates make a GitHub release the deploy (no wp.org, no CI). - The agent does exactly what you steer it to, so responsibility stays human — proven by the Dismissed.FYI account-name leak and the July 1 "never render against live sites" pivot. ## 🗒️ Notes — Literature atoms ### Direction, not code, is the valuable output > [!quote] > The code output isn't the valuable part anymore. The direction is. - **Where**: Slide 03, the talk's stated "one idea to take home" - **Why**: the core lens for the whole deck — value shifts from artifact to steering ### The bottleneck moved from typing to steering > [!quote] > The bottleneck moved from typing to steering. - **Where**: Slide 03, supporting the "build anything" claim - **Why**: names the concrete shift a WP developer feels; explains why domain fluency beats raw coding speed ### The GitHub release is the deployment > [!quote] > The release is the deploy. No wp.org, no CI. - **Where**: Slide 06, step 5 (self-hosted `manifest.json` updater) - **Why**: a copyable distribution pattern independent of wp.org; parallels Courtney's self-hosted deployer ### Steering the agent keeps responsibility with the human > [!quote] > The agent will do exactly what you steer it to. That responsibility stays yours. - **Where**: Project 02 (Dismissed.FYI), stated after the July 1 pivot away from live-site rendering - **Why**: the safety thesis; grounds "build anything" with human accountability ## 🔖 Permanent candidates - In AI-assisted development, direction is the durable craft — when an agent writes the code, the reusable, valuable skill is the human's architectural direction, not the code it emits. ## Links - [[AI & the Future of Knowledge Work MOC]] — home; a working example of how AI-directed work reshapes the craft, with the valuable artifact moving from code to direction - [[DevRel MOC]] — a copyable five-step pipeline and a `/dev-<slug>` "cut a release" skill that's directly packageable as developer-advocacy demo material - [[Developing for WordPress with Claude Code and WordPress Studio]] — same design→Claude Code→local→browser-verify→ship arc from a different practitioner; corroborates the workflow - [[My AI Security Pipeline for WordPress Plugins]] — the same author's security-scanning counterpart: build anything, then audit the build (not the install) across the ecosystem. ## ✅ Processing checklist - [x] Claim atoms carried from deep-read analysis - [ ] Permanent candidates reviewed for promotion - [ ] Version History Diff check