The @rtorcato React monorepo — a pnpm workspace that publishes reusable
React packages to the public npm registry. The repo itself is private and
unpublished; the umbrella name react-common is the brand and the docs-site
identity.
📖 Docs: https://docs.torcato.dev/react-common/
| Package | Description |
|---|---|
@rtorcato/shadcn-ui |
React 19 shadcn/ui component library — shadcn/ui + Radix primitives, extended components, Tailwind CSS v4. Dir: packages/shadcn-ui. |
@rtorcato/react-common |
Foundation package — headless hooks, the cn class-merge utility, and ThemeProvider. Dir: packages/react-common. |
apps/docs is the private Docusaurus site (@rtorcato/react-common-docs).
pnpm add @rtorcato/shadcn-ui # shadcn/ui components (pulls in @rtorcato/react-common)
pnpm add @rtorcato/react-common # hooks, cn, ThemeProvider (standalone)
# react & react-dom 19 are peer dependenciesAn in-repo skill teaches AI coding tools to use the packages correctly (barrel
vs subpath imports, styles.css + Tailwind setup, theming).
Claude Code — install the self-hosted skill:
/plugin marketplace add rtorcato/react-common
/plugin install react-common@react-common
Any agent with the skills CLI —
install the skill straight from GitHub, no clone or package install:
npx skills add https://github.com/rtorcato/react-common --skill react-commonOther tools (Cursor / Copilot / Codex) — read AGENTS.md,
the cross-tool convention many agents pick up automatically. It stays in sync
with the Claude skill in skills/react-common/SKILL.md.
Requires Node ≥ 24 and pnpm 11 (see .nvmrc / packageManager).
pnpm install
pnpm verify # typecheck + biome check + tests, across all packages
pnpm build # build every package (build-prod)Scripts run recursively (pnpm -r) across the workspace. Tooling (TypeScript,
Biome, Vitest, Commitlint, Husky, CI) is shared from
@rtorcato/repo-tooling — run
npx @rtorcato/repo-tooling doctor to check for drift.
main is protected; work happens on branches and merges via PR:
git switch -c feat/short-name origin/main
# …conventional commits + `pnpm changeset` for anything user-facing…
git push -u origin feat/short-name
gh pr create --fill
gh pr merge --auto --squash --delete-branch # ships when CI is greenReleases are driven by Changesets:
merging PRs with changesets does not publish. The release workflow
(.github/workflows/release.yml, on every push to main) opens or updates a
"Version Packages" PR. Merging that PR, plus one approval, publishes the changed
packages to npm. See RELEASING.md for the full flow,
npm-token requirements, and the public-API change checklist.
ISC © Richard Torcato