Working with Nuxie

Use the Task conversation and Editor together to create and refine Experiences

Nuxie can create screens, connect their Flow, add behavior, bind Products and data, and revise existing work. You work with it through the Task while the resulting Project stays visible in the Editor.

Start with the outcome

Strong requests name the user, the moment, the desired outcome, and the constraints that matter. For example:

Build a three-step onboarding for first-time users of our running app. Ask about their weekly goal, adapt the final recommendation to the answer, allow Skip, and treat reaching the personalized plan as success.

This is more useful than prescribing every component because it gives Nuxie the information needed to make coherent design and Flow decisions.

Supply real context

Tell Nuxie about anything it cannot safely infer:

The app and environment this work belongs to.
The audience and entry moment.
Existing Products or Features that must be used.
Brand or accessibility constraints.
What counts as success.
Paths that must never be changed.

Attach visual references or assets when they materially define the result. Nuxie keeps Task assets with the work so they can be reused during iteration.

Iterate at two levels

Use the Task for broad or semantic changes:

“Make the annual option the clear recommendation without hiding monthly.”
“Add a path for users who do not want notifications.”
“Use our existing premium_annual Product.”

Use direct editing for precise changes you can verify immediately, such as text, spacing, component properties, a route target, or the placement of a Goal action.

Review what changed

Do not treat a successful agent turn as publish approval. Check the artifact:

Design quality and app fit in Design.
Starting point, branches, actions, trigger, and Goal in Flow.
Complete user paths in Preview.
Responses and schemas in Data, when applicable.
Target app, audience, delivery, and Experiment changes in Publish.

Recovery

If a generation fails, the affected screen is marked as failed and Publish blocks while it remains blank. Ask Nuxie to retry the failed screen or delete it before publishing.

If the Task result is incomplete, describe the observed gap rather than starting over. The Project preserves the work that already exists.