arrange

arrange is a skill for Claude Code from arnabdeypolimi/claude_code_setup. It costs 52 tokens per session (1,566 once invoked), scanned A, a copy of arrange, MIT.

A guide for improving the arrangement of interface elements, including spacing, alignment, hierarchy, and the overall flow of a page.

In plain words
What is it for?
Use it to review or adjust page composition, spacing systems, visual grouping, and responsive layout structure.
Why use it?
It helps fix crowded screens, monotonous grids, inconsistent gaps, and layouts that do not clearly show what matters most.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to review or adjust page composition, spacing systems, visual grouping, and responsive layout structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arnabdeypolimi/claude_code_setup/arrange
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.

Any agent
npx skills add arnabdeypolimi/claude_code_setup --skill arrange
Clone the repo
git clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setup

Made for: Claude Code.

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 arrange

README.md
[![agentmods](https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/arrange/github.svg)](https://agentmods.dev/skills/arnabdeypolimi/claude_code_setup/arrange)
Your own site
<a href="https://agentmods.dev/skills/arnabdeypolimi/claude_code_setup/arrange"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/arrange/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 arrange

Your own site · 80×15
<a href="https://agentmods.dev/skills/arnabdeypolimi/claude_code_setup/arrange"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/arrange.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,566 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 95% copy Near-identical to another mod 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.00052 $0.01566
Opus 5.5 $0.00021 $0.00626
Sonnet 5.5 $0.00010 $0.00313
Haiku 4.5 $0.00005 $0.00157

Measured 2mo ago against content hash 775f157cd6f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

arrange 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 2mo 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.

Origin

This is a copy

95% identical to arrange — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/arrange/SKILL.md · 124 lines

How it starts

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

Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions.

MANDATORY PREPARATION

Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.


Assess Current Layout

Analyze what's weak about the current spatial design:

  1. Spacing:

    • Is spacing consistent or arbitrary? (Random padding/margin values)
    • Is all spacing the same? (Equal padding everywhere = no rhythm)
    • Are related elements grouped tightly, with generous space between groups?
  2. Visual hierarchy:

    • Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings?
    • Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?)
    • Does whitespace guide the eye to what matters?
  3. Grid & structure:

    • Is there a clear underlying structure, or does the layout feel random?
    • Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly)
    • Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule)
  4. Rhythm & variety:

    • Does the layout have visual rhythm? (Alternating tight/generous spacing)
    • Is every section structured the same way? (Monotonous repetition)
    • Are there intentional moments of surprise or emphasis?
  5. Density:

    • Is the layout too cramped? (Not enough breathing room)
    • Is the layout too sparse? (Excessive whitespace without purpose)
    • Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air)

CRITICAL: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention.

Read the full file on GitHub · 124 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. 2mo ago First seen · 124 lines · 52 tokens per session scan A 775f157cd6f0

Subscribe to this mod's changes

arrange is a skill published in the GitHub repository arnabdeypolimi/claude_code_setup (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,566 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to arrange, differing in 5 lines, and is treated as a copy.

Related

arrange compared with skills from other repositories

arrange next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
arrangearnabdeypolimi/claude_code_setupSkill51mo agoMITA52Claude Code
brainstormingVimalk0703/shipworthySkill67mo agoMITA44Claude Code
accessibilityVimalk0703/shipworthySkill67mo agoMITA33Claude Code
figma-verificationjoryeugene/tripodSkill22mo agononeA34Claude Code
interaction-designjoryeugene/tripodSkill22mo agononeA53Claude Code
figma-extractjoryeugene/tripodSkill22mo agononeA0Claude Code
visual-designjoryeugene/tripodSkill22mo agononeA38Claude Code