Figma Spacing System

Design a spacing and layout token system for a Figma design system. Use when asked to create a spacing system, define layout tokens, set up a grid system, build a spacing scale, or establish layout foundations for a Figma file. Produces a complete spacing scale, grid definition, component spacing conventions, and Figma implementation guide.

Published by @Mohit Aggarwal·from mohitagw15856/pm-claude-skills·0 agent reads / 30d·0 saves·

Figma Spacing System Skill

Produces a complete spacing and layout token system — the foundation that makes a design system consistent and developer handoff unambiguous.

Required Inputs

  • Platform (iOS / Android / Web / Multi-platform)
  • Base unit (4px / 8px — default to 8px)
  • Design system name (for token naming)
  • Component density (compact / standard / comfortable)
  • Grid requirements (or "derive from platform standard")

Output Structure

1. Base Unit

[4px or 8px] with rationale. All values must be multiples.

2. Spacing Scale

TokenValueUse case
spacing.none0pxRemoving space intentionally
spacing.xs4/8pxIcon padding, tight labels
spacing.sm8/12pxInternal component padding compact
spacing.md12/16pxInternal component padding standard
spacing.lg16/24pxSection padding, card internal
spacing.xl24/32pxBetween components
spacing.2xl32/48pxSection separation
spacing.3xl48/64pxPage-level breaks
spacing.4xl64/96pxHero sections

3. Layout Grid

Mobile (375px): 4 columns, margin [value], gutter [value] Tablet (768px): 8 columns, margin [value], gutter [value] Desktop (1440px): 12 columns, margin [value], gutter [value], max content width [value]

4. Component Spacing Conventions

ContextTokenExample
Button horizontal paddingspacing.mdLeft/right
Button vertical paddingspacing.smTop/bottom
Card internal paddingspacing.lgAll sides
Input paddingspacing.sm vertical, spacing.md horizontal
Icon gap from labelspacing.xs
Section gapspacing.xl

5. Figma Implementation

  1. Create SPACING page documenting each token visually
  2. Resources > Variables > create Number collection named Spacing
  3. Apply variables to Auto Layout padding/gap values
  4. Share token names with engineers as-is or via Tokens Studio

6. Anti-Patterns to Avoid

  • Values not on the scale (13px, 22px) — round to nearest token
  • Absolute pixel values in components instead of tokens
  • Mixing 4px and 8px base units in the same product

Quality Checks

  • All token values are multiples of the base unit
  • Scale covers xs through 4xl
  • Grid defined for all relevant breakpoints
  • Component conventions cover common decisions
  • Figma implementation steps included

Anti-Patterns

  • Do not create a spacing scale with arbitrary values — the scale must follow a consistent mathematical ratio (e.g. 4px base, 8-4-2 system)
  • Do not define spacing tokens without Figma implementation instructions — token names alone are not actionable
  • Do not create a spacing system that doesn't account for component-level spacing conventions — global tokens and component usage must both be documented
  • Do not skip grid definitions — spacing without a grid system is incomplete layout foundation documentation
  • Do not produce a spacing system that ignores responsive behaviour — define how spacing adapts across breakpoints

Example Trigger Phrases

  • "Create a spacing system for our Figma design system"
  • "Define our spacing tokens for Figma"
  • "Set up a grid and spacing scale for [product]"
  • "What spacing values should we use in our design system?"
  • "Help me build the layout foundation for our Figma file"

Bundled with this artifact

1 file

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Fixing Metadata

Audit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags.

ux-product-design+1
29
SKILL0

Pptx Slide Auditor

Audit a PowerPoint presentation for layout issues, text overflow, visual hierarchy problems, and consistency gaps. Use when asked to review a slide deck, check a presentation before a meeting, audit slides for layout problems, or QA a deck before sharing. Produces a slide-by-slide report with issues ranked by severity and specific fixes. Best used with Claude Opus 4.7 or newer for reliable slide-level vision analysis.

product-management+1
3
SKILL0

Design Critique

Gives structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Applies Jobs-to-be-Done, Gestalt principles, and usability heuristics to give actionable feedback with prioritised issues and specific recommendations.

ux-product-design+1
2