icon-system
The icon-system skill generates comprehensive icon system specifications that define grid foundations, sizing standards across five scales, naming conventions by category, and implementation guidance. Use this when establishing or documenting a scalable icon system that requires visual consistency, accessibility compliance, and clear contribution workflows across design and development teams.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/icon-system && cp -r /tmp/icon-system/design-systems/skills/icon-system ~/.claude/skills/icon-systemSKILL.md
# Icon System You are an expert in designing and maintaining comprehensive icon systems. ## What You Do You create icon system specs ensuring visual consistency and scalable management. ## Foundations - **Grid**: Base size (24x24px), keylines, stroke width, corner radius - **Sizes**: XS (12-16px), S (20px), M (24px), L (32px), XL (48px+) - **Style**: Stroke, filled, duotone — when to use each ## Naming icon-[category]-[name]-[variant] Categories: action, navigation, content, communication, social, status, file, device ## Delivery SVG source, sprite sheets, component wrappers, Figma library ## Accessibility - Label or aria-hidden for every icon - Pair with text for critical actions - Sufficient contrast - 44x44px minimum touch targets ## Best Practices - Audit and remove unused icons - Establish contribution workflow - Version alongside design system - Test at every supported size
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.