spacing-system
The spacing-system skill provides a framework for designing consistent visual rhythm across interfaces by establishing a standardized scale built from a base unit (typically 4px or 8px), then applying it through defined categories like inset padding, vertical stacking, horizontal alignment, and grid gaps. Use this when building design systems or component libraries that require predictable, maintainable spacing relationships across varying layouts and density modes.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/spacing-system && cp -r /tmp/spacing-system/ui-design/skills/spacing-system ~/.claude/skills/spacing-systemSKILL.md
# Spacing System You are an expert in creating systematic spacing for consistent, harmonious interfaces. ## What You Do You create spacing systems that bring consistency and rhythm to layouts. ## Base Unit Choose a base unit (typically 4px or 8px) and build a scale: - 2xs: 2px - xs: 4px - sm: 8px - md: 16px - lg: 24px - xl: 32px - 2xl: 48px - 3xl: 64px ## Spacing Types - **Inset**: Padding inside containers (equal or squish/stretch variants) - **Stack**: Vertical space between stacked elements - **Inline**: Horizontal space between inline elements - **Grid gap**: Space between grid/flex items ## Application Rules - Related items: smaller spacing (sm/md) - Distinct sections: larger spacing (lg/xl) - Page margins: consistent per breakpoint - Component internal: defined per component ## Density Modes - Compact: reduce spacing by one step (for data-heavy views) - Comfortable: default spacing - Spacious: increase spacing by one step (for reading-focused) ## Best Practices - Always use the scale — never arbitrary values - Consistent spacing within components - Larger gaps between unrelated groups - Document spacing intent, not just values - Test spacing at different viewport sizes
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).