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;
@latest is 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, not Arrow Up.
- Use Lucide's American English names:
color, not colour.
- 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, not
dashed-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: ...
1---2name: suggest-lucide-icons3description: 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.4---56# Suggest Lucide Icons78Use this skill to choose existing Lucide icon names, not to invent symbolic9artwork. Optimize for recognizable meaning in the user's context.1011## Workflow12131. When the project uses Lucide, inspect its manifest, lockfile-resolved version,14 and installed package first. Prefer installed assets or exact-version package15 assets as proof; `@latest` is not proof of project compatibility.162. Identify the concept, action, object, state, and UI placement.173. Generate 4-6 plausible Lucide icon names in kebab-case.184. Verify candidates against installed, lockfile-resolved, or exact-version19 package assets. If no project version exists, confirm the icon through the20 official current package metadata or release, the current upstream package,21 or `https://lucide.dev/icons/<icon-name>`. Consult current official framework22 integration documentation when needed, not as sole proof of icon existence or23 version.245. Discard names that cannot be verified.256. Present up to 3 confirmed candidates and recommend one, stating the verification26 source and version.2728If verification is blocked by network or tooling, say that candidates are29unverified and do not present them as confirmed.3031## Naming Rules3233- Use kebab-case: `arrow-up`, not `Arrow Up`.34- Use Lucide's American English names: `color`, not `colour`.35- For grouped variants, use the icon family first: `badge-plus`.36- For multiple elements, lead with the larger or containing element:37 `circle-user`, `square-arrow-out-up-right`.38- For modifiers, put the base object first: `circle-dashed`, not39 `dashed-circle`.4041## Selection Rules4243- Prefer icons whose visual metaphor works without explanation.44- Match the placement: toolbar actions need simpler shapes than navigation or45 section icons.46- Prefer action icons for commands (`save`, `download`, `trash-2`) and object or47 state icons for labels (`database`, `shield-check`, `file-warning`).48- Avoid novelty when a conventional icon exists.49- For multiple requested icons, choose a visually coherent set with similar50 density and stroke complexity.5152## Output5354```text55Candidates56- icon-name: why it fits57- icon-name: why it fits58- icon-name: why it fits5960Recommendation: icon-name61Reason: ...62Verification: ...63```
nledford