ds-parity-maintenance

Automate Figma-to-code design parity monitoring and structured JSON reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill runs a deterministic, headless parity engine to maintain daily design-parity between Figma and code for the Signal DS, reporting asymmetry, day-over-day delta, and alarms on regressions while driving the unanchored backlog.

Core Features & Use Cases

  • Deterministic parity engine that compares Figma designs to code and outputs a structured parity report.
  • Daily and on-demand execution with scheduled runs and ad-hoc parity checks to surface regressions.
  • Weekly live-Figma bridge reconciliation and team digest to keep stakeholders informed.
  • Backlog-driven graduation workflow guiding prioritization from unanchored components to anchored status.

Quick Start

Run a parity check on your daily schedule or on-demand to generate today’s parity report.

Frequently Asked Questions about ds-parity-maintenance

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

FAQPage Schema
How do I automate Figma to code design parity monitoring?

You can automate Figma to code design parity monitoring by running a headless parity engine that reads design maps and tokens from your repository, comparing them to output structured JSON summaries with totals and anchored counts.

What is a design parity audit and how does delta tracking work?

A design parity audit compares Figma components against code implementations to identify asymmetry, calculating a day-over-day delta by writing dated snapshots for trend analysis to surface regressions and track unanchored backlog items.

How do I set up daily design health checks for my design system?

Schedule daily design health checks by running the parity engine against your main branch, generating structured JSON summaries with anchored and unanchored counts alongside day-over-day deltas for trend analysis.

Can I run an on-demand parity check for Figma and code regressions?

Yes, you can run on-demand parity checks for Figma and code regressions by executing the parity engine ad-hoc, which reads current design tokens and emits a structured report alarming you on detected asymmetry and regressions.

Does the design parity audit require specific repository branches?

Yes, the design parity audit requires the origin/main branch, as the engine reads the design map and tokens directly from this branch to compute deterministic parity reports and write dated snapshots.

How do I manage unanchored components in a design parity backlog?

Manage unanchored components in a design parity backlog by using the graduation workflow, which prioritizes unanchored items through weekly live-Figma bridge reconciliations to guide components toward anchored status.