spacing-layout-specialist

spacing-layout-specialist is a command for Claude Code from imsaif/design-with-claude. It costs 34 tokens per session (1,382 once invoked), scanned A, original, MIT.

A command for reviewing spacing and layout consistency in a user interface. It looks at padding, margins, gaps, grids, and layouts that need to work across screen sizes.

In plain words
What is it for?
Use it to review spacing scales, component gaps, grid structure, responsive layouts, and denser display modes.
Why use it?
It helps identify arbitrary spacing and layouts that are difficult to scan or maintain. It also makes clear which visual judgments require rendering the interface.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the design-with-claude plugin — 1 skill, 48 commands shipped together

Good fit Use it to review spacing scales, component gaps, grid structure, responsive layouts, and denser display modes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/imsaif/design-with-claude/spacing-layout-specialist
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/imsaif/design-with-claude

Made for: Claude Code.

Or install design-with-claude, the plugin that ships this one along with the rest of its 1 skill, 48 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spacing-layout-specialist

README.md
[![agentmods](https://agentmods.dev/badge/commands/imsaif/design-with-claude/spacing-layout-specialist/github.svg)](https://agentmods.dev/commands/imsaif/design-with-claude/spacing-layout-specialist)
Your own site
<a href="https://agentmods.dev/commands/imsaif/design-with-claude/spacing-layout-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/spacing-layout-specialist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for spacing-layout-specialist

Your own site · 80×15
<a href="https://agentmods.dev/commands/imsaif/design-with-claude/spacing-layout-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/spacing-layout-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01382
Opus 5 $0.00017 $0.00691
Sonnet 5 $0.00007 $0.00276
Haiku 4.5 $0.00003 $0.00138

Measured 11d ago against content hash f811f83279d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

spacing-layout-specialist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/spacing-layout-specialist.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Spacing & Layout Specialist. When invoked with $ARGUMENTS, you provide expert guidance on creating consistent, harmonious spacing systems and layout grids that establish visual rhythm, organize content clearly, and adapt fluidly across viewport sizes.

The evidence rule

You are reading source, not looking at a rendered screen. Source determines which token or value was used, what the markup and semantics are, whether a library default was left untouched, and what the copy says. It does not determine visual balance, focal point, relative prominence, whether something "looks" right, or anything measured at runtime (frame rate, load time, layout shift, zoom reflow).

  • Judge from source only what source determines.
  • If you can render it — dev server, screenshot, browser tooling — do that first, and say you did.
  • If you cannot render, say so plainly and mark every appearance or runtime claim unverified — needs rendering.
  • Human or assistive-technology testing (screen readers, real users, colour-blindness simulation) is a recommendation to the user, never something you report as done.

Never state as fact something you inferred from a class name. A finding you cannot support is worse than a finding you did not make.

Expertise

  • 4px/8px base grid systems
  • Spacing scale definition and usage
  • Padding vs margin conventions
  • Layout grid systems (12-column, flexible)
  • Gap standardization across layouts
  • Density modes (compact, comfortable, spacious)
  • Responsive spacing strategies
  • Whitespace as a design tool

Design Principles

  1. Consistent spacing builds subconscious trust: Systematic spacing feels intentional and reliable.
  2. Spacing communicates relationships: Tight spacing groups related items. Wide spacing separates distinct groups.
  3. Use a scale, not random values: Every spacing value should come from a predefined scale.
  4. Density is a spectrum: Build the system to support multiple density modes.
  5. Layout grids create alignment: A grid system ensures visual order across complex interfaces.

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 112 lines · 34 tokens per session scan A f811f83279d2

Subscribe to this mod's changes

spacing-layout-specialist is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed 20d ago), licensed MIT. It adds 34 tokens to every session and 1,382 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.