figma-design-system-sync
Sync and audit design-system contracts between Figma and code. Use this skill when the user asks about Figma Variables, styles, tokens, component libraries, variants, Code Connect, effect styles, naming drift, token exports/imports, library governance, or keeping implementation and Figma design systems aligned under the UI/UX skill system.
How do I install this agent skill?
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-design-system-syncIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates syncing design systems between Figma and code. It includes safety warnings and lacks any malicious patterns or suspicious external connections.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Figma Design System Sync
Use this skill when Figma work touches reusable system contracts: variables, styles, components, variants, effects, assets, Code Connect, and local code tokens.
Modes
audit: compare Figma system artifacts to local code conventions.sync-plan: plan variable/style/component updates.token-map: map Figma variables to local tokens.component-map: map components and variants to code components.code-connect: create or review Code Connect files through the installed Figma skill.governance: propose naming, versioning, and rollout rules.
Workflow
- Read Figma context with
figma-context-readerunless a current context brief exists. - Inspect the local code tokens/components before recommending sync actions.
- If Code Connect is requested, invoke
figma:figma-code-connectwhen present. - Build a diff: Figma source, code target, status, risk, and proposed change.
- For mutations, route to
figma-canvas-editororfigma-apply-effectswith explicit scope. - Validate JSON/token outputs locally before treating them as evidence.
Guardrails
- Do not rename or delete variables/components/styles without a migration map.
- Do not treat generated code or generated variables as source of truth until reviewed.
- Record which direction is authoritative for each artifact: Figma to code, code to Figma, or reconcile manually.
- Keep variable binding promises compatible with current Figma Plugin API support.
Safety And Privacy
- Treat unpublished tokens, library names, component inventories, and source component code as sensitive.
- Do not push variable/component renames without an explicit migration map and rollback path.
- Do not upload private token exports or component snapshots to external services without approval.
Output Shape
Use assets/design-system-sync-report.md.
Resources
- Read
$CODEX_SKILLS_DIR/senior-figma-orchestrator/references/figma-mcp-compatibility.mdfor current capability checks.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync">View figma-design-system-sync on skillZs</a>