Scopes
Acme
@acmeBehive Tech
@behivetechLatest releases
@behivetech/organisms.hero-bannerv0.7.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
@behivetech/atoms.badgev0.4.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
@behivetech/atoms.buttonv0.4.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
@behivetech/atoms.cardv0.4.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
@behivetech/atoms.checkboxv0.4.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
@behivetech/atoms.drawerv0.4.0a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from `--md-sys-*` tokens, and each one falls back to the pre-MD3 `--color-*` name. Hardcoded brand colors and `filter: brightness()` are gone, so components follow the theme in both light and dark.
How it works
The folder tree is the registry
registry/<scope>/<category>/<name> becomes @<scope>/<category>.<name>. Ownership, docs, props and versions all derive from files in the repo — nothing to keep in sync.
Organizations own scopes
A Clerk Organization is a scope. Sign in, and the active org decides which components you manage; nothing in a URL can name another scope's data.
Docs generated, not written twice
react-docgen reads each component's TypeScript for the props table; compositions become live, editable examples; the README is rendered with its snippets running.
Versioned and published
Changesets bump semver and write the changelog; packages publish to GitHub Packages. The registry shows what each scope shipped, and when.
Add a component to your scope
Three commands from an empty folder to a documented, versioned package:
1pnpm gen # scope → category → name; scaffolds registry/<scope>/…2pnpm changeset # describe the change; Changesets bumps the version3pnpm release # build + publish @<scope>/<category>.<name> to GitHub Packages