Verification
Check the implementation and report evidence honestly.
Before shipping
- Inspect actual desktop and small-mobile renders in each supported theme.
- Check normal text at 4.5:1, large text at 3:1 and applicable essential UI contrast at 3:1. Do not use color as the only signal.
- Test keyboard order, visible focus, accessible names, touch targets, reduced motion, zoom and long content.
- Exercise loading, empty, failure and success paths. Confirm persistence before showing a saved state.
- Check links, images, fonts, console errors, layout shifts and production build output. Measure performance under recorded conditions.
Evaluating the skill
Use fixed briefs for a data-heavy dashboard, expressive landing and portfolio. Keep model, content, assets and iteration budgets comparable. Record all meaningful revisions and failures.
Evaluate task clarity, composition, product fit, distinctness, responsiveness, accessibility, states and implementation quality. A few examples cannot establish universal quality.
Current evidence limits
The landing’s handcrafted examples explain the workflow. They are not controlled model outputs or measured improvement claims.
The full three-brief controlled comparison remains unperformed. Local build and interaction checks are recorded in the repository review notes. Physical-device testing and a complete assistive-technology audit remain separate checks.