← ClaudeAtlas

iconographylisted

Decide and wire a project's UI icon system once — choose the icon set (lucide, Tabler, Iconoir, Heroicons, Phosphor, Hugeicons, Remix, Radix) from verified facts (license, count, default size, stroke prop, aria default, shadcn-migrate and Next optimizePackageImports support), write a one-paragraph icon spec in precise vocabulary (grid, base size, stroke weight, caps/joins, corner radius, optical size), normalise every set through one typed <Icon> wrapper (size tokens, constant stroke, aria-hidden vs label), swap lucide out of shadcn with `shadcn migrate icons` (and know when that command can't help), keep bundles tree-shaken, and judge when to commission custom icons instead. Use this whenever someone asks "which icon set", "replace lucide", "swap shadcn icons", "icons look generic / too thick / off-brand", "match icons to our font", "1.5 stroke icons", "outline vs filled", "Phosphor vs Tabler vs Heroicons", "icon library for React/Next", "custom icon set", "icon style guide", "icon audit", "icons are blowing
shashidharbabu/rocketride-design-skills · ★ 0 · Web & Frontend · score 62
Install: claude install-skill shashidharbabu/rocketride-design-skills
# Iconography Icons are a system decision. Make it once per project, early, then enforce it mechanically. This skill owns three things: **which set**, **the spec it must satisfy**, and **how it is wired** (wrapper, imports, shadcn swap). Verified Oct 2026 against npm, rendered output (React 19.3.1) and the shadcn 4.22.1 / 2.3.0 sources. Anything not tested is marked *(unverified)*. ## Policy: this skill decides; other skills' icon lines are defaults Several skills carry a one-line icon default that suits their own context. `shadcn` and `motion-primitives` assume `lucide-react`. `taste-skill`, `soft-skill`, `minimalist-skill` and `redesign-skill` steer away from stock lucide to avoid a templated look. Both positions are reasonable, and they conflict. Resolve the conflict here, record the decision in the project's direction doc (`icons: <set> @ <weight>, <size scale>`), and that record overrides every skill's default for that project. Lucide is a legitimate choice when the brief is neutral or speed matters, especially when it's re-weighted through the wrapper. ## Position in design-arsenal - **Phase 2 (Identity):** choose the set and write the spec. The icon stroke should sit next to the type weight; a 1.5px stroke reads best beside a regular or medium sans. - **Phase 4 (Component base):** run the shadcn swap right after init and token remap, then add `<Icon>` before any feature code lands. - **Phase 8 (QA / licensing):** add one line, `Icons: <pkg>@<ver> — <licence>