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
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.