Photo of Çağatayhan KurtChatto
UTC +3

Ventures

Toolkit

Connect

© 2026 | Made with curiosity & caffeine.

EN
All work

Create UI · Case study · 4 min read

Create UI: a hand-crafted Figma design system and an AI-native React library, in sync

Create UI is my own product: a complete Figma design system and an installable React library that share the same tokens, names and variants. I designed the brand and every component by hand; the code was built AI-native with expert developers, so AI coding agents build with the real components instead of guessing.

Client
Create UI
Year
2025
Role
Founder & design lead
Duration
Ongoing
Industry
Design systems, Developer tools, AI
Tools
Figma, React, Tailwind CSS, Radix UI
  • Brand & Logo Design
  • Design System
  • Product Design
  • User Interface Design
  • Digital Designs

At a glance

Challenge

Figma files and code drift apart, and AI agents guess at components they can't see.

Solution

A hand-crafted Figma system and an AI-native React + Tailwind + Radix library on one token foundation, with a CLI and an MCP server.

Outcome

Four releases in four months, from a 40-component pre-sale to 18,500+ variants, blocks and AI components.

Deliverables

  • Logo & brand identity
  • Figma design system
  • React component library
  • Responsive tokens & themes
  • Blocks & AI components
  • CLI, MCP & agent skill
The website today: products, changelog, roadmap and docs in one place.

Overview

Create UI is a design system in two parts: a Figma file and an installable React library built on Tailwind CSS and Radix UI. They share the same tokens, names and structure, and AI coding agents can read the library through an MCP server and an agent skill. [1]

File Upload, one of our two most popular components: progress, completion, then change or download.
Segmented Control, the other favourite, followed by button groups, spinners and more, in light and dark.

It is my own product, not a client project. I designed the logo, the brand and every component, variant and token by hand in Figma. The code side was built AI-native: expert developers wrote the React library together with AI, so that coding agents can read it and use it correctly.

The challenge

Most teams have a design system twice: once in Figma and once in code, maintained by different people and slowly drifting apart. Now there is a third reader, the AI agent writing the UI, and it can't see either of them.

  • Drift: a button in Figma and a button in code rarely have the same sizes, states and names.
  • Guessing agents: without context, AI tools invent components instead of using the ones you have.
  • Scale: a useful system needs every state, size, theme and screen size, which quickly runs into thousands of variants.
  • Speed: as a product, it had to ship early and keep improving in public.

Goals

  • One token foundation for Figma, code and agents.
  • The same component names, props and variants on both sides.
  • Responsive radius, spacing and typography, light and dark themes, built in rather than bolted on.
  • Install in one command and let AI agents build with the real components.
  • Ship small, release often, and grow from components to blocks and AI patterns.

Approach

1. Tokens first

Colour, type, spacing, radius and shadow were defined as variables before any component existed. Components only reference tokens, so a theme change reaches every screen in Figma and every component in code. [1]

Primitive colours with contrast ratios: every component colour comes from these scales.
Anatomy of one component: every value points to a token or another component.
The foundation layers: tokens, colour variables, component logic, spacing scale and themes.

2. One name for one thing

A component has the same name, variants and states in Figma and in React. Designers and developers talk about the same Button, and an agent reading the docs finds what the designer drew.

One Button in Figma, switched between variants, colours and states in light and dark.
Each component page lists its variants, sizes, states and accessibility notes.

3. Hand-crafted design, AI-native code

The interface is drawn by hand, component by component; no screen in Create UI was generated. The code side was built by expert developers working together with AI, and every component is described for machines too: an MCP server and a skill file tell coding agents what exists and how to use it, so they compose with the system instead of guessing. [1]

Asked for 20 buttons, the agent reuses the hand-made Button, so every result is a valid variant.

4. Ship in public

Instead of waiting for a perfect 1.0, Create UI opened as a pre-sale with 40+ components and grew release by release, with a public changelog and roadmap. [2]

Open questions were shared as A/B options before a component was locked.
Where it started: the scope announced for the June 2026 pre-sale.

The solution

Logo and brand

I designed the Create UI logo, a selection frame with a cursor, the way a designer marks something on a canvas, and the brand around it: deep indigo gradients, a fine grid and the product's own components as illustration. The same pieces carry the website, social profiles and launch posts.

The logo: a selection frame and a cursor, the first thing you do in a design tool.
Cover design: the product's own components are the illustration.
The X banner, built from the same components and tagline.

Figma design system

Auto-layout components with variables, every state and size as a variant, light and dark modes, a type scale and usage notes. The file now holds more than 18,500 components and variants and 950+ variables and styles, and every component ships with guidelines and an interactive example. [1]

Every colour, size and state is a real variant, not a note in a spec.
Guidelines and a live prototype side by side, inside the Figma file.

Components

Buttons, form controls, badges, chips, toasts and file upload share one visual language: the same radius, focus ring and colour logic. Each one is designed by hand with its real states, from loading and error to disabled.

Core controls with the same radius, focus ring and colour logic.
Feedback and form components, designed with their real-world states.
Toast / Snackbar: payment failed, changes saved, sync in progress, update available.

Navigation and data

Product screens need more than controls. Tables with selection, filters and bulk actions, sidebars and headers were built from the same parts, so a dashboard assembled from Create UI looks designed, not stitched together.

The Table: selection, filters and bulk actions are part of the component, not extras.
Sidebar and header patterns that hold real product content.

Responsive tokens and themes

Radius, spacing and typography are responsive: each has its own values for desktop, tablet and mobile on a 4 px grid, so the same component is tuned for every screen without a separate mobile version. Twenty-plus prebuilt themes and dark mode sit on the same tokens. [1]

One component, two themes: dark mode comes from the tokens, not from a second drawing.
Button groups in dark mode: view switchers, billing periods, split buttons and inbox actions.

Blocks

Version 1.5 added ready-made sections: 73 code blocks in seven categories and 58 Figma blocks, built only from the system's own components. [2]

A performance card block, built only from system components.
A map and places block: blocks are ready-made sections, not new components.

React library, CLI and MCP

The code library is built on React, Tailwind CSS v4 and Radix UI and was written AI-native from the start by expert developers working together with AI. A CLI creates a new app or adds components to an existing one, writing the design tokens into the project's stylesheet. [3]

The same CLI installs an MCP server and an agent skill, so coding agents such as Claude build with the real components. AI components like chat, prompt input, markdown and chain of thought cover the screens AI products need most. [1] [2]

The Tree View component, demoed with a code-style project tree.

Results

  • Four releases between June and September 2026: v0.5, v1.0, v1.1 and v1.5. [2]
  • From 40+ components and 700+ tokens at pre-sale to 49 free and 35 Pro code components, 73 Pro blocks and 18,500+ variant combinations. [2]
  • A free React library anyone can install, and a paid Pro tier for design, code or both. [1]
  • Rated 5.0 on Product Hunt. [4]
What designers and developers posted about Create UI on X.

Key takeaways

  • Sync is a naming problem before it is a tooling problem.
  • Hand-crafted design and AI-native code work together: people design the system, agents use it.
  • Shipping early and in public beats polishing in private.

FAQ

What is Create UI?

Create UI is a design system sold as two parts that stay in sync: a Figma design system and an installable React library built on Tailwind CSS and Radix UI. Both share the same tokens, component names and variants, and AI coding agents can read the library through an MCP server and an agent skill.

What did you design for Create UI?

Everything people see, by hand: the logo and brand, the token foundation, every Figma component and variant, light and dark themes, responsive radius, spacing and typography, blocks, documentation and marketing visuals. The React library was built AI-native together with expert developers and mirrors those decisions one to one.

How long did it take?

Create UI is a living product that I started in 2025. The design system pre-sale (v0.5) opened on 1 June 2026, v1.0 shipped on 6 July, v1.1 on 15 July and v1.5 with blocks and AI components on 28 September 2026.

How do you keep a Figma design system and code in sync?

Start from one set of tokens and use it in both places, give components and variants the same names in Figma and code, and ship changes to both in the same release. Create UI adds a third consumer, AI agents, so the components are also described in an MCP server and a skill file.

Can you build a design system for my company?

Yes. I design systems and products for AI, SaaS, fintech and Web3 teams through my studio, Beew, and you can start from Create UI or from scratch. Book a call from the contact page.

Sources

  1. [1] Create UI — official website
  2. [2] Create UI changelog
  3. [3] Create UI installation docs
  4. [4] Create UI on Product Hunt

Have a product to design?

I help teams turn complex products into websites and interfaces people understand in seconds. Tell me about yours.

Next case study

Omuz

Explore case study
Omuz