About spacing-system
A spacing-system skill for interface design. It uses a base unit and scale to establish consistent layout rhythm, with guidance for component spacing, application rules, and density modes.
Key features
- 01Choose a base unit and build a spacing scale
- 02Define inset, stack, and inline spacing
- 03Set grid item gaps
- 04Establish spacing application rules
- 05Plan compact, comfortable, and spacious modes
Use cases
- 01Standardize spacing within components and page sections
- 02Set compact spacing for data-heavy views
- 03Adjust density for reading-focused interfaces
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ owl-listener/ designer-skills --skill spacing-systemAfter installing, type/spacing-systemin Claude Code to confirm it loaded.
Details
From the project READMESpacing 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
Comments
Markdown supported