WordPress Studio MCP  🔗 **Source:** [WordPress Studio MCP](https://www.youtube.com/watch?v=dCS6WExmCYQ) > [!note]+ Document Notes > tags: [wordpress-studio, mcp, ai-workflow, wordpress-development, agentic-development, block-themes] > author: Jonathan Bossenger > source: Jonathan Bossenger (YouTube) > reference: https://www.youtube.com/watch?v=dCS6WExmCYQ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: WordPress Studio MCP > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [WordPress Studio](https://developer.wordpress.com/studio/) - [Studio CLI blog post](https://developer.wordpress.com/blog/) - [WordPress MCP server (npx-installable)](https://github.com/Automattic/wordpress-mcp) ## 📝 Summary - Bossenger live-streams a hands-on walkthrough of the new WordPress Studio MCP server, which connects Studio (Automattic's free local WordPress dev environment) to AI coding tools over the Model Context Protocol. - Why it matters: it pushes WordPress toward "true agentic development" — an agent can spin up a local site, install plugins from GitHub, scaffold and restyle a full block theme, all while you do something else. - Key stakeholders: Automattic/WordPress.com (ships Studio + the CLI/MCP), Vladimir (built the integration, watching the stream), Nick (wrote the Studio CLI blog post before leaving), and WordPress developers experimenting with agentic workflows. - Risks and tradeoffs: clone-the-repo install friction (vs. the npx convenience of the WordPress MCP server), "always allow tools" security exposure, and a UX wrinkle where template-based editing leaves the Pages homepage empty and confuses users. - Bottom line: he builds a passable full block theme for a fictional coffee shop in under an hour without writing code — proof the workflow is real, with a human still tweaking the output. ## 📖 Main Content - The Studio MCP server bridges WordPress Studio with AI tools via MCP. It rides on the recently shipped Studio CLI, which gives "full feature command line completion" for much of the Studio workflow — creating and managing sites, and running WP-CLI through `studio wp ...` (or just `wp` if WP-CLI is already installed). The CLI is framed as an on-ramp to get Studio users into WP-CLI. - Setup: he configures the MCP server in VS Code (normally per-project, here in the global config). He notes Claude desktop doesn't hot-reload config changes — you must stop and restart it "like it's Windows 95." He also contrasts Claude desktop's opaque "pulsating icon" with Claude Code, where you can click the running process and see what's happening. - Workflow demo 1 — scaffold: he prompts an agent ("You are an expert WordPress developer... you create custom block theme templates") to build a custom block theme for a fictional client, a small coffee shop selling beans and accessories online. The agent (he notes Vladimir used Opus, which can generate images; he's unsure GPT can) names theme colors after coffee-related things and produces what he calls "a pretty good start" for anyone who's never built a block theme. - Workflow demo 2 — restyle: he switches to Opus and prompts "you are an expert WordPress theme designer/developer. Help me make the John's coffee theme more modern and exciting. Include bold colors, fonts, and layouts." He stresses he's "not a designer," yet the agent returns "certainly not a horrible looking website," done in about an hour. - Contested/uncertain points: whether GPT can generate images like Opus (he's unsure); and a WordPress-level UX critique, not an MCP bug — with template-based site editing, editing the front page template works, but the Pages > homepage entry shows "nothing," which he calls confusing for users. - The friction he wants fixed: having to clone the repository. He'd prefer the npx pattern the WordPress MCP server uses — an npm package you run without cloning. The reveal: install Studio CLI as a package and "MCP would just come with it and it all just works." ### 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=0) What the Studio MCP server is - Studio MCP "connects WordPress studio with AI tools via MCP." - Built on the updated Studio CLI from a blog post Nick posted before leaving Automattic. - Studio CLI = "full feature command line completion for much of your studio workflow including creating and managing sites running WPCLI." - Run WP-CLI via `studio wp ...`; if WP-CLI is already installed, just `wp`. Framed as a way to get Studio users into WP-CLI. #### ⏱️ [00:01:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=90) MCP config and tool ergonomics - Configures MCP in VS Code — usually per-project, here global "just for now." - Claude desktop "still doesn't refresh when you change the config" — must stop/start "like it's Windows 95." - Likes Claude Code over Claude desktop: you can click the running process and see what's happening, vs. the desktop's "pulsating icon" with no visibility. - "Always allow tools from studio. I don't care." Mitigated by a two-machine setup — disposable streaming laptop, separate work workstation. #### ⏱️ [00:03:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=210) Scaffolding the coffee-shop block theme - Prompt persona: "You are an expert WordPress developer... designer developer... you create custom block theme templates." - Use case: a small coffee shop selling coffee beans and accessories online. - Vladimir used Opus, "which can probably generate images" — unsure GPT can. - Agent names colors after coffee-related stuff; "a pretty good start" for first-time block-theme builders. #### ⏱️ [00:05:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=330) Agentic WordPress and the template UX problem - "a step towards like true agentic WordPress development" — spin up a site, install a plugin from GitHub, give it a theme, get it going while doing something else. - Template-editing UX critique (a WordPress problem, not MCP): edit the front page template and it changes, but Pages > homepage shows "nothing in the homepage," which confuses users. - Install friction: dislikes cloning the repo; wants the npx pattern from the WordPress MCP server. Reveal: install Studio CLI as a package and MCP "would just come with it." #### ⏱️ [00:07:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=450) Restyle with Opus and the verdict - Switches to Opus: "Help me make the John's coffee theme more modern and exciting. Include bold colors, fonts, and layouts." - Caveat: "I am not a designer. I'm a guy who writes code for a living or used to." - "this is the kind of thing you can do while you are making a cup of coffee." - Result: "certainly not a horrible looking website," done in an hour, "without writing any" code — "full block theme implementation." - Stance: pro-AI "as long as there is an human element involved." ## 📚 References - [WordPress Studio](https://developer.wordpress.com/studio/) - [Studio CLI announcement (developer.wordpress.com blog)](https://developer.wordpress.com/blog/) - [Automattic WordPress MCP server (npx pattern)](https://github.com/Automattic/wordpress-mcp) - [Model Context Protocol](https://modelcontextprotocol.io/) ## 🗣️ Paraphrase - The WordPress Studio MCP server wires Studio into AI tools through MCP, building on the recently shipped Studio CLI (announced by Nick before he left) that brings command-line control of Studio sites and WP-CLI. - After configuring the server in VS Code's global MCP config — and grumbling that Claude desktop needs a full restart to pick up config changes — Bossenger has an agent scaffold a custom block theme for a fictional coffee shop, then switches to Opus to restyle it with bolder colors and layouts. - He flags two snags: the clone-the-repo install (he wants the npx convenience of the WordPress MCP server) and a WordPress-level UX quirk where template-based editing leaves the Pages homepage empty. Still, he builds a decent full block theme in under an hour without writing code, calling it a real step toward agentic WordPress development with a human in the loop. ## 📰 Newsletter - Fancy spinning up a WordPress site while your coffee brews? Jonathan Bossenger takes the new **WordPress Studio MCP server** for a live test drive — and it's a genuine glimpse of agentic WordPress. Riding on the fresh Studio CLI, the MCP server lets an AI agent create local sites, run WP-CLI, and scaffold a full block theme on command. - His demo: a made-up coffee shop, a "make it modern and exciting" Opus prompt, and a respectable block theme built in under an hour without hand-writing code. Highlights for builders: it's a great on-ramp if you've never built a block theme, and it pairs nicely with VS Code or Claude Code (where, unlike Claude desktop, you can actually watch the agent work). - Two gripes worth knowing before you try it: you currently clone the repo (he'd love the `npx` convenience the [WordPress MCP server](https://github.com/Automattic/wordpress-mcp) already has), and template-based editing can leave your Pages homepage looking empty — a WordPress UX thing, not an MCP bug. Grab [Studio](https://developer.wordpress.com/studio/), wire up the MCP server, and let the agent do the boring scaffolding. ## ✅ Action Items #### DevRel - Developer advocacy: produce a short "Studio MCP in 10 minutes" demo with the npx-style install once it ships; measure setup-completion rate. - Education: write a beginner block-theme tutorial that uses the agent-scaffold-then-hand-tweak flow Bossenger models. - Developer experience: document the global vs. per-project MCP config choice and the Claude-desktop restart gotcha in setup docs. - Developer marketing: capture the "full block theme in under an hour without code" claim as a social proof artifact (with the human-in-loop caveat). - Community management: collect feedback on the template-vs-Pages homepage confusion as a recurring onboarding pain point. - Internal/external/cross-project: feed the clone-vs-npx request to the Studio CLI team as a packaging requirement. #### OSPO - Policy & Governance: define a default tool-approval posture for MCP servers so "always allow" isn't the path of least resistance. - License Compliance: confirm license terms for AI-generated theme code before it ships in client work. - Security Management: document the trust boundary an MCP server with filesystem/site access crosses; recommend disposable/sandboxed environments. - Software Inventory: track Studio CLI + MCP as a paired dependency for SBOM once bundled. - Developer Support: publish guardrails for granting agents site/repo access. - Community Engagement: N/A — no upstream funding or operator-agreement angle in this source. - Strategic Alignment: map agentic local-dev tooling to the broader WordPress AI roadmap. #### Community - Maintainers: N/A — source is a single-author demo, not a maintainer-governance topic. - Contributors: invite first-time block-theme builders to try the agent-scaffold path as an onboarding ramp. - Sponsors: N/A. - Ecosystem: coordinate the Studio MCP and WordPress MCP server install patterns so they converge. #### WordPress - Core: address the template-edit vs. Pages-homepage "empty homepage" UX confusion Bossenger calls a WordPress problem. - Core Performance: N/A. - Core AI: define responsible-AI guardrails and an evaluation set for agent-generated themes. - **Core Program Team:** coordinate Studio CLI, MCP, and the block-editor template UX threads across teams. - Mobile: N/A. - Playground: build a reproducible Playground lab that mirrors the Studio MCP scaffold flow for users without a local install. - Community: N/A. - Training: turn the demo into a Learn WordPress lesson on agentic block-theme scaffolding. - Marketing: N/A. - Support: prepare a KB entry for the empty-Pages-homepage confusion. - Design: audit the template-vs-page editing model for the confusion noted here. - Documentation: examples-first docs for the npx install pattern once shipped. - Photos / TV / Polyglots / Meta / Hosting / Tide / Openverse / Themes / Plugins: N/A — out of scope for this source. - Accessibility: review AI-scaffolded themes against WCAG before treating "looks fine" as done. - CLI: align Studio CLI command UX and docs with WP-CLI conventions. #### The WPCC - Programs / Projects / Funding experiments: N/A — no governance or funding angle in this source. ### FAIR - Technical independence: N/A — source doesn't touch metadata, provenance, or distribution independence. ## 🧪 Hypotheses - Bundling MCP into the Studio CLI npm package (no repo clone) measurably increases first-run setup completion vs. the clone workflow. - Agent-scaffolded block themes give first-time theme builders a faster path to a working theme than starting from a blank `theme.json`. - "Always allow tools" defaults raise the rate of unintended filesystem/site changes vs. per-tool approval. - The template-edit / empty-Pages-homepage gap drives a measurable share of beginner support tickets. - Agentic local-dev (spin up site + install plugin + theme unattended) reduces time-to-first-working-environment for developers. - A human tweak pass after agent generation produces higher-quality output than agent-only generation (Bossenger's stated model of the future). ## 📊 Methodology - Setup-completion A/B test: clone install vs. npx-bundled install, measure % reaching a working MCP connection and median setup time. - Beginner usability study: novices build a block theme with agent-scaffold vs. blank-start; measure time-to-working-theme and error counts. - Telemetry on tool-approval mode: compare unintended-change incidents under "always allow" vs. per-tool prompts. - Support-ticket text analysis: classify beginner tickets to size the empty-homepage confusion. - Task timing: instrument end-to-end "spin up site → plugin → theme" runs for time-to-environment. - Blind quality rating: panel scores agent-only vs. agent-plus-human theme outputs. ### ❓ Questions - Can the MCP be bundled into the Studio CLI package so install is a single npx/npm step? - Which models can generate theme images in this flow, and which can't (GPT vs. Opus)? - What's the right default tool-approval posture for an MCP server with site and filesystem access? - How should WordPress resolve the template-vs-Pages editing model so the homepage isn't "empty"? - What guardrails keep agent-generated themes accessible and secure by default? ### 🔮 Future Research - Packaging study on npx-bundled MCP adoption vs. clone-based adoption. - A maturity model for "agentic WordPress development" stages and where Studio MCP sits. - Quality and accessibility benchmarks for AI-generated block themes. - UX research on the block-editor template/page mental model for beginners. ### 💡 Implications - Practice: local WordPress dev shifts toward agent-orchestrated scaffolding with a human polish pass. - Policy: organizations need explicit MCP tool-approval and sandbox policies before agents touch sites. - Security: MCP servers with site/filesystem access expand the trust surface; disposable environments matter. - Education: block-theme onboarding can start from a working agent scaffold instead of a blank file. - Funding/roadmap: signals demand for packaging convergence between Studio MCP and the WordPress MCP server. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~7–8 — conversational, contraction-heavy spoken transcript with short clauses. #### 👀 Visual learners - Present: live screen-share of the agent building and restyling the theme; visible color choices named after coffee. - Improve: add an architecture diagram of Studio ↔ MCP ↔ AI tool; before/after theme screenshots with captions. #### 🔊 Aural learners - Present: it's a spoken live stream; narration throughout. - Improve: ship a 2–5 minute clean audio recap without the "jumpy" music he mentions. #### 🗣️ Verbal learners - Present: defines Studio CLI in plain terms; coffee-shop analogy for the demo client. - Improve: a short glossary (MCP, Studio CLI, block theme, WP-CLI) and plain-language callouts. #### 🧩 Kinesthetic learners - Present: a reproducible end-to-end build (config → scaffold → restyle). - Improve: a step-by-step checklist and a copy-paste prompt set to follow along. #### 🧠 Logical learners - Present: cause→effect framing (config change → restart needed; clone → friction → npx wish). - Improve: a decision tree for global vs. per-project MCP config and model choice. #### 🧑‍🤝‍🧑 Social learners - Present: live chat interaction; explicit invitation to comment on social media. - Improve: a discussion prompt or community thread for sharing agent-built themes. #### 🧘‍♀️ Solitary learners - Present: self-paced follow-along format. - Improve: a self-check ("did your homepage render?") and reflection prompt on where to hand-tweak. #### 🌿 Naturalistic learners - Present: N/A — no sustainability or environment framing beyond the coffee theme. - Improve: note the compute cost of agentic generation as a lifecycle consideration. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: N/A for the video itself; the generated theme's semantics aren't audited on stream. - Improve: have the agent emit landmark roles and heading order; audit generated `theme.json`/templates. #### Keyboard navigation - Present: not addressed. - Improve: verify generated theme is keyboard-navigable with visible focus. #### Contrast and readability - Present: "bold colors" requested without a contrast check. - Improve: enforce 4.5:1 text contrast in agent-generated palettes (the coffee colors need verification). #### Text resizing and reflow - Present: not addressed. - Improve: test the generated theme at 200% zoom for clipping/reflow. #### Media and captions - Present: it's a YouTube video; auto-captions likely. - Improve: add a human-corrected transcript; the background music is described as "jumpy" — keep it low. #### Forms and interactions - Present: N/A — no forms in the demo. - Improve: if the theme adds a contact form, validate labels and error handling. #### Standards reference - Map gaps to WCAG 2.2 AA: 1.4.3 (contrast), 1.4.10 (reflow), 2.1.1 (keyboard), 1.2.2 (captions). ### 🌍 DEIB Assessment #### Cultural breadth - Present: generic small-business example (coffee shop) with broad appeal. - Improve: show multilingual/RTL theme variants the agent can produce. #### Inclusive language - Present: casual, friendly, non-exclusionary tone; jargon mostly explained. - Improve: define MCP/WP-CLI on first use for newcomers. #### Neurodiversity support - Present: chunked live-demo structure. - Improve: a written outline with consistent headings for those who prefer text over a 9-minute stream. #### Representation - Present: credits named contributors (Vladimir, Nick) generously. - Improve: N/A — single-presenter format limits representation scope. #### Psychological safety - Present: explicitly non-combative — "I'm not here to argue with you about that"; mentions blocking/reporting a chat message, signaling moderated space. - Improve: state community guidelines for the social-media comment invite. ### ✅ Logical Validity #### Strong reasoning - Inductive (demo → claim): builds a working theme in under an hour without code, then concludes the workflow is real and "things are heading" agentic — evidence directly supports the modest claim. - Causal: identifies a real cause→effect (clone install → friction; npx package → "it all just works"), grounded in the existing WordPress MCP server precedent. - Analogical: "like it's Windows 95" and "while making a cup of coffee" make the restart annoyance and low-effort workflow concrete. #### Fallacies - Hasty generalization (mild): "this is where things are heading" / "the way we do things is changing" generalizes from one successful hour-long demo. Fix: bound the claim to "for greenfield block-theme scaffolding, this works today." - Appeal to self-authority caveat: "I am not a designer" both disclaims and boosts the result ("even a non-designer got this"). Fix: have a designer rate the output to substantiate quality. #### Tone of voice - Casual, enthusiastic, self-deprecating, community-aware. Examples: "well done agentbot thing," "I'm pro it," "Good job. Seriously." Mild frustration at tooling ("most annoying thing in the world"). ### 🛡️ DARVO Analysis - Deny: N/A — no accusation is being deflected; no minimization of wrongdoing. - Attack: N/A — no attack on accusers. The closest note is blocking/reporting a chat message, which is moderation, not DARVO. - Reverse victim/offender: N/A — no recasting of an accused party as victim. - Emotional cues are present (frustration with config reloads, enthusiasm for the result) but there's no defensive DARVO structure; this is a product demo, not a dispute. ## 🎯 Conclusion - Bottom line: the WordPress Studio MCP server, built on the new Studio CLI, lets an AI agent scaffold and restyle a full block theme on a local Studio site — Bossenger ships a passable coffee-shop theme in under an hour without writing code, with a human still tweaking the result. It's a credible step toward agentic WordPress development. - Next steps for readers: install Studio and the MCP server (currently clone-based; watch for an npx-bundled release), try the agent-scaffold-then-hand-tweak flow, set a deliberate tool-approval posture rather than "always allow," and verify generated themes for accessibility and the template/Pages homepage quirk before shipping. ## 🔄 Refactor Appendix — WordPress Studio MCP > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. ### 📚 Literature Atoms (H3) #### [H1] Studio MCP server connects Studio to AI tools via MCP > [!quote] ID:rw_studio_mcp_h1 > WordPress Studio MCB server connects WordPress studio with AI tools via MCP. **Context & use**: - ⏱️ [00:00:00](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=0) - The one-line definition of what the integration is; anchors the whole demo. ("MCB" is a transcription slip for MCP.) **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=0) <!-- atomicity: 1 idea ✓ --> #### [H2] Studio MCP is a step toward agentic WordPress development > [!quote] ID:rw_studio_mcp_h2 > I definitely think this is a step towards like true agentic WordPress development. **Context & use**: - ⏱️ [00:05:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=330) - Frames the integration's significance: spin up a site, install a plugin from GitHub, give it a theme — unattended. **Tags**: #xref #addendum **Highlight**: [view highlight](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=330) <!-- atomicity: 1 idea ✓ --> #### [H3] Agents scaffold a first version that humans then tweak > [!quote] ID:rw_studio_mcp_h3 > you'll use an agent to create like a first version of something and then you will manually come along and tweak it **Context & use**: - ⏱️ [00:07:30](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=450) - His stated model of the development future: agent-generated draft + human polish, "as long as there is an human element involved." **Tags**: #xref #articleseed **Highlight**: [view highlight](https://www.youtube.com/watch?v=dCS6WExmCYQ?t=450) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Agentic tooling shifts the developer from author to editor **Claim** (one sentence, Courtney's voice): As local-dev agents scaffold working first versions, the developer's primary job moves from writing the code to reviewing and refining what the agent produces. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds for greenfield scaffolding (block themes, site setup) where a passable draft is fast to generate; breaks for novel or high-stakes logic where the human still authors from scratch. **Links**: - [[AI identity and effort]] — because extends - [[WordPress agentic development]] — because applies-in WordPress local dev - [[Human-in-the-loop review]] — because evidence-for <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Convergence question — should Studio MCP and the Automattic WordPress MCP server share one npx install pattern? — https://github.com/Automattic/wordpress-mcp #fleeting #inbox - [F2] WordPress UX bug to track — template-edit leaves Pages > homepage empty; confuses beginners #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Try the Studio MCP server scaffold flow on a throwaway Studio site — dev environment #things - [ ] Watch for an npx-bundled Studio CLI + MCP release and re-test install friction — tooling #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/WordPress Studio MCP.md|WordPress Studio MCP by Jonathan Bossenger]] ## Highlights - Okay, so WordPress Studio MCB server connects WordPress studio with AI tools via MCP. Yeah, end of last month there was an updated studio CLI blog post which Nick posted before he left. Miss you Nick. And basically it's full feature command line completion for much of your studio workflow including creating and managing sites running WPCLI D and there you go WordPress studio CLI. ([View Highlight](https://read.readwise.io/read/01kw2n102ps4q0tq9hjqrb3sdm)) - Note: One-line definition (MCB = transcription slip for MCP): the server connects Studio to AI tools via MCP, exposing the full Studio CLI workflow. - Tags: atom/literature/h1, mcp - So as a user that makes confusing, but that's more of a WordPress problem. I definitely think this is a step towards like true agentic WordPress development. And so being able to spin up a site from my agent, spin up a new site, install this plug-in from GitHub that I'm busy working on, give it a theme, give it a whatever, spin it up and get it going while I'm doing something else. I am I am liking this kind of automation between my development environment and my local local development installation, my local WordPress installation. ([View Highlight](https://read.readwise.io/read/01kw2n12rbk7zxhcwzabx059h3)) - Note: The significance: a step toward true agentic WP development — agent spins up a site, installs a GitHub plugin, applies a theme, unattended. - Tags: atom/literature/h2, agentic-development - I'm a guy who writes code for a living or used to. Now, ironically, this is the kind of thing you can do while you are making a cup of coffee. I do feel like this is where things are heading. I do feel like we're heading towards a world where you'll use an agent to create like a first version of something and then you will manually come along and tweak it and style it and fix it and change it and customize it. ([View Highlight](https://read.readwise.io/read/01kw2n15kk4zq39cazeme82tzj)) - Note: Bossenger's model of the dev future: agent-generated first version + human polish — the same author→editor shift across the AI-content thread. - Tags: atom/literature/h3, wordpress-development ## Links - [[Implementation Is Cheap So Taste Becomes the Bottleneck]] — existing Permanent captures the shift from writing the first version to selecting, correcting, and styling it. - [[Structured AI Edits Need Platform-Native Validation]] — applies-in: agent-created WordPress themes need platform-native checks before human polish begins.