agentleFS
MaxPrehodaMaxPrehoda/motif/skills/choose-icons/SKILL.md

choose-icons

Skill1 starsChanged 45 days agoMITView on GitHub

Lists the icons a product needs, checks which icon libraries actually have them, then installs one library and replaces every existing icon, inline SVG and emoji with it. Use after the design-system pipeline, or when an app mixes icons from several sources.

  • Installs packages

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:

    Check what a library has before choosing it.

    line 10
  2. Distinctive:

    Write the list as ideas, not icon names.

    line 23
  3. Distinctive:

    Remove any imports and SVG files that are no longer used.

    line 73

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

Choose Icons

Work out which icons the product needs, check that a library has all of them, then use that one library everywhere.

Check what a library has before choosing it. A library picked for its looks will be missing specific icons, and the gaps get filled with hand-drawn ones that don't match.

Step 1: List the icons the product needs

Find what the code uses now:

grep -rhoE '<(svg|Icon)[^>]*|lucide-|react-icons|@heroicons|phosphor' src --include="*.svelte" --include="*.tsx" | head -40
grep -rn -E '[\x{1F300}-\x{1FAFF}\x{2600}-\x{27BF}]' src --include="*.svelte" --include="*.tsx" | head -20

Then look through the product: navigation, buttons and actions, empty states, status indicators, file types, integrations.

Write the list as ideas, not icon names. Write "export", "merge", "webhook", "billing", not "arrow-down-tray". You check libraries against the ideas. Every library has home, user and settings, so the specific ones are what decide it.

Step 2: Check which libraries have them

For each candidate library, look up every idea on the list, especially the ones specific to this product.

LibraryRoughly how many iconsStyle
Lucide1,6002px outline, geometric
Phosphor9,0006 weights
Heroicons300outline and solid
Radix Icons300drawn on a 15x15 grid
Tabler5,8002px outline

These counts go out of date. Check each library's current catalog.

Report how many ideas each library covers, and name what's missing: "Phosphor 34 of 34. Lucide 31 of 34, missing webhook, merge and oauth."

Choose in this order:

  1. Coverage. Missing icons turn into hand-drawn ones.
  2. One library only. Different line weights and grid sizes look wrong next to each other.
  3. A line weight that matches the rest of the UI.
  4. A library that lets you import icons one at a time, not the whole set.

Show the user the top two with their coverage and let them choose.

Step 3: Size icons to match the text

Icons usually sit next to text, so their size comes from the font sizes in DESIGN.md, not from a separate icon scale.

Next toIcon size
text-sm16px
text-base20px
text-lg24px
on its own24 to 32px

Line icons up with the height of the capital letters, not the whole text box. This usually takes a 1px nudge.

Set icon color to currentColor so each icon takes the color of the text around it.

Step 4: Replace the icons

npm install <library>

Replace icons one component at a time, not one icon at a time. Replace inline SVGs and emoji too, since emoji look different on every platform.

Remove any imports and SVG files that are no longer used.

Report

The library, its coverage ("34 of 34"), how many icons you replaced from each source (old library, inline SVG, emoji), and how the bundle size changed. List any idea that has no good icon.

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.