How this works
This tool finds where users struggle on our platform and helps you turn that into finished designs for engineering โ no design software or technical skills needed.
Just type what you want, like you'd explain it to a designer:
"Design a version of the appointment card where rescheduling is one tap."
"Show me the current doula dashboard and design a simpler version."
"Make the booking flow feel less overwhelming on a phone."
The design appears in the preview on the right. Keep talking to change it โ every change is saved as a version (the v1 v2 pills), so you can always go back. The assistant knows our real screens and brand, can pull usage numbers from PostHog, and will look at the current design before changing it.
Every night the tool reviews session recordings from care.findraya.com and picks out the moments users actually got stuck (rage-clicks, dead ends). Each finding shows what happened, screenshot evidence, and a โถ link to watch the real session.
Approve โ it goes to engineering in Asana. Deny with a reason โ the analyzer learns and stops suggesting that pattern. Your denials genuinely make it smarter.
You can also ask the Studio chat things like "what did the scans find?", "show me the videos from yesterday", or "scan the doula dashboard sessions".
Accounts, access, or anything broken: Al (CTO). Technical documentation lives in Confluence โ Engineering โ "Raya Design Studio".