agentleFS
Sign inStart free
shashidharbabushashidharbabu/rocketride-design-skills/skills/iconography/SKILL.md

iconography

Skill0 starsChanged 2 days agoLicence not identifiedView on GitHub

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 up the bundle", or an iconography.co link appears — and whenever another design skill's icon rule (lucide required vs lucide discouraged) conflicts with the project. This skill is the single place the per-project icon decision is made.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.

Check your setup, free