Create your first project from one clear brief

Prepare one sentence that explains what to make, who it is for and what outcome matters. Brand sources and reference images can be added later; you do not need to wait for a complete specification.

1. Sign in, open the workspace and choose Conversational development.
2. Enter a brief at the top of the project library. If you need a starting point, use the refreshable random project example shown in the input.
3. Use the add menu to connect an existing knowledge space or attach supported text, code and image files. Nemeow understands the images first and then uses them for the build.
4. When the brief explicitly needs real dish, product, person or scene imagery and no usable image was uploaded, Build uses Pro image generation instead of imitating an image with a solid block. One Build generates at most three 1024×1024 images.

Nemeow shows your submitted request first, then interprets it using the current project and previously confirmed requirements, including goals, pages, features, data and explicit non-goals. It interrupts only for critical questions that materially change the goal, project, data, permissions, workflow, integration or reference direction, and every question uses directly clickable choices. Reversible, low-risk gaps such as warning thresholds or display styles receive minimal first-version defaults marked as inferred, so you do not have to answer them one by one. The first version always shows its proposal and waits for confirmation: understood does not mean executed. If interpretation fails, your input remains available to edit and submit again.

Once a first version exists, a change follows the mode you selected in the composer: Build starts immediately, Plan returns a proposal first, and Chat answers with advice you can act on. The proposal card reappears only when the change creates or alters business data such as tables or fields.

1. Review the plain-language summary of pages, features and the business information that will be saved. The interface does not expose technical Schema diffs or internal identifiers.
2. Whether or not business data is needed, choose Confirm and build once. When data is needed, the server prepares and atomically applies the data plan in the same flow, then starts page generation only after that succeeds.
3. If data setup fails, page generation has not started. Choose Retry and build to try again.
4. If a controlled App preview requests access, review its resources and actions, then separately choose Approve and open preview. Build does not approve access or publish for you.

The editor shows a preview; on a phone, use Preview at the top to open the movable preview panel.

• Use device controls to review desktop, tablet and phone layouts.
• Use the page menu to move between the home page and subpages.
• Confirm structure before polishing details; use authorized test records when previewing real data.

Ask for the next concrete change, such as “use a warm orange primary color,” “move registration into the hero,” or “add an FAQ page.” Projects save to the current account and keep version history.