vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-arc-reveal-hero

herounclassifiedmotion on file

A client-side React hero transition that cycles configurable greetings, then lifts an animated SVG arc to expose supplied page content. It ships as a shadcn registry component, uses Motion for sequencing and reduced-motion handling, and expects Tailwind theme classes plus the usual cn utility alias.

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

Verdict

A polished, configurable reveal with clean mounting, responsive containment, reduced-motion behavior, and no detected accessibility violations. It needs a shadcn-style setup because the bare project cannot resolve its shared utility import.

Use it if

  • You want a full-screen branded intro before revealing custom hero content.
  • You need configurable greeting copy, timing, styling hooks, and optional session replay suppression.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and Motion.

Skip it if

  • Visitors must reach the primary hero content immediately without waiting through an intro sequence.
  • You are minimizing client-side animation dependencies or JavaScript bundle cost.
  • Your design system does not provide Tailwind utilities and background or foreground theme tokens.

Install

Installation record for ruixen-arc-reveal-hero
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, install Motion, provide a cn class-merging helper at the expected alias or change the import, configure that alias, and supply Tailwind with background and foreground theme tokens. Render it from a client-capable React boundary.

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