Make the brief clear and shape the product through conversation

A strong brief does not need technical language, but it should cover:

• Business: what product or service you offer.
• Audience: whose problem you are solving.
• Scope: which pages and actions belong in the first version.
• Style: the intended tone and any direction to avoid.
• Outcome: whether visitors should sign in, enquire, purchase or register interest.

The editor supports different stages of work. Build creates or changes pages but first clarifies missing high-cost decisions when necessary. Plan produces a reviewable implementation plan; confirming a Plan proposal does not change pages or create tables, fields or records. Chat discusses direction, explains results or shapes the next executable request without changing the project.

If a Build proposal includes new business tables, data is prepared only after the user confirms Start building. Discovery answers, proposal review and Plan confirmation remain read-only. Questions about an unconnected third-party service stay conversational, and Nemeow does not present an unsupported or unauthorized integration as complete.

The preview displays the current page and switches between desktop, tablet and phone widths. Multi-page projects include a page list, and navigation is generated together with the pages.

Each completed generation creates a project version. Open version history to review an earlier result and restore it as a new current version; existing history is not overwritten.

If a task is interrupted, keep the current project and use Resume when the editor exposes a safe recovery point. Resume continues the original task without requiring the same request to be sent again.