Skip to main content
Publish Figma Dark

​
Why it matters

When you publish a library in Figma, developers need to know what changed. But Figma’s version history doesn’t tell the full story. “Updated Button” doesn’t explain that spacing.button.horizontal changed from spacing.md to spacing.sm. Lyse bridges this gap. It detects every change, generates an AI summary of what happened, and creates a task developers can act on. They know what changed, why it matters, and what to update in code.

​
How it works

  1. You connect Figma and select which libraries to track
  2. You publish a library in Figma (as you normally would)
  3. Lyse detects the changes via Figma’s webhook
  4. AI analyzes what changed and generates a summary
  5. Tasks appear in your inbox for review
  6. You approve and they land in your issue tracker
You stay in control. Nothing reaches developers until you review and approve.

​
What Lyse detects

​
Component changes

When you modify an existing component, Lyse identifies:
Colors, spacing, typography, borders, shadows
Padding, margins, alignment, constraints
New variants added, existing variants modified
New properties, renamed properties, removed properties
Example task: 
Button/Primary — --spacing.button.horizontal changed from 
--spacing.md to --spacing.sm

The horizontal padding on the primary button was decreased. 
This makes the button more compact. 

Developers should update --spacing-button-horizontal and verify it 
doesn't break layouts where buttons appear inline with text.

​
New components

When you add a component to your library:
  • Lyse creates a task announcing the new component
  • The summary describes what the component is for
  • Developers know a new building block is available
Example task: 
New component: Card/Elevated

A new card variant with elevation shadow has been added to the library. 
Use this for content that needs visual prominence. Includes hover state 
with increased elevation.

​
Deleted components

When you remove a component:
  • Lyse flags it as a deletion
  • The task warns developers about the deprecation
  • Teams can plan migration before removing from code
Example task: 
Deleted: Badge/Legacy

The legacy badge component has been removed from the library. If this component 
is still used in code, migrate to Badge/Default before the next release.

​
Publish workflow

Your publishing workflow doesn’t change:
  1. Make changes to components in Figma
  2. Click Publish library as usual
  3. Confirm the publish
Lyse picks up the webhook automatically. Within seconds, tasks appear in your inbox.

​
Tips for better results

​
Clear names

Lyse uses component names in task titles. Clear names make for clear tasks.
  • Button/Primary is better than btn-1
  • Card/Elevated is better than card-v2-new

​
Review first

Lyse summaries capture most changes accurately. Take a few seconds to check the content before publishing. If something needs adjustment, copy the content and modify it manually.

​
Batch actions

When you publish many small changes, use the batch approve feature in your inbox. Select multiple tasks and approve them all at once—perfect for routine updates.

​
Team publishing

Lyse tracks the file, not the user. Any team member can publish the library and Lyse will detect the changes. Tasks appear in the inbox of the Lyse account that connected the file. You only need one Lyse account connected per file.

​
Troubleshooting

​
Changes not detected

  • Verify the file is selected in Figma
  • Make sure you published the library (not just saved the file)
  • Check your Figma connection status
  • If multiple Lyse accounts track the same file, webhook conflicts may prevent detection

​
Missing details

  • For complex changes, copy the content and adjust manually
  • Use clearer component names

​
Variables not showing

  • The Figma file containing your local variables hasn’t been synced with the Lyse plugin
  • If you recently added or updated variables without re-syncing, they will appear as raw values instead of semantic names
  • Open the file in Figma, run the Lyse plugin, and click Sync to update variable mappings

​
Wrong components detected

  • Lyse tracks published library changes, not regular file edits
  • Make sure you’re editing components that are part of the library
  • Check that the component is published (not just local)

​
Duplicate tasks

  • Each Figma file should be linked to only one Lyse account
  • If multiple accounts track the same file, you may get duplicate or conflicting tasks
  • Remove the file from one account in Figma

​
Learn more

Figma integration

Connect your Figma account and libraries

The Reviewer

Review and approve tasks

Tasks from Slack

Create tasks from Slack conversations

Notification agent

Get notified when changes are detected