design-sync

Generate Signal DS component stubs and detect token drift from Figma designs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligning visual design with code can be error-prone and time-consuming. This Skill helps engineers translate Figma designs into Signal DS components, detects token drift, and validates DS usage to speed up safe, consistent delivery.

Core Features & Use Cases

  • Detect token drift between Figma references and DS tokens, and generate DS-aligned component stubs.
  • Validate DS usage across components, flag missing tokens, and propose DS-consistent patterns for new components.
  • Use during design-to-code handoffs, DS compliance checks, and early validation before implementation.

Quick Start

Run a design-sync session on a Figma design to generate DS-aligned stubs and token checks.

Frequently Asked Questions about design-sync

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

FAQPage Schema
How do I sync Figma designs to Signal DS components during handoff?

To sync Figma designs to Signal DS, run a design-sync session that generates DS-aligned component stubs and validates token usage, ensuring accurate design-to-code translation. This produces reviewable artifacts teams can integrate directly.

What is token drift detection between Figma and design systems?

Token drift detection identifies mismatches between Figma design references and your Signal DS tokens, flagging inconsistencies before implementation. It checks that components adhere to DS tokens and highlights missing or non-compliant values.

How do I validate design system compliance across multiple Figma components?

Validating DS compliance involves running a design-sync session that scans components against Signal DS tokens, flags missing tokens, and proposes DS-consistent patterns for new components to ensure uniform adherence.

Can I generate frontend component stubs from Figma designs using Signal DS tokens?

Yes, you can generate component stubs from Figma designs by running a design-sync session that produces token-consistent, DS-aligned stubs for frontend integration. These stubs serve as accurate starting points for engineers.

Do I need a Figma file to run a design system audit for Signal DS?

A Figma design reference is required to run a design-sync audit, as the Skill compares visual designs against Signal DS tokens to detect drift and validate compliance across components and patterns.

What's the best way to prevent design-to-code token drift in frontend workflows?

The best way to prevent token drift is running early design-sync validation before implementation, detecting mismatches between Figma references and Signal DS tokens, and generating DS-aligned component stubs for consistent handoffs.