Spotlighting

Production-ready React hooks you can copy, adapt, and ship.

useKit turns reusable React hooks into a toolkit you can browse, copy, or install fast. The goal is simple: fewer throwaway utilities, less package churn, and cleaner patterns getting into production faster.

155+

hooks ready to copy or install

CLI

registry access through `uselab`

TS

TypeScript-first patterns throughout

Faster path to shipped code

Use the docs as a catalog and the CLI as a shortcut.

Registry install
npx uselab@latest add use-network-status

Pull a hook into your project, inspect the code, and keep only the pieces that deserve to stay.

What you get

You stop rebuilding the same browser wrappers and state helpers under deadline pressure.

Why it matters

Hooks stay editable, readable, and close to the product code that depends on them.

Starter paths

docs + CLI + source

Why teams use it

Practical hooks for the browser, state, async flows, and interface details that show up in real applications.

Copy-paste first

Use the registry as a source of clean patterns instead of another runtime dependency to drag through every app.

CLI when speed matters

Pull hooks straight into a project with `uselab` when you want faster setup, repeatability, and less manual wiring.

Built for real product work

The collection leans toward browser APIs, async control, state ergonomics, and UI behaviors teams reach for repeatedly.

Workflow

Keep the good parts of a library without inheriting its weight.

The strongest part of useKit is not just the number of hooks. It is the delivery model: discover the pattern, pull it into your codebase, and keep control of the final abstraction.

Step 1

Find the right primitive

Browse the registry by problem space and scan hooks that already solve the awkward pieces of browser and UI state.

Step 2

Install or inspect quickly

Use the CLI for speed, or read the docs and source directly when you want a pattern you can reshape for your own stack.

Step 3

Adapt without lock-in

Keep only the code you need, rename it, trim it, and let it become part of the application instead of another abstraction layer.

Ready when you are

Start with the catalog, then use the CLI when you want fewer steps between idea and implementation.

    A collection of reusable react hooks - useKit