brand-ui — NavNotifications

import { NavNotifications } from "@elabs-ai/components-ui";

Install

npm install @elabs-ai/components-tokens @elabs-ai/components-ui

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui NavNotifications component (from @elabs-ai/components-ui) to this project.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Look NavNotifications up before writing code: `npx -y @elabs-ai/components-cli docs NavNotifications` prints its real props, variants, what it pairs with and what to avoid.
3. If @elabs-ai/components-ui is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
4. Use it here: [the screen or file, and what it should show]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

Examples

3 live examples

Top Bar Placement

The top-bar placement: `side="bottom" align="end"` puts the menu under the bell and flush with its outer edge. The caller passes NOTHING else — the rail's 24px vertical inset is derived from `side` inside the component, so a bottom-side menu drops it on its own and there is no inset to cancel here. (`className` styles the bell TRIGGER, not the portalled menu, so a `my-0` override would land on the wrong element anyway.) Asserted on Radix's own resolved `data-side`/`data-align`, which report where the menu ACTUALLY landed after collision handling — a class-name assertion would pass on a menu that flipped back across the controls beside it.

Custom Trigger Class

`className` styles the component ROOT — the bell trigger — and merges LAST, so a caller-supplied radius replaces the shipped `rounded-full`.

API

`NavNotifications`

Prop	Type	Description
`notifications`required	`NavNotification[]`
`viewAllLabel`	`string`	Label for the "view all" footer item. @default "View all notifications"
`side`	`ComponentProps<typeof DropdownMenuContent>["side"]`	Which side of the trigger the menu opens on. The default is `"right"`, which is right for the surface this component was extracted from — a bell sitting in a left-hand nav rail. It is WRONG for a trigger at the end of a top bar: Radix collision-handling then flips the menu back across the trigger and it covers the controls beside it. Set `side="bottom"` (usually with `align="end"`) for a top-bar bell. @default "right"
`align`	`ComponentProps<typeof DropdownMenuContent>["align"]`	How the menu aligns along that side. Radix's own default is `"center"`; pass `"end"` so a top-bar menu hangs from the trigger's outer edge instead of straddling it.
`className`	`string`	Extra classes for the component ROOT — the bell trigger — merged last, so a caller can override the shipped `rounded-full` (`component-api.md`). There is deliberately NO seam for the portalled menu surface: nothing needs one today, and an unused prop is a worse API than a missing one. The one thing a caller used to reach for it (dropping the rail's vertical inset for a top-bar menu) is now derived from `side` instead — see below.