vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-floating-toolbar

inputgradient-glowmotion on file

A compact floating control that combines selectable filter tabs with an expanding search field. It ships as a client-side React component from a shadcn registry, styles itself with Tailwind utility classes, and uses Motion for layout changes, hover feedback, and spring transitions. Callbacks expose tab and query changes.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-floating-toolbar at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-floating-toolbar at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-floating-toolbar at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for ruixen-floating-toolbar
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal61.3 KB (126.7 KB build, 65.4 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

A polished, focused option for filterable lists when the combined tabs-and-search interaction matches the product. It works without framework-specific providers, but the global keyboard listener and Motion cost deserve scrutiny for such a compact control.

Use it if

  • You need a small filter bar that can switch into search without opening a separate panel.
  • Your interface already uses a dark neutral palette and animated micro-interactions.
  • You can wire its tab and search callbacks into your own filtering logic.

Skip it if

  • Your app already assigns the global search shortcut or escape key to another command surface.
  • You need full tab semantics, controlled selection state, or URL-backed navigation out of the box.
  • You want a lightweight static control and cannot justify adding Motion for one toolbar.
  • Your design system cannot accommodate its dark, utility-class-driven styling without a rewrite.

Install

Installation record for ruixen-floating-toolbar
Declared dependenciesmotion
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn project, copy the client component, install Motion, and ensure React and Tailwind are configured to compile its utility classes. No context provider or shared shadcn primitive is required.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Author repository

github.com/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the input pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.