Figma for Devs

The designer drew your excuses away.

▶ the lesson · narrated sketch video · tap for sound

the intro

Designers hand over Figma files, and developers who can read them build the right thing faster. Frames show the structure, auto layout reveals spacing logic, and dev mode hands you measurements, colors, and exportable assets.

fun fact ✦

Figma runs in the browser too — the design tool is itself a big web app.

the docs

the deep dive

the ideas behind the video — concepts, diagrams, a walkthrough and the traps to avoid

A Figma file is your component tree wearing art supplies. Frames are divs, auto layout is flexbox with a design degree, and styles are CSS variables with opinions. Reading a design well means translating one tree into another — not squinting at a picture and guessing paddings.

translate the tree, skip the guessing

design filepage / canvasframeauto layout
same nesting as your markup: file, page, frame, layout

key terms

frame

A container with its own size and clipping — the closest thing to a div in design land.

press F to draw one

auto layout

Flexbox for designers: direction, gap, padding, and children that reflow when content changes.

gap 16, padding 24

component

A reusable master element; every copy is an instance that inherits updates.

one Button, many instances

dev mode

An inspect view built for engineers: measurements, spacing, tokens, and code values per element.

measures, colors, snippets

how it works

  1. 1
    Switch to dev mode

    It turns the canvas into an inspector: click any element for measurements, spacing, colors, and code values.

  2. 2
    Read the layer tree

    The left panel is the component hierarchy — frames inside frames with auto layout between them. It maps almost one-to-one onto your markup.

  3. 3
    Take values, not CSS

    Copy the colors, sizes, radii, and spacing — then rebuild layout with your own flex and grid. Figma CSS assumes absolute positioning.

  4. 4
    Export assets properly

    SVG for icons and logos, 2x PNG for raster images. Check the export tab in dev mode before asking a designer.

  5. 5
    Click the prototype

    Hit play and walk the flow like a user. A confusing flow costs one minute to find and one sprint to fix later.

the code, explained

values from dev mode, layout is yours

1/* values from dev mode, layout yours */
2.card {
3 display: flex; /* auto layout */
the panel direction and gap, translated
4 gap: 16px; /* item spacing */
auto layout gap lands as gap
5 padding: 24px;
6 border-radius: 12px;
corner radius, straight over
7 background: #101418;
8}

side by side

copied CSS

  • absolute positions baked in
  • breaks on real screen sizes
  • ignores your design system
  • fast today, painful next sprint
VS

rebuilt layout

  • flex and grid from auto layout
  • responsive by default
  • uses your tokens and classes
  • survives the next redesign
🪤 gotcha

The design is one frozen width — usually 1440 pixels — and it does not know your breakpoints. You own responsiveness: check the layout at 375 and 1920 before shipping what the file shows.

quick answers

The design uses a color not in our code. What now?

Ask before inventing. It is usually token drift, and silently adding a new hex fragments the design system one shade at a time.

Do developers need to learn Figma?

Read-level, yes: dev mode, the layer tree, and prototypes. You are not designing — you are reading specs that happen to be visual.

Why does my build look different from the file?

Usually line-height, letter-spacing, or font fallback. Copy all the text values from dev mode, not just the font size.

quick hits about Figma for Devs

short answers · interviews, tips, trivia & hidden gems

📚 tutorial

Read the structurewatch ↗

🔧 useful

Inspect like DevToolswatch ↗

💎 deep

Copied CSS is a starting pointwatch ↗

💎 deep

Click the design before coding itwatch ↗