figma-storybook-sync
Skill19 starsChanged 5 months agoNo licenceView on GitHub
Detect which Storybook stories need updating from Figma-side edits and produce a routed sync-back report, using a three-way comparison between the synced baseline payload, the current Storybook export, and the current Figma state. Use after components or pages exported with the design-system-to-storybook Figma export addon were refined in Figma and the user wants to know what changed, in which direction, and how each change should flow back — token differences to the design-system-extractor Late-Arriving Authoritative Source Pass, visual differences to ui-compare-to-reference, structural differences to manual handling. This skill classifies and routes; it never modifies product component code, token CSS, or component spec documents.
- Sends data out
In this repository68 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-workspace-starter/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-workspace-starter/CLAUDE.mdCLAUDE.md
- agent-automationSkill
- design-system-extractorSkill
- design-system-to-storybookSkill
- spectra-analyzeSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- spectra-verifySkill
- storybook-product-prototypeSkill
- api-data-integrationSkill
- automation-pipeline-boardSkill
- automation-portfolioSkill
- spectra-analyzeSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- spectra-verifySkill
- storybook-product-prototypeSkill
- create-design-workspaceSkill
- cross-platform-paritySkill
- design-system-extractorSkill
- design-system-to-storybookSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- storybook-product-prototypeSkill
- design-automation-hubSkill
- design-system-extractorSkill
- design-system-governanceSkill
- design-system-to-storybookSkill
- executive-proposalSkill
- figma-componentizeSkill
- figma-m3-variablesSkill
- frontend-product-implementationSkill
- ios-foldable-adaptationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.