antislop-layoutmobile

Reviews and fixes responsive layouts for mobile breakpoints, grids, overflow, and tap targets.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-layoutmobile-zeeforc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-layoutmobile
Source: https://github.com/zeeforc/website-lpkpaiton/tree/main/agent/skills/antislop-layoutmobile
Command: npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-layoutmobile-zeeforc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mobile layouts often fail because they are just shrunken desktop designs: columns collide, content overflows horizontally, tap targets are too small, and navigation breaks on phones. This Skill provides a structured rule set for AI coding agents to detect and fix these mobile layout anti-patterns. ## Core Features & Use Cases - Breakpoint and Scale Rules: Enforces content-driven breakpoints, fluid type with clamp(), mobile-specific sizing, and avoidance of 100vh and oversized padding pitfalls. - Grid, Overflow, and Touch Fixes: Covers collapsing multi-column grids, eliminating horizontal scroll leaks and clipped content, and ensuring 44x44 px tap targets with proper spacing and tap equivalents for hover-only interactions. - Mobile Navigation Patterns: Guides collapsing desktop nav bars into bottom navs or labeled menus, reserving space for fixed bars, and keeping sticky headers compact. - Use Case: When asked to make a landing page responsive, the agent loads this Skill alongside the antislop core and runs the Layoutmobile Skill Checklist to verify the layout reflows correctly at narrow widths. ## Quick Start Load this skill together with the antislop core and review my page layout so it reflows correctly on phone screens.

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 fitting. Use minmax() with auto-fit or auto-fill instead of fixed pixel tracks 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 image, then contain or reflow it with max-width: 100%, wrapping, or a scroll container. Verify zero horizontal scroll at the narrowest target width.

What is the minimum tap target size for mobile buttons?▼

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

Why should I avoid 100vh for mobile sections?▼

On mobile browsers, 100vh includes browser chrome, so full-height sections overflow the visible area and push content below the fold. Size sections to their content with auto, or use the dynamic viewport unit dvh when full height is intended.

How should hover-only menus work on touchscreens?▼

Touchscreens have no hover state, so every hover-only interaction needs a tap equivalent: menus open on tap, reveals trigger on click, and interactive elements show visible :active feedback. Test the UI using touch input alone.