@mind-studio/ui

A shadcn-native, multi-brand design system for Mind projects. Ships React components, theme tokens, and blocks, with a generated styles.css token sheet.

Published to GitHub Packages under the MIND-Studio org.

Install (consumers)

GitHub Packages requires authentication even for public packages, so each consumer repo needs a scoped .npmrc:

# .npmrc
@mind-studio:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}

Then set NODE_AUTH_TOKEN to a GitHub PAT with read:packages (in CI, the job's GITHUB_TOKEN works for same-org repos), and:

npm install @mind-studio/ui

Wire the styles in your globals.css (Tailwind v4):

@import "tailwindcss";
@import "../../node_modules/@mind-studio/ui/dist/styles.css"; /* real path, not the exports subpath */
@source "../../node_modules/@mind-studio/ui/dist";

Publishing (maintainers)

pnpm build            # gen:css → bunchee → copy-styles
npm version <patch|minor|major>
npm publish           # publishConfig points at npm.pkg.github.com

Requires a token with write:packages (gh auth refresh -s write:packages,read:packages). The package links to its repo via the repository field in package.json.

Develop

pnpm storybook        # component workbench on :6006
pnpm test             # vitest
pnpm typecheck

See PRD.md / GOAL.md / GLOSSARY.md for design rationale.

Releases

Versioning, CHANGELOG.md, and tags are automated with release-please — don't tag or edit CHANGELOG.md by hand.

1. Commit to main using Conventional Commits: fix: → patch, feat: → minor, feat!: / BREAKING CHANGE: → major. chore: / docs: / refactor: / test: don't trigger a release.
2. release-please keeps an open "chore(main): release X.Y.Z" PR that rolls the pending commits into CHANGELOG.md and bumps the version.
3. Merge that PR to release: it creates the vX.Y.Z tag + GitHub Release, which fires publish.yml to publish the package to GitHub Packages.