better-layout

Reviews and structures web interface layouts using grouping, alignment, and adaptive breakpoint principles.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/zomeru/zomlab --skill better-layout-zomeru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-layout
Source: https://github.com/zomeru/zomlab/tree/main/.agents/skills/better-layout
Command: npx skills add https://github.com/zomeru/zomlab --skill better-layout-zomeru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web interfaces often suffer from cluttered grouping, misaligned edges, controls that blend into content, and layouts that break under resizing, translation, or RTL mirroring. This Skill provides concrete layout principles and a structured review format to catch and fix these structural problems in frontend code. ## Core Features & Use Cases - Layout Principles: Ten core rules covering grouping with negative space, shared alignment edges, logical CSS properties for RTL, importance-based ordering, progressive disclosure affordances, safe-area handling, and content-driven breakpoints. - Structured Layout Reviews: Produces findings tables with severity levels (HIGH/MEDIUM/LOW), file-and-line locations, before/after fixes, verification steps, and a Block/Needs changes/Approve verdict. - Use Case: When building a settings page in React with Tailwind, apply the grouping rules to replace separator lines with 2x inter-group spacing, switch margin-left to margin-inline-start for RTL support, and verify controls stay inside layout margins at small viewports. ## Quick Start Review the layout of my dashboard component and report any grouping, alignment, or responsiveness issues with suggested fixes.

Frequently Asked Questions about better-layout

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

FAQPage Schema
How do I structure a web page layout with good visual hierarchy?▼

Group related items with negative space instead of separator lines, keeping inter-group gaps at least twice intra-group gaps. Place the most important content near the top and leading edge, and align elements to a small set of shared edges.

How to make CSS layouts work with RTL languages?▼

Use logical CSS properties like margin-inline-start and padding-inline-end instead of physical left/right properties so layouts mirror automatically under dir="rtl". In Tailwind, use ms-, pe-, and text-start utilities instead of ml-, pr-, and text-left.

When should I use container queries instead of media queries?▼

Use container queries when a component should adapt to the column or panel it sits in rather than the viewport, such as a card inside a narrow sidebar. Viewport media queries break components reused in different-width containers.

Why does my layout break when translated into other languages?▼

Fixed widths and heights sized to English labels overflow or truncate when strings expand in other languages. Use max-width with wrapping, min-height instead of fixed height, and let buttons size from their label padding, then test with pseudo-localization.

How much spacing should there be between buttons and controls?▼

Without an established density system, start with 12px between adjacent bordered or filled controls and 24px of clearance around borderless text or icon buttons. Unrelated control groups need 24px or more, at least twice the intra-group gap.