layout-and-spacing
Skill0 starsChanged 3 months agoMITView on GitHub
Create coherent interface layouts and spacing systems that preserve relationships across screen sizes.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessible-interfaceSkill
- color-and-contrastSkill
- design-contextSkill
- design-system-auditSkill
- forms-and-validationSkill
- interaction-and-motionSkill
- interface-critiqueSkill
- loading-empty-error-statesSkill
- responsive-designSkill
- typographySkill
- visual-hierarchySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 9
Use this for page structure, grids, component composition, density, or inconsistent spacing across viewports.
- Distinctive: line 12
Do not force every surface onto one grid.
- Distinctive: line 28
Test narrow and wide widths, zoom, long content, missing content, nested components, focus rings, touch targets, and dynamic state changes.
- Distinctive: line 30
Check that source order remains logical and that visual rearrangement does not break reading or keyboard order.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Layout and Spacing
Clarify relationships through containment, alignment, proportion, and space. Use this for page structure, grids, component composition, density, or inconsistent spacing across viewports.
Do not force every surface onto one grid. Do not use fixed coordinates for content that must reflow, and do not add containers where spacing alone communicates the relationship.
Workflow
- Map content relationships and interaction order before selecting columns or breakpoints.
- Identify the true containing blocks, alignment anchors, repeated gaps, and regions that need independent scrolling or sticky behavior.
- Reuse existing spacing and layout tokens where they express the intended relationships. Consolidate near-duplicates instead of adding arbitrary gaps.
- Design from intrinsic content outward. Prefer fluid sizing, min/max constraints, wrapping, and layout primitives over viewport-specific patches.
- Make spacing carry meaning: tighter within a group, larger between groups, consistent around equivalent components.
- Test narrow and wide widths, zoom, long content, missing content, nested components, focus rings, touch targets, and dynamic state changes.
- Check that source order remains logical and that visual rearrangement does not break reading or keyboard order.
Output
Return the layout model, key alignment and spacing decisions, reusable tokens or constraints, breakpoint reasons, and verified edge conditions.
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.