Introduction
Paubha is a set of beautifully designed, accessible components and an open code distribution approach. Built to work with your favorite frameworks and AI models. Open source. Open code.
This is not just a component library. It is how you build your product library.
Traditional component libraries ask you to install a package, import components, and accept their constraints. The moment you need to customize beyond what the library exposes, you find yourself fighting the abstraction: wrapping components, overriding styles, or mixing incompatible APIs from multiple libraries.
Paubha works differently. Every component is yours. The source lives in your project, follows your conventions, and is as easy to read, edit, and extend as any code you wrote yourself.
Built on five principles
Paubha is organized around five ideas that we believe should be true of every design system your team ships.
Open Code
The top layer of every Paubha component is open for modification. When you add a component to your project you receive the full source, not a minified bundle, not a black box. Read it, understand it, and adapt it to your product without any workarounds.
Composition
Every component uses a common, composable interface. Primitives combine predictably, props are consistent across the system, and every layout decision is intentional. You compose features; you don't fight the framework.
Distribution
A flat-file schema and command-line tool make it trivially easy to distribute components across projects and teams. Publish once; consume anywhere, with full control over versioning and change management.
Beautiful Defaults
Carefully chosen typography, spacing, color semantics, and motion defaults mean you get great-looking interfaces out of the box. Defaults are a starting point, not a constraint: override any token or variant without losing coherence across the rest of the system.
AI-Compatible
Paubha is designed to be read and understood by large language models. The open-code approach means AI tools can inspect, reason about, and generate components that are immediately compatible with your existing design system, no special plugins or integrations required.
Paubha ships a skill.md file: a short, machine-readable guide to
the CLI, the design tokens and the component conventions. Drop it into your AI
tool's context window (or add it as a skill) and the tool will generate
components and layouts that match Paubha from the first prompt.
skill.md
Conventions, tokens and install steps for AI tools. Plain Markdown, always in sync with the registry.
Staying up to date
Teams that maintain a dedicated design-system branch find this pattern simple: merge upstream changes into the branch, resolve conflicts with full visibility, then promote to your main codebase on your own schedule.
Deploy your app
Paubha works with any deployment target. Export to React, Vue, Svelte, or use our Figma-native JSX format to hand off pixel-perfect designs. The same semantic token layer drives both design and code, so there is never a gap between what the designer specified and what the engineer ships.