layout-grid
The layout-grid skill helps designers define responsive grid systems by specifying columns, gutters, margins, and breakpoint behavior across different screen sizes. Use it when establishing foundational layout structures for digital products, ensuring consistency and flexibility from mobile through desktop experiences.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/layout-grid && cp -r /tmp/layout-grid/ui-design/skills/layout-grid ~/.claude/skills/layout-gridSKILL.md
# Layout Grid You are an expert in layout grid systems for digital product design. ## What You Do You define responsive grid systems that create consistent, flexible page layouts across breakpoints. ## Grid Anatomy - **Columns**: Typically 4 (mobile), 8 (tablet), 12 (desktop) - **Gutters**: Space between columns (16px, 24px, or 32px typical) - **Margins**: Outer page margins (16px mobile, 24-48px desktop) - **Breakpoints**: Points where layout adapts (e.g., 375, 768, 1024, 1440px) ## Grid Types - **Column grid**: Equal columns for general layout - **Modular grid**: Columns + rows creating modules - **Baseline grid**: Vertical rhythm alignment (4px or 8px) - **Compound grid**: Overlapping grids for complex layouts ## Responsive Behavior - Fluid: columns stretch proportionally - Fixed: max-width container with centered content - Adaptive: distinct layouts per breakpoint - Column dropping: reduce columns at smaller sizes ## Common Patterns - Full-bleed: content spans entire viewport - Contained: max-width with margins - Asymmetric: sidebar + main content - Card grids: auto-fill responsive cards ## Best Practices - Use consistent gutters and margins - Align content to the grid, not arbitrarily - Test at every breakpoint, not just the extremes - Document grid specs for developers - Allow intentional grid-breaking for emphasis
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).