iconography-system

Guides selection, design, and auditing of UI icon families against platform design systems.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill iconography-system-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iconography-system
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/iconography-system
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill iconography-system-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often place mismatched SVG icons wherever space allows, mixing unrelated icon libraries, breaking visual consistency, and creating accessibility issues with tiny touch targets or color-only state indicators. This Skill turns icon work into a repeatable visual-language process grounded in established platform references. ## Core Features & Use Cases - Family-First Selection: Audit the existing icon language, then align with established families like SF Symbols, Material Symbols, Fluent 2, or IBM Carbon instead of mixing random icon sets. - Custom Icon Design Rules: Extract family geometry (stroke, corner radius, optical size, negative space) before creating custom extensions, with metaphor and licensing checks. - State, Size & Localization Verification: Validate selected/disabled variants, optical sizing per rendered pixel size, icon-text alignment, touch targets, and RTL mirroring behavior. - Use Case: When adding a new toolbar action icon, use this Skill to confirm the metaphor, match the current family's stroke and corner treatment, verify the selected state uses fill rather than color alone, and render the full icon set side by side for coherence. ## Quick Start Use the iconography-system skill to audit the icons in my toolbar and recommend a consistent family with proper selected states and touch targets.

Frequently Asked Questions about iconography-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose icons for a design system?

Start by auditing the existing icon language, then classify each needed icon by meaning (action, object, navigation, status). Prefer an established family like SF Symbols, Material Symbols, Fluent, or Carbon that matches your platform before creating custom icons.

How do I design custom icons that match an existing icon family?

Extract the family profile first: artboard size, stroke width, cap and join style, corner radius, fill ratio, and negative space. Reproduce those properties in the custom icon rather than copying exact values, and verify the asset license before modifying reference icons.

Should I mix Material Symbols and SF Symbols in one UI?

No. Mixing unrelated icon families on the same surface breaks visual coherence because stroke weights, corner treatments, and optical sizing differ. Pick one family per surface and extend it with custom icons that follow its visual grammar when coverage is missing.

How should icons behave for right-to-left languages?

Directional icons like back, forward, and chevrons should mirror in RTL layouts, while icons whose shape carries meaning should keep their orientation. Separate semantic direction from physical direction and test text-bearing icons with localized labels.

Why shouldn't selected icon states use color alone?

Color-only state changes fail for colorblind users and low-contrast contexts. Use outline-to-fill transitions, weight or grade changes, background containers, or shape markers while keeping the same underlying metaphor so the icon's identity stays intact.

When should I use a text label instead of an icon?

Use text when the concept is ambiguous, the action is unfamiliar, destructive, or high-consequence, or when no recognizable metaphor exists. Forcing a pictogram onto an abstract concept creates puzzle-like icons that users cannot decode reliably.