antislop-layoutmobile

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mobile layouts often fail because they are desktop designs squeezed into a narrow viewport: grids that never collapse, horizontal overflow, oversized type, and tap targets too small for thumbs. This Skill gives an AI coding agent a structured rule set to detect and fix those mobile layout failures. ## Core Features & Use Cases - Breakpoint and Scale Rules: Enforces content-driven breakpoints, fluid type with clamp(), and mobile-specific sizing instead of fixed pixel values carried over from desktop. - Grid, Overflow, and Tap Target Checks: Covers collapsing multi-column grids, eliminating horizontal scroll leaks, and enforcing 44x44 px minimum touch targets with adequate spacing. - Mobile Navigation Patterns: Guides reflowing desktop nav bars into bottom navs or labeled menus, with safe-area and sticky-header handling. - Use Case: When asked to make a landing page responsive, the agent applies the Tell/Why/Fix patterns and runs the Layoutmobile Skill Checklist to verify the layout holds at narrow widths. ## Quick Start Load this skill together with the antislop core and ask the agent to review and fix the responsive layout of your page for mobile viewports.

Frequently Asked Questions about antislop-layoutmobile

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

FAQPage Schema
How do I fix a grid that overflows on mobile screens?▼

Collapse multi-column grids to a single column at the breakpoint where content stops fitting. Size tracks with minmax() or auto-fit/auto-fill instead of fixed pixels, and verify there is no 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 through padding or a larger hit box even when the visual element is smaller. Adjacent targets also need clear spacing so a thumb tap does not hit the wrong control.

Why does 100vh cause layout problems on mobile browsers?▼

The 100vh unit includes mobile browser chrome, so full-height sections overflow the visible area and push content below the fold. Use auto sizing or the dynamic viewport unit dvh where a full-height section is genuinely intended.

How should breakpoints be chosen for responsive design?▼

Place breakpoints where the content actually breaks, not at specific device widths like 375px or 768px. Narrow the viewport, watch where columns become unreadable or rows get too tight, and set the breakpoint there.

Does this skill work without the antislop core file?▼

No, it is designed to load together with antislop.md, which holds the core mechanism and numbered rules. This skill references those rules by number and adds mobile-layout depth without duplicating them.