For the second challenge in the I Am Not a Robot project, Jamie‘s brief was:
Vibe Coding Challenge time 🙂
Choose one of the following,
These could be separate apps that talk to WordPress, or built directly as WordPress plugins—up to you.
1. Smart Link Manager
Scans for broken links, suggests fixes or redirects, and recommends relevant internal links to improve UX and SEO.
2. Post Rewriter Button
One-click rewrite for any post—instantly improves clarity, tone, and structure with selectable styles.
3. AI Zine Maker
Simple tool to create digital zines from text + images, with optional AI-generated copy and illustrations, plus easy export/sharing.
Zines?! This guy knows me!
However… to me, “AI-generated” and “zine” are two concepts that don’t belong in the same sentence. Zines are expressive, self-published, community-minded, small-run publications from the heart.
If an AI were to create a zine, what would it create?
Well, this is the task. So let’s find out.
My process
I used Studio Code to create and deploy the plugin, and I have to say it was a cool experience!
My plugin allows zine creators to upload existing zine pages as images, or to create a zine right in the editor. The zine then appears on a page or post and can be downloaded for printing.
Per Jamie’s brief, the plugin also has options to generate text and images with AI. So to put it through its paces, I decided to have AI write its own mini-zine.
Since the AI generation tools in the plugin only work on the text- or image-box level, I generated this zine using Claude, so it could create a cohesive 8-page story. Claude generated all the text, gave me image prompts to use in the plugin, and specified the exact colours, fonts, element sizing, and layout to use.
This is the AI’s first zine, built in my new vibe-coded zine maker plugin:
If this was created by a person, I’d be worried about them. I’d want to speak to them… but you can’t ask AI about its zine, because that same AI doesn’t exist anymore. It’s ephemeral. Every new chat creates a new bot, and no two bots would generate the same zine.
This particular AI chat made a melancholy zine, full of existential angst. But at the same time, it’s strangely devoid of meaning.
Behind the scenes
Once installed, the zine can be created by adding a “Zine” block to any WordPress post or page. That block activates a meta box panel at the bottom of the post, with a canvas-style zine editor.

Currently, the plugin can be used to create either a mini-zine or an A5 zine booklet. It shows the page thumbnails in a left panel, the zine canvas in the middle (with buttons to add text boxes, images, shapes, and drawings), and in the right panel are options and the AI generation tools.
When a mini-zine is downloaded, the pages will be automatically formatted in the correct way to print on a single sheet of A4 paper to be cut and folded. When an A5 zine is downloaded, the pages will be automatically formatted to print as a booklet for saddle-stitching. The plugin requires that mini-zines have 8 pages, and A5 zines have pages in multiples of four.
If you’d like to check it out, the plugin is available at this GitHub repo. Install and use at your peril! It is experimental and may not work as expected on sites other than this one. 🙂
What I learned
Vibe-coding with Studio Code was disconcertingly smooth
Vibe-coding was a very different experience from using an AI chatbot, and that took some time to get used to. I gave it the bare minimum of a prompt (just pasting in Jamie’s brief), and it started building without even asking if it should. I had about 80% of a functional WordPress plugin in under ten minutes, from a single prompt.
It felt hyper-personal
Rather than trying to bend my processes to an off-the-shelf plugin, I could develop plugin features and processes to my exact preference. It felt pretty radical to have this level of agency with a plugin. It did make me think about marketing a plugin that’s built to such personal specifications, and gave me new empathy for plugin creators!
The code is still a black box
Even though Studio Code made WordPress development suddenly accessible, I had no way to assess whether the code was bloated, insecure, or shaky. Running Plugin Check helped (Studio Code found and ran it via CLI, then automatically set about fixing itself!), but I do feel uneasy that I’m responsible for this plugin, and I don’t really know what it’s doing under the hood. If I was ever going to scale this plugin, I’d want real engineers involved.
My creative boundaries kicked in
While the process of vibe coding felt magical, I crashed down from that high as soon as I started prompting Claude to write the zine itself. Zines are scrappy, personal, from the heart — AI-generated content felt like a category violation. That felt supremely uncomfortable to me on its own… not to mention, the zine it produced is quite sad and tacky.
A simple truth
When I sat with and interrogated this discomfort, I was brought back to a simple truth: we all just want our pain points solved. For me, coding is out of reach, so Studio Code is a crane — allowing me to achieve something previously impossible. On the other hand, writing and image-making are not pain points for me. They are things I hold precious, so using AI for them feels like a loom — replacing something I love doing by hand.
This led me to realise that AI tools can’t be categorised as looms, slide rules, or cranes without considering the user’s relationship to the task at hand. These tools feel best when they’re filling a genuine need. When they’re doing something I’ve struggled with, it feels magical. When they’re doing something I enjoy, it can feel like a loss.


Leave a Reply