04 — UX Library · Internal

One kit. Every wireframe, the same hand.

Initiator & Owner
Internal
Design System
Figma
The Challenge

One studio, a team of UX designers, and every wireframe looked like it came from a different one. Each designer rebuilt inputs, dropdowns and tables from scratch, in their own grey, at their own level of finish, with states missing and directions mixed. Clients noticed. Onboarding meant weeks of “how do we draw this here”. The studio needed one wireframe language: neutral enough for any client, complete enough to ship a wireframe without inventing anything.

0 Shared components Every wireframe started from a blank canvas
2 Languages in most files Hebrew and English, often in the same wireframe
1 Standard to agree on Neutral for any client, complete for any wireframe
Goals

For the team

  • Start wireframing in minutes, not hours
  • The same quality from a first-week designer and a ten-year one
  • Less time on components, more on the problem

For the studio

  • One recognizable UXpert level, whatever the client
  • Faster onboarding, fewer reviews about pixels
  • A living asset that compounds with every project
Process · 01 — Discover

What every project kept rebuilding

I went through the studio’s recent projects the way I would audit a product: what repeats, what contradicts, what gets skipped. Every project had built its own components again, from zero: the same dozen each time, each drawn slightly differently, and with the same things missing every time.

Process · 02 — Define
"The kit carries the standard, so the designer can carry the thinking."

The goal wasn’t to remove design decisions. It was to remove the ones teams shouldn’t have to make repeatedly. Common behaviors, states and constraints moved into the system — leaving designers more time for the problems unique to each product.

Process · 03 — Deliver

What success looks like

Success was defined by what stops happening.

Speed Wireframing starts in minutes, not hours
Quality Every state and both directions, built in
Consistency Every wireframe leaves the studio at the same level
The Design

Six decisions that turned a component file into a studio standard.

01

Every state, every time

Error, disabled, focus and filled were the first things dropped when a designer was in a hurry, and the first things a developer asked about. Now they are built into each component as variants. You can’t place an input without its states coming along.

The Button component set in Figma — 90 variants generated by six properties: size, icon only, hierarchy, state, icons, text
02

Bilingual at the component level

Half the studio’s work is Hebrew, half is English, and most files are both. Every component exists as an RTL and an LTR pair, with Hebrew and English type set side by side, so a mixed-direction wireframe is a switch, not a rebuild.

The Input component set in Figma — 56 variants, with Language (Hebrew / English) as a property next to style, type and state
03

Tables as a system, not a drawing

Tables are where wireframes go to die. Header cells, cells, tooltips, avatars, progress bars and pagination were built as parts, and then assembled into ready table examples. A designer picks a table, not forty rectangles.

The Table section in Figma — progress bar, header text and cells, pagination, card header, and assembled table examples
04

Grids, type and icons come with it

Six layout grids from 1920 to 360 plus container grids, one type scale in both scripts, and a full icon set, all in the same file. Nothing to import, nothing to hunt for, nothing to be inconsistent about.

The icon set page in Figma, zoomed out — dozens of categories, each a labeled sheet
05

Variables, not values

Nothing in the kit is a hard-coded value. Four variable collections, 214 tokens: grid, typography, primitives, and a semantic layer that points at them, so a component asks for text-accent, not Blue/500. Change a token once and every wireframe in the studio moves with it. That is how the library stays one version instead of forty copies.

Figma variables — four collections (grid, typography, primitives, semantic) and a semantic layer aliasing the primitives
06

Neutral by design

A wireframe has to read like a product without being mistaken for one. So the palette is grey and one blue, the type is a workhorse, and nothing is styled enough to be argued about. Clients discuss flows and content. The visual design comes later, from whoever owns it.

A real wireframe built from the kit — ten mobile onboarding screens in grey and one blue, reading like a product without pretending to be one
Impact
Adopted By the whole studio Every UX designer starts from the kit. A new hire wireframes at the team’s level in their first week.
Faster Hours back on every project Components, states and both directions arrive ready. The time goes to the product’s own questions.
Alive A year in, still moving Updated with every real project need. v2.0 today, and the standard travels with the work.

What changed is what stopped being discussed. Reviews moved from pixels to flows, clients see one UXpert level whichever designer they get, and the library became the place where the studio’s way of working actually lives.

My Role

Initiated, designed and built the library in Figma, rolled it out across the studio, and keep maintaining it: every new project need becomes a component, and every component becomes the standard.

Next project

Champion Motors · Automotive