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 generate tickets when your Figma library is published. The plugin’s role is to sync variables so issues include accurate token names, collections, modes, and values.

Capture – Understand the Change

Capture is how Lyse detects and structures changes inside your Figma library. Lyse indexes the file via your Personal Access Token and understands components, variants, and variables.

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

When variables change, run Lyse Sync Variables in Figma so the latest token graph is available. This keeps the captured context complete and ready to enrich tickets after you publish.

Orchestration – Deliver the Work

Once Capture knows what changed, Orchestration turns those diffs into actionable tasks in your connected tools such as Linear, Jira, or GitHub.

The publish event in Figma is the single trigger. On publish, Lyse generates tasks with links to the precise nodes and, if you synced variables, embeds the relevant token details so developers or AI agents like Cursor or GitHub Copilot can execute with confidence.

The Impact Today

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.

• Faster delivery: from Figma publishes to provider ticket in a few steps.