Sections

FeatureMatrix

Comparison table showing which features each plan includes

Quick Preview

Features	Starter	Pro	Enterprise
Core
Projects	3	Unlimited	Unlimited
Team members	1	5	Unlimited
Storage	1 GB	50 GB	Custom
Support
Email support	✓	✓	✓
Priority support	—	✓	✓
Dedicated manager	—	—	✓

Installation

# No extra dependencies

// Copy component from
src/components/sections/FeatureMatrix.tsx

Usage

import FeatureMatrix from '@/components/sections/FeatureMatrix'

<FeatureMatrix
  plans={[{ name: 'Starter' }, { name: 'Pro', highlight: true }]}
  features={[{
    category: 'Core',
    items: [{ feature: { name: 'Projects' }, coverage: ['3', 'Unlimited'] }]
  }]}
/>

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a sections component named FeatureMatrix in React/Next.js.
Goal: recreate the same overall UI and behavior as the FeatureMatrix reference from a component gallery.
What it needs to communicate: Comparison table showing which features each plan includes.

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Treat the result as a full-width section with strong layout rhythm and responsive spacing.
- Preserve headline hierarchy, supporting copy, and clear CTA emphasis.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- plans: Plan[] — Column headers (plan names)
- features: FeatureGroup[] — Grouped feature rows with coverage per plan

Reference usage patterns:
- Default

```tsx
<FeatureMatrix plans={[]} features={[]} />
```

Feature expectations:
- Sticky header row
- Category grouping
- Boolean/string coverage cells
- Highlighted plan column

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`plans`	`Plan[]`	-	Column headers (plan names)
`features`	`FeatureGroup[]`	-	Grouped feature rows with coverage per plan