Measured entry
hextaui-team-prompt-library
A client-side team prompt catalog with search, category filters, prompt cards, favorites, usage actions, deletion, and a creation dialog. It ships as a shadcn registry block built from React, lucide icons, Radix-backed UI primitives, Tailwind classes, and a local class-name utility; persistence is supplied through callbacks.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 78.4 KB (143.8 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 28s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/team/team-prompt-library.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A credible starting point for an internal prompt library, with useful callback boundaries and responsive empty-state behavior. It needs a shadcn-style setup before it will mount in a bare app, and the current color contrast should be corrected before production use.
Use it if
- You need a ready-made interface for teammates to browse, filter, and reuse shared prompts.
- Your app already uses shadcn-style primitives, Tailwind theme tokens, and path aliases.
- You can connect the supplied callbacks to your own prompt storage and authorization rules.
Skip it if
- You need a standalone package that works without adopting shadcn-style project conventions.
- You require an accessibility-clean component without first adjusting the muted text and control colors.
- You expect built-in persistence, permissions, confirmation flows, or server integration.
- You want categories driven entirely by application data rather than editing the component's fixed category list.
Install
| Declared dependencies | @radix-ui/react-avatar, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-dropdown-menu, @radix-ui/react-label, @radix-ui/react-separator, @radix-ui/react-select |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add the referenced Radix packages and lucide-react, provide React and Tailwind, recreate the imported avatar, badge, button, card, dialog, dropdown, empty-state, field, input-group, select, separator, and textarea primitives, define the theme tokens, add the local class-name helper, and configure matching path aliases. Then wire the action callbacks to real data services.
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/preetsuthar17/HextaUIAlternatives
Other published entries for the team pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-team-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.4KB
- Bare
- pass
- Prov
- NO
- meraki-team-side-by-sideminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- meraki-team-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-team-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.1KB
- Bare
- pass
- Prov
- NO
- hyperui-team-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.2KB
- Bare
- pass
- Prov
- NO
- meraki-team-backgroundminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.5KB
- Bare
- pass
- Prov
- NO