ds-qa-coverage

To run a Figma design system QA pass, validate screen inventory and state coverage by executing a final audit that verifies all screens exist, states are defined, and navigation integrity is maintained across the ecosystem.

Design token binding validation in a Figma design system detects unbound fills, unlinked text styles, and spacing inconsistencies to enforce strict design-token discipline and maintain visual governance across all components.

Yes, you can validate Figma prototype connections and component hygiene by running an auditing process that checks component usage consistency and verifies prototype connections to guarantee DS library conformity.

Yes, loading the figma-use skill is required before any use_figma calls to ensure all screens and prototype flows are completed and accessible for the final QA coverage validation.

The best way to ensure design system conventions are followed is to perform a structured QA pass that validates screen inventory, token bindings, and DS component usage consistency before production.

Unbound fills during a Figma quality audit indicate that components have colors applied directly instead of through linked design tokens, which breaks token binding discipline and requires re-linking to the DS styles.