Help CenterUse this guide when you want Aivah Code to turn an idea into a working website or web application. A useful first brief names the user, the job, the important screens, and the result.
Before you begin
Prepare:
- A one-sentence description of the product and its audience.
- The main workflow a user must be able to complete.
- Any required pages, data, forms, or integrations.
- Screenshots, a PDF, or a Figma reference when the visual direction matters.
- A list of details that must not appear in a public preview.
Steps
1. Open Aivah Code
Choose aivah code in the workspace navigation. The start screen provides the product brief area, optional attachments, a model selector, Sandboxes, and My Projects.
2. Describe one complete product
State what to build, who it serves, the primary action, and the most important interface requirements. Include required mobile behavior and accessibility needs.
For example: “Build a mobile-first customer portal where clients can sign in, review onboarding progress, upload requested documents, and contact their support employee.”
Avoid combining unrelated products in the same first brief.
3. Add useful references
Use the add control to attach the supported references shown in your workspace. Add a Figma reference when you need Aivah Code to follow an existing interface direction. Remove confidential or unnecessary information before attaching a file.
4. Choose the model
Open the model selector and choose an available model for the task. Availability can change by account. The model helps with the build, but the project brief, files, and your review remain the source of direction.
5. Start the build
Submit the brief. Review any questions or proposed plan before approving the build. Clarify missing requirements instead of accepting assumptions that would change the product.
6. Return to existing work
Use My Projects to reopen a project. Use Sandboxes to review active build environments. Confirm the project name before continuing so changes do not land in the wrong workspace.
Expected result
Aivah Code creates a project workspace with your brief and begins preparing a live preview. You can continue the conversation, review the product, inspect code, and connect supported services from the same project.
Status meanings
Planning or building means Aivah Code is still preparing work. A ready preview can be reviewed but is not necessarily published. Published means a public delivery is available at its assigned address.
Usage credit impact
Building and revising with an AI model can use credits. Check the usage information shown in the project and your account before beginning a large build.
Information stored or shared
The project can store your brief, messages, attached references, generated files, code, and preview details. Do not include secrets, passwords, private customer data, or production credentials in the brief.
Limits and permanent actions
Available models, attachment types, sandboxes, and project controls can vary. Deleting a project or generated file can be permanent. Confirm the project name and keep an approved copy of important work before removal.
Common problems and recovery
- The result is too generic: add the audience, primary workflow, required pages, and visual references.
- The build solves the wrong problem: stop adding visual polish and correct the product brief first.
- An attachment is ignored: confirm it finished uploading and explain what Aivah Code should learn from it.
- You opened the wrong project: return to My Projects and confirm the project name before editing.