vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hyperui-team-3

teameditorial

A static team roster laid out as a responsive grid of circular portraits, names, and roles. It ships as raw HTML styled with Tailwind utility classes, with no component library or runtime dependency. The sample portraits load from Unsplash, so production use depends on replacing or deliberately retaining those remote assets.

Specimen
Harness screenshot of hyperui-team-3 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hyperui-team-3 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hyperui-team-3 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 hyperui-team-3
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal17.4 KB (82.8 KB build, 65.4 KB baseline)
Bare modeOK
Provider requiredNO
Demo usednone

Verdict

A dependable, low-complexity roster for teams that already use Tailwind. It builds and mounts cleanly, stays within the tested viewports, and introduces no accessibility findings, but the repeated placeholder content and remote portraits must be replaced before launch.

Use it if

  • You need a compact staff or contributor grid that adapts cleanly across common viewport sizes.
  • Your project already processes Tailwind utility classes and you want markup that is easy to populate from team data.
  • Portraits are decorative beside visible names and roles, matching the source's empty image alternatives.

Skip it if

  • You need biographies, social links, contact actions, or expandable profiles without extending the markup.
  • Your design system does not use Tailwind and translating the utility classes would cost more than recreating the layout.
  • Each portrait must convey information that is not already present in nearby text, because the supplied images have empty alternatives.

Install

Installation record for hyperui-team-3
Declared dependenciesnone declared
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn project, add a Tailwind-compatible CSS pipeline or translate the utility classes into local styles. Copy the HTML into your template or component layer, replace the sample names, roles, and Unsplash URLs, and add meaningful image alternatives when portraits carry information. No shadcn package or provider 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/markmead/hyperui
License
MIT
Record published
2026-08-13

Alternatives

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.