Nov 10, 2025
Introducing Watcher Automate Design Systems
Why handoff still breaks in 2025?
Design systems move fast. Components evolve, variants shift, tokens are refactored, and styles get renamed to match new brand rules.
What actually changed in Figma often gets scattered across long Slack threads, screenshots, and copy-pasted checklists.
Tickets reach engineering without enough intent, links, or acceptance guidance. Teams lose traceability. Developers ask for clarification. Work stalls.
The cost is not just time. It is version risk, duplicated effort, and a widening gap between the design system and production code.
Meet Watcher
Watcher is Lyse’s first core feature. It captures the full diff of your Figma library on each publish and writes clean, structured tickets to your tracking tools.
Connect Figma once, select one or several providers (Jira, Linear, GitHub, GitLab), and Watcher delivers the right updates to the right place every time the library is published.
What teams gain ?
Zero blind spots: every component, variant, style, and token change is captured at the moment of publish.
Lower ops cost: tickets start “ready to work” with links to Figma nodes and usage evidence.
Real alignment: design, product, and engineering act from the same source of truth.
Agent-ready context: copilots and code agents operate on explicit design intent, not vague summaries.
What Watcher captures
The result is a task that is both actionable and verifiable, without hunting through threads.
Components and variants: structure, props, and state patterns.
Design tokens: color, typography, spacing, radius, elevation, and usage shifts.
Styles and naming: renames, merges, and deprecations with impact hints.
Behavior notes: usage guidelines or constraints attached to components.
Evidence links: direct pointers to Figma nodes and relevant artifacts.
Lyse is built for humans and AI agents
High-quality context is the fuel that tools like GitHub Copilot, Claude, Cursor, and Windsurf need to be useful in real workflows.
Because Watcher makes intent explicit and links evidence precisely, agents can draft safer diffs, suggest accurate refactors, and reduce back-and-forth with designers.
Engineers benefit either way: clear tickets they can run with, or agent-assist that actually reflects design intent.
Before and after
Before
Publish in Figma. Someone writes a ticket from memory, pastes screenshots, forgets a token rename, and omits links. Engineers ask for context. Work pauses.
After (with Watcher)
Publish your Figma Library. Tickets appear in Jira, Linear, GitHub, or GitLab, already populated with the diff, references, and acceptance hints. Engineers focus on implementation, PMs on priorities, designers on the next iteration. The handoff loop tightens.
Setup in minutes
Connect Figma on Lyse’s webapp
Connect your Figma variables on Lyse’s Plugin
Connect one or more trackers: Jira, Linear, GitHub, GitLab.
Publish your library as usual. Watcher handles capture and structure your tickets from components changes.
Minimum requirement: Figma plus at least one ticket provider. You can connect several in parallel to match how your organization works.
Our vision for Lyse
Watcher is the foundation of Product Context Intelligence.
Our thesis: when change is captured at the source, linked to evidence, and distributed with intent, the entire product pipeline accelerates.
Lyse is building a standard layer that:
Captures change precisely and immediately.
Keeps memory across design, tickets, code, docs and insights.
Orchestrates the right follow-ups so teams and agents execute with confidence.
Elevates intelligence with reliable context that compounds over time.
One change should propagate into an up-to-date product experience in minutes, inside the tools you already use.
Watcher is the first brick. Next comes deeper memory, smarter orchestration, and higher-leverage intelligence for every team that ships from a design system.
Questions we hear from teams
Do we need both Figma and a tracker?
Yes. Figma is required to capture the diff. Connect at least one provider so Watcher can create tickets automatically.
Can we use multiple providers at once?
Yes. Many teams route developer-facing issues to GitHub while using Jira or Linear for product and design.
What types of changes create tickets?
Component, variant, style, and token updates, plus relevant notes and links. You can scope, group, or filter according to your workflow.
Does Watcher replace PMs or Design System Managers?
No. Watcher removes mechanical translation and bookkeeping so leaders focus on prioritization, reviews, and outcomes.
Try Lyse for free
If your team ships from a Design System, Watcher is the fastest way to keep design, tickets and code in lockstep.
Request early access and watch your next Figma publish turn into clean, ready-to-run tickets in the tools your team already lives in.
