Getting started
Prompting for a useful first version
Give Layerwise enough product context to produce a testable first project.
The initial prompt defines the starting point. A useful prompt says who the app is for, what they need to do, what information the app stores, and any design constraints.
Include the essentials
- Users — Who will use the app and whether they need to sign in.
- Main workflow — The important steps a user completes.
- Data — Records the app needs to create, view, or update.
- Screens — Key pages or dashboards.
- Design direction — Brand, tone, layout, or examples to follow.
Start specific, then iterate
Ask for one clear outcome per follow-up message. After each result, inspect the local preview and test the affected user path before requesting the next change.
Attach reference images when your selected model supports image input. Use them to communicate layout, style, or content hierarchy; also describe the behavior the image cannot show.
To show which part of the current preview a follow-up is about, select an element or draw on the page from the preview toolbar. See Point to part of the page.
For a larger change, turn on Plan mode to agree on the approach before the agent edits anything, or set a Goal to let it work across many turns. See Direct the agent.
Example
Build an internal tool for a five-person support team. Agents need to view a
queue of customer requests, assign each request to a teammate, update its
status, and add internal notes. Add email sign-in. Use a compact desktop-first
layout with a left navigation panel and a table on the main screen.Verify the first result
Before moving on, confirm that the preview loads, the primary screen exists, and the main workflow can be exercised. If it does not, use a concrete follow-up such as “The assignment menu is missing from the request detail page; add it and keep the existing table.”