agentleFS
dembrandtdembrandt/dembrandt-skills/skills/ui-density/SKILL.md

ui-density

Skill194 starsChanged 4 months agoMITView on GitHub

Match information density to platform and user type. Use when designing data tables, dashboards or toolbars, or adapting a desktop product for mobile.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never port a dense desktop layout directly to mobile.

    line 69
  2. Distinctive:

    Not every feature belongs on every platform.

    line 115
  3. Distinctive:

    Front-load the scannable bit: Put the word or number the user scans for at the start of the line/label, so they don't read the whole thing …

    line 144

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

UI Density

Density describes how much information and how many interactive elements appear in a given area. The right density is not a universal standard — it depends on platform, user type, and session context.

Platform Defaults

PlatformDefault densityReason
DesktopMedium to highLarge screen, precise input, often primary work surface
TabletMediumTouch input, larger than phone but less than desktop
MobileLowSmall screen, touch targets need space, interrupted sessions

Never port a dense desktop layout directly to mobile. Remove, collapse, or deprioritise features rather than shrinking them.

User Type and Density

User typeAppropriate densityExamples
Power user / enterpriseHigh density acceptableTrading platforms, ERP, analytics, developer tools
Occasional / general userMedium — clear visual breathing roomSaaS dashboards, project management
Consumer / first-time userLow — guided, unclutteredOnboarding flows, consumer apps, e-commerce

A trading platform operator sits in the product for 8 hours a day and has learned every pixel — high density serves them. A user visiting a settings page once a month needs clear space and obvious labels.

Domain experts tolerate complexity — if it solves the right problem quickly. People who know the domain (especially in internal tools) will happily use dense, complex, feature-rich interfaces, because the complexity maps to a mental model they already hold. Two conditions make this work rather than overwhelm:

  • Terminology matches their vocabulary. The labels, abbreviations, and jargon are the ones they already use. A term that's opaque to a consumer is a precise, fast signal to an expert — don't dumb it down for an audience that isn't there.
  • The outcome stays quickly reachable. Density is fine as long as the result — the answer they came for, or the action they need — is fast to see or do, typically through an obvious primary action (see [[visual-emphasis-and-hierarchy]]). Complexity that surrounds a clear path to the outcome is power; complexity that buries the outcome is clutter.

Design a power-user mode around this: high density, expert terminology, keyboard-driven, primary action always in reach — distinct from a casual/first-time mode that guides and unclutters. The same product may offer both; match the mode to who is actually using the view.

Density Tokens

Define spacing scale with density in mind. A compact variant reduces padding without changing structure:

/* Default density */
--density-row-height:    44px;
--density-cell-padding:  var(--space-3) var(--space-4);
--density-gap:           var(--space-4);

/* Compact (enterprise / data-heavy) */
[data-density="compact"] {
  --density-row-height:    32px;
  --density-cell-padding:  var(--space-2) var(--space-3);
  --density-gap:           var(--space-2);
}

/* Spacious (consumer / onboarding) */
[data-density="spacious"] {
  --density-row-height:    56px;
  --density-cell-padding:  var(--space-4) var(--space-6);
  --density-gap:           var(--space-6);
}

Feature Count by Platform

Not every feature belongs on every platform. For each feature ask: does a mobile user need this right now?

PriorityMobileTabletDesktop
Core taskAlwaysAlwaysAlways
Secondary actionsCollapsed (menu/sheet)VisibleVisible
Filters and sortingAccessible but not persistentCollapsiblePersistent sidebar or toolbar
Bulk actionsHidden or minimalReducedFull
Advanced settingsLink to separate screenLink or panelInline or panel
Data visualisationSimplified (key metric only)Reduced chartFull chart

Density and Feature Reduction on Mobile

Sections and features can be removed, collapsed, or repositioned on smaller viewports — not just resized.

  • Remove: Decorative sidebars, secondary data columns, promotional banners
  • Collapse: Filters, advanced options, secondary navigation into accordions or bottom sheets
  • Reposition: Toolbars move from top to bottom (thumb reach), sidebars move to drawers
  • Simplify: A multi-column data table becomes a card list; a full chart becomes a single key metric

Progressive disclosure is the principle: show the minimum needed to complete the primary task, reveal more on demand.

Reading Is Time

The most under-counted cost in a dense UI is reading. Every word the user must read to orient themselves is time spent, and it compounds — the more there is to read, the slower the whole interface feels, on every visit. Density is not just "how much fits on screen"; it's "how much the user has to read to act." Reduce that load:

  • Cut words before you shrink them. The fix for a cramped screen is usually less content, not smaller type (see [[modular-scale-typography]]).
  • Let recognisable icons replace reading where a concept has an unambiguous, standard icon — the eye recognises a shape faster than it reads a word (see [[brand-visual-language]]).
  • But don't over-ice with icons. A wrong or decorative icon adds a thing to interpret instead of removing one; and an icon on everything is its own noise. Right icon, relevant place only.
  • Front-load the scannable bit. Put the word or number the user scans for at the start of the line/label, so they don't read the whole thing to find it.

The goal: a user should be able to glance, not read, to know where they are and what to do next.

Review Checklist

  • Is the density appropriate for the primary platform (desktop = can be denser, mobile = must be sparse)?
  • Is the density appropriate for the user type (power user = higher density, consumer = more space)?
  • Are spacing tokens used to define density — not one-off padding values?
  • On mobile: are secondary features collapsed, repositioned, or removed rather than shrunk?
  • Are touch targets ≥ 44×44px even in compact density variants?
  • Is a density toggle offered for enterprise tools where users have strong personal preferences?

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.