Good work needs the right place and the right question. I make the place, and I ask.

About

Product and UX design by origin, now shipping design systems, interface code, and the agentic workflows that carry one into the other.

Now: UX/UI Designer, Ivím, since June 2025

Roles: Product designer, design engineer, UX/UI designer, interaction designer

Based: Orange County, California

Contact:

Email (jmarvrafael@gmail.com)

LinkedIn (https://www.linkedin.com/in/john-rafael-6a0656248)

A little context

I came from product and UX design and moved toward the build. The work I take now is the part where the design decision and its implementation are the same decision: design systems and their tokens, the pipeline from Figma into code, and the agentic workflows that run that pipeline.

Three things ship from me: agentic workflows, design systems built to be read by models as well as people, and prototypes real enough to be tested instead of described.

I am a UX/UI Designer at Ivím, working as a design engineer: I design it and build it.

How I work

Where I can, I show the working thing rather than a picture of it. A rendering of an interface can promise things the build cannot keep, so I would rather hand you the build.

A portfolio of screenshots asks you to believe the hard part went well. An operable artifact shows you.

Where this is thin

My design judgment is further along than my code. I write interface code and I am still getting stronger at it. What closes the gap is verification: I do not trust output, mine or generated, until it has been run. In the case studies that means labeling 22 screens by eye before trusting my own checks, which then failed against them, and holding a deletion until 66 frames matched before and after.

A little history

2025 to now. UX/UI Designer, Ivím.