When Enterprises Vibe Code On A Grand Scale and Its a Rare W!

Source: Dev.to

How This All Started

I was scrolling through tech Twitter, minding my own business, when OpenAI dropped a blog post about their new coding model. Standard stuff: benchmarks, charts, “state‑of‑the‑art performance,” the usual.

Then I read this:

I stopped scrolling.

They used early versions of Codex 5.3 to debug its own training, to manage its own deployment, to diagnose its own test results. The model helped build the model.

Are we living in a simulation? Because that reads like the opening crawl of a sci‑fi movie, not a product announcement.

The Idea

I don’t normally do testing on brand‑new models, but this intrigued me. I had to stress‑test the thing immediately— not with a todo app or a dashboard, but with the weirdest, most out‑of‑comfort‑zone design prompts I could imagine. I wanted to see if a model that apparently helped create itself could handle creative direction that would normally take human developers days to execute.

The Setup

• Four prompts – each a wildly different visual style for a personal portfolio website.
• Each prompt packed with specific aesthetic direction, 12‑16 negative constraints (telling the model what NOT to do), and exact content for every section.
• One shot each – gpt‑codex‑5.3, high‑reasoning mode. No follow‑ups, no corrections.

Prompt 1 – 90s American Comic Book

Todd McFarlane’s Spawn. Jim Lee’s X‑Men. Early Image Comics.
Halftone dot textures, POW/ZAP action bursts, speech‑bubble CTAs, angled comic‑panel layouts with gutters.
Negative constraints: “don’t use generic fonts, don’t use a standard grid, don’t make it look like every other developer portfolio on the internet.”

Result:

• Panels had actual gutters.
• Action bursts pulsed on hover.
• Palette was loud, saturated, unapologetically 90s.
• Minor alignment quirks (ten‑minute fixes) but the design intent was spot‑on.

Prompt 2 – New York Cartoonist Minimalism

Saul Steinberg. Roz Chast. New Yorker covers.
Thin pen‑and‑ink line art, generous whitespace, wobbly hand‑drawn borders, witty margin annotations.
Negative constraints: “no bold colors, no sans‑serifs, no CSS gradients, no hamburger menus, no corporate startup energy whatsoever.”

Result:

• Codex generated inline SVGs that actually looked hand‑drawn – wobbly lines, cross‑hatch patterns, pen‑sketch icons.
• The layout breathed; it didn’t fall back to the default card grid that most AIs default to.
• This was the prompt I expected to break it, yet Codex just… got it on the first try.

Prompt 3 – Deep Space Sci‑Fi Terminal

Nostromo from Alien meets 2001: A Space Odyssey.
CRT scan lines, glowing neon text on void‑black, radar grids, HUD overlays. Skills displayed as ship‑system diagnostics; projects as classified mission briefings. Contact form labeled “SENDER IDENTIFICATION” instead of “Name.” I even asked for a hidden easter egg.

Result:

• CSS‑generated star field.
• Authentic typing boot‑up animation.
• Glow effects balanced perfectly – bright enough for sci‑fi, readable enough for everyday use.
• The easter egg was present and functional.

Prompt 4 – Pixel Art / Minecraft Style

Design the entire website as a Minecraft inventory screen.
Skills in a 3 × 2 inventory‑slot grid with Minecraft‑style tooltips (dark purple background, rarity tags like “LEGENDARY”). Projects as quest‑log entries. An XP bar showing “Level 8” for years of experience.
Negative constraints: “all animations must use steps() timing, image‑rendering: pixelated everywhere, generate all icons using CSS box‑shadow pixel art, no image files.”

Result:

• Pure CSS pixel art: block textures from repeating gradients, stepped frame‑based animations.
• Inventory slots looked right; tooltips felt right.
• A hidden creeper easter egg was included.

What Actually Impressed Me

The “created itself” headline is wild, but three practical things sold me:

1. Negative prompting actually worked.
   I didn’t just tell Codex what to build—I told it what NOT to do. No generic fonts, no smooth gradients, no card grids, no “every portfolio ever” vibe. The model listened, and each result had a distinct personality because the constraints forced it away from its defaults.

2. Asset generation was genuinely good.
   Every prompt demanded “generate all visual assets — no placeholders, no broken links.” Codex delivered inline SVGs, CSS pixel art, code‑generated star fields, hand‑drawn borders— all self‑contained, no external dependencies.

3. Speed and token efficiency surprised me.
   These weren’t simple prompts. They contained detailed aesthetic direction, a dozen‑plus constraints, and four page sections with exact content, all run in high‑reasoning mode. Yet the model processed them quickly without truncating.

The Bigger Point

Everyone’s focused on the existential angle—simulation theory, recursive AI, “should we be worried?” Those are fun questions, but they miss the practical truth staring us in the face:

The gap between imagining something and having it exist just collapsed.

I described four visual styles—styles that require genuine design taste—in plain English. They materialized. Not perf… (the original text cuts off here, but the core message remains intact).

Exactly. But well enough that the remaining work is tweaking, not building.

Honestly, the real shift isn’t about whether AI can create itself. It’s about what it lets you create.

• A product manager who’s never written CSS can now describe their vision and see it built.
• A developer with strong backend skills can now explore visual directions they’d never attempt manually.
• A freelancer who can’t afford a designer can prototype four aesthetics before their first client call.

You’re the pilot now. Codex is the ship. And a ship that helped build itself? Turns out it flies pretty well.

The Prompts

I’m sharing all four prompts — complete with direction, constraints, and specs. Grab them, stress‑test Codex yourself.

Public GitHub Gist with all the prompts

Try throwing something weird at it—something you’d need a few days and a mood board to build yourself.

A model that helped create itself can probably handle your landing page.

Couple of Announcements

Check out a couple of open‑source projects created by yours truly:

• Ukiyo‑tone – Themes inspired by ancient Japanese techniques.
• TerminalSnap – Imagine carbon.now.sh but for terminals! Create beautiful terminal screenshots for your docs and blogs.

Loved this post?

I write about AI, productivity, and code in my Substack newsletter – Coffee, Code & AI. Join curious minds to get way more stuff like this in your inbox.

🔗 Subscribe now and never miss an update!