Introduction

Feature Kits is a collection of opinionated, composable building blocks for real product workflows. It helps product engineers build forms, data listings, application layout, and spreadsheet imports without rebuilding the same state and interaction patterns for every screen.

The repository is a pnpm monorepo. The ui package provides primitives and tokens; feature/* packages compose those primitives into workflow-level APIs. The host application still owns domain data, API calls, permissions, and business rules.

The composition modelCopy Anchor Link

UI primitives
    ↓
Feature-level composition
    ↓
Workflow patterns
    ↓
Production application screens

Choose a lower-level UI component for a local control. Choose a feature kit when the screen needs behavior such as validation, URL state, selection, import validation, or confirmation flows.

How to read these docsCopy Anchor Link

Pages follow a consistent structure (similar to shadcn/ui app docs):

1. When to use — choose the right kit or API
2. Installation — workspace dependency + import
3. Preview + code — toggle between live UI and sample source
4. Recipes — common combinations (URL sync, server errors, bulk actions)
5. API reference — props and exports aligned with source types
6. Troubleshooting — practical integration pitfalls
7. Examples — focused previews under /docs/examples

Kits at a glanceCopy Anchor Link

Start hereCopy Anchor Link

1. Read Getting started to run the playground.
2. Review Architecture to understand ownership boundaries.
3. Follow Installation and Providers for app integration.
4. Build a form or data table.

Examples indexCopy Anchor Link

All runnable previews live under Examples—form field matrices, table filters, layout chrome, and uploader configs. Use them as regression fixtures when upgrading kits in your fork.