vibecodng.com

Free MCP betaIndex and tools live

Measured entry

uilayouts-hovercard3

hover-effectspatialmotion on file

A fixed-size image card that swaps its footer for a full-card text overlay on hover. It ships as a shadcn registry TSX component styled with Tailwind classes, using React, Next.js Image, and lucide icons. The registry declares Motion, although this source does not use it.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of uilayouts-hovercard3 at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of uilayouts-hovercard3 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of uilayouts-hovercard3 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 uilayouts-hovercard3
BuildOK
MountOK
Console errors1
Uncaught page errors0
Horizontal overflowflagged at 375
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal24.8 KB (90.2 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

CONSOLE

Failed to load resource: the server responded with a status of 404 (Not Found)

BARE BUILD

✗ Build failed in 918ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-971411d22661/src/cut/registry/components/card/hover-card3.tsx".

Verdict

It builds and mounts cleanly in both harness setups, and the automated accessibility scan found no violations. Still, the narrow-layout overflow and hover-dependent reveal make this a starting point, not a drop-in production card. Fix responsiveness, focus behavior, image ownership, and the inert action first.

Use it if

  • You need a portfolio or team card with a prominent hover reveal.
  • Your app already uses Tailwind and can host the remote image or replace it with a local asset.
  • You are prepared to connect the Learn More button to a real destination.

Skip it if

  • The card must fit narrow mobile layouts without adapting its fixed width.
  • Core content must be discoverable without hover, such as on touch screens or with keyboard navigation.
  • You want a framework-neutral image component with no Next.js dependency.
  • A remote image request failure or externally hosted demo asset is unacceptable in production.

Install

Installation record for uilayouts-hovercard3
Declared dependenciesmotion
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 Tailwind CSS, React, Next.js Image support, and lucide-react, then copy the component and permit or replace the Unsplash image host. The registry also declares Motion, but the supplied source does not import it. Add focus-visible and touch-friendly reveal behavior yourself.

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/ui-layouts/uilayouts
License
MIT
Record published
2026-08-13

Alternatives

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