Typed Ruby components
Closed Phlex APIs make component vocabulary explicit and verifiable.
A UI kit Rails applications and agents can understand
Caller-owned customer outcomes add evidence without introducing testimonial components.
- Typed components
- 36
- Direct Phlex APIs
- Template helpers
- 0
- Rails helpers still welcome
- Theme variables
- 84
- Light and dark ready
Static, themeable CSS
Gem-owned styles use documented custom properties without runtime compilation.
Rails-native forms
Model values, errors, names, multipart behavior, and submission semantics stay intact.
Built with application teams
Fixed example outcomes demonstrate public proof without putting marketing claims into Nitro components.
| Organization | Outcome | Detail |
|---|---|---|
| Analytical Engines | 42% fewer interface regressions | A single typed vocabulary replaced six project-specific component wrappers. |
| Orbital Research | 18 production flows verified | Agents compose Rails screens from the same documented components engineers review. |
| North Sea Systems | Zero runtime styling dependencies | Static CSS ships with the gem and adapts through organization theme variables. |