Getting Started

Key concepts

Lyse rests on two pillars: Capture and Orchestration. Together they convert updates in your Figma Design System into clear, developer ready work.

Lyse generates tickets when your Figma library is published. The publish event is the single trigger that starts the loop.

Capture – Understand the Change

Capture is how Lyse detects and structures changes inside your Figma library.

Using your Figma Personal Access Token, Lyse indexes the file and understands your components and variants.

On each publish, Lyse compares the new state of the library with the previous one and detects:

Even small edits are recognized, such as tweaking a button style or renaming a variant property.

Even small edits are recognized, from tweaking a button’s background-color to renaming a variant property or deleting a token.

Once Capture knows what changed, Orchestration turns those diffs into actionable tasks and team updates.

For every publish, Lyse can:

Create scoped tickets in your connected tools such as Linear, Jira, GitHub or GitLab
Post a concise summary to Slack so the whole team sees what changed in the channel you choose

Each task includes links back to the precise nodes in Figma so developers and product teams can review the change in context.

For now, we capture and orchestrate, Lyse already streamlines the handoff workflow for product teams:

Time saved: several minutes per ticket, multiplied across your backlog
Less back and forth: one source of truth from publish to ticket and Slack summary
Faster delivery: from Figma publishes to provider tickets in a few steps, without manual ticket writing