preview-verify

Verify visual changes to a web app by rendering them in a local browser preview.

Updated May 6, 2026
One-click install
npx skills add https://github.com/BanePlayss/primitivao --skill preview-verify-baneplayss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preview-verify
Source: https://github.com/BanePlayss/primitivao/tree/main/.opencode/skills/preview-verify
Command: npx skills add https://github.com/BanePlayss/primitivao --skill preview-verify-baneplayss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Visual changes to a web app (layouts, colors, icons, new components) are often edited blind and shipped without confirmation that they actually render correctly. This Skill encodes a working local preview loop so you can inspect the rendered result before shipping. ## Core Features & Use Cases - Local Preview Server Setup: Configure a static server via launch.json to serve the app and start a named preview session. - Login and Navigation Automation: Log in with admin credentials, persist sessions via localStorage, and click navigation elements by text using synchronous eval. - Layout Verification Without Screenshots: Work around screenshot timeouts by using computed styles, bounding boxes, and synchronous eval to detect overflow, overlap, alignment, and color issues. - Use Case: After changing a tabloid layout component, rebuild the bundle, bump the cache-busting query param, then measure real element bounding boxes against the container to confirm nothing overflows before shipping. ## Quick Start Ask the assistant to start the local preview, log in as admin, and verify that the new layout change renders correctly without overflow.

Frequently Asked Questions about preview-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a visual change to a web app before shipping?▼

Serve the app locally with a static server, rebuild the bundle first, then load the page in a browser preview and inspect the rendered result. Use computed styles and bounding boxes to confirm layout, colors, and alignment are correct.

How to check for layout overflow without taking a screenshot?▼

Use getBoundingClientRect() on child elements and compare them against the container's rect to detect overflow or overlap. Reading computed styles via synchronous eval also reveals font sizes, colors, and positions reliably.

Why does the browser preview show old code after my change?▼

The browser caches compiled.js and styles.css by their version query parameter. Rebuild the bundle, bump the ?v= parameter, and navigate with a cache-busting query like ?cb= plus a timestamp to see the new code.

What can I do when preview screenshots always time out?▼

Rely on DOM inspection instead of images: read computed styles, bounding boxes, element counts, classes, and rendered text via synchronous eval. This covers most layout problems like overflow, overlap, and misalignment.

Does the login session persist across page reloads in the preview?▼

Yes, the session persists in localStorage, so reloading the page keeps you logged in. You only need to fill the login form and submit once per browser profile.