Fast publishing lane
VibeComposer Guide
Composer is the shortest path from idea to runnable publish. It favors speed and iteration while still preserving canonical app identity.
Single-file workflow optimized for fast publish and remix loops.
Implementation focus
Choose Composer when your work is single-file or quick-turn and you want public feedback before deeper architecture work.
Expected outcomes
- Publish single-file vibes quickly with low setup overhead.
- Keep remixability intact while iterating through BUMP IT cuts.
- Hand off to Studio only when complexity justifies it.
What Composer is for
VibeComposer is optimized for fast single-file publishing. It is the right tool when the idea is small enough to fit in one surface and the goal is to get feedback quickly without building a whole workspace structure.
Composer still participates in the same publication model as Studio. The published work gets a public post, a runnable artifact, metadata, and the ability to move forward through later releases.
- Use it for small games, experiments, widgets, visual sketches, and quick app ideas.
- Keep dependencies small and browser-safe.
- Move to Studio once the project needs multiple files, imported assets, or backend coordination.
Handoff to Studio
Composer is not a dead end. When a quick idea starts needing structure, treat the published vibe as the public seed and move deeper implementation work into Studio.
The important continuity rule is identity: if the same app should keep living at the same public route, use the update flow instead of scattering new posts for every iteration.
- Keep the original app identity when updates are part of the same project.
- Use Studio for source organization, import-built output, richer previews, and Pulse attachments.
- Preserve remixability by keeping browser-visible code free of credentials.
Example and read next
Example: you pasted a single-file p5 sketch, confirmed it runs in preview, and want feedback quickly. Use Composer first, then move to Studio only when assets, multiple files, or backend behavior become part of the project.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: Studio (/docs/studio)
- Read next: BUMP IT (/docs/bump-it)
- Read next: Source & Versions (/docs/source)
- Read next: How-To Guides (/docs/how-to)