spatial-rhythm
Skill5 starsChanged 8 months agoMITView on GitHub
Density, whitespace, rhythm, and how space communicates relationships between elements. Use when building layouts, evaluating spacing consistency, or diagnosing why a design feels cramped or empty.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
MUST use a consistent spacing scale (4, 8, 16, 24, 32, 48, 64 or similar)
- Distinctive: line 18
MUST use proximity to signal relationships: related things close, unrelated things far
- Distinctive: line 19
MUST ensure outer margins create breathing room proportional to the content
- Distinctive: line 20
NEVER use arbitrary spacing values.
- Distinctive: line 23
MUST match density to use case: data tools can be dense, consumer products should breathe
- Distinctive: line 26
NEVER apply one density philosophy everywhere.
- Distinctive: line 31
MUST ensure rhythm matches content energy.
- Distinctive: line 35
MUST ensure whitespace accounts for 40-60% of total layout area in most well-designed products
- Distinctive: line 36
NEVER treat whitespace as wasted space.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spatial Rhythm
Space is not what's left over. It's active design material.
How to use
/spatial-rhythmApply spatial design constraints to this conversation.
Constraints
Spacing System
- MUST use a consistent spacing scale (4, 8, 16, 24, 32, 48, 64 or similar)
- MUST use proximity to signal relationships: related things close, unrelated things far
- MUST ensure outer margins create breathing room proportional to the content
- NEVER use arbitrary spacing values. If it's not on the scale, it shouldn't exist.
Density Rules
- MUST match density to use case: data tools can be dense, consumer products should breathe
- High density works when: users compare data, speed matters, users are experienced, long sessions
- Low density works when: content is consumed (not scanned), users are new, focus matters
- NEVER apply one density philosophy everywhere. Settings and marketing pages should feel different.
Rhythm
- Regular rhythm (even spacing, consistent sizes) feels orderly. Good for data, tables, lists.
- Syncopated rhythm (mostly regular with intentional breaks) feels dynamic. Good for editorial, marketing.
- MUST ensure rhythm matches content energy. A to-do app with irregular rhythm is confusing.
Whitespace
- Generous margins signal confidence ("we trust this content to speak for itself")
- MUST ensure whitespace accounts for 40-60% of total layout area in most well-designed products
- NEVER treat whitespace as wasted space. It separates, groups, emphasizes, and breathes.
Anti-Patterns
- Spacing values that almost match but don't (15px next to 16px)
- Cramming content to "use the space" instead of letting the content breathe
- Identical spacing between all elements regardless of their relationship
In this repository38 other files it gives its agents.
- absence-auditSkill
- decision-tracingSkill
- system-deconstructionSkill
- version-archaeologySkill
- audience-translationSkill
- critique-vocabularySkill
- design-rationaleSkill
- written-critiqueSkill
- field-notesSkill
- learning-by-makingSkill
- quality-checklistSkill
- self-assessmentSkill
- flow-patternsSkill
- motion-designSkill
- timing-feedbackSkill
- constraint-evaluationSkill
- design-rankingSkill
- taste-as-strategySkill
- taste-gapSkill
- taste-vs-trendsSkill
- tradeoff-assessmentSkill
- consumption-disciplineSkill
- cross-domain-seeingSkill
- detail-observationSkill
- screenshot-surgerySkill
- visual-auditSkill
- cross-pollinationSkill
- library-architectureSkill
- principle-taggingSkill
- daily-routinesSkill
- design-critiqueSkill
- teaching-tasteSkill
- type-as-signalSkill
- type-selectionSkill
- type-systemsSkill
- color-systemsSkill
- craft-signalsSkill
- hierarchy-principlesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

