brand-ui — FeatureGrid

import { FeatureGrid } from "@elabs-ai/components-marketing";

Install

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

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 FeatureGrid component (from @elabs-ai/components-marketing) 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 FeatureGrid up before writing code: `npx -y @elabs-ai/components-cli docs FeatureGrid` prints its real props, variants, what it pairs with and what to avoid.
3. If @elabs-ai/components-marketing is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-marketing` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-marketing`). 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.

Avoid

Three identical icon-tile-above-heading cards — the canonical landing-page tell; vary the structure (bento, split, asymmetry).
Shipping placeholder feature copy as real content — a dead showcase reads as a demo.

Works with

Pairs with

Examples

5 live examples

Two Columns

Four Columns

No Icons

Ruled

`ruled` — dashed hairline dividers between padded cells instead of a gap. Wrap it in `hairline-frame` (as here) and the rails run past the grid's corners and fade, so the block reads as one drawing rather than a boxed table.

API

`FeatureGrid`

Prop	Type	Description
`features`required	`Feature[]`
`columns`	`2 \| 3 \| 4`
`ruled`	`boolean`	Rule the grid with dashed hairlines: each cell becomes a padded panel separated from its neighbours by a `--hairline-*` rule, and the gap closes. The lines are drawn as cell edges clipped by the grid, so every column count and every wrap is ruled correctly with no per-breakpoint bookkeeping. Default `false` — the open, gapped grid.
`animate`	`boolean`	Stagger the cells in on mount. Motion-gated. Defaults to true.
`className`	`string`