responsiveness-check

Identify viewport widths where web page layouts break via automated resizing and screenshot comparisons.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/moughamir/justwaitit-review --skill responsiveness-check-moughamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responsiveness-check
Source: https://github.com/moughamir/justwaitit-review/tree/main/.agents/skills/responsiveness-check
Command: npx skills add https://github.com/moughamir/justwaitit-review --skill responsiveness-check-moughamir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Responsiveness-check helps teams pinpoint the specific viewport widths where a website’s layout breaks, so you can fix CSS breakpoints with concrete evidence instead of guessing.

Core Features & Use Cases

  • Viewport sweep with screenshot evidence: Resizes a single browser session across breakpoints and captures above-fold (and optional below-fold) screenshots to compare results.
  • Layout-transition detection: Flags where navigation mode changes, column/grid counts change, sidebars appear/disappear, and cards reflow—then summarizes the exact width range.
  • Actionable failure reporting: Produces a structured report that maps issues to severity (Critical/High/Medium/Low) and the exact breakpoint widths affected.

Quick Start

Use the responsiveness-check skill to test a page’s layout across breakpoints by running a standard check on your target URL.

Frequently Asked Questions about responsiveness-check

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

FAQPage Schema
How do I find exact viewport widths where my website layout breaks?

Responsive layout transition detection works by sweeping a single browser session across predefined breakpoints, capturing above-fold screenshots, and flagging exact width ranges where navigation modes change, columns reflow, or sidebars disappear.

What's the best way to automate responsive QA for frontend layout transitions?

The best way to automate responsive QA for frontend layout transitions is to perform adjacent-width transition analysis with screenshot comparisons, generating a breakpoint-scoped report that maps layout failures to severity levels for deterministic debugging.

Can I test touch-target sizing and above-the-fold CTA visibility across breakpoints?

Yes, you can test touch-target sizing and above-the-fold CTA visibility by running a viewport sweep that captures screenshots across breakpoints and flags layout issues like media scaling problems, whitespace imbalance, and hidden CTAs in a structured report.

Do I need any browser automation dependencies to run a viewport testing sweep?

No browser automation dependencies are required to run a viewport testing sweep, as the responsiveness check operates within a single-session workflow using predefined breakpoints to perform automated resizing and screenshot comparisons.

Why does my responsive layout break between adjacent viewport widths without an obvious CSS breakpoint?

Your responsive layout may break between adjacent viewport widths due to column reflow, overflow, or media scaling issues that occur within transition ranges, requiring adjacent-width transition analysis to pinpoint the exact failure width.