I'm Ramona. I build interfaces the way designers wish engineers would: motion, states, accessibility and all.
A travel-operations dashboard that shows status, budgets, and departures at a glance. A custom AI skill scaffolded the token-driven component library, with Storybook docs and light/dark theming, and then generated the dashboard from those same components.
A trivia game where the score is the artwork. Every answer lights a star in a constellation that draws itself. Each round has ten AI-generated questions set in a living night sky built with Next.js and Tailwind on a full design-token system.
A conceptual green-tea brand site that teaches instead of selling. It includes evidence-led copy, color that behaves like ink, and a steep timer you can actually brew with. It was built with JavaScript, CSS, a small Node backend for email sign-up, and AI to help refine the interactive details.
Loading, empty, and error get the same code review as the happy path, each one designed and built before QA ever sees a build.
Every color, radius, and easing curve lives in a variable. The design survives refactors because it was never hardcoded in the first place.
Motion curves picked per component in code, never the library default. Hover the stage to feel one.
Agents scaffold components, explore variants, and surface the states I'd forget. Every line still gets read before it merges.
I came up through front-end engineering, turning Figma files into production code and finding everything the mockups didn't say: loading states, awkward breakpoints, focus rings. At some point I stopped asking designers to fill the gaps and just designed those parts in the browser myself. Now I ship working components instead of tickets.