When a build goes wrong

Say what you see

Describe the symptom rather than diagnosing it. “The page is blank after I submit the form” gives Sneh something to reproduce. “I think the API route is broken” sends it hunting for a cause you guessed at.

When a change made it worse

Say so plainly — “the last change broke the header, put it back how it was”. Sneh can read the project as it stands and undo the specific thing, which is usually better than you trying to describe the previous version from memory.

When it keeps missing the point

• Narrow the request to one concrete change instead of several.
• Name the screen and the element you mean.
• Say what the correct result should look like, not just that the current one is wrong.
• If the misunderstanding is fundamental, revisit the brief — the plan may be describing a different product than the one in your head.

If a turn has clearly gone off the rails, a higher-capability model on the next attempt is often cheaper than three more turns of the same thing.

Read next

• How Sneh checks its own workBefore calling a build done, Sneh opens the app, walks through it on desktop and mobile, and reports honestly.
• Building your first appFrom a single sentence to a checked, deployed app — what happens at each step and what Sneh needs from you.

Did this miss what you needed? Email hello@sneh.ai — or browse the rest of the help centre.