# Reshaped ships React and Figma components from one monorepo with three npm packages > Reshaped is a TypeScript pnpm monorepo that publishes a styled React design system, a headless layer and a vanilla utilities package. This piece maps the three packages, the checks behind each release, and the questions the README leaves open. **reshaped-ui/reshaped** — Reshaped provides accessible React and Figma components for building beautiful products or starting your own design system - Repository: https://github.com/reshaped-ui/reshaped - Website: https://reshaped.so - Stars: 2,253 · Forks: 160 - Language: TypeScript - License: MIT - Published: 2026-10-14 · Updated: 2026-10-30 · Language: en - Canonical page: https://hysenlabs.com/projects/reshaped-ui-reshaped ## Three packages, split by how much styling you want from the library The README lists three packages and the split between them is the whole architecture of the project. reshaped is described as a React design system with components, hooks, utilities and design tokens. @reshaped/headless holds headless React components and utilities for building your own design system or product with custom styles. @reshaped/utilities is a framework-agnostic set of UI utilities written in vanilla TypeScript. That gives three entry points depending on what you already own. A team without a design system takes reshaped as is. A team with its own visual language and its own CSS takes @reshaped/headless and brings the styles. A team that is not on React, or that wants helper functions without components, has @reshaped/utilities. The repository root is named @reshaped/root in package.json, marked private, and described as the Reshaped monorepo root. Beyond the three above, the root scripts mention a @reshaped/theming package, which builds themes that the reshaped package then consumes. The README does not list it among the packages. ## The React library is synced with a Figma file The README makes one specific promise about the main package: its implementation is synced with the Reshaped Figma library, which is published as a Figma community file. That is the reason the project describes itself as React and Figma components, and it is the feature to check before choosing it. In practice the claim covers designers and developers working from the same component set. What the README does not say is how the sync happens, who updates which side first, or what the tolerance is when the two disagree. It gives no versioning link between Figma file revisions and npm releases. The description line on GitHub adds a second claim, that the components are accessible. The package.json for the monorepo includes @storybook/addon-a11y, which is the Storybook accessibility add-on, so there is an accessibility check wired into the component workshop. The README itself does not state which accessibility standard the components target, so treat the claim as unspecified until the documentation site says otherwise. ## Where the install steps live: nowhere in this repository The README has no install command. It gives a Documentation heading with one sentence and one link, to the getting started overview on reshaped.so. There is no code block and no package manager instruction in the README, so this article gives none either. That is a real cost for evaluation. A developer looking at the repository on GitHub cannot copy a command, see a minimal example, or learn the peer dependencies without leaving for another site. The package.json shown here belongs to the private monorepo root, and its version and dependency lists describe the workspace tooling, not what a consumer installs. The homepage is reshaped.so. The README points its documentation there, and the contribution guide sits in CONTRIBUTING.md in the repository, where it covers principles, development process and testing. For anything about using the components, the repository itself is silent and the documentation site is the only stated source. ## A pnpm workspace with Storybook, Chromatic and a size budget The root package.json pins packageManager to pnpm@11.5.2, and the layout includes pnpm-workspace.yaml, pnpm-lock.yaml and a packages directory. The dev script is pnpm -r --parallel run dev, build is pnpm -r run build, and clean runs the clean script in every workspace package. The quality checks are unusually specific. test:unit and test:browser run per package. test:vrt calls Chromatic for visual regression, built from a Storybook build in the chromatic environment and limited to changed stories. test:size builds the theming package, then the reshaped size bundle, and runs size-limit, so bundle growth is checked as part of testing. Linting is split three ways: oxlint with warnings denied, stylelint over packages/**/*.css with zero warnings allowed, and oxfmt for formatting. The devDependencies include Storybook 10.5.0 with the a11y, docs and vitest add-ons, and an @storybook/addon-mcp at 0.7.0. Contributors need pnpm and should expect a failing lint on any warning. ## Releases go through changesets, with canary builds ahead of stable ones The repository uses changesets: the .changeset directory exists, and package.json has a changeset script plus @changesets/cli and @changesets/changelog-github as dev dependencies. Release scripts are separate: release runs bin/release.sh, release:canary runs bin/release-canary.sh, and release:local runs bin/release-local.sh. The recent tags show the pattern. reshaped@4.2.0-canary.1 appeared on 2026-08-17, the stable reshaped@4.2.0 followed on 2026-09-08, and reshaped@4.3.0-canary.0 was published on 2026-10-22. A canary precedes each stable version, so anyone who installs from the canary tag is testing the next minor before it settles. The repository is not archived and the last push was on 2026-10-25. The latest stable version in the listing is 4.2.0, which means 4.3.0 exists only as a canary at this point. Pin exact versions in a production project if you do not want canary behaviour to reach you, and check the changeset notes before moving between minors. ## One named maintainer and an MIT license The README names a single maintainer, Dmitry Belyaev, with a handle on X. The project's only governance statement is the contribution guide, which the README describes as covering principles, development process and testing. Nothing in the README discusses a roadmap, a support policy or a code of conduct. The license is MIT, stated both in the README and in the root package.json. The repository also contains a LICENSE.md file. The README opens with a link to the Vercel open source program, which indicates the project takes part in it, though the README gives no further terms. A single named maintainer is a fact about the project, and the decision depends on how much you rely on the library. If you depend on Reshaped for a product, you depend on one person's attention for design tokens, hooks and the Figma file. The headless and utilities packages narrow that exposure only if you are willing to own the styling and keep the code if upstream slows down. ## A skills directory and tooling for AI assistants The repository root has a skills directory, and the Storybook dependency list includes an MCP add-on. The README does not explain either. They show up only as entries in the top-level listing and the devDependencies, so any claim about what they do for users would be a guess. What the listing does confirm is the shape of the working tree: .storybook for the component workshop, .czrc for commit conventions, lefthook.yml for git hooks, renovate.json for dependency updates, and .oxlintrc.json and .oxfmtrc.json for the linter and formatter. A contributor cloning the repository gets a pre-configured environment, but has to learn it from the files, since the README sends them to CONTRIBUTING.md. One limitation follows from all of this. The repository documents the process of building Reshaped well and the process of using it hardly at all. Component names, prop tables, theming options and the browser or React version range are all missing from the files supplied here, so check them on reshaped.so before you commit to it. ## Conclusion Choose Reshaped if you want finished React components that stay in step with a Figma library, or if you want the headless package as a base for your own styles. Look elsewhere if you need installation steps and API details inside the repository, since the README only links out to reshaped.so for both. Before adopting, open the documentation site, confirm the license terms in LICENSE.md match your use, and decide whether a project with a single named maintainer fits your support needs. ## FAQ ### what is reshaped open source Reshaped is a library of React and Figma components for building products or starting your own design system. It is MIT licensed and lives in the reshaped-ui/reshaped monorepo on GitHub. ### what is reshaped so reshaped.so is the project's homepage. The README sends readers there for the getting started documentation. ### reshaped vs shadcn The repository does not compare Reshaped with shadcn. What it states is that reshaped ships styled React components synced with a Figma library, while @reshaped/headless offers unstyled components for custom styles. ## Sources - [License: MIT](https://github.com/reshaped-ui/reshaped/blob/main/LICENSE) - [Project website](https://reshaped.so) - [README](https://github.com/reshaped-ui/reshaped/blob/main/README.md) - [Releases](https://github.com/reshaped-ui/reshaped/releases) - [reshaped-ui/reshaped on GitHub](https://github.com/reshaped-ui/reshaped) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/reshaped-ui-reshaped