Running on Figma?

Figma handoff mismatched or tokens drifting? We ship it properly.

Figma is the shared surface between designers and engineers, which is why a broken handoff shows up as a very visible bug. We bring the design tokens into the codebase, keep the component library honest, fix the plugin that will not load after a manifest change, and leave the design-to-code loop short enough to use.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

figma-plugin.log

still broken

What it is

Figma at a glance

Figma is a browser-based design tool launched in 2016 by Dylan Field and Evan Wallace. It became the default interface design tool across product teams largely because real-time collaboration was built in from day one, and it was acquired by Adobe in 2022 before the deal was abandoned in 2023 under regulatory pressure. The tool now runs as an independent company again.

The platform covers interface design, prototyping, FigJam whiteboards, Dev Mode (the handoff view), Variables (design tokens), Code Connect (linking Figma components to real code), a plugin API and a REST API with webhooks. Most problems we see are not with the canvas; they are with the bridge between design and code: tokens that drift, component props that do not match, plugins that stop loading after a manifest schema bump, or exports that break because a node was quietly detached from its master component.

Type
Collaborative interface design and prototyping
First released
2016
License
Proprietary SaaS, per-editor pricing with Starter, Professional, Organization and Enterprise tiers
Maintained by
Figma, Inc.
Typically used for
UI design, prototyping, design systems, developer handoff, FigJam whiteboarding

The honest version

Figma pros and cons

No technology is all upside. This is where Figma earns its place and where it tends to cause trouble.

Where Figma is strong

  • Collaboration is genuinely real-timeMultiple designers can work on the same frame without saving conflicts, comments stay in context, and reviewers see the current state rather than an export from last Tuesday.
  • Dev Mode is a serious handoff surfaceSpec, measurements, variables and Code Connect links come through to engineers in a view that matches what they need, not what the designer thinks they need.
  • Variables cover design tokensColors, numbers, strings and booleans with modes (light, dark, brand) let a design system express tokens that can round-trip to CSS, tokens.json or a Tailwind config.
  • Plugin ecosystem is hugeThousands of plugins cover icon libraries, content generators, accessibility checks, token exporters and connectors to Jira, Linear and Notion, so most workflow gaps have a ready solution.
  • REST API and webhooks for automationFile metadata, component inventories, library analytics and change notifications are reachable programmatically, which keeps a design system healthy at scale.
  • Cross-platform accessThe browser build is the canonical one, which means Chromebook, Linux, Windows and Mac users get the same experience without a native-client lag.

Where Figma bites

  • Per-editor pricing climbs quicklyEvery person who edits counts against the seat count, including part-time contributors, and the Organization and Enterprise tiers add real line items for medium-size teams.
  • Component libraries drift without disciplineTeams that let anyone publish libraries end up with multiple almost-identical button components, and the tokens in the file no longer match the ones in code.
  • Dev Mode is only as good as the inputsIf designers do not use auto-layout, name layers or publish components, Dev Mode shows nicely laid-out junk, and engineers still screenshot the frame to measure it.
  • Plugin API breaks occasionallyManifest schema changes, Variables API additions and removals, and sandbox limits have all broken plugins over the years. A plugin that was fine in 2023 can fail to load after a 2026 version bump.
  • Offline is weakFigma relies on connectivity, and a long flight with the mobile hotspot off is an unproductive one. Local caching exists but is limited.
  • Exports are not a design systemA SVG or PNG export per icon, or a token.json dropped into the repo, is not a design system, and teams that treat Figma exports as the source of truth get a slow drift between design and code.

Sound familiar?

Common Figma problems we fix

The Figma problems that bring people to us, and what you have once each one is fixed.

manifest.json: 'editorType' required

A plugin fails to load after a Figma update

A manifest schema that moved an optional field to required, or a new build of the plugin that targeted a newer API version than the manifest declared. The plugin appears in the sidebar but refuses to run.

Plugin loads and runs cleanly

Design tokens: 14 colors not in Variables

Design tokens drift from the codebase

Hardcoded hex values pasted into frames that bypass the Variables system, or tokens that exist in CSS but were never backfilled into Figma. The drift is invisible until an engineer and a designer look at the same component together.

Tokens in sync, one source of truth

Code Connect props mismatch

Dev Mode shows the wrong code for a component

A React component whose props do not match the Figma component variants, or a Code Connect link that points at a stale file path. Engineers copy code that is not quite right.

Code Connect accurate per component

REST API: 403 Forbidden, lacks scope

An automation lost access to a file

A personal access token that was created before Dev Mode scopes existed, or a webhook consumer that was switched to a token with narrower permissions during a rotation.

Tokens scoped and refreshed

Library update available: 42 components

A library sync broke many consumer files

A design system release that renamed or restructured components, propagated into every consumer file, and reset auto-layout constraints on frames that had local overrides.

Library sync planned, overrides preserved

Webhook signature invalid

Webhook deliveries are being rejected

A consumer that was written before webhook signatures were required, or a shared secret that was rotated without updating the receiver. Deliveries succeed at Figma and fail silently at your end.

Webhooks signed and processed

Export failed: node detached from component

Icon or component export breaks

A node that was detached from its master component, usually by accident during a quick edit. The export script loses the reference and skips the asset, or produces the wrong artwork.

Components attached and exportable

What we do

Figma help, design system to handoff

Call us for one failing plugin, or let us own the whole design system pipeline.

Rescue
A plugin that will not load, a library sync that broke every consumer file, or a Dev Mode that shows the wrong code. We stabilise the file and then explain the real cause.
Design tokens and Variables
Colors, spacing, typography and semantic tokens expressed as Figma Variables with modes, and a build pipeline that exports them to the codebase so drift becomes visible.
Code Connect
React, Vue or Svelte components linked to their Figma counterparts, with prop mapping that matches the real API, so Dev Mode produces code that compiles.
Component library audits
Duplicates merged, variants rationalised, publishing rules agreed, and a review step before a library release ships to consumer files.
Plugins and REST automation
Custom plugins that pass review, REST integrations into Jira, Linear and the warehouse, and webhook consumers that sign-check properly and survive retries.
Managed Tech
Weekly checks on library drift, plugin compatibility with the current Figma version, token sync status, and an engineer who can answer when a release breaks the consumer files.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Figma alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Figma questions

Something else? Call+1 737 727 7327

How do we keep Figma design tokens in sync with our codebase?

The reliable pattern is a build step. Design tokens live as Figma Variables with modes, a plugin or the REST API exports them to a tokens.json file, and the codebase consumes that file through its own token system (CSS custom properties, Tailwind config, or Style Dictionary). The drift becomes a pull request rather than an argument, and either side can propose a change through the same pipeline.

Why does our Figma plugin stop loading after an update?

Manifest schema changes are the usual culprit. Figma periodically adds required fields or renames old ones, and a plugin that was happy in 2024 can fail to load after a 2026 update. The fix is to bring the manifest up to the current schema, bump the API version in the manifest to match the plugin code, and verify the plugin loads in a fresh file rather than a cached one.

How do we make Dev Mode actually useful for engineers?

Three disciplines: components are real components with variants (not loose frames), auto-layout is used properly so spacing is meaningful rather than visual, and tokens come through as Variables rather than hardcoded values. If those three are in place, Dev Mode turns handoff into a copy-paste exercise. Without them, it is a slightly prettier screenshot.

Can we connect Figma components to our React or Vue code?

Yes, through Code Connect. Each Figma component gets a mapping that points at the real source file and describes how Figma variants translate to component props. Engineers viewing the component in Dev Mode see code that matches their codebase, not generic snippets. The setup is a one-time investment per component and pays off every handoff after that.

How do we stop a library update from breaking every consumer file?

By treating a design system release like a code release. Breaking changes are announced, consumer files are migrated in waves, the first wave is a small set of pilot files, and auto-layout overrides that matter are preserved during the swap. The tooling exists; it is the process around it that most teams skip.

How much does Figma help cost?

A quote is free. Share the file or the plugin repo and a short description of what is wrong, and we come back with a scope and a fixed price before we open the organization.

Free estimate

Figma giving you trouble?

Design tokens, Dev Mode, Code Connect, plugins and REST integrations. We work on both sides of the design-to-code boundary.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.