agentleFS
phazurlabsphazurlabs/sumi/skills/icon-illustration-systems/SKILL.md

icon-illustration-systems

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

Icon and illustration systems: grid and sizing scales, library selection (Lucide, Heroicons, Phosphor, SF Symbols, Material Symbols), illustration style guides, SVG optimization, and accessible iconography. Use when choosing an icon set, sizing icons, or establishing an illustration style.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every recipe in the reference files emits these.

    line 28
  2. Distinctive:

    Never scale a 24px icon down to 12px by setting width/height — use a dedicated small variant

    line 45
  3. Distinctive:

    When to reach for it, and the simpler option to try first

    line 106
  4. Distinctive:

    Every icon is either meaningful (conveys information) or decorative (visual embellishment).

    line 114
  5. Very specific:

    Every icon: must have either aria-hidden="true" (decorative) or an accessible name (meaningful)

    line 145
  6. Very specific:

    Add focusable="false" to inline SVGs in IE/Edge legacy to prevent tab-stop issues

    line 146
  7. Very specific:

    Use role="img" when the SVG is meaningful and uses <title> for its label

    line 147

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

Icon and Illustration Systems

Mental model

An icon is a compression of meaning, and compression only works when the reader already has the key. Most icon failures are the designer assuming a metaphor is universal when it is learned.

  • Universal metaphors are a short list. Home, search, close, play, plus, trash, settings, back. Everything else is learned, and learned means a label.
  • If you have to debate whether an icon is self-explanatory, add a label. The debate is the evidence. Icon-only navigation measurably reduces discoverability; icon-plus-label costs a few pixels and removes the problem.
  • Optical alignment beats mathematical alignment. A triangle centred by bounding box looks off-centre. Centre by visual mass, which for a play glyph means nudging right.
  • One grid, one stroke weight, one corner radius. Mixing icon sets is the fastest way to make an interface look assembled rather than designed.
  • Decorative icons are invisible to screen readers, meaningful ones are not. That distinction is a decision you make per icon, not a default.

Constants

Every recipe in the reference files emits these.

TokenSizeLine HeightUse CasesTouch Target
icon-xs12px12pxStatus dots, inline indicators, badge counts, color swatchesN/A (not interactive)
icon-sm16px16pxInline with small text (12-13px), table row icons, tag icons, breadcrumb separators24x24px min
icon-md20px20pxDefault size — nav items, buttons, form field icons, list item icons, dropdown arrows32x32px min
icon-lg24px24pxProminent actions, card header icons, section markers, tab bar icons (mobile)44x44px min (mobile)
icon-xl32px32pxFeature icons, section headers, sidebar category icons, dialog icons44x44px min
icon-2xl40px40pxHero feature icons, onboarding step icons, empty state accentsN/A (usually decorative)
icon-3xl48px48pxLarge empty state illustrations, marketing feature blocks, landing page iconsN/A (usually decorative)

Sizing Rules

  • Icons below 16px should use simplified glyphs (fewer details, thicker relative strokes)
  • Icons at 12px may need to be redesigned as filled shapes rather than stroked outlines
  • At 32px+, icons can support more detail (inner strokes, secondary elements)
  • Never scale a 24px icon down to 12px by setting width/height — use a dedicated small variant
  • Design at 24px, then create size-specific variants for 16px and 12px

4. Icon Design Rules

StateOpacityColor TokenTransformCursorAdditional
Default100%--icon-default (gray-600)nonedefault—
Hover100%--icon-hover (gray-900)nonepointertransition: color 150ms ease
Active / Pressed100%--icon-active (primary-600)scale(0.95)pointertransition: transform 100ms ease
Disabled38%--icon-disabled (gray-400)nonenot-allowedpointer-events: none
Selected / On100%--icon-selected (primary-600)nonepointerSwitch to filled variant if available
Focus-visible100%--icon-focus (gray-900)nonepointer2px focus ring offset 2px
Drag80%--icon-defaultscale(1.05)grabbingdrop-shadow for lift effect

State Transition CSS

.icon-button {
  color: var(--icon-default);
  transition: color 150ms ease, transform 100ms ease, opacity 150ms ease;
}
.icon-button:hover { color: var(--icon-hover); }
.icon-button:active { color: var(--icon-active); transform: scale(0.95); }
.icon-button:disabled { color: var(--icon-disabled); opacity: 0.38; pointer-events: none; }
.icon-button[aria-selected="true"] { color: var(--icon-selected); }
.icon-button:focus-visible { outline: 2px solid var(--focus-ring); outline-offset: 2px; }

8. Animated Icons

Index

NeedReference
Choose an icon set (Lucide, Heroicons, Phosphor, Tabler)icon-library-catalog.md
SF Symbols and Material Symbols conventionsicon-library-catalog.md
Licence and coverage comparisonicon-library-catalog.md
React icon component, inline vs sprite vs fonticon-implementation-recipes.md
Animated icons: spinner, toggle, hamburger morphicon-implementation-recipes.md
SVGO config and size targetsicon-implementation-recipes.md
Choosing an illustration styleillustration-systems.md
Empty-state and spot illustrationsillustration-systems.md
The 24x24 grid, keyline shapes, safe zonesicon-geometry-and-color.md
currentColor, multi-colour icons, dark modeicon-geometry-and-color.md

Reference architecture

FileCoversLines
references/icon-library-catalog.md6 libraries + platform conventions237
references/icon-implementation-recipes.mdcomponent, states, animation, SVGO206
references/illustration-systems.md16 styles, empty states, spot art168
references/icon-geometry-and-color.mdgrid, keylines, colour71

What every reference file contains

  1. When to reach for it, and the simpler option to try first
  2. Complete code, not fragments
  3. The accessibility wiring for that specific case
  4. Dark-mode behaviour
  5. The mistake that case invites

Meaningful vs Decorative Icons

Every icon is either meaningful (conveys information) or decorative (visual embellishment). The treatment differs completely:

Meaningful icons (icon is the only way to understand the action):

<!-- Method 1: aria-label on the button -->
<button aria-label="Search">
  <svg aria-hidden="true"><!-- icon --></svg>
</button>

<!-- Method 2: title element inside SVG -->
<svg role="img" aria-labelledby="search-title">
  <title id="search-title">Search</title>
  <!-- icon paths -->
</svg>

<!-- Method 3: Visually hidden text -->
<button>
  <svg aria-hidden="true"><!-- icon --></svg>
  <span class="sr-only">Search</span>
</button>

Decorative icons (icon accompanies visible text):

<button>
  <svg aria-hidden="true" focusable="false"><!-- icon --></svg>
  <span>Search</span>
</button>

Accessibility Rules

  1. Every icon must have either aria-hidden="true" (decorative) or an accessible name (meaningful)
  2. Add focusable="false" to inline SVGs in IE/Edge legacy to prevent tab-stop issues
  3. Use role="img" when the SVG is meaningful and uses <title> for its label
  4. Toggle icons must announce their state: aria-pressed="true/false" or aria-expanded
  5. Icon-only buttons require a minimum 44x44px touch target (WCAG 2.5.8)
  6. Color alone must not be the only indicator — pair colored icons with shape changes (e.g., filled vs outline for selected)
  7. Animated icons must respect prefers-reduced-motion (WCAG 2.3.3)

14. Icon Color

Routing

For choosing an icon set -- style, weights, coverage, licence, import pattern, and the SF Symbols and Material Symbols platform conventions: read references/icon-library-catalog.md.

For getting icons into the codebase -- the React component, inline vs sprite vs font, state transitions, animated icons, and SVG optimization: read references/icon-implementation-recipes.md.

For illustration -- sixteen styles with the brands that use them, plus empty-state and spot illustration practice: read references/illustration-systems.md.

For drawing icons -- the 24x24 grid, pixel alignment, keyline shapes, safe zones, and how icons take colour across themes: read references/icon-geometry-and-color.md.

Cross-References

  • ui-visual-design-system -- where iconography sits in the visual language
  • platform-visual-standards -- SF Symbols and Material Symbols in their native context
  • animation-recipe-library -- the easing tokens animated icons use
  • accessibility-inclusive-design -- the full decorative-vs-meaningful story
  • design-systems-architecture -- icon size tokens in the three-tier model

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.