I’ve been using Woody Code Snippets to manage code in WordPress for a client, but I wanted a different experience when working with snippets. Something closer to VS Code, with better navigation, revision history, and a cleaner interface.
So I decided to build it.
The interesting part is that I used three different AI tools, each with a specific responsibility.
I started with GPT to plan how the plugin should work, what features it needed, technology behind it, and how it should interact with Woody without interfering with its existing functionality.
Then I used Claude to work on the interface and design, based on that plan and that tech. I wanted something familiar to developers, not another typical WordPress admin screen.
Finally, I moved to Cursor to implement everything, connecting the frontend with WordPress and Woody’s existing data structure.
About three hours later, I had the first version of Snippet Studio.
It’s built with PHP, React, TypeScript, CodeMirror 6, Zustand, and Tailwind CSS. It works alongside Woody, so Woody remains responsible for executing snippets.
Of course, building something in three hours doesn’t mean testing, maintenance, or security suddenly stop mattering, but I find the change in the development process interesting.
Instead of spending most of my time writing the implementation, I spent more time deciding how things should work, defining constraints, and reviewing the results.
And I think that’s where development is moving.
Maybe the interesting question isn’t how fast AI can write code anymore, but how well we can guide it to build something useful.
Snippet Studio is free and open source.
