Rick Rubin Vibe Coding: What It Means for Game Devs

Rick Rubin vibe coding began as an internet joke, and it turns out to be a useful way to think about building games with AI. The joke goes like this: one of the most successful record producers alive says he has no technical ability, so maybe you don’t need any either. The useful part is less obvious. Rubin’s real skill is taste, direction and editing, and those are exactly the skills that decide whether an AI-built game feels good or just average.

This post covers where the meme came from, what vibe coding actually means, what holds up in Rubin’s approach and what doesn’t, and how to apply it to a real game project step by step.

What is Rick Rubin vibe coding?

Rick Rubin is an American record producer who co-founded Def Jam Recordings and founded American Recordings. He produced records that helped bring hip-hop into the mainstream, then went on to work in rock, metal, country and pop. His production style is known for being stripped down to the essentials, without piles of reverb or layered sound.

The meme grew out of an interview clip in which Rubin says he has no technical ability. What he offers artists is his taste and his confidence about what he likes. Developers saw the parallel immediately. Someone who can’t write code, but knows what good feels like, sits in front of an AI and directs it. That became the Rick Rubin vibe coding meme: the producer who never touches the mixing desk, applied to software.

Rubin then took it further himself. He released The Way of Code, a reworking of the Tao Te Ching for the age of AI, framed as a meditation on vibe coding and made with Claude, Anthropic’s AI model. It exists as an interactive website and a book. In a podcast conversation he also compared vibe coding to punk rock: anyone can pick it up and make something before they are “ready.”

So when people search for Rick Rubin vibe coding, they usually want one of two things:

• The meme: the “no technical ability” clip and the jokes built on it.
• The philosophy: the idea that directing AI is a creative skill like producing, and Rubin’s book about it.

Both lead to the same practical question: how do you work like a producer when the AI is your session musician?

What does vibe coding mean?

Vibe coding is a way of programming where you describe what you want in plain language and an AI writes the code. You judge the result mainly by running it, not by reading every line. The term comes from AI researcher Andrej Karpathy, who described it as giving in to the vibes and forgetting the code even exists. Anthropic’s Wikipedia entry links the spread of the practice to agentic tools such as Claude Code. An agent is an AI that can write files, run them and fix its own errors in a loop, instead of only answering in chat.

A few terms beginners run into straight away:

• Prompt: the instruction you give the AI. In vibe coding, prompts often describe how something should feel, not just what it should do.
• Iteration: one round of “change something, run it, judge it.” Vibe coding is mostly iteration.
• Regression: when a new change breaks something that used to work. This is the most common way vibe-coded projects fall apart.

What is possible with vibe coding? A lot, at small scale. Game jam entries, browser prototypes, one-screen arcade games, level editors and small tools are all realistic for someone with little or no programming background. It gets harder as projects grow. Large codebases, multiplayer netcode, performance-critical systems and anything security-sensitive still need someone who understands the code. The Rick Rubin vibe coding framing doesn’t remove that limit. It just tells you what to focus on inside it.

What Rick Rubin says about creativity, translated to code

Across his interviews and writing, Rubin keeps returning to a few ideas. Taste matters more than technique. Attention matters more than effort. The best version of a work is usually the one with less in it. His punk start shows the attitude too: as a teenager he formed a punk band called the Pricks, and later he played guitar in the band Hose, whose track became Def Jam’s first release. He made things before anyone would have called him qualified.

Each of those ideas maps onto a concrete vibe coding habit:

Studio principle	What it means when vibe coding a game
Taste over technique	Your job is knowing what fun feels like and saying it precisely. The AI handles syntax.
Listen before you judge	Play every build. Don’t approve code you haven’t experienced.
Strip to the essentials	Cut features that don’t serve the core loop, even if the AI built them well.
Ask for another take	If a version feels wrong, ask for an alternative. Don’t patch it ten times.
Punk: start before you’re ready	Ship a small playable thing this weekend instead of planning a big one forever.

One honest caveat. Rubin’s “no technical ability” line works because he spent decades training his ear. A beginner’s taste in game feel is real but untrained. The fix is the same one musicians use: play a lot of games in your genre, notice what you like, and put names to it (“tight,” “floaty,” “crunchy,” “readable”). That vocabulary is your instrument.

What does Rick Rubin do in the studio?

Rubin produces. He isn’t the main performer or the engineer. He listens to takes, says what is working and what isn’t, pushes the artist toward their strongest material, and removes whatever is unnecessary. The musicians do the playing. He makes the decisions.

That is the role you take on when you vibe code. The AI is a tireless session player: fast, capable, and happy to play whatever you ask for. A session player with no direction plays something generic. Developers on forums often make the same point about coding agents: if you don’t know what you want, the agent gives you something average, and you spend your time and energy correcting it. The Rick Rubin vibe coding lesson is that direction is the scarce skill, not output.

A producer’s brief for a game

Before the first prompt, write a brief of five lines or fewer:

1. The feeling: one sentence on what playing it should feel like (“tense, quick runs, die and retry instantly”).
2. The core loop: the action the player repeats (“jump between moving platforms to reach a lantern”).
3. The reference: a game or two whose feel you want, named in plain words.
4. The cut list: what this version will not have (no menus, no saves, no story).
5. The done test: how you’ll know it works (“a friend plays three runs without asking how”).

The cut list is the most Rubin-like line in that brief. Saying what to leave out early stops the AI from piling on features you never asked for.

Rick Rubin vibe coding with WizardGenie: a worked example

A producer needs a room where takes happen quickly. For games, that room is WizardGenie, the AI game engine inside Sorceress. A game engine is the software layer that handles rendering, input and the game loop so you don’t have to build them from scratch. WizardGenie is AI-native: you describe the game you want, and it writes it, runs it and iterates on it in real time. That fits the producer loop of take, listen, note, next take.

WizardGenie drives the leading AI coding models, and you can switch between them freely with your own API key. In studio terms, that means swapping session players without leaving the room. It runs on the web with nothing to install, and as a Windows desktop app with an auto-updater that adds native file access and longer agent sessions. The WizardGenie overview explains the engine in more depth.

The project: “Lantern Hop”

Here is a one-screen platformer, built the Rick Rubin vibe coding way.

Take 1: the brief. Paste the five-line brief into WizardGenie: “A one-screen platformer. Tense, quick runs, instant retry. Jump across moving platforms to reach a lantern. No menus, no score, no story. Done when a new player finishes in under a minute.”

Listen. Play it straight away. Don’t read the code yet. Notice how it feels: maybe the jump is floaty, the platforms are too slow, and respawning takes a beat too long.

Notes, not fixes. Give notes the way a producer would, specific and about feel: “Jump feels floaty. Cut hang time, make the fall faster than the rise. Respawn should be instant.” You don’t need to know the physics terms. The engine’s job is to turn the note into code.

Ask for a tuning block. One technical request is worth learning early: ask the AI to put every feel-related number in one place. Then you can tweak feel without another full round. Here is what that looks like in a small browser platformer written with Phaser 3. It is an example of the pattern, not code the engine is guaranteed to produce:

const TUNING = {
  runSpeed: 220,
  jumpVelocity: -460,
  gravity: 1300,
  coyoteMs: 90 // grace period to jump just after leaving a ledge
};

class Play extends Phaser.Scene {
  create() {
    this.player = this.add.rectangle(100, 300, 32, 32, 0xffcc55);
    this.physics.add.existing(this.player);
    this.player.body.setCollideWorldBounds(true);
    this.keys = this.input.keyboard.createCursorKeys();
    this.lastGrounded = 0;
  }

  update(time) {
    const body = this.player.body;
    if (body.blocked.down) this.lastGrounded = time;

    const dir = (this.keys.right.isDown ? 1 : 0) - (this.keys.left.isDown ? 1 : 0);
    body.setVelocityX(dir * TUNING.runSpeed);

    const canJump = time - this.lastGrounded <= TUNING.coyoteMs;
    if (Phaser.Input.Keyboard.JustDown(this.keys.up) && canJump) {
      body.setVelocityY(TUNING.jumpVelocity);
      this.lastGrounded = -Infinity;
    }
  }
}

new Phaser.Game({
  type: Phaser.AUTO,
  width: 800,
  height: 450,
  physics: { default: "arcade", arcade: { gravity: { y: TUNING.gravity } } },
  scene: Play
});

With a block like this, “less floaty” becomes a quick edit: raise gravity, keep jumpVelocity about the same, and play again. That is the closest a vibe coder gets to riding a fader.

Cut. By take five or six the AI may have added a particle trail, a double jump and a timer you never asked for. Play with each one switched off. If the game feels just as good without it, cut it. Rubin’s stripped-down sound came from removing things that were technically fine.

Dress it. Once the loop feels right, replace the placeholder rectangles. Auto-Sprite v2 (Pro) creates game-ready 2D characters, items and effects, and Sound Studio covers music, sound effects and voice, with a built-in editor for trimming. If you also work in other coding agents, the Sorceress API gives them a single key to generate the same kinds of assets.

Common mistakes with the Rick Rubin vibe coding approach

The meme makes it sound like taste alone is enough. In practice, these are the ways it goes wrong:

• Treating “no technical ability” as a goal. Rubin’s ear took decades to develop. Use the AI to learn: when it fixes a bug, ask it to explain the fix in two sentences. Within a few projects you’ll be able to read error messages and spot bad fixes.
• Vague notes. “Make it better” gets you a random change. “Enemies telegraph too late, add a half-second flash before they attack” gets you the change you wanted.
• Approving takes you haven’t played. A producer never signs off on a track without hearing it. Run every build, especially after the AI says the change is done.
• Patching instead of retaking. If a system has been patched five times and still feels wrong, ask for a clean rewrite of that one system from a fresh, short brief.
• Scope creep. AI makes adding features cheap, so projects bloat. Keep the cut list from your brief and stick to it.
• No safety net. Save a copy or commit every time a version feels good. Regressions are the main way vibe-coded games die, and a saved good take lets you roll back in seconds.
• Mistaking philosophy for method. The Way of Code is about attitude, not technique. Read it for mindset, then pair it with a loop you can repeat.

The workflow at a glance

Rick Rubin vibe coding works best as a short, repeatable loop rather than one magic prompt:

1. Brief: five lines covering feeling, core loop, reference, cut list and done test.
2. Take: let the engine build a first version. In WizardGenie it writes, runs and iterates in real time.
3. Listen: play it before reading anything.
4. Note: give specific feedback about feel, one or two notes per round.
5. Tune: keep feel numbers in a single tuning block and adjust them directly.
6. Cut: remove anything the game doesn’t need.
7. Dress: add real art and audio once the loop is fun.
8. Save the good take: keep a copy of every version that works, then export the build and host it wherever you like.

Rubin is right that taste is the scarce skill, and the meme is right that you can start without being an expert. The part people skip is that taste only counts when you apply it every round: play, react, cut. If you want to see what else fits around the engine, the Sorceress tools guide lists every tool in one place. Then go make something small, and do it this weekend.