Why Forza?
Forza is a styled Vue library for teams that want its visual direction: condensed display typography, compact geometry, a restrained accent palette, and coordinated interaction states. You can install the package or copy source with the CLI.
It is an early library. Choose it because the components fit your application, not because it claims to replace every alternative.
How this project is made
Forza UI is an independent project by Chrisdalbano, developed with AI assistance. Chrisdalbano sets the direction and reviews the visual experience. AI tools assist with research, implementation, documentation, and automated checks.
This includes AI-generated code and copy. The repository makes the implementation and checks available for inspection; it does not claim that every change has had an independent human code review.
Compared with shadcn-vue
| Decision | Forza UI | shadcn-vue |
|---|---|---|
| Starting point | A defined visual and motion language | A broader foundation you adapt into your own system |
| Styling | Scoped CSS variables; no Tailwind requirement | Tailwind-based styling with CSS-variable theming |
| Component interface | Higher-level wrappers with props, slots, and parent-owned state | More primitive composition and a wider range of components |
| Delivery | npm package, versioned GitHub releases, or source-copy CLI | Source installation and an established registry ecosystem |
| Current scope | 25 components in an early 0.x release | A substantially broader catalog, including calendars, command menus, and sidebars |
Both offer editable source, typed Vue code, and accessible primitives through Reka UI. Source ownership, CSS variables, and AI-readable code are not exclusive advantages of Forza. Neither primitive selection nor automated checks removes the need to test accessibility in your finished application.
Forza's distinction is the set of design decisions supplied together. Its smaller API can make common compositions direct; it can also be limiting when you need behavior the wrapper does not expose. Inspect the component API before committing to it.
Choose Forza when
- Its typography, density, colors, and feedback suit your product.
- You prefer props-driven components and CSS tokens without adopting Tailwind.
- The existing catalog covers your first workflows and you can maintain an early dependency.
Choose shadcn-vue when breadth, registry integrations, or more direct primitive composition matter more than Forza's supplied visual treatment. There is no universal winner.
What is available today
The component index and workbench use the current library catalog. The library and source-copy CLI are published to npm. Versioned GitHub Release assets are also available. The installation guide contains the supported commands.
The marketing site's GSAP choreography is separate from the library. Installing a button does not install the landing page's animation system. Component motion uses CSS, Reka primitives, AutoAnimate for list changes, and Embla for the carousel where appropriate.
References
This comparison is based on shadcn-vue's own introduction, component catalog, theming guide, and registry directory, reviewed September 17, 2026. Both projects will continue to change.