Vibe
The runnable app people open in the browser.
A vibe is the interactive part of the project: the page, toy, demo, tool, game, or experiment people can run and remix.
Lingo
What words like Vibe, Pulse, Combo, and BUMP IT 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 Pulse handles backend work, a Combo uses both, and BUMP IT is how you update a project without starting over.
Start here
If this is your first time on Vibecodr, these are the quickest ways to understand what this page is trying to help you do.
Pulse
The backend side when your project needs one.
Pulses handle things like secrets, scheduled jobs, outside APIs, and other work that should not live in public browser code.
Combo
A project that uses both a Vibe and a Pulse.
Some projects are just a vibe. Some need both the interactive front end and a backend helper. When both are present, that is a Combo.
BUMP IT
The way you ship an update without abandoning the same project.
BUMP IT lets you publish a new version while keeping the public link, identity, and history tied to the same work.
How it works in practice
This is the more concrete side of the story: what changes as your project grows, what stays the same, and where Vibecodr draws the line.
Capsule
The source workspace that holds your project files.
Think of a capsule as the editable home for the code and assets behind a project.
Artifact
A published build frozen at a specific moment.
An artifact is the published cut Vibecodr can point to later, which is how version history, pinned embeds, and rollbacks stay understandable instead of turning mushy.
Player
The focused page for opening a published project.
The player gives a vibe more room to run while still keeping the social context nearby.
Route intent
Whether a route is public, private, or meant for search.
You do not need this term every day, but it helps explain why some pages are built for discovery while others are just utility surfaces inside the app.
Keep exploring
If you want to go deeper, these nearby pages explain the next part of the picture without assuming you already know the vocabulary.
FAQ
Why does Vibecodr use domain-specific terms instead of generic ones?
Because the same few patterns come up over and over. Short, consistent names make it easier to understand what you are building and where a new feature belongs.
Is a vibe the same as a post?
Not exactly. A post is the social container; a vibe is the runnable software unit attached to that social context.
Do terms like Pulse and Combo affect implementation choices?
Yes. They are not just branding words. They point to real differences between browser-side code and backend-side work.
Where should teams confirm term definitions when in doubt?
Start here, then use the docs and the linked pages if you want the deeper version with examples.