Free · 8 min read

How to make a UI kit in Figma: a step-by-step guide for beginners

How to build your own UI kit in Figma: scope, file structure, styles, components with variants, and testing on screens. Five steps for a learning project.

  • Decide which components a first UI kit needs and which it doesn't
  • Name and organize components so they're easy to find in Assets
  • Test the kit by building new screens without detaching anything
Share your UI kit
  • Free
  • 1,504 members
  • Join in 1 click

Five steps to your first UI kit

  1. 1

    Step 1

    Decide what the kit is for and what goes in it

  2. 2

    Step 2

    Plan the file structure

  3. 3

    Step 3

    Build the foundation: styles and variables

  4. 4

    Step 4

    Build components with variants and properties

  5. 5

    Step 5

    Test the kit on screens and share it

1,504
community members
8,915
messages with questions since July 2024
9
design games since September 2024
759
people wrote in the chat

This guide is for you if you

  • Can already make components

    You know what a component and a variant are, but haven't yet gathered them into one tidy file.

  • Are tired of copying elements

    Every new layout starts with hunting for "that same button" in old files.

  • Want a portfolio project

    You're looking for an exercise that shows precision, systems thinking and Figma skills at once.

In short

  • A UI kit is a file of ready-made components, styles and example screens that you build new layouts from.
  • Don't start from a complete list of elements but from two or three screens: only what's on them goes into the kit.
  • Colors, text and spacing first, components second: otherwise you'll be redoing your buttons.
  • Consistent names and slashes in names (Button/Primary) make the kit easy to use in the Assets panel.
  • The kit is ready when you can build a new screen from it without detaching anything from its components.

Five steps to your first UI kit

  1. 1

    Step 1

    Decide what the kit is for and what goes in it

    A UI kit is always made for something specific: a mobile app, a website, a user dashboard. Pick a learning product, such as a barber booking app or a habit tracker, and sketch two or three key screens. Then list every element that repeats on them. That's your kit list:

    • foundations: colors, fonts, spacing, corner radii, shadows;
    • basic elements: buttons, input fields, checkboxes, toggles, icons;
    • larger blocks: a card, a list item, a top bar, bottom navigation, a modal.

    💡 Don't add components "just in case". A small kit where every component is actually used is more useful than a big one where half of them sit idle.

  2. 2

    Step 2

    Plan the file structure

    A tidy kit is easy to read even for someone opening it for the first time. Split the file into pages: Cover (with the name and version), Foundations (color, text, spacing), Components (all components) and Examples (screens built from the kit). Use slashes in component names: in Figma each "/" creates a new level in the Assets panel and in the instance swap menu.

    • example names: Icon/Arrow, Icon/Close, Navigation/Top bar, Navigation/Tab bar;
    • one language and one naming style throughout the file — English, as is usual in teams;
    • a short text label next to each component: what it is and where to use it.

    Put your kit in other people's hands

    The best test of a UI kit is someone other than the author building a screen with it. Share your file link in the community and ask someone to build one screen.

    Share your UI kit

    Free. 1,504 designers are already in the community.

  3. 3

    Step 3

    Build the foundation: styles and variables

    Before drawing buttons, fix your base values. Figma has five types of styles: color, text, effect, layout guide and animation. For a kit, the first three plus variables for spacing are enough. Show everything on the Foundations page: named color swatches, an example of each text style and the spacing scale.

    • colors: primary, accent, error, success and warning, plus neutrals for text, lines and backgrounds;
    • text styles: two or three heading levels, body text, a caption and button text;
    • effects: one or two shadows for cards and modals;
    • spacing and radii: a small scale, for example 4, 8, 12, 16 and 24 px.

    💡 Check text contrast against backgrounds at this stage: Figma's color picker has a Check color contrast button. Fixing a color in a style now is cheaper than fixing it later in every component.

  4. 4

    Step 4

    Build components with variants and properties

    Select your layers and create a component: Create component in the right sidebar, or Option + Cmd + K (Mac) / Ctrl + Alt + K (Windows). Make states and types variants: in Figma a variant name looks like Property=value, for example State=Hover, Size=Large. Use component properties for small settings so you don't multiply variants:

    • Boolean: show or hide a layer, such as an icon in a button;
    • Text: text that can be changed right in the right sidebar;
    • Instance swap: a nested component that can be replaced, such as an icon;
    • Slot: a flexible area where you can add your own content in an instance, such as a modal body or list items.

    💡 Figma recommends not grouping different icons as variants of one component. Each icon is its own component, and you swap it inside a button with Instance swap.

    Button variants grown to a hundred? Show your file to the community →
  5. 5

    Step 5

    Test the kit on screens and share it

    On the Examples page, build two or three new screens using only instances from the kit. Make the texts longer, switch states, remove icons. If something breaks or you have to detach an instance, go back to the component and fix it. To use the kit in other files you publish it as a library, which is available on paid plans and the Education plan. On the free Starter plan, keep the kit and your working screens in the same file.

    💡 Share a link to the file in the community and ask someone to build one screen from your kit. Wherever they get stuck is the best list of fixes.

You're not alone with these questions

We counted what people ask about most in our community. Figma is in the top three, and questions about components and how to organize them are among the most practical.

You're not alone with these questions
Learning and courses938
Portfolio and case studies705
Figma647
AI tools380
Jobs and vacancies314
UX research131

Messages by topic in Spaceberry Community, July 2024 — November 2026. Keyword search.

Practice with a deadline and live feedback

The best teacher is a task with a deadline that other people see. That's why the community regularly runs design games: the same brief for everyone, a deadline and a vote.

  • Design game · January 2026

    NAOMA website redesign

    The academy's home page through the eyes of an applicant, a student and a teacher. Three finalists; the community chose the winner.

  • AI challenge · May 2025

    A landing page made by AI

    Logo, copy and visuals made only with AI tools. Four entries, an anonymous vote, and participants shared their prompts.

  • Workshop · April 2026

    Figmosha: AI in Figma

    The tool's author showed how to generate interfaces in Figma and analyze a design system.

Share your UI kit

Free. 1,504 designers are already in the community.

How to join: 1 minute

  1. 1

    Tap the button

    Telegram opens with the Spaceberry community.

  2. 2

    Join

    It's free: all you need is a Telegram account.

  3. 3

    Introduce yourself

    Say where you're starting from and ask your first question.

Questions and answers

Didn't find your answer? Ask it in the community.

How is a UI kit different from a design system?

A UI kit is a set of ready-made elements: components, styles and example screens. A design system also includes principles, usage rules and documentation, and a team keeps maintaining it. Your own UI kit is a good first step toward understanding design systems: once you add notes on when and how to use each component, it's already close to a mini system.

Can I use a ready-made UI kit instead of my own?

Yes, and it's useful for learning. Figma offers ready-made UI kits, including Google's Material 3 Design Kit, Figma's Simple Design System and Apple's iOS and iPadOS kits (Apple's kits require accepting a license agreement). You add them via Assets → Libraries → UI kits. But building your own kit teaches more: you make every decision yourself.

How many components should a first UI kit have?

As many as your two or three screens need: the foundations (color, text, spacing) and the components that repeat on those screens, such as buttons, fields, checkboxes, a card and navigation. There's no universal number. Fewer is better, as long as each one has all its states.

Is Figma's free plan enough?

For a learning kit, yes: components, variants, styles and variables are available on the Starter plan. The limits are that you can't publish a library for other files, and the team folder holds only three Figma Design and Figma Sites files in total (you can have unlimited drafts).

Is the Spaceberry community paid?

No, Spaceberry Community is completely free. It's supported by Spaceberry Foundation, a non-profit public organization. All you need to join is a Telegram account: tap the button on this page, introduce yourself and ask your first question. The community has 1,504 designers who share their work, give feedback and take part in design games with the same brief for everyone. Conversations are in Ukrainian.