Components you actually own.

Copy the file into your repo, remap the tokens, and ship. React and Tailwind, free under MIT.

Laptop showing code on a bright desk next to a monitor
npx paubha@latest add button
NorthwindHelixParcelOrbitKiteSummit

Why own the code

Dependencies change under you. A file in your repo does not.

  • The file lands in your repo

    add writes into components/ui. There is no package to upgrade and no black box between you and the markup.

  • Remap tokens, not components

    Every color, radius and shadow reads from semantic tokens. Change the brand blue once and the whole set follows.

  • Fork it without asking

    MIT on the full catalog. Delete a variant, rename a prop, ship it to production.

33 base components and 27 patterns, built to be edited

A hand pinning a user-flow map onto a wall of app screens

Patterns for whole screens

Tables, date pickers, activity feeds and dashboards, built from the same base components.

We never share it.

Tab to the field. The glow-focus ring comes with the file.

BrandSuccessWarning

Light and dark ship together, bound to one token layer.

Close-up of syntax-highlighted code on a screen
Overhead view of a shared desk covered in laptops, notebooks and phones

Accessibility tests ship with every component.

“We stopped buying template kits. The focus ring alone made the product feel like ours.”

Maren Holloway

Design Lead, Northwind

“I read the Button source in ten minutes and changed it in five.”

Dario Quintela

Staff Engineer, Helix

“Tests and keyboard behavior were already there. Review got shorter.”

Leila Marchetti

Product Manager, Parcel

Add your first component in a minute

Run init once, then add what you need.

npx paubha@latest init
npx paubha@latest add button

New components, once a month

One short email when new patterns land. Unsubscribe any time.

Paubha updates

No spam, just the changelog.