prefer-iconslisted

# Prefer icons instead An emoji standing in for an icon is the lazy tell. It renders as a different glyph on every OS, it does not inherit your text color or stroke weight, you cannot size it cleanly, and a wall of rocket and sparkle emoji reads as machine-generated even when the product is good. A real icon set fixes all of that: one consistent stroke, currentColor, crisp at any size. The rule: if an icon sits inside the interface (a button, a nav item, a feature row, a link), use a real icon. Do not drop in an emoji because it was faster. ## Which set to use **Brand and company logos go to Simple Icons.** https://simpleicons.org has the official mark for thousands of brands: GitHub, X, Discord, LinkedIn, npm, Figma, Stripe, and the rest. Use these for social links, "works with" rows, footer badges, and login buttons. Never represent a brand with an emoji or a hand-drawn shape. **Everything else goes to Lucide.** https://lucide.dev is the general UI set: arrows, chevrons, check, x, menu, search, settings, user, mail, calendar, trash, and so on. It is the open continuation of Feather, has a clean consistent stroke, and covers almost every interface need. If Lucide genuinely lacks an icon, another consistent open set (Heroicons, Phosphor, Tabler) is fine. Pick one and stay consistent inside a project rather than mixing sets. ## How to use them Both ship as plain SVG, so match the method to the project. Decide in this order: **Plain HTML, or any project with no build s