agentleFS
aksuharunaksuharun/skills/lucide-icons/SKILL.md

lucide-icons

Skill1 starsChanged 6 months agoMITView on GitHub

Use Lucide icons correctly across any framework or environment. Lucide is a tree-shakeable SVG icon library with 1000+ icons. Use this skill when working with Lucide icons in React, Vue, Svelte, Solid, Preact, Angular, Astro, React Native, Vanilla JS, or static/server-side environments. Triggers include installing lucide icons, importing lucide components, customizing icon appearance, using dynamic icons, or using Lucide lab custom icons.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All framework packages share the same core props:

    line 18
  2. Very specific:

    All packages also accept any SVG presentation attribute as a prop (e.g.

    line 27
  3. Very specific:

    Always tree-shake: Import only the icons you use.

    line 31
  4. Very specific:

    Dynamic by name: Use DynamicIcon (React) or a generic wrapper only when icon names come from dynamic data (e.g.

    line 33
  5. Distinctive:

    Read the relevant reference file for the framework in use:

    line 38

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

Lucide Icons

Lucide provides framework-specific packages—each icon is an individually importable component/element that renders an inline SVG. All packages are fully tree-shakeable.

Icon Naming

  • Package exports use PascalCase: Camera, ArrowRight, CircleAlert
  • CSS/HTML data attributes and icon font classes use kebab-case: data-lucide="circle-alert", icon-circle-alert
  • Find icon names at lucide.dev/icons

Universal Props

All framework packages share the same core props:

proptypedefault
sizenumber24
colorstringcurrentColor
strokeWidthnumber2
absoluteStrokeWidthbooleanfalse

All packages also accept any SVG presentation attribute as a prop (e.g. fill, stroke-linejoin).

Best Practices

  • Always tree-shake: Import only the icons you use. Never import * as icons in production bundles.
  • Direct icon imports (e.g. from 'lucide-react/icons/camera') improve build performance by bypassing the package barrel.
  • Dynamic by name: Use DynamicIcon (React) or a generic wrapper only when icon names come from dynamic data (e.g. a CMS).
  • Accessibility: Icons default to aria-hidden="true". Add aria-label when the icon conveys meaning.

Framework Reference Files

Read the relevant reference file for the framework in use:

Framework / EnvironmentPackageReference file
Reactlucide-reactreferences/lucide-react.md
Vue 3lucide-vue-nextreferences/lucide-vue-next.md
Svelte 5 (or 4)@lucide/sveltereferences/lucide-svelte.md
SolidJSlucide-solidreferences/lucide-solid.md
Preactlucide-preactreferences/lucide-preact.md
Angularlucide-angularreferences/lucide-angular.md
Astro@lucide/astroreferences/lucide-astro.md
React Nativelucide-react-nativereferences/lucide-react-native.md
Vanilla JS / HTMLlucidereferences/lucide.md
Static / No-framework / Node.jslucide-staticreferences/lucide-static.md

Lucide Lab (Custom / Unofficial Icons)

Lucide lab provides additional icons not in the main library. All packages support lab icons via their Icon component:

// React example — same pattern works across React, Preact, Solid, Astro, Svelte, Vue
import { Icon } from 'lucide-react';
import { coconut } from '@lucide/lab';

<Icon iconNode={coconut} color="red" size={32} />

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.