Measured entry

cultui-feature-carousel

carouselliquid-glassmotion on file

An animated product-feature carousel shipped as a shadcn registry client component for Next.js. It combines Motion transitions, Next Image, react-wrap-balancer, clsx, Tailwind utility classes, a local cn helper, and a global CSS rule for its cursor-following card effect. Its step labels and descriptions are embedded in the source.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of cultui-feature-carousel at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of cultui-feature-carousel at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of cultui-feature-carousel 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 cultui-feature-carousel
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal78.7 KB (144.1 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 50.43s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/ui/feature-carousel.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished, specialized starting point for a product tour, but not a drop-in general carousel. It needs a shadcn-style setup, and teams should plan to fix the hardcoded copy, final asset, click behavior, and noisy debug logging before production use.

Use it if

  • You want an auto-advancing product walkthrough built around layered screenshots.
  • Your app already uses Next.js, Tailwind, and shadcn-style path aliases and utilities.
  • You are comfortable editing the source to replace the bundled step copy and final asset.

Skip it if

  • You need slide content to come from props, a CMS, or an arbitrary data array.
  • You need conventional carousel controls, since the step labels do not select slides and the card advances through a full-cover click target.
  • You cannot host the fixed final-step asset or revise the source to use the provided image data.
  • You want a lightweight carousel without a substantial animation dependency cost.

Install

Installation record for cultui-feature-carousel
Declared dependenciesmotion, react-wrap-balancer
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, add Motion, react-wrap-balancer, clsx, Next Image support or an equivalent image adapter, Tailwind with the referenced theme utilities, an alias-backed cn helper, the animated-cards global CSS rule, and the final-step image asset.

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.

Alternatives

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