Skip to main content

BentoGrid

Layout

Responsive CSS-grid container.

import { BentoGrid } 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 BentoGrid 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 BentoGrid up before writing code: `npx -y @elabs-ai/components-cli docs BentoGrid` 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

5 live examples

Interactive

Clickable tiles via the stretched-link pattern: an inner `<a className="absolute inset-0">` makes the whole tile a single link, and `interactive` gives it a pointer cursor + a `focus-within` ring (keyboard-visible).

Spotlight

The cursor-following spotlight is OPT-IN. Set `spotlight` on the `BentoGrid` to enable it for every tile; a tile's own `spotlight` prop still wins, so one tile can opt back out. Suppressed entirely under OS reduced-motion — the hover elevation carries the interaction on its own there.

Explicit Spans

Explicit `span` overrides the size presets for bespoke layouts.

Edge States

Edge states: a very long unbroken string (must not overflow) and a per-tile spotlight opt-in.

API

BentoGrid

PropTypeDescription
classNamestringAdditional className merged via cn().
spotlightbooleanEnable the cursor-following spotlight on every tile in this grid. Individual tiles can still opt out (or in) with their own `spotlight` prop. Disabled entirely under OS `prefers-reduced-motion` regardless of this prop. @default false

Also accepts: HTMLAttributes<HTMLDivElement>

BentoGridItem

hero
truefalse (default)
interactive
truefalse (default)
PropTypeDescription
sizeBentoGridSizeSize preset. Resolves to a col + row span. Overridden by explicit `span`. @default "sm"
span{ col?: number; row?: number }Explicit grid span. Wins over `size`. Spans clamp gracefully on narrow layouts — a `col: 4` on a 2-col grid becomes `span min(4, 2)`.
spotlightbooleanEnable the cursor-following spotlight gradient on this tile. Omit to inherit the parent `BentoGrid`'s `spotlight` (itself `false` by default) — so the effect is opt-in, per grid or per tile. Disabled entirely under OS `prefers-reduced-motion` regardless of this prop. @default false (inherited from BentoGrid)

Also accepts: HTMLAttributes<HTMLDivElement>, BentoGridItemVariants