Get from zero to first install.
Wensity is a component library you install with a CLI. You don't add a runtime package to your dependencies. The CLI copies real .tsx files into your project, and you own the code from that moment on.
Most libraries ship as a versioned npm package. Wensity instead lands source in your repo so your linter, formatter, and team can treat each file like local code. Every component has a live preview, an install command, and a usage snippet. Free components install without an account. Pro components and blocks can be previewed by anyone, but source unlocks only when your session or CLI token has an active component license.
This page walks through the shortest path from browsing the gallery to shipping your first component, then explains when you need an account and how Pro access works.
The short path
Open the component gallery. Pick a preview, read the tagline, and open the Code tab when you are ready to install.
Run wensity init once in your project root. It writes wensity.json and a small cn() helper.
Run wensity add <slug> to copy the component into src/components/wensity by default.
Import the file like any local component. Review the git diff, then ship.
For framework requirements, peer dependencies, and troubleshooting, see the Installation guide.
Browse the library
Every component detail page has two tabs:
Preview shows the live component so you can judge fit before touching your repo.
Code shows install options. CLI is the default path for teams. Manual shows dependencies, source, and usage for copy-paste review.
Pro components show the preview to everyone. Source stays locked until your session has an active component license.
Start at /components. Free items install immediately. Pro items are marked in the registry metadata.
Install a free component
Run these commands from your project root. liquid-multimodal-input is a free component and works well for a first install.
$npx wensity init
$npx wensity add liquid-multimodal-input
Import the installed file like any local component:
import { LiquidMultimodalInput } from "@/components/wensity/liquid-multimodal-input";export default function Page() {return (<main className="grid min-h-screen place-items-center"><LiquidMultimodalInput placeholder="Ask anything" /></main>);}
wensity add will not overwrite an existing file. Use wensity update <slug> when you want to replace your local copy with a fresh upstream version, then review the diff.
When you need an account
You can browse previews and install free components without signing in. Create an account when you need any of the following:
Dashboard API tokens for Pro CLI installs.
Pro component or block source in the browser.
Billing history and license status.
Paid template downloads from the marketplace.
Free vs Pro
Anyone can preview and install source. No license required.
Anyone can preview. Source unlocks only for signed-in users with an active component license.
Component name, category, preview, install metadata, and access flag are public. Raw Pro source is only returned by authenticated, license-aware endpoints.
Pro blocks follow the same license rules as Pro components. Signed-in Pro users can view source in the browser, and the CLI can install premium blocks with wensity add <block-slug> --type block after login.
Unlock Pro source
- Choose a component plan on pricing.
- Return to the component or block page. Signed-in Pro users see source in the browser immediately after the license is active.
For CLI installs, create an API token in the dashboard, then run:
$npx wensity login
After login, wensity add <pro-slug> fetches source from /api/cli/<slug>. If the token is revoked, the next authenticated request fails immediately.
See Billing for plan details and API tokens for token limits and revocation behavior.
Before you ship
Run wensity init once and commit wensity.json.
Install one free component and import it from @/components/wensity/<slug>.
Confirm Tailwind v4 theme tokens are present in your global CSS. See the Theming guide if colors look wrong.
Create a dashboard API token before any Pro CLI install.
Review the git diff after every wensity add or wensity update.