agentleFS
rschuftrschuft/ai-frontend-skill-packs/skills/design-layout-and-grid/SKILL.md

design-layout-and-grid

Skill4 starsChanged 5 days agoMITView on GitHub

Repair visual composition, whitespace, alignment, grouping and responsive layout grids using Gestalt proximity, consistent spacing, CSS Grid and content-driven breakpoints.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this specialist when the actual task involves layout issues.

    line 10
  2. Distinctive:

    crowded-groups: Use proximity: tighten within a group, increase gaps between groups and align major edges.

    line 16
  3. Distinctive:

    broken-responsive-grid: Use CSS grid minmax(), min(), auto-fit or container queries.

    line 17
  4. Very specific:

    Read references/playbook.md for exact discriminating checks, implementation examples, tradeoffs and acceptance tests.

    line 20

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Layout and grid

Scope

Use this specialist when the actual task involves layout issues. Check documented brand/system decisions before prescribing changes. Do not conflate taste with accessibility standards or make assumptions from screenshots alone.

Affecting category: layout. Related governing principles: balance, proportion. Route from design-diagnose or design-review when observations match this category, or load directly during a focused implementation.

Procedure

  • crowded-groups: Use proximity: tighten within a group, increase gaps between groups and align major edges. Verify: At mobile and desktop widths, related elements are identifiable without outlines.
  • broken-responsive-grid: Use CSS grid minmax(), min(), auto-fit or container queries; allow content-driven stacking. Verify: No lost content, overlap or horizontal scroll at narrow viewports and zoom/reflow.
  • uneven-alignment: Set shared grid tracks and layout tokens; allow variable content while aligning semantically similar landmarks. Verify: Across content variants, rows/columns remain visually stable without truncating text.

Read references/playbook.md for exact discriminating checks, implementation examples, tradeoffs and acceptance tests. Keep the fix within the existing component architecture. Report original observation, selected recipe and evidence. For usability, engage ux-*; for normative accessibility, engage wcag-*.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.