First build and preview
Last reviewed:
The best first experience is not a tour of buttons. It is a small, real outcome: send a clear request, follow the build, and verify the preview yourself.
Project workspace
The workspace combines your conversation with Codey and the project tools. Use the conversation for outcomes and decisions, and tools for files, preview, logs, and deployment.
Choose the message intent
Auto chooses the suitable path, Build requests project changes, and Discuss gives advice without changing files.
When to use a plan
Keep planning enabled for large or multi-page work. Review scope and steps before execution to reduce rebuilds and surprises.
Follow the Project Doc
After the first build request for a new project, the Project Doc takes shape automatically alongside the build. Open it to watch features, design, images, and technical details fill in. Projects created before the feature do not receive the written document retroactively. See every surface in the Project Doc guide.
Write a verifiable request
Name the user, pages or flow, core behavior, visual direction, and success or error outcomes. Avoid relying on a phrase such as “make it professional” by itself.
Verify the preview
After a successful build, open the preview and test the primary flow on desktop and mobile. A success badge is not a substitute for trying the actual result.
First build and preview
Start with a small scope you can test, then add improvements through separate, focused requests.