fix-design-system-finding

Fixes a single design-system audit finding in a Figma node with minimal scope.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/yerzong/TEMP-LEAGUE --skill fix-design-system-finding-yerzong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-design-system-finding
Source: https://github.com/yerzong/TEMP-LEAGUE/tree/main/.claude/skills/fix-design-system-finding
Command: npx skills add https://github.com/yerzong/TEMP-LEAGUE --skill fix-design-system-finding-yerzong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a design-system audit flags issues in Figma files, teams need a controlled way to remediate one specific finding without accidentally rewriting entire screens or drifting into unrelated cleanup. ## Core Features & Use Cases - Targeted Remediation: Accepts a single audit finding (JSON or paraphrased) and fixes only the offending node, classifying the fix as swap-instance, compose-from-primitives, bind-tokens, or align-variant. - Compatibility Gating: Runs a local compatibility check before any write, stopping with blocked or needs-human-choice when a library component cannot preserve text, icon, or sizing contracts. - Safe Writes with Backup: Duplicates only the affected node before destructive edits and validates the specific finding afterward rather than the whole screen. - Use Case: An audit reports that a button was recreated as a raw frame instead of the library Button component. Provide the finding JSON, and the skill swaps in the correct component, backs up the original, and confirms the issue is resolved. ## Quick Start Use the fix-design-system-finding skill on this audit-design-system finding and fix only that targeted issue in my Figma file.

Frequently Asked Questions about fix-design-system-finding

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

FAQPage Schema
How do I fix a design-system audit finding in Figma?▼

Provide one finding from the audit output, either as JSON or a paraphrase with a Figma URL, fileKey, and nodeId. The skill normalizes the finding, checks component compatibility, backs up the affected node, applies the smallest valid fix, and validates only that issue.

What input does a Figma finding fix require?▼

It accepts a single JSON finding from audit-design-system, the full review JSON plus the selected finding, or a paraphrased issue with a Figma URL or fileKey and nodeId. If no specific node is identified, it stops and asks for the raw finding or direct node reference.

When should I use a full design-system pass instead of fixing one finding?▼

Use a broader apply-design-system pass when multiple sections need coordinated changes, the task is a screen-wide reconnect, or you explicitly want the whole frame reviewed. The single-finding skill intentionally refuses to widen scope beyond the selected issue.

What happens if the Figma library lacks the needed component?▼

The fix is marked blocked when the library lacks the required component family, the import fails, or the replacement cannot preserve the node's text, icon, or sizing contract. It reports the blocker instead of improvising a fake connection or forcing an unsuitable swap.

Does fixing one finding change the rest of the Figma screen?▼

No. Write scope stays pinned to the offending node or smallest enclosing section, with a backup created before destructive edits. Validation confirms only that the specific complaint is resolved, and unrelated drift is left for a separate pass.