- Tailwind CSS v4 only. Do NOT create a `tailwind.config.js` - v4 config lives in CSS via `@theme`. If the project is on v3, convert unsupported syntax rather than downgrading the components. - Scan the library for class names or everything renders unstyled: `@source '../node_modules/@appica/ui-react/dist';` in the stylesheet that imports Tailwind. The path is relative to that stylesheet - count the `../` needed to reach the project root. A bare package name resolves to nothing and fails silently. - React 19 is a hard requirement. No `forwardRef` - `ref` is a plain prop. - Import from the subpath, one component per import: `import { Button } from '@appica/ui-react/button'`. - Never write hex colors, px radii, or duration literals. Use the role-based tokens: `bg-background-muted`, `text-foreground-intense`, `border-border-strong`, `var(--radius-md)`. Full list: https://appica.dev/ui/docs/react/colors.md - Never write hue-based utilities (`bg-gray-100`, `text-slate-600`). The palette is organized by role, not hue. - Prefer v4 variant syntax (`*:`, `**:`, `data-*:`, `not-*:`) over `[&_...]` arbitrary selectors. - For a link styled as a button, put `buttonVariants(...)` on the `` - never `}>`. - Put `className` overrides on the wrapper component, not on the JSX passed to `render`. - Do not hand-roll a component that exists in the library. Check the component list first: https://appica.dev/llms.txt - Every documentation page is served as clean markdown at `.md` - fetch that, not the HTML.