npx @buoy-design/cli status

One command.
See every component.

Don't have a formal design system? Doesn't matter. See what's actually in your codebase.

Your component inventory.

Every component in your codebase, listed and categorized. Finally, clarity.

Terminal
$ npx @buoy-design/cli status
Component Alignment
โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›โ›
46/46 components ยท 100% aligned
Aligned:
NavigationPartial
LayoutCshtml
FooterCshtml
SidebarCshtml
BannerCshtml
PaginationPartial
ShareButtonsCshtml
SocialsPartial
LoginPartialCshtml
MessagesPartial
TagsPartialCshtml
LabelsPartialCshtml
PhotoViewerPartial
RecaptchaCshtml
TurnstileCshtml
... and 31 more
โœ“ 46 components discovered.
๐Ÿคฏ

"I never knew all these components existed in our code."

That's the moment. You finally see what's there โ€” the building blocks you can affect, improve, document, and design for. No more guessing. No more "I think we have a sidebar somewhere."

Now you know what's there.

Use this list to build a real design system โ€” or just understand what you're working with.

๐ŸŽจ
Match to Figma
Create Figma components for each one. Build your design library from code truth.
๐Ÿ“–
Add to Storybook
Know exactly which components need stories. Prioritize what matters.
๐Ÿ–ผ๏ธ
Sync with Framer
Build prototypes with the real components your codebase actually has.
๐Ÿ“
Document
Create a component inventory. Share it with your team. Everyone knows what exists.

You can't design for components you don't know exist. Now you know.

The codebase is a black box.

For designers, code has always been invisible. You know your Figma file. You don't know the codebase.

The Old Way
โ“
"What components do we actually have?"
โ“
"Is there already a sidebar component?"
โ“
"Where's the navigation partial?"
โ“
"What can I actually affect as a designer?"
๐Ÿคท
Ask a developer. Wait. Maybe get an answer.
With Buoy
$
npx @buoy-design/cli status
โšก
...2 seconds later...
๐Ÿ“ฆ
NavigationPartial, LayoutCshtml, FooterCshtml, SidebarCshtml, BannerCshtml...
โœ“
Every component. Listed. Named. Visible.

No formal design system? Perfect.

You don't need tokens or Storybook to use Buoy. It finds what's already there.

๐Ÿ“ฆ
"What components exist?"
Get a complete inventory of every reusable piece in your codebase.
๐Ÿ”
"Where's that sidebar thing?"
Find components by name. See exactly where they live.
๐Ÿ—๏ธ
"What are the building blocks?"
See layouts, partials, views โ€” the architecture of your UI.
๐ŸŽฏ
"What can I design for?"
Know which components exist so you can create matching designs.
๐Ÿ“‹
"What needs documenting?"
Use the list to prioritize which components to add to Storybook.
๐Ÿš€
"Where do I start?"
This list IS your starting point. Build your design system from here.

One language. Two audiences.

Whether you're a designer or a frontend engineer, the output speaks to you.

๐ŸŽจ
For Designers
Design System Leads
  • โœ“ See if your design system is actually being used
  • โœ“ Prove adoption with real numbers
  • โœ“ Find where tokens are being bypassed
  • โœ“ No code knowledge required
โšก
For Engineers
Frontend Developers
  • โœ“ Quick codebase health check before PRs
  • โœ“ Find and fix drift during development
  • โœ“ Exact file paths and line numbers
  • โœ“ Integrates with CI/CD pipelines

Just one line.

No install. No config. No learning curve.
Copy, paste, understand.

npx @buoy-design/cli status

Works with React, Vue, Svelte, Angular, and more.