Why UiPool?
UiPool helps teams see, measure, and improve design system adoption across real code—not just intentions.
As frontends grow, UI patterns and components multiply fast, spreading across pages, repos, and teams. Over time, it gets harder to answer simple questions:
- Which patterns are actually used, and where?
- Which components are used but not mapped to the design system?
- Which patterns exist in code but have no docs?
- Are we still shipping deprecated UI?
- What changed since the last release?
UiPool makes those answers obvious by connecting code annotations to a shared workspace of patterns and components, then turning each scan into a clear, actionable view of what's happening in production code.
The problem
Most teams track UI consistency through a mix of design files, Storybook, and tribal knowledge. But the real source of truth is the codebase—and codebases drift:
- Patterns get implemented without documentation
- Components get copied, renamed, or forked without mapping
- Deprecations linger quietly and keep shipping
- Adoption progress is hard to quantify, so it's hard to prioritize
When you can't measure it, it's easy to debate it.
The solution
UiPool introduces a lightweight workflow:
- 1Annotate patterns and components where they're implemented
- 2Scan your repo with the CLI
- 3Upload the scan to UiPool
- 4Act on what's missing, unmapped, or deprecated
Each scan surfaces what matters most:
Coverage
Documented patterns vs undocumented, mapped components vs unmapped
Hotspots
The files that drive the most usage (and risk)
Needs attention
The top offenders you can fix first
Trends over time
Compare scans to see improvement (or regression)
What you get
- A shared, searchable inventory of patterns + components
- A repeatable way to track adoption and compliance
- A practical bridge between design system intent and implementation reality
- A simple path to cleaner UI: document what's used, map what's real, retire what's old
Where to start
If you're new to UiPool: