vibecodng.com

Free MCP betaIndex and tools live

Measured entry

cultui-three-d-carousel

hero-effect3dmotion on file

A client-side React photo carousel shipped as a shadcn registry source file. It arranges a fixed set of remote Picsum images around a draggable cylinder and opens a clicked image in an overlay. It depends on React hooks, Motion, Tailwind utility styles, browser media queries, and network access for its demo images.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of cultui-three-d-carousel at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of cultui-three-d-carousel at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of cultui-three-d-carousel at 1440 pixels wide
Harness screenshot at 1440 pixels wide. This viewport scrolled sideways.

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 cultui-three-d-carousel
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal61.2 KB (126.6 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 579ms
error during build:
[vite]: Rollup failed to resolve import "motion/react" from "<sandbox>re-b5e2dafd9d14/src/cut/components/ui/three-d-carousel.tsx".

Verdict

It builds and mounts on its own, but it overflows every tested viewport and the narrow capture does not visibly show the carousel. Treat it as a strong visual prototype, not a drop-in component, unless you can refactor its sizing, data API, and interaction semantics.

Use it if

  • You want a dramatic, draggable image ring for an editorial hero or visual showcase.
  • Your React app already uses Motion and Tailwind, and you are comfortable adapting registry source.
  • Remote image loading and a client-only interaction are acceptable for the page.

Skip it if

  • You need a responsive component that stays within its container without layout work.
  • You need product data or caller-supplied slides because the image list is fixed inside the component.
  • You require keyboard-operable slide selection and dialog semantics without an accessibility refactor.
  • You want a lightweight static hero with no animation runtime or remote image dependency.

Install

Installation record for cultui-three-d-carousel
Declared dependenciesnone declared
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, copy the client component, add React and Motion, configure Tailwind for the utility classes and the mauve background token, and allow images from Picsum or replace the fixed URLs. Provide a client-component boundary where your framework requires one.

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/nolly-studio/cult-ui
License
MIT
Record published
2026-08-13

Alternatives

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