Use case guide
This guide shows how to write clear use cases for Lucide icons.
Write from the interface's perspective
Describe what the interface tells the user. Do not write from the contributor's point of view.
This describes the role the icon plays in an interface.
This explains the contributor's situation, not the icon's purpose.
Describe real usage, not the icon name
A use case should explain what the icon means in context. Do not repeat the icon name or only describe the drawing.
This explains microchip without repeating the name.
This duplicates the icon name and does not explain where the icon would be used.
Add context when it clarifies meaning
Some icons have broad meanings. Add context when it makes the use case clearer.
The phrase explains both the action and the product area.
This is less useful because it omits the level and context.
Keep each use case focused
Each entry should cover one clear idea. Split different meanings into separate entries.
This is short, clear, and focused on one interface function.
This reads like a tag list and mixes several ideas.
Write variant-specific use cases
For related icons, describe what makes each variant different.
This is specific to battery-low and sets it apart from other battery icons.
This is too generic and could apply to every battery variant.
Avoid pull request references
Use cases should make sense after the pull request is merged.
This keeps the useful meaning without depending on outside context.
This depends on a discussion readers may never see.
Keep entries concise
Use cases should usually be 4 to 12 words. Prefer a short phrase over a long explanation.
This is short enough to scan and specific enough to understand.
This is too long and reads like product copy instead of metadata.
Do not end with punctuation
Use cases are metadata phrases, not full sentences.
This matches the phrase style used across icon metadata.
The period adds unnecessary punctuation and makes entries inconsistent.
Avoid markdown and emoji
Use plain text only. Formatting belongs in documentation, not metadata values.
This works in search, generated pages, and other places that use metadata.
Markdown and emoji can show up in generated UI and make metadata harder to reuse.
Avoid implementation details
Use cases should describe meaning, not how the SVG was made.
This explains the icon's interface meaning.
This describes construction details that do not help people find or understand the icon.