browser-verification-measure

Verifies layout conclusions with computed-style measurements and scripted browser probes.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill browser-verification-measure-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-verification-measure
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/browser-verification-measure
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill browser-verification-measure-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Visual checks and code searches cannot confirm whether a layout actually renders correctly — browser defaults, inherited styles, and transient loading states are invisible to both. This Skill replaces "looks fine" with measured evidence from the live page. ## Core Features & Use Cases - Computed-value audits: Break down getComputedStyle results across every node to find defects like wrong typefaces that no code search can catch. - Multi-width batch measurement: Run all responsive breakpoints at once inside hidden iframes and compare heights, horizontal scroll, and escaped elements in a single pass. - Waiting-state capture: Substitute and delay fetch responses so loading spinners and skeletons can actually be measured before the request resolves. - Use Case: After editing a responsive form, you batch-measure it at 360–1440px widths, confirm equal row heights and no horizontal overflow, and verify the submit button's loading state by holding its request for five seconds. ## Quick Start Verify the responsive layout of the current page by measuring row heights and overflow across all breakpoints in one batched iframe pass.

Frequently Asked Questions about browser-verification-measure

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

FAQPage Schema
How do I verify a responsive layout at multiple breakpoints at once?

Create one hidden iframe per width, wait for all to load, then measure getBoundingClientRect heights, horizontal scroll, and escaped elements in a single pass. Measuring widths in separate calls gives numbers from different page states that cannot be compared.

How to test a loading spinner that disappears too fast?

Substitute window.fetch for the target URL and return a promise that resolves with an error response after a few seconds of delay. This holds the waiting state long enough to measure, and ending with a refusal avoids writing real records to the stand.

Why does resize_window not change innerWidth in Chrome?

resize_window fails silently when Chrome is in full-screen mode: the tool reports success but innerWidth and media queries stay desktop. Check narrow widths inside a nested iframe of the needed width, where matchMedia counts from the frame.

Why do computer-tool clicks miss the element I see on the screenshot?

Click coordinates are screenshot pixels, not CSS pixels: at a 2560 viewport the screenshot may arrive 1568 wide, so the seen coordinate lands elsewhere. Recompute by the actual scale or target elements through find instead.

Can I simulate scrolling by setting scrollTop directly?

No. Assigning the scroll value fires no event, so subscribers on document, window, or root never run and event-driven state stays stale. Test mechanics with a real wheel event, and test layout under the resulting state by setting the class by hand.