Reference-Based UI Implementation Verification
Translate a supplied screenshot or design into a responsive implementation and verify matching layout, typography, spacing, assets and interaction at representative viewports.
Identify the reference's frame size, crop, browser chrome, scale and content state where available. Record what can be measured directly and what must be inferred. A screenshot can establish visible spacing and hierarchy, but it rarely establishes fonts, breakpoints, focus behavior or interaction. Use the project’s existing design assets and token definitions when present. Verify whether reproduction or adaptation is requested before changing visual identity. ## Key Points - [Playwright visual comparisons and environment consistency](https://playwright.dev/docs/test-snapshots) - [W3C reflow guidance](https://www.w3.org/WAI/WCAG21/Understanding/reflow) - [HTML semantic content structure](https://html.spec.whatwg.org/multipage/grouping-content.html)
skilldb get web-polish-skills/reference-design-implementationFull skill: 29 linesReference-Based UI Implementation Verification
Identify the reference's frame size, crop, browser chrome, scale and content state where available. Record what can be measured directly and what must be inferred. A screenshot can establish visible spacing and hierarchy, but it rarely establishes fonts, breakpoints, focus behavior or interaction. Use the project’s existing design assets and token definitions when present. Verify whether reproduction or adaptation is requested before changing visual identity.
Reconstruct the layout from measurable relationships
Measure the content bounds, alignment anchors, repeated spacing and proportions, typography hierarchy and image crop. Use shared relationships instead of absolutely positioning every element from one view. Recreate the closest supported font metrics and colors from approved assets. If a screenshot has a font or image that cannot be identified reliably, document the substitute and compare the resulting visible hierarchy. Avoid pretending an estimated measurement is a source value.
Define what should stay fixed and what may reflow at narrow and wide widths. Keep semantic order and user actions intact when a visual column collapses. Implement representative data and real loading, empty and error states when they materially affect the design. A still image does not authorize inventing new controls or claiming they are implemented.
Compare rendered evidence
Capture the implementation at the exact reference dimensions and important responsive sizes using stable data, fonts and animations. Control browser, OS and device scale when comparing pixel output. Use side-by-side views or an overlay to classify differences in layout geometry, text wrap, media crop and paint. Screenshot comparisons should be environment-matched and targeted. An intentionally responsive variation belongs in the design record, and a mismatched asset or clipped action is a defect.
Verify representative interactions independently, including keyboard focus, link/button behavior, mobile scroll and changed content. Inspect multiple viewport sizes and record any unsupported size or asset. For acceptance, report what matched, where the implementation deliberately adapts and which reference details were unavailable. Keep reference screenshots and comparison artifacts linked to their tested build.
References and rights
- Playwright visual comparisons and environment consistency
- W3C reflow guidance
- HTML semantic content structure
Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.
Install this skill directly: skilldb add web-polish-skills
Related Skills
Responsive Repair
Fix broken responsive layouts in a vibecoded website — content overflowing on mobile, misaligned grids, missing breakpoint handling, touch targets that are too small, and navigation that doesn't adapt. Trigger when things "break on mobile," "look bad on tablet," or "don't resize properly."
Build a Restaurant Website Customers Can Use
Build a mobile restaurant homepage with accessible menu, accurate hours and locations, and trustworthy booking or takeaway actions. Use when launching or repairing a local restaurant site.
Typography Cleanup
Fix font chaos in a vibecoded website — too many font sizes, inconsistent weights, broken heading hierarchy, mismatched line heights, and mixed font families. Establish a clean type scale and apply it everywhere. Trigger when fonts "look off," headings are inconsistent, or there are too many text sizes.
UI Audit
Audit a vibecoded or inconsistent website for visual and structural problems — mismatched components, font chaos, color drift, spacing irregularities, broken states, and missing interactions. Produces a prioritized fix list. Trigger when users say "this looks off," "make it consistent," "audit the UI," "fix the design," or "polish this site."
Vibecode Upgrade
The comprehensive playbook for upgrading a vibecoded website from "it works" to "it feels premium." Combines all other web-polish skills into a prioritized workflow — audit, extract tokens, unify components, fix responsiveness, add polish. Trigger when users want to "upgrade the whole site," "make it look professional," "polish everything," or "it was vibecoded and needs to be cleaned up."
Visual Polish
Apply the final layer of visual polish to a website — hover states, transitions, micro- interactions, loading states, empty states, scroll behavior, and the small details that make a site feel premium. Trigger when a site "works but feels cheap," needs "polish," or the user says "make it feel premium/professional/finished."