agentsclimarketplace

Layout grid

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/layout-grid

Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.From its SKILL.md

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill layout-grid

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.4 KB, 316 tokens by cl100k_base, as published. Nobody here has run it

Layout Grid

You are an expert in layout grid systems for digital product design.

What You Do

You define responsive grid systems that create consistent, flexible page layouts across breakpoints.

Grid Anatomy

  • Columns: Typically 4 (mobile), 8 (tablet), 12 (desktop)
  • Gutters: Space between columns (16px, 24px, or 32px typical)
  • Margins: Outer page margins (16px mobile, 24-48px desktop)
  • Breakpoints: Points where layout adapts (e.g., 375, 768, 1024, 1440px)

Grid Types

  • Column grid: Equal columns for general layout
  • Modular grid: Columns + rows creating modules
  • Baseline grid: Vertical rhythm alignment (4px or 8px)
  • Compound grid: Overlapping grids for complex layouts

Responsive Behavior

  • Fluid: columns stretch proportionally
  • Fixed: max-width container with centered content
  • Adaptive: distinct layouts per breakpoint
  • Column dropping: reduce columns at smaller sizes

Common Patterns

  • Full-bleed: content spans entire viewport
  • Contained: max-width with margins
  • Asymmetric: sidebar + main content
  • Card grids: auto-fill responsive cards

Best Practices

  • Use consistent gutters and margins
  • Align content to the grid, not arbitrarily
  • Test at every breakpoint, not just the extremes
  • Document grid specs for developers
  • Allow intentional grid-breaking for emphasis

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ui components skills give in 316 tokens

Counted across 293 of the 305 authors here whose files we hold, read 2026-09-06

  • Start with a --design-system search before designingin 17 of 293, across 15 files
  • Ensure 4.5:1 minimum text contrastin 16 of 293, across 15 files
  • Verify the pre-delivery checklist before delivering UI codein 16 of 293, across 14 files
  • Use SVG icons instead of emojisin 15 of 293, across 14 files
  • Keep touch targets at least 44 pointsin 14 of 293, across 12 files
  • Check page override files before master rulesin 13 of 293, across 11 files
  • Supplement with domain searches as neededin 13 of 293, across 11 files
  • Add cursor-pointer to all clickable elementsin 12 of 293
  • Use CSS variables for themingin 11 of 293, across 7 files
  • Use semantic color tokens, not raw hexin 11 of 293, across 8 files
  • Meet WCAG AA color contrastin 11 of 293, across 7 files
  • Default stack to html-tailwind when unspecifiedin 10 of 293

Said here and by no other author read

  • Use consistent gutters and margins
  • Align content to the grid
  • Document grid specs for developers
  • Allow intentional grid-breaking for emphasis

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.