Example Markdown Studio
A browser-based editor post that shows how a tool can be played, shared, and remixed.
Vibecodr
The social runtime where code can be opened, remixed, and shared.
A static preview of the loop: play the work, remix the idea, publish the next branch.
Example Feed
Illustrative cards, not live activity
Use the links to explore live public surfaces
APP
Run
CGPA Calculator
A small calculator-style app someone can open and use in the browser.
APP
Run
Versioned Notes
A self-versioning note and doodle pad shaped as a public web app.
APP
Run
Bridge Builder
Some of my favorite games as a kid were bridge simulators.
APP
Run
React-Cobbler
Just a little recipe for Cobbler on the web.
APP
Run
Generative Awareness Sketch
A quick runnable micro-app for an idea that wants motion, input, and a public URL.
APP
Run
Aquarifarm
Fun little web based Aquarium simulator.
Vibecodr is a community for runnable code
Where creative coding becomes a social space.
Vibecodr is a social platform for runnable web apps: not screenshots, not repo links, not "here's my" code. Real vibes you can play instantly, remix into your own version, and discuss with people who actually ship.
Play the thing. Trace the remix lineage. Publish your own version when the idea starts pulling at you.
How it works
Play it. Remix it. Publish the next branch.
The homepage should explain the loop quickly, then get out of the way.
01
Play instantly
Open the post and run the web app immediately. No clone, no install, no setup tax before the first impression.
02
Remix with attribution
Branch the idea into your own vibe while keeping the lineage visible. Remix culture is a product feature here, not an afterthought.
03
Publish as a real post
Turn the project into a public player page that people can revisit, discuss, and share as a living thing.
When backend work shows up
Pulses when backend work shows up
Keep the homepage focused on runnable posts first. When a vibe needs secrets, schedules, webhooks, or external APIs, that is where Pulses come in. Learn Pulses
Public paths
Follow the crawlable parts of the place.
Vibecodr's public surface is not only a JavaScript app. There are readable paths for runnable web apps, creative coding, docs, the journal, public conversations, and player pages so search engines and no-JS readers can understand what is here.
Agent references
Machine readers can start here.
Vibecodr exposes the public documentation corpus as plain markdown for parsers. Start with the concise discovery file, use the full reference for broad context, then fetch specific docs routes as markdown when you need route-level detail.
Why Vibecodr exists
Sharing working code got harder than writing it. To show off a tiny animation, toy tool, or half-finished experiment, you can end up trapped in build pipelines, hosting steps, and production ceremony before anyone touches the thing.
Vibecodr makes the shareable unit small again. A vibe is fast to publish, fast to play, and easy to remix. The social layer stays attached to the actual runnable work instead of orbiting around screenshots, repo links, and disconnected commentary.
If you miss the old build-in-public web, this is for that moment: post the runnable thing, let people feel it, and let the next branch start from there.
FAQ
Is Vibecodr a no-code builder?
No. You write real code. Vibecodr is about making that code runnable, shareable, and remixable - with community feedback built in.
Do I need JavaScript enabled?
For playing and editing vibes: yes. But this page is intentionally readable without JavaScript, and you can still browse links and understand the product.
What is a Pulse?
A Pulse is serverless edge logic deployed from src/server/ (or server/). Each file maps to /api/* so your vibe stays interactive while the trusted backend work stays separate.