AgentKit's /ak:page-builder skill lets AI edit production websites
The new AgentKit skill converts an existing codebase into layouts and blocks an AI can safely manipulate, exposes them through an OAuth-protected MCP server, and lets ChatGPT or Claude edit landing page copy and layout in one sentence.
AgentKit just got a new skill: /ak:page-builder It basically lets AI… edit your production website 😂 Okay, okay. That’s the stupidly simplified explanation. But it’s actually pretty close. Most pages on my product websites are now built with this thing, and the idea behind it is surprisingly simple. Instead of asking an AI to randomly jump into your codebase every time you want to change some copy, move a section, or redesign a landing page, /ak:page-builder first turns your existing website into something the AI can safely understand and manipulate. Roughly speaking, it does this: Analyzes the existing codebase Discovers the components and design system already available Converts them into layouts and predefined blocks the AI can compose Exposes the whole thing through an MCP server using HTTP transport Adds OAuth so access and permissions can be controlled And suddenly… Your previously static pages become dynamically manageable by AI. Now plug that MCP endpoint into ChatGPT, Claude, or another MCP-compatible AI. From that point on, instead of: “Open repo -> find component -> change text -> fix styling -> run build -> deploy -> realize I broke something -> swear a little -> redeploy” You can basically say: "Change the hero copy on the pricing page and make the CTA section more prominent." The AI does the work. Normally, it generates a preview first so I can review the changes. If everything looks good: Publish it. Done. 😁 No manually editing source code. No rebuilding the whole damn thing just because somebody wants to change “Start free trial” to “Get started”. No opening a page builder and dragging rectangles around like it’s 2013. And this is the part I find interesting. We’ve spent years building abstractions like WordPress, Wix, Webflow, Elementor, CMS dashboards, visual editors, etc. because normal humans obviously shouldn’t need to touch source code to update a website. But AI changes the interface completely. The new abstraction doesn’t necessarily need to be another dashboard. It can just be: intent -> AI -> structured components -> preview -> publish The website still has real code underneath. Developers still own the components, constraints, design system, infrastructure, and permissions. AI simply becomes the interface for operating it. Which, IMO, is much more interesting than “AI website builders” that generate another disposable pile of HTML every time you type a prompt. The important part isn’t generating the page. It’s giving AI a controlled way to operate an EXISTING production system. I remember building websites with Wix/Elementor years ago and thinking visual page builders were already magical. If you told me back then that one day I’d just tell an AI: “Move this section up, rewrite this paragraph, make it look better, show me a preview, then publish it.” …I’d probably tell you to stop smoking whatever you were smoking. 😂 Yet here we are. It’s 2026. Who still needs a CMS or drag-and-drop page builder anyway? Right? Ps. The video below was NOT made by Opus. I hit the damn usage limit already 😂