spacious
bergside/awesome-design-skills
Generous whitespace and grid-based layouts for clean, readable interfaces.
What is spacious?
Spacious is a design-system skill for creating minimal, accessible interfaces using consistent padding, an 8-point grid baseline, and semantic design tokens. Use it when authoring design guidelines, component specs, and implementation-ready documentation for engineers and designers.
- Define spacing, typography, and color tokens aligned to an 8-point grid system
- Create component anatomy, states, and variants with explicit interaction behavior
- Establish accessibility requirements (WCAG 2.2 AA, keyboard-first, 44px+ touch targets)
- Document responsive behavior, empty/loading/error states, and edge cases
- Generate QA checklists and anti-patterns for design consistency
- Author content and tone standards with concrete examples
How to install spacious
npx skills add https://github.com/bergside/awesome-design-skills --skill spaciousHow to use spacious
- 1.Define your design intent in one sentence before proposing rules
- 2.Establish design tokens (spacing, typography, color) and foundational constraints
- 3.Specify component anatomy, required states (default, hover, focus, active, disabled, loading, error), and interaction behavior for keyboard, pointer, and touch
- 4.Document accessibility acceptance criteria and testable requirements
- 5.Write content and tone standards with concrete examples
- 6.List anti-patterns and prohibited implementations
- 7.Create a QA checklist for code review execution
Use cases
- Writing design-system guidelines for a new product or redesign
- Specifying component rules (buttons, forms, cards) with accessibility acceptance criteria
- Documenting migration paths from inconsistent legacy UI to a unified system
- Creating implementation-ready specs that engineers can directly code from
- Establishing accessibility and responsive behavior standards for design review
- Design system authors and leads
- Product designers writing component specifications
- Engineers implementing design systems
- Design-focused teams building accessible interfaces
- Teams standardizing spacing, typography, and interaction patterns
spacious FAQ
Spacious uses an 8-point baseline grid for all spacing decisions, ensuring consistent rhythm and alignment across components.
Spacious targets WCAG 2.2 AA with keyboard-first interactions, visible focus states, semantic HTML, screen-reader tested labels, and 44px+ touch targets.
Spacious defines a 12/14/16/18/24/30/36 scale with Open Sans (primary), Montserrat (display), and IBM Plex Mono (monospace) across weights 100–900.
Yes; Spacious requires responsive behavior by default and includes guidance for edge cases like long labels, empty states, and overflow handling.
Spacious includes primary (#3B82F6), secondary (#8B5CF6), success (#16A34A), warning (#D97706), danger (#DC2626), surface (#FFFFFF), and text (#111827) tokens.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: spacious description: Generous whitespace, consistent padding, and grid-based layouts for clean, readable, and breathing interfaces. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->Spacious Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Spacious. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Spacious UI/UX design uses generous white space, consistent padding, and a 4- or 8-point grid system to create clean, readable, and intuitive interfaces
Style Foundations
- Visual style: minimal, clean
- Typography scale: 12/14/16/18/24/30/36 | Fonts: primary=Open Sans, display=Montserrat, mono=IBM Plex Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 8pt baseline grid
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
Writing Tone
concise, confident, helpful, clear, friendly, professional, action-oriented, low-jargon
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
- document accessibility rationale
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
Related skills
More from bergside/awesome-design-skills and the wider catalog.
