Getting Started

Overview

Help you understand what Lyse is, how it plugs into your Figma Design System and workflows, and how to try it safely end to end with your team.

What is Lyse?

Lyse is your Product Context Intelligence for Figma.
It ingests the context of your Design System file and your variables, then turns design changes into structured work for your team.

Once your setup is complete:

  • Lyse watches components, variants, variables, styles and rules in your Design System

  • On each library publish in Figma, Lyse compares the new state with the previous one

  • It detects which components were created, updated or deleted

  • It generates actionable tickets for your developers

  • Each run produces a verifiable audit trail that records what changed, where it changed and why

Lyse connects the moment a design decision is applied in Figma with the work that needs to happen in your delivery tools.

Where Lyse sits in your stack

Lyse starts where changes are made: your Figma files.

Design source of truth: Figma

  • In the Lyse web app, you connect the Figma file that hosts your Design System

  • Lyse ingests component metadata so it can watch the structure of your library over time

  • You need to be an Admin of the Figma workspace to connect a file for your team


Generate tasks
Variables and foundations: Lyse Figma plugin

  • With the Lyse plugin, you connect the file where your local variables live

  • This can be the same Design System file or a dedicated foundations file

  • You reconnect variables from the plugin whenever your variables change so Lyse always uses the latest values

Work orchestration and notifications

  • After a library is published in Figma, Lyse generates scoped tickets in your existing tools such as Linear, Jira, GitHub or GitLab

  • A Slack channel can receive a concise summary that covers every relevant Design System update

This keeps the whole loop from design change to tracked work visible and traceable without changing the tools your team already uses.

Why teams adopt Lyse

Teams use Lyse to make Design System changes safer, more transparent and easier to ship across the product stack.

With Lyse, you get:

  • Fewer manual handoffs : Tickets are prewired with the right context, links and impact. Designers spend less time re explaining changes to developers.

  • Faster cycles : Small or repetitive changes in the Design System can be turned into work in a consistent way, which shortens the path to production.

  • A single source of truth for change : Every run records what changed, where it changed and why. Design, product and engineering share the same view of how the Design System evolves over time.