frontend-ui-engineering

Use design-to-code fidelity checks by preserving design tokens, interaction patterns, and semantic structure when bridging design specifications to component libraries. This ensures accessibility, focus behavior, and responsive design are maintained during implementation.

Anti-slop reporting is an evidence-driven verification process that requires artifact-bound proof and gate-specific blockers before approving UI readiness. It uses a fail-closed approach to prevent incomplete or drifting visual surfaces from landing in production code.

To implement accessible and responsive design after prototype handoff, enumerate all UI states, consume capability-contracts for advanced runtimes, and verify browser runtime behavior. This ensures the final code matches the approved design across all conditions.

Yes, an approved design handoff is required. This skill applies to engineering real screens, flows, forms, dashboards, and extension or mobile UI after the prototype design is approved, ensuring implementation starts from a finalized specification.

Verify browser runtime behavior by consuming capability-contracts and generating fail-closed, artifact-bound evidence. This approach enforces gate-taxonomy-specific blockers, ensuring advanced visual surfaces meet strict accessibility and state-matrix requirements before completion.