Orvain UI is the design system I kept wishing I had. This is who builds it, and why it exists.

Oussema Ajmi
I've designed and built products for more than ten years. Orvain is one description of every component, shared by the Figma library, the React and Vue code and an MCP server, so designers, engineers and AI assistants work from the same thing.
Every message is read, and answered, by me.
Built with
What exists today
What I care about
I've spent more than ten years designing and building products, and one problem followed me through almost all of them: the design file said one thing and the code said another.
Designers work in the Figma library, engineers in React or Vue, and AI assistants read the same components through MCP, so a handoff is a lookup rather than a translation.
Not because anyone was careless, but because they were two separate descriptions of the same component, kept in step by memory, and memory loses. AI coding assistants have widened that gap. Ask one for a date picker and it produces something that looks right and invents the props, because it is guessing your library from thousands of others it has read.
A better prompt doesn't fix that. Giving the assistant the real component to read does. Orvain is my answer to both: the Figma library, the React and Vue code and the MCP server are all built from one description. The Figma library, the code library and the MCP server are all available today.

Oussema Ajmi · Founder, Orvain UI
600+
Figma components
Every primitive, pattern and page template, drawn and named.
11,000+
Variants
States, sizes and themes, mapped across the whole set.
130+
Design tokens
Colour, type, spacing and elevation: the same names as the code.
238
Blocks
In 48 families, each one drawn live on this site.

Questions go straight to me.
Or follow along: Newsletter, RSS feed, X, LinkedIn, GitHub.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain UI is the design system I kept wishing I had. This is who builds it, and why it exists.

Oussema Ajmi
I've designed and built products for more than ten years. Orvain is one description of every component, shared by the Figma library, the React and Vue code and an MCP server, so designers, engineers and AI assistants work from the same thing.
Every message is read, and answered, by me.
Built with
What exists today
What I care about
I've spent more than ten years designing and building products, and one problem followed me through almost all of them: the design file said one thing and the code said another.
Designers work in the Figma library, engineers in React or Vue, and AI assistants read the same components through MCP, so a handoff is a lookup rather than a translation.
Not because anyone was careless, but because they were two separate descriptions of the same component, kept in step by memory, and memory loses. AI coding assistants have widened that gap. Ask one for a date picker and it produces something that looks right and invents the props, because it is guessing your library from thousands of others it has read.
A better prompt doesn't fix that. Giving the assistant the real component to read does. Orvain is my answer to both: the Figma library, the React and Vue code and the MCP server are all built from one description. The Figma library, the code library and the MCP server are all available today.

Oussema Ajmi · Founder, Orvain UI
600+
Figma components
Every primitive, pattern and page template, drawn and named.
11,000+
Variants
States, sizes and themes, mapped across the whole set.
130+
Design tokens
Colour, type, spacing and elevation: the same names as the code.
238
Blocks
In 48 families, each one drawn live on this site.

Questions go straight to me.
Or follow along: Newsletter, RSS feed, X, LinkedIn, GitHub.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.