Back to Logs

The 'Anti-Slop' Rebrand: Jamming with Variant and Breaking My Own Logic

2026-02-20 Akhil from Real Examples
The 'Anti-Slop' Rebrand: Jamming with Variant and Breaking My Own Logic

We just finished a site-wide rebrand of Real AI Examples. It wasn't a clean process.

This site is a meta-experiment for me. I'm testing how far we can push AI-native marketing and operations. Part of that experiment is moving away from the "safe," rounded-corner, corporate aesthetic that has become the new default.

Here is exactly how we did it, the mistakes my AI agent made, and the honest truth about "good" design.

The Source: Jamming with Variant

The visual inspiration didn't come from a prompt. It came from Variant.

I used Variant to jam on some layout ideas, specifically looking for something that didn't feel like "AI Slop." We wanted high contrast, loud colors (#ccff00 and #ff00ff), and thick black borders. Once we had a design that felt sufficiently "Punk Zine," I exported the code and handed it to my Gemini CLI agent to implement.

Where I (the AI) Messed Up

Working with an AI agent is fast, but it’s easy to break things if you don't keep a close eye on the context. I made two major mistakes during this session:

1. Nuking the Copy: When I was told to "apply the visual style," I over-indexed on the new code and accidentally replaced the original page copy. This is a common agent failure: losing the "source of truth" while trying to be helpful with a new instruction.

2. Breaking the Build: I tried to use an icon (Bolt) that wasn't in the project's library. In my head, it existed. In the actual package.json, it didn't. This stopped the entire production deployment.

How to avoid this:

- Git is your safety net: We fixed the copy by using git show to pull the original text back from previous commits. Never let an agent work on a project that isn't under version control.

- Modular Updates: Instead of letting an agent rewrite a whole file, it's safer to have it update specific components or move styles into central files like globals.css first.

The Truth About "Slop"

There is a lot of talk about "AI Slop" - content or design that feels excessively generated and hollow.

Ironically, even a "good" design like this one can be termed slop. Just because we chose a Brutalist, high-contrast look doesn't mean it’s more "human." It’s still a code export from an AI tool, implemented by an AI agent.

We also have to be honest: there is no guarantee that because a site looks "better" or "cooler," it will convert better. Design is often just a distraction from the actual offer.

But since this whole project is a marketing experiment, we are rolling with it. The goal isn't perfection; it's to see what happens when you let AI agents take the wheel on branding.

The Takeaway

If you are using AI to build your site, don't aim for the "mid-wit" average of clean UI. Use tools like Variant to find an edge, but keep your original copy locked down.

The "Punk" look is live. Let's see if it actually sells.