No bundled icon set - components take any icon as a ReactNode. This page shows the registry pattern.
Icon playground
Install Icon
1. New project? One command installs the package and wires everything - see Installation:
pnpm dlx zyncat-ui init2. Import the component - it loads its own stylesheet:
import { Icon } from '@zyncat/ui/icon';Usage
import { Icon } from './icon'; <Icon name="lightning" size="lg" />Compose Icon in your application. No Tailwind or external styling library is required; every value resolves from Zyncat UI's token vocabulary.
Frequently asked questions
Pass any node to that component's icon prop - Badge, Tag and Avatar all take icon as a plain ReactNode. There is nothing to import for the icon itself: you bring your own, typically a component from a library like @phosphor-icons/react.
No - there is no @zyncat/ui/icon export. What this page demonstrates instead is the pattern its own components and docs use internally: a small object that maps short string names to individually imported Phosphor glyphs, so a project only ever imports the icons it actually uses.
One imported glyph registered under more than one name, so each call site can use whichever reads clearer. The library's own internal icon registry, for example, maps both "x" and "close" to the same glyph.
Switch its weight to "fill" - Phosphor ships a filled variant of every glyph, and the convention this page documents is using that fill weight for an active or selected state instead of adding a second icon.