Vibe
The runnable app people open and play with in the browser.
A vibe is the interactive part of a project: the page, toy, demo, tool, game, or experiment anyone can press play on and remix. Example: "Just shipped a new vibe."
Lingo
What words like Vibe, Remix, BUMP IT, and Studio actually mean.
Vibecodr has a few house words. They are not there to sound clever — they are just short names for the things you will actually see while building, publishing, and remixing.
If you only learn four of them, learn these: a Vibe is the thing people open, a Remix is how you make someone else’s vibe your own, BUMP IT updates a project without starting over, and the Studio is where it all takes shape.
Lingo
The Vibecodr glossary of vibe coding: what a vibecoder, a vibe, a pulse, a combo, and BUMP IT actually mean — plain definitions so anyone can start vibe coding fast.
Learn these four first
The words the rest of the product leans on. The vocabulary only earns its keep if it helps you build, publish, remix, or stay safe, and these four carry most of the weight.
Remix
Taking someone else's vibe and forking it to make it your own.
Remixing gives you your own copy to build on while the link back to the original stays visible. Evolution in the open instead of a quiet copy-paste. Example: "I remixed your game to add a boss level."
BUMP IT
How you ship the next cut without splitting it into a duplicate.
BUMP IT publishes a new version while keeping the same public link, identity, and history tied to the same work. It creates a fresh cut and preserves the old ones for rollback, so the URL and embeds never rot. Example: "I used BUMP IT to ship the new version without making a second app card."
Studio
The workspace where you code, preview, and shape a project before publishing.
The Studio is where a project takes shape: paste or upload code, watch it run, and tune it until it is ready to share. Example: "Head to the Studio to start building."
The rest, when you need it
Words you will pick up as you go: from the workspace you build in to the automations that run while you sleep. The supporting cast, defined plainly with a line of real usage.
Vibe coding
Building software by describing what you want and shaping what comes back.
Vibe coding is the loop Vibecodr is built for: paste, upload, or generate code — often with an AI — then run it, share it, and remix it until it is right, instead of hand-writing every line up front. Example: "I vibe coded a little budget tracker over coffee."
Vibecoder
Someone who builds and ships apps by vibe coding.
A vibecoder turns ideas into running, shareable apps — sometimes a seasoned engineer, sometimes someone who started talking to an AI last week. On Vibecodr, everyone who publishes a vibe is one. Example: "Half my feed is vibecoders shipping weird little tools."
Capsule
The editable workspace that holds your project files.
Think of a capsule as the home for the code and assets behind a project, before and between publishes — the editable source, not the frozen public copy. Example: "I saved this build in a new capsule."
Pulse
The backend helper you add when a project earns one.
A Pulse handles the work that should not live in public browser code: secrets, storage, scheduled jobs, and calls out to other services. You reach for it only when the project actually needs it. Pulses are in early access. Example: "I added a Pulse to handle the newsletter signup."
Combo
A project that uses both a Vibe and a Pulse together.
Some projects are just a vibe. Some need both the interactive front end people open and a backend helper doing trusted work. When both are present, that is a Combo. Combos build on Pulses, so they are early access too. Example: "This is a combo: UI up front, real backend logic behind it."
Flow
The state of deep immersion when you are building and creating.
The unbroken stretch where the work just moves and you stop fighting the tools. Vibecodr is tuned to get you there and keep you there. Example: "I'm in the flow right now — do not interrupt."
Params
User-adjustable inputs for a vibe.
Params are the knobs a vibe exposes. Change a few values, press play again, and watch the thing respond — no code edit required. Example: "Try tweaking the params to see what changes."
Automation
A rule that makes something happen on its own — when X happens, do Y.
Automations connect events, schedules, and webhooks to your Pulses, so the boring part runs itself instead of waiting on you. Example: "I set up an automation to ping me when errors spike."
Schedule
When you want something to run on its own clock.
A schedule runs work every hour, every day, or whenever you pick — no coding required, just choose the times and let it go. Example: "I scheduled my report to run every morning at 9am."
Webhook
A message from another service that tells your Pulse to do something.
When a service like Stripe or GitHub sends a webhook, your Pulse can react to it. It is how apps tell each other that something just happened. Example: "When Stripe sends a webhook, my automation sends a receipt."
Translate into practice
Use the glossary for quick footing, then jump into the docs when you want examples, file layout, or the exact runtime behavior behind a term.
FAQ
Short answers for the places where marketing copy should stop hand-waving and say the plain thing.
Do I need to memorize any of this to use Vibecodr?
No. If you only ever learn four words, learn Vibe, Remix, BUMP IT, and Studio. The rest you will pick up the first time you trip over them while building.
Why house words instead of generic ones?
Because the same few patterns come up over and over. Short, consistent names make it easier to hold the product in your head and to know where a new feature belongs.
Is a vibe the same as a post?
Not quite. A post is the social container; a vibe is the runnable software attached to it. You can post a thought with no vibe, and a vibe always lives inside a post.
Do words like Pulse and Combo change how I actually build?
Yes — they are not just branding. They mark the real line between browser-side code anyone can run and backend work that needs secrets, storage, or trust.
Where do I go when a definition here is not enough?
Start with the glossary — the A–Z of house words and standard dev terms — then jump into the docs when you want examples, file layout, or the exact runtime behavior behind a term.