Library Change Preflight
by SeeyaWorks
Review supported component changes against a baseline you capture before publishing.
Installs
0
Likes
0
Users
1
Views
8
Preview
About this plugin
Before you manually publish local component-library changes, see which supported structural edits deserve a closer look.
Library Change Preflight is for individual component-library and design-system maintainers, consultants, freelancers and practitioners. Capture a known-good baseline in your editable Figma Design source file, make your edits, then run a deterministic preflight with concrete before/after evidence.
Your workflow1. At a known-good point, choose Set / Refresh Baseline.
2. Edit your local components and component sets.
3. Choose Run Preflight before publishing and inspect the Review Queue.
4. Publish manually, then refresh the baseline once the new state is known good.
What the queue showsHIGH: Supported removals of components, component properties, variant properties or options. Property rename/type-change findings require safe identity matching.REVIEW_REQUIRED: Descendant names or structure, and component identity, membership or variant-assignment changes that need human review.INFO: Supported additions and component-name changes with retained identity.
Each finding identifies the component or set and gives baseline/current evidence, a concise explanation and relevant limitations. One edit can produce more than one finding.
The baseline is explicitly captured by you. The plugin does not retrieve a previously published version. No baseline means NO_BASELINE, never a pass. Unreadable or incompatible data produces ERROR. “No supported changes found” means only that the supported comparison found no changes; compatibility is not guaranteed.
The plugin inspects local Components and Component Sets in the current document. It does not scan consumer files, count organization usage, simulate actual instance breakage, inspect Variables or Styles, or automatically migrate, fix or publish anything.
Your visible design is not modified. Private baseline metadata is stored in the Figma document. The Product has no network path, backend, analytics, telemetry, AI, REST or OAuth.
Support: seeyaworks.support@gmail.com