Prompting guide

Zzz understands plain language: no syntax to learn. But some habits reliably produce better apps. Here are the ones that matter.

Be specific, not long

A good prompt isn’t a novel, it’s precise. Compare:

❌ "Make a fitness app."

✅ "A workout tracker for runners: log distance and time, see a weekly chart, dark style like Spotify."

Same length, but the second one names the user, the core action, the key screen and the look.

One change at a time

After the first build, iterate in small steps. One message, one intention:

✅ "Add a settings screen with notification toggles."

then, once you’ve checked the result:

✅ "In settings, add a dark mode switch."

Bundling five changes into one message makes results harder to check, and harder to undo if one of the five isn’t right.

Give real content

Placeholder text produces placeholder design. Feed Zzz your actual words:

"The onboarding titles are: 'Track every run', 'See your progress', 'Beat your best'."

Real names, real numbers, real sentences: the design instantly looks like a real product.

Use design words

A few well-chosen words steer the whole look: "minimal", "pastel", "glass effect", "editorial", "like Duolingo". See Design styles for the vocabulary Zzz responds to.

Describe bugs like a tester

When something is wrong, say what you did, what happened and what you expected:

✅ "On the workout screen I tap Save and nothing happens. It should add the workout and go back home."

That single sentence usually gets a one-shot fix.

Good to know

• You can paste screenshots of apps you like: "make the home feel like this" works great.
• If a result surprises you, ask Zzz why: "why did you put the button there?" often reveals a good reason, or gets it fixed.