esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

UI Kit: The Ready-Made Visual Parts Designers Drag Into Screens

Learn what a UI kit holds, how it differs from a full design system, and how designers use and update one shared file.

In short

A UI kit is a shared file of ready-made visual parts, such as styles, components, states and variants, that designers drag into screens, unlike a full design system.

15 min readFree

What you will learn

A UI kit is one part of a design system. It is a shared set of ready-made visual parts, such as buttons, text boxes, icons and colors, that you place into your screens instead of drawing them from nothing. In this lesson you will learn what a UI kit holds, how its parts are organized, how it differs from a full design system, and how designers use and update one kit so that every screen stays consistent.

Key words

UI kit
A collection of ready-made interface parts and styles, kept in one design file, that designers reuse when they draw screens.
Design tool
A program where designers draw screens. Figma is a common example, and it is the tool this lesson uses.
Design system
The full set of shared parts, rules, written guidance and governance that a team uses to design products. A UI kit is one part of it.
Component
A piece of a screen that you make once and reuse, such as a button or a text input.
Main component
The original version of a component. You edit it to change the design everywhere it is used.
Instance
A copy of a main component that you place on a screen. It stays linked to the main component.
Variant
A different version of the same component, such as a small button or a disabled button, grouped together in one set.
State
The condition a component is in at a moment, such as default, hover, focus, pressed or disabled.
Style
A named setting you save once and reuse, such as a color, a text style or a shadow.

Keep these words in mind as you read. Each one returns later in the lesson, and the worked example uses all of them.

What is a UI kit?

Think of a UI kit as a toolbox for drawing screens. A designer opens the file, picks a part, and drags it onto the canvas. Many sources describe a UI kit this way: it is a library of ready-to-use visual pieces that helps designers build interfaces faster and more consistently. You can read a short overview in the Glow UI and Radian UI pages in the sources list.

In this course, a UI kit has three traits. It lives in a design tool such as Figma. It holds only the visual side of the product. And it is the design-side library of a larger design system. It is not the coded version of the parts, and it is not the full system.

  • It lives in a design file

    The kit is one shared file. Anyone on the team who opens it can see the same parts and use them.

  • It covers the visuals

    The kit shows how things look: colors, letters, spacing, buttons, fields and icons. It does not, by itself, explain when to use them.

  • It is built for designers

    Designers use it to draw screens and test ideas. Engineers may later build the same parts in code, but that is a separate job.

What does a UI kit contain?

A complete kit usually has three layers. Some teams add more, such as page templates, but these three are the core. Each layer answers a different question: what style should things use, what basic parts exist, and what reusable pieces are built from those parts?

  • Styles

    These are the named settings for color, type and spacing. A style is saved once and then applied to many parts.

  • Basic elements

    These are simple building blocks such as icons, and the raw materials that components are built from.

  • Reusable components

    These are finished pieces such as buttons, inputs, checkboxes, cards and navigation bars. Each one can have states and variants.

A common kit includes buttons, inputs, checkboxes, radio buttons, toggles, dropdowns, badges, tags, tooltips, modals, alerts, navigation pieces and cards. Many kits also include a set of icons. A good kit keeps the icons in the same file as the components, so they are easy to reach.

Tip

Look at any kit you have access to and sort its contents into the three layers. If you cannot tell which layer a part belongs to, the kit may be missing clear groupings.

Here is what each layer does in daily work. Styles keep colors and letters the same across every screen. Basic elements give you the raw parts. Components are where most of your time goes, because they are the pieces you drag onto a screen and then adjust.

Styles: color, type and spacing

Styles are the rules that make a kit look like one product. A color style is a named color, such as a brand blue for main buttons. A text style holds the font, size and weight for a heading or a label. A spacing setting holds the gaps used between parts. When you change a style, every part that uses it changes too.

In Figma, the styles in a kit are saved as named settings that components point to. This is the reason a kit can update many screens with one change.

Components, states and variants

A component is a part you make once and reuse. Most kit components have several states. A state is the condition a part is in at a given moment. A button can be default, hovered by a mouse, focused by a keyboard, pressed or disabled. A good kit shows every state, so a designer does not have to invent them.

Figma groups these versions with variants. A variant is one version of a component, and all the versions sit together in one set.

  • State

    Default, hover, focus, disabled. The button looks different in each one.

  • Size

    Small, medium and large versions of the same button, so the same part fits tight and roomy layouts.

  • Type

    Primary for the main action, secondary for a backup action, and ghost or destructive for special cases.

Tip

Give every variant a clear name in a consistent pattern, such as Category, then Component, then Variant. The ProductHub guide recommends this kind of naming, because it makes the component picker easier to search.

Organized in one shareable file

A kit is only useful if people can find things in it. Many teams put every part in one file and divide the file into pages. A common first layout has a page for notes on how to use the kit, a page for styles, a page for components and a page for example screens. Inside the components page, groups such as Forms, Navigation, Feedback and Overlays keep related parts close together.

  1. 1

    Start with a notes page

    Write one short page that says what the kit is for, who uses it and where the other pages are.

  2. 2

    Set up the styles

    Save the main colors, text styles and spacing values as named styles before you draw any component.

  3. 3

    Build components in groups

    Put each component in a group such as Forms or Navigation so the file is easy to scan.

  4. 4

    Name everything the same way

    Use one pattern for every name, so the same kind of part looks the same across the file.

  5. 5

    Share the file

    Publish the kit as a library so other designer files can reach the same parts.

Sharing matters. A kit kept in one file means a new designer does not have to search old screens or copy parts from a colleague's file.

How is a UI kit different from a design system?

Many people mix up the two terms. The simplest way to remember the difference is this: a UI kit gives you the visual parts, and a design system gives you the parts plus the rules, guidance and structure that keep them in use over time. Several sources in the list use the same comparison, and they agree on the core idea.

  • What the UI kit covers

    Visual parts, styles, states and variants, all kept in a design file. It is aimed mostly at designers.

  • What the design system adds

    Written guidelines, documentation that explains when to use each part, design principles, accessibility rules, and matching code. Its users include developers too.

  • How they fit together

    The kit is one part of the system. A kit can become limiting as a project grows.

Some sources note that a kit can be large and still be only a kit. Hundreds of components do not turn a kit into a system. What matters is whether the rules, guidance and governance around the parts exist. In this course, the kit is the visual toolbox, and the system is the whole workshop.

Quick check

A solo designer has two weeks to make a clickable prototype for a class project. She needs buttons, fields and icons that look consistent. Which tool fits her job best?

How do designers use a UI kit?

A kit saves time only when designers use it the right way. The main habit is simple: pick the part from the kit, and do not redraw it. When every screen draws its own version of a button, the buttons slowly drift apart. When every screen uses the same kit part, they stay alike.

  1. 1

    Open the kit file

    Go to the kit before you draw anything, and check whether a part already exists for the job.

  2. 2

    Place an instance

    Drag the component from the library onto your screen. The copy you place is an instance.

  3. 3

    Change only what the screen needs

    Edit the label or choose a variant, such as the primary button or a small size. Do not rebuild the part.

  4. 4

    Check every state

    Look at how the part behaves in hover, focus and disabled states, so the screen works for every user.

  5. 5

    Ask for a new part only when none fits

    If the kit lacks what you need, propose an addition to the kit instead of building a one-off copy.

This flow keeps screens consistent and fast to build. The team spends less time on repeated drawing and more time on the flow and content of the product.

Designers also need to know which pieces are linked to the kit.

Main components and instances

Figma uses two forms for every component. The main component defines the part. Each copy you place is an instance. Instances stay connected to the main component, so changes to the main reach them.

You can change an instance in limited ways. You can change its text, or swap a nested part for another, but you should not treat the instance as a new design. If you need a lot of change, Figma lets you detach the instance. A detached instance no longer receives updates from the main component, so it can drift away from the kit.

Tip

Make structure changes on the main component, and make screen-specific changes on the instance. If you edit many instances by hand, the kit is probably missing a variant.

How do you update the kit in one place?

The biggest benefit of a kit is that you update it once. Suppose the brand color changes. You change the color style or the main component in the kit. Every instance that uses it updates to match, on every screen that uses the kit. Designers do not hunt through the product to fix each button.

This works only when the parts are linked. A button drawn by hand is not linked, so a color change will miss it. A detached instance is also out of step. This is why the rule to pick from the kit matters so much.

Tip

After a change to the kit, open a few real screens and check them. A linked update should appear everywhere, but a quick check catches the copies someone detached by mistake.

Worked example: a food-delivery checkout screen

The screen below is a made-up example of a food-delivery app checkout, used to show the idea. It is not taken from a real company's file. Suppose the screen has a summary of the order, a text field for a delivery address, a row of icons, and a main button labeled Pay now. Every one of these pieces comes from the team's UI kit.

  1. 1

    Open the kit and start the screen

    Create a new screen frame in the product file. The kit stays in its own shared file, and the product file links to it.

  2. 2

    Place the primary button

    Drag the primary button from the library onto the screen. Change its label to Pay now. The button is an instance, so it is linked to the kit.

  3. 3

    Add the text input

    Drag the text input for the delivery address. Pick the default state, and use the focus state in a second copy to show how a selected field looks.

  4. 4

    Group the order details in a card

    Use the card component to hold the item list and total. Fill in the text, and leave the card's structure as the kit defines it.

  5. 5

    Add icons from the kit

    Place a lock icon near the payment area and a bag icon in the order summary. Both come from the icon set saved in the same kit file.

  6. 6

    Change the brand color once

    Edit the brand color style in the kit. Every instance of the primary button that uses that style changes at once, including the Pay now button on this checkout and on every other screen.

The last step is the point of the whole lesson. The designer changed one style in one file, and the change spread to every button that depended on it. No one had to redraw anything.

Tip

When you present a screen built from a kit, name the kit parts you used. Your reviewers can then see which pieces are standard and which are new.

Common mistakes to avoid

  • Redrawing a part that exists

    A hand-drawn copy will not follow kit updates. Search the kit first, every time.

  • Editing the main part for one screen

    A change to the main component reaches every instance. Make screen-only changes on the instance instead.

  • Detaching too often

    A detached instance stops receiving updates. Detach only when you truly need a different design, and say so in your notes.

  • Making too many variants

    A pile of near-identical variants is hard to use. Add a variant only when a state, size or type is truly needed.

Each of these mistakes breaks the one benefit a kit gives you: one place to change, and many places that follow.

Check yourself

Quick check

A teammate redraws the Pay now button by hand on each of 12 screens. Later the brand color changes. Using the idea of a UI kit, what would have saved time, and why?

Quick check

Priya places a kit button on her sign-up screen, then detaches it so she can change its shape. Weeks later, the kit's button color changes. What happens to her sign-up button?

Quick check

A five-person team builds three apps for one company. They need the same buttons, colors and rules across all three, and developers will build parts in code. Which choice best fits their need?

Where to go next

You now know what a UI kit holds, how it is organized, how it differs from a design system, and how designers use and update it. Your next steps in this course cover related topics in their own lessons. These include the coded counterpart of the kit, the named values that hold colors and spacing, the way parts are grouped into larger pieces, and the detailed rules for color, type, spacing and icons.

Tip

Before you read the next lesson, open any kit you can access and find one button, one input and one style. Note where each one lives. This short check makes the next ideas easier to follow.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.