qa-detect-layout

Detect responsive layout defects across viewports and browser sizes.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-detect-layout
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-layout
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps detect responsive layout defects that make pages hard to use on mobile and desktop, such as clipped content, hidden actions, and broken grid or flex behavior.

Core Features & Use Cases

  • Overflow and cutoff checks: Finds fixed or sticky elements extending beyond the viewport, dropdowns that get cut off, and tables that overflow without a scroll wrapper.
  • Usability and visibility checks: Flags content that is too narrow, primary CTAs below the fold, critical buttons hidden or covered, and sticky headers or footers blocking interactions.
  • Responsive structure checks: Detects whitespace-heavy sections, inertness issues behind open dialogs, element collisions, and grids or flex layouts that fail to collapse on smaller screens.
  • Use Case: Run it against a product page before release to catch a mobile-only CTA overlap caused by a sticky footer and a two-column grid that no longer fits the viewport.

Quick Start

Ask the qa-detect-layout skill to inspect the current page for responsive layout defects across the active viewport and report any overflow, cutoff, overlap, or hidden-action issues.

Frequently Asked Questions about qa-detect-layout

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

FAQPage Schema
How do I detect responsive layout defects across different browser viewports?

To detect responsive layout defects, you need to verify viewport fit, scroll safety, and overlap collisions across mobile, tablet, laptop, and desktop states. This process checks sticky headers, grids, and interactive controls to find clipped content.

What causes UI overlap and viewport overflow on mobile screens?

UI overlap and viewport overflow on mobile screens are typically caused by fixed elements extending beyond the viewport, sticky footers blocking interactions, or two-column grids that fail to collapse. Checking element visibility and CSS flex behavior isolates these layout failures.

How do I check if a sticky header is blocking content or hiding primary CTAs?

Checking if a sticky header blocks content involves running usability and visibility checks to flag critical buttons that are hidden or covered. It verifies whether primary CTAs fall below the fold and if fixed elements obstruct user interactions.

Can I test CSS grid collapse behavior for tables and dialogs on multiple device sizes?

You can test CSS grid collapse behavior by verifying responsive structure checks across mobile, tablet, laptop, and desktop states. This detects whitespace-heavy sections, inertness behind open dialogs, and grids that fail to collapse on smaller screens.

What is the best way to find dropdown menus and tables that get cut off without a scroll wrapper?

The best way to find cut-off dropdowns and overflowing tables is to perform overflow and cutoff checks. This identifies fixed elements extending beyond the viewport and tables that overflow without a scroll wrapper, ensuring scroll safety.

Does responsive testing work for forms and interactive controls on both mobile and desktop?

Responsive testing works for forms and interactive controls by verifying action visibility and overlap collisions across mobile, tablet, laptop, and desktop states. It ensures that critical buttons remain visible and usable regardless of browser size.