spacing-system

Standardize interface layout gaps using a tokenized 4px-base scale.

3|3|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KyaniteLabs/tastecheck --skill spacing-system-kyanitelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spacing-system
Source: https://github.com/KyaniteLabs/tastecheck/tree/main/skills/spacing-system
Command: npx skills add https://github.com/KyaniteLabs/tastecheck --skill spacing-system-kyanitelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill eliminates arbitrary, inconsistent spacing and layout slop by enforcing a unified, tokenized 4px-base scale that ensures visual coherence across interfaces.

Core Features & Use Cases

  • Semantic Tokenization: Maps layout gaps to specific roles like attachment, control, task, group, region, and chapter.
  • Evidence-Based Auditing: Provides a structured framework to identify and remediate off-scale values, ensuring every margin and padding choice is intentional.
  • Use Case: Use this skill when a design system audit reveals inconsistent gaps or when a developer needs to transition from hardcoded pixel values to a scalable, responsive spacing system.

Quick Start

Use the spacing-system skill to audit the current layout and generate a tokenized spacing scale with an evidence table.

Frequently Asked Questions about spacing-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit inconsistent CSS spacing values in a design system?

To audit inconsistent CSS spacing values, this skill provides an evidence-based framework that identifies off-scale margins and padding, mapping them to a standardized tokenized 4px-base scale for visual coherence.

What is a tokenized 4px-base scale for layout spacing?

A tokenized 4px-base scale for layout spacing is a standardized system that eliminates arbitrary gaps by enforcing a unified rhythm, mapping values to semantic roles like attachment, control, task, group, region, and chapter.

How do I transition hardcoded CSS pixels to semantic spacing tokens?

To transition hardcoded CSS pixels to semantic spacing tokens, use this skill to remediate off-scale values and generate an evidence table mapping layout primitives to specific semantic roles.

Can I establish a content-derived spacing hierarchy without external dependencies?

Yes, you can establish a content-derived spacing hierarchy without external dependencies, as this skill operates independently to deliver standardized layout primitives and gap consistency through its internal tokenized scale.

What is the best way to standardize layout rhythm for frontend refactoring?

The best way to standardize layout rhythm for frontend refactoring is enforcing a unified 4px-base scale with semantic tokenization, ensuring every margin and padding choice is intentional and evidence-backed.

When should I not use a 4px-base spacing system for my layout?

You should not use a 4px-base spacing system when your interface requires highly custom, non-standard spacing rhythms that cannot conform to a unified scale, as this skill enforces strict remediation of off-scale values.