back
loading skill details...
Layout structure for web interfaces. Use when structuring a page or component, deciding what collapses at small sizes, or reviewing frontend code for layout.…
Layout Position, spacing and alignment carry hierarchy before a word is read. This skill builds that structure and stress-tests it: resize it, translate it, mirror it for RTL. Write every fix in the project's styling system. The numbers below are starting points for interfaces with no established density system, and where one applies, use it as written rather than a familiar-looking substitute. Keep deliberate platform chrome, compact professional tools and project tokens where they still pass the stress tests. Hit areas and focus behavior belong to better-accessibility. Radius, shadows and animation belong to better-ui. Line length and text spacing belong to better-typography. Group with space, not lines Space groups first, background shapes second, separator lines last and only where space alone can't carry the structure. The gap between groups must be at least 2× the gap within one (8px intra-group to 16px+ inter-group), or the grouping reads as noise. Alignment edges and importance ordering are in grouping-and-alignment.md. Keep controls distinct from content Give every interactive element a background shape, a border, or a consistent placement zone. A control styled like the static text beside it does not read as a control. Align to shared edges Pick alignment edges and stick to them; every stray edge reads as noise. Use one project spacing step per level of subordination, where 16px is a useful default.
don't have the plugin yet? install it then click "run inline in claude" again.