vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-card-carousel-hero

hero-effectunclassifiedmotion on file

A client-side Next.js hero that presents a centered headline above a fanned stack of image cards animated with GSAP. It ships as a shadcn registry item and imports the project Card and Button primitives, Tailwind utility classes, the Next Image component, and an alias-based utility used by the Card primitive. The registry also declares Motion, although this component does not import it.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-card-carousel-hero at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of ruixen-card-carousel-hero at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of ruixen-card-carousel-hero 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-card-carousel-hero
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal63.3 KB (128.7 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 32.22s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished entrance effect, but the source behaves more like a static fanned card display than an interactive carousel. It builds and mounts in the prepared harness, yet it overflows on narrower layouts and needs a shadcn-style setup. Choose it when the visual composition matters more than carousel behavior.

Use it if

  • You want a cinematic entrance for a fixed set of promotional image cards beneath hero copy.
  • Your Next.js app already uses Tailwind, shadcn primitives, path aliases, and GSAP.
  • You are prepared to tune the card spread for narrower layouts.

Skip it if

  • You need an actual carousel with navigation, autoplay, gestures, or changing active cards.
  • Horizontal overflow on phone and tablet layouts is unacceptable without modification.
  • You want a lightweight hero without GSAP and extra registry dependencies.
  • Your app is not based on Next.js or cannot use the Next Image component.

Install

Installation record for ruixen-card-carousel-hero
Declared dependenciesmotion, gsap, radix-ui
Missing on installgsap
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

For a non-shadcn project, add Tailwind, GSAP, the Next Image equivalent or an adapted image element, Button and Card primitives, the configured component and library path aliases, and the class-merging utility required by the Card primitive. Remove the unused Motion dependency if your integration does not use it, and revise the layout rules to prevent narrow-screen overflow.

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 hero-effect pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.