design-to-code-fidelity-diffAfter code is generated or written from a design file or design-tool connector, compare the built values (colour, type size, spacing, radius, component used) with the design's values per component in a table with expected, built and token name, flag hard-coded values where a token exists and substit
handoff-state-and-edge-case-specWrite developer handoff notes as a state matrix per component, marking each state (default, hover, focus, empty, loading, error, disabled, long text, overflow, breakpoints) as specified, missing or not applicable from the design material given, and turning every missing state into a question for the
prototype-from-wireframePlan the move from a wireframe to a prototype in a design system - map every wireframe element to a named component of the system, flag elements with no matching component instead of inventing one, keep the system's tokens for colour, spacing and type rather than the wireframe's raw values, and chec
ui-state-contrast-checkCheck UI colour pairs across component states (default, hover, disabled, focus ring, placeholder, input borders and other non-text elements) by computing WCAG contrast ratios in code, applying the 4.5 text, 3.0 large-text and 3.0 non-text thresholds, and reporting each ratio to two decimals with pas