Vibe Creator vs. Vibe Coder

Andrej Karpathy's February 2025 tweet did something unusual for a technical post: it named a feeling. "There's a new kind of coding I call 'vibe coding,'" he wrote, "where you fully give in to the vibes, embrace exponentials, and forget that the code even exists." The phrase landed because it captured something developers were already experiencing but hadn't named — a qualitative shift in how they worked with AI, less like giving instructions to a compiler and more like collaborating with a capable partner who could take vague intent and return working software.

Within months, "vibe coding" had colonized the tech discourse. Cursor and Windsurf built marketing campaigns around it. Paul Graham quoted it. It became shorthand for a generation of builders who'd stopped caring whether they were "real" programmers and started caring only about whether the product shipped.

The word "vibe" was doing a lot of work. And it was doing that work far beyond software.

What Vibe Coding Actually Is

To understand the comparison, we need to be precise about what vibe coding actually describes. Karpathy's original framing has three components:

1. Natural language direction — You describe what you want in plain language, not in syntax.
2. AI execution — The AI writes, refactors, debugs, and builds. You're not primarily in the code.
3. Human creative ownership — You define the vision, the constraints, the aesthetic, the product direction. The authorship is yours.

What Karpathy called a new kind of coding was, in structural terms, the familiar logic of creative direction applied to software. A product manager who writes a spec has always been "directing" the engineering team. What changed is that the entity receiving the direction is now an AI with the capability to act on natural language at high quality, collapsing the gap between intent and output to minutes instead of sprint cycles.

That's the insight that generalized. The same three-part structure — natural language direction, AI execution, human creative ownership — works for film. For music. For design. For advertising. For writing. The domain changes. The pattern doesn't.

The Hierarchy: Vibe Creating ⊃ Vibe Coding

This is not a competition between two rival terms. It's a taxonomy. Vibe Coding is a specific instance of Vibe Creating — the instance that applies to software development. Vibe Creating is the meta-category. Every Vibe Coder is a Vibe Creator. Not every Vibe Creator is a Vibe Coder.

The relationship looks like this: Vibe Creating is to Vibe Coding what "creative director" is to "art director." One is the category, one is the discipline. The art director does visual work. The creative director might oversee visual work, copy, strategy, film, and experience — all at once. The Vibe Creator operates at the creative director level across every domain that AI now makes executable.

	Vibe Coder	Vibe Creator
Domain	Software, apps, tools	All creative disciplines (18 mapped)
Primary tools	Cursor, Windsurf, GitHub Copilot, Claude Code	Runway, Suno, Midjourney, Claude, v0, Kling, and all the above
Output	Working software	Film, music, design, campaigns, code, writing, and more
Direction mode	Natural language → code	Natural language + Quiver references → any medium
Authorship	Human retains product ownership	Human retains creative authorship across all outputs
Scarce resource	Product taste + system thinking	Cross-domain taste + directorial precision

The practical implication: if you understand vibe coding, you already understand the core pattern of Vibe Creating. What expands is the scope — the number of disciplines you can direct, the range of media you can work in, the breadth of creative problems you can tackle with AI as execution partner.

What a Vibe Coder Does Day-to-Day

A vibe coder opens Cursor. They describe a feature in a chat window — "I need a modal that shows a user's subscription history with a way to cancel right from that modal." They iterate on the output, refining behavior through conversation rather than syntax. They test. They ship. The code exists and they own it, but they may never have written a line of it manually.

The skills that make a vibe coder effective: product thinking (knowing what to build), system intuition (understanding how components interact even without reading every line), and taste (knowing what "good" looks like at the interface level). A vibe coder with weak product sense and no taste produces slop fast. A vibe coder with strong product thinking and a clear vision produces software at a speed that was impossible eighteen months ago.

The tools are purpose-built for the pattern. Cursor's Composer mode keeps context across the codebase. Windsurf's Cascade agent can reason across files autonomously. GitHub Copilot integrates into the existing IDE workflow for developers who want to dip in rather than go all-in. Each tool makes the same bet: that the quality of your direction matters more than whether you can write the code yourself.

What a Vibe Creator Does Day-to-Day

A Vibe Creator opens a different set of tools depending on the discipline they're working in — but the mental posture is identical. They hold a clear creative vision. They reach into a curated body of references (what we call a Quiver). They communicate intent with precision. They let AI execute. They evaluate output against their taste. They iterate.

A Vibe Creator making a short film uses Runway Gen-3 to generate shots, Kling for specific motion sequences, ElevenLabs or Murf for voice, Suno for score. They're not operating any of these tools like technicians — they're directing them like a cinematographer directs light. The shot needs a specific quality of grain, a specific length, a specific camera behavior. The Vibe Creator knows that because they have a reference in their Quiver — they've seen it somewhere, saved it, and can articulate why it works.

A Vibe Creator making a music track uses Suno or Udio to generate stems, directs the feel through reference tracks and descriptive prompts, edits and arranges in a DAW, and outputs something that sounds intentional because it was — just not executed by hand at the level of individual notes.

A Vibe Creator building a campaign uses Claude or GPT-4o to generate concept variants, Midjourney or Flux to visualize them, Runway to animate key assets, and their own strategic judgment to choose which version deserves to live. The campaign has a point of view because the Vibe Creator had one going in.

The Shared Core: The Quiver

What unifies vibe coders and Vibe Creators — the thing that separates the practitioners who produce remarkable work from those who produce generic AI output — is the Quiver.

The Quiver is the operational repertoire of curated references a creator maintains over time. For a vibe coder, the Quiver might be a library of products they admire, UI patterns they've bookmarked, interaction models they want to replicate. "I want the onboarding to feel like Linear — that combination of speed and confidence, no friction, no fuss." That reference is drawn from the Quiver. The AI knows what Linear's onboarding feels like because the vibe coder has studied it, internalized it, and can point to it with precision.

For a Vibe Creator working in film, the Quiver might contain 10,000 film references organized by cinematography style, color palette, emotional register, and era. When they direct a shot in Runway, they're not typing a generic description. They're pointing at something specific in that archive: "the quality of the light in the Paris sequences of Before Sunset, exterior, late afternoon, handheld, intimate." The AI closes the gap between the reference and the generated output. The Quiver is what made the reference precise enough to be useful.

Whether you're coding or composing, designing or directing — the Quiver is the core skill. Build it deliberately, keep it curated, organize it by function rather than just by format, and your output will be categorically different from someone who shows up to the AI with a vague prompt and no point of view.

Why Non-Coders Need to Know This

The tech press covered vibe coding because it was about developers — the traditional audience for tech journalism. But the story it was telling wasn't a developer story. It was a creative story. And the pattern it described was about to arrive in every creative discipline, one by one, as the tools matured.

Musicians who dismissed vibe coding as a tech trend were months away from their own version of the same disruption. Vibe composing — generating high-quality music through natural language direction — became real with Suno v3 and Udio. Filmmakers who ignored it were eight months away from Runway Gen-3, which made AI-generated shots usable in actual productions. Designers who rolled their eyes at it were a year away from v0 and Claude Design, which made interface prototyping conversational.

Every creative professional who understood vibe coding as a pattern — not as a coding tool — had a head start. They recognized the shape of what was coming for their own discipline. They started building their Quivers earlier. They started adapting their workflows. They arrived at their discipline's vibe moment already fluent in the posture it required.

That head start compounds. The Quiver you've been building for two years produces better direction than the Quiver you started building six months ago. The habits of taste-first direction, developed early, produce more refined work than the same habits developed under pressure when the tools arrive.

Not a Competition. A Lineage.

Nothing in this comparison diminishes what vibe coding is or what it's enabling. The wave of solo founders and small teams building products at speeds and scales that were previously impossible is one of the most significant developments in software in a decade. Vibe coding is real, it's substantive, and the people doing it well are building important things.

The Vibe Creator framework isn't arguing that vibe coding was misnamed or that a bigger term should replace it. It's arguing that vibe coding belongs to a larger family. That the same shift — from technical execution to creative direction, from syntax to taste, from "how" to "what" — is happening everywhere, not just in software. And that having a name for the whole family matters.

When Karpathy wrote that tweet in February 2025, he was naming something real about his discipline. Two days later, we extended that name to everything. Not as a land grab — as a map. The map helps practitioners in every discipline recognize the same pattern when it arrives in their work, arm themselves with the same core skills, and not have to invent the vocabulary from scratch.

Vibe coder. Vibe filmmaker. Vibe composer. Vibe advertiser. Same orientation. Different instruments. One framework.

— IMAJIM