suggest-lucide-icons
Skill11 starsChanged 14 days agoMITView on GitHub
Pick real Lucide icons for a concept, UI placement, button, section header, or note frontmatter. Use when the user asks what Lucide icon to use, requests icon candidates, or needs an icon name verified. Do not use for non-Lucide icon libraries or general icon or artwork design.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- graphif/project-graphtheir own version, first seen Oct 8, 2026
- Aver005/agent-skillstheir own version, first seen Feb 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- graphif/project-graph★ 4.5ksame name
- Aver005/agent-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-reviewSkill
- api-designSkill
- architecture-reviewSkill
- behavior-driven-developmentSkill
- brainstormingSkill
- ci-release-engineeringSkill
- clean-architectureSkill
- code-reviewSkill
- container-engineeringSkill
- create-agent-skillSkill
- csharp-dotnet-engineeringSkill
- css-scss-stylingSkill
- data-platform-engineeringSkill
- dependency-supply-chain-reviewSkill
- digital-asset-managementSkill
- documentation-engineeringSkill
- domain-driven-designSkill
- domain-modelingSkill
- donsetch-web-researchSkill
- gherkinSkill
- git-commitSkill
- git-workflowsSkill
- hexagonal-architectureSkill
- impeccableSkill
- internationalization-localizationSkill
- javascript-typescript-engineeringSkill
- justfilesSkill
- mcp-server-engineeringSkill
- mysql-mariadb-sql-engineeringSkill
- observability-engineeringSkill
- onion-architectureSkill
- parallelism-engineeringSkill
- performance-reviewSkill
- playwright-e2eSkill
- postgresql-sql-engineeringSkill
- prompt-engineering-reviewSkill
- python-antipatternsSkill
- python-design-patternsSkill
- python-engineeringSkill
- random-data-identifiersSkill
- release-readinessSkill
- review-verification-protocolSkill
- root-cause-analysisSkill
- ruby-engineeringSkill
- rust-antipatternsSkill
- rust-async-webSkill
- rust-code-reviewSkill
- rust-design-patternsSkill
- rust-desktop-guiSkill
- rust-engineeringSkill
- rust-persistence-sqlSkill
- rust-testing-qualitySkill
- script-engineeringSkill
- security-review-evidenceSkill
- security-reviewSkill
- semantic-versioningSkill
- sql-engineeringSkill
- sqlite-sql-engineeringSkill
- svelte-sveltekit-engineeringSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to choose existing Lucide icon names, not to invent symbolic artwork.
- Very specific: line 13
When the project uses Lucide, inspect its manifest, lockfile-resolved version, and installed package first.
- Distinctive: line 18
Verify candidates against installed, lockfile-resolved, or exact-version package assets.
- Distinctive: line 28
If verification is blocked by network or tooling, say that candidates are unverified and do not present them as confirmed.
- Very specific: line 33
Use kebab-case: arrow-up, not Arrow Up.
- Very specific: line 34
Use Lucide's American English names: color, not colour.
- Distinctive: line 43
Prefer icons whose visual metaphor works without explanation.
- Very specific: line 46
Prefer action icons for commands (save, download, trash-2) and object or state icons for labels (database, shield-check, file-warning).
- Distinctive: line 48
Avoid novelty when a conventional icon exists.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Suggest Lucide Icons
Use this skill to choose existing Lucide icon names, not to invent symbolic artwork. Optimize for recognizable meaning in the user's context.
Workflow
- When the project uses Lucide, inspect its manifest, lockfile-resolved version,
and installed package first. Prefer installed assets or exact-version package
assets as proof;
@latestis not proof of project compatibility. - Identify the concept, action, object, state, and UI placement.
- Generate 4-6 plausible Lucide icon names in kebab-case.
- Verify candidates against installed, lockfile-resolved, or exact-version
package assets. If no project version exists, confirm the icon through the
official current package metadata or release, the current upstream package,
or
https://lucide.dev/icons/<icon-name>. Consult current official framework integration documentation when needed, not as sole proof of icon existence or version. - Discard names that cannot be verified.
- Present up to 3 confirmed candidates and recommend one, stating the verification source and version.
If verification is blocked by network or tooling, say that candidates are unverified and do not present them as confirmed.
Naming Rules
- Use kebab-case:
arrow-up, notArrow Up. - Use Lucide's American English names:
color, notcolour. - For grouped variants, use the icon family first:
badge-plus. - For multiple elements, lead with the larger or containing element:
circle-user,square-arrow-out-up-right. - For modifiers, put the base object first:
circle-dashed, notdashed-circle.
Selection Rules
- Prefer icons whose visual metaphor works without explanation.
- Match the placement: toolbar actions need simpler shapes than navigation or section icons.
- Prefer action icons for commands (
save,download,trash-2) and object or state icons for labels (database,shield-check,file-warning). - Avoid novelty when a conventional icon exists.
- For multiple requested icons, choose a visually coherent set with similar density and stroke complexity.
Output
Candidates
- icon-name: why it fits
- icon-name: why it fits
- icon-name: why it fits
Recommendation: icon-name
Reason: ...
Verification: ...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
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.

