antislop-layoutmobile

Reviews responsive layouts for mobile reflow failures across breakpoints, grids, overflow, and tap targets.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-layoutmobile-daxrpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-layoutmobile
Source: https://github.com/daxrpm/epn-tracker/tree/main/.claude/skills/antislop-layoutmobile
Command: npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-layoutmobile-daxrpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mobile layouts often ship as squeezed desktop designs: columns that never collapse, horizontal overflow, undersized tap targets, and navigation that crowds or covers content. This Skill gives AI coding agents a concrete rule set and checklist to detect and fix those mobile layout failures. ## Core Features & Use Cases - Breakpoint and Scale Rules: Enforces content-driven breakpoints, fluid type with clamp(), mobile-specific spacing scales, and avoidance of 100vh traps. - Grid, Overflow, and Tap Target Checks: Detects grids that fail to collapse, horizontal scroll leaks, overflow clipping, under-sized touch targets, and hover-only interactions. - Mobile Navigation Patterns: Covers collapsing desktop nav bars, labeled hamburger menus, bottom nav safe-area handling, and compact sticky headers. - Use Case: While building a responsive landing page, load this Skill alongside the antislop core so the agent reflows the grid to a single column, sizes tap targets to 44px, and verifies zero horizontal scroll at narrow widths. ## Quick Start Load the antislop core and this layoutmobile skill, then review my page layout for mobile responsiveness and fix any reflow, overflow, or tap target issues.

Frequently Asked Questions about antislop-layoutmobile

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

FAQPage Schema
How do I make a CSS grid collapse properly on mobile?▼

Collapse multi-column grids to a single reflowing column at the breakpoint where content stops working. Size tracks with minmax() or auto-fit and auto-fill instead of fixed pixels so columns shrink and wrap with the content.

How do I fix horizontal scrolling on mobile pages?▼

Find the element wider than the viewport, such as a table, code block, or fixed-width child, then contain or reflow it. Use max-width: 100% on images, wrapping on code blocks, and verify zero horizontal scroll at the narrowest target width.

What is the minimum tap target size for mobile?▼

Interactive targets should be at least 44 x 44 px, achieved through padding or a larger hit box even when the visual is smaller. Adjacent targets also need clear spacing so a thumb tap does not hit the wrong control.

Why should breakpoints not be based on device widths like 375px?▼

Device widths change with every model, so breakpoints tied to a device list follow a spec sheet instead of the content. Place breakpoints where the layout actually breaks by narrowing the viewport and watching where columns stop being readable.

When should this skill be loaded versus the antislop core alone?▼

Load it together with the antislop core whenever the task builds or edits a layout that must hold up on a phone. The core provides the mechanism and Delivery Gate; this skill adds mobile-specific depth on reflow, overflow, and tap targets.