Making changes with chat
How the follow-up chat loop works, what Raina remembers, and how to ask for changes that land correctly.
Once your app exists, the chat box becomes an ongoing conversation, not a one-time generator. Describe a change in plain language — "add a dark mode toggle," "add a late fee for overdue bookings" — and Raina edits only the files that change, instead of rebuilding everything from scratch.
Raina remembers the whole conversation
Your original prompt, the summary of what got built, and every change you've asked for since all stay in context — including if you close the tab and come back another day. You never have to re-explain what the app is or why a field exists.
The moment you send a message, you'll see a short acknowledgment of exactly what's about to happen before the real work starts, so you're never left wondering whether your request was understood.
Getting good results from a change request
Be as specific as you'd be with a teammate: "make the header blue" works, but "make the header a deep navy blue and increase its height slightly" removes guesswork. If a request is genuinely ambiguous, Raina makes the most reasonable product decision and explains the assumption in its reply — you can always correct it in the next message.