What this guide covers
Prompt-first building, Preview and iteration, Version and code access, Hosted platform controls.
DocumentationCoverage Format
CodeSplash Vibes docs
Use Vibes as the simplified entry point into AI app creation: prompt in plain English, iterate quickly, keep previews and generated output aligned, and avoid exposing technical complexity unless you need it.
Available now as a desktop app backed by a hosted platformNon-technical founders, creators, operators, and fast builders
How to use this page
Work from top to bottom the first time, then use the section links as a reference once the product becomes part of your normal workflow.
Start your first project
The best Vibes workflow begins with clarity in plain language, not technical setup.
Describe the app in normal English
State what the app should do, who it is for, and what the user should feel when using it. Avoid over-specifying implementation details unless they matter.
Use intent, not jargon
Instead of naming frameworks or low-level patterns, tell Vibes the outcome you want: landing page, dashboard, booking flow, content app, or internal tool.
Review the first draft quickly
Treat the initial result as a starting point. The speed advantage comes from iterating fast rather than trying to craft a perfect first prompt.
Iterate toward the right design and behavior
Vibes is most effective when you make focused requests that shape one layer of the experience at a time.
Adjust layout and visual direction
Refine structure, typography, spacing, and mood before you obsess over edge-case logic. The product is optimized for visible progress.
Refine flows one screen at a time
If something needs work, focus on that screen or flow instead of rewriting the whole app prompt. Smaller corrections usually land better.
Use previews as the source of truth
Stay anchored to what is actually rendered. Vibes works best when you evaluate changes in the live result rather than in abstract descriptions.
Keep iterations and generated code organized
Under the simple surface, the platform still exposes project state, versioning, and code access so useful work does not disappear into a black box.
Use project and version history
Treat versions as checkpoints while the app evolves so you can compare directions instead of losing a promising earlier state.
Inspect generated output when needed
The platform keeps generated code accessible so technical users can audit, refine, or extend what the prompt workflow produced.
Separate visual changes from structural changes
That makes rollbacks, comparisons, and team handoffs much easier once the project becomes more serious.
Use the hosted platform controls when the project grows
Vibes stays simple for end users, but the platform includes the admin and monetization layers needed for a real product.
Manage plans, billing, and access
Use the hosted system for account state, subscriptions, and commercial controls once the product moves past experimentation.
Choose models intentionally
Model selection matters when you want to balance speed, quality, or cost across different kinds of projects.
Track performance with analytics and admin views
The deeper platform surfaces let you operate Vibes as a serious product and not only as a prompt demo.