figma-doc-sync

Sync Figma component descriptions with DESIGN-STATE.md and design-map.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill figma-doc-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-doc-sync
Source: https://github.com/Scripsteam/scrips-stack/tree/main/figma-doc-sync
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill figma-doc-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps Figma in sync with locked design decisions and design-map.json to prevent drift.

Core Features & Use Cases

  • Synchronize Figma component descriptions with DESIGN-STATE.md and design-map.json.
  • Update component metadata when tokens change or components are renamed.
  • Serve as a governance step in the design-to-dev pipeline to keep design docs in sync with implementation.

Quick Start

Use this skill to refresh all component descriptions in Figma when DESIGN-STATE.md is updated or a new component is added to design-map.json.

Frequently Asked Questions about figma-doc-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Figma component descriptions in sync with design decisions?▼

To sync Figma component descriptions with locked design decisions, this skill cross-references DESIGN-STATE.md and design-map.json to automatically update annotations and prevent design drift.

What's the best way to update Figma annotations when design tokens change?▼

The best way to update Figma annotations when design tokens change is to trigger this synchronization skill, which detects modifications in tokens/design-tokens.ts and pushes updates to Figma.

Do I need the Figma Desktop Bridge to synchronize my design system documentation?▼

Yes, you need the Figma Desktop Bridge workflow to execute this design system documentation synchronization and apply updates directly to component metadata.

How does design-map.json integration prevent design system drift?▼

Design-map.json integration prevents design system drift by serving as a structural reference: whenever a new component is added, the skill automatically updates its Figma description to match.

Can I automate governance steps in my design-to-dev pipeline?▼

Yes, you can automate governance steps in your design-to-dev pipeline by running this skill whenever DESIGN-STATE.md is updated, ensuring implementation always matches locked documentation.

Why are my Figma component descriptions out of sync with locked decisions?▼

Figma component descriptions fall out of sync with locked decisions when manual updates are skipped; this skill automatically applies changes from DESIGN-STATE.md to prevent such drift.