vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-faq-chat-accordion

chatunclassifiedmotion on file

A client-side React FAQ styled as a chat thread: question buttons open one answer bubble after a typing indicator. It ships as a shadcn registry TSX file and depends on React, motion/react, Tailwind theme utilities, and the shadcn cn helper.

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

Verdict

A polished, focused choice for playful support FAQs, with clean single-answer behavior and no observed runtime or accessibility issues in the configured harness. It needs a shadcn-style setup; a bare React project will not resolve its utility helper or styling assumptions.

Use it if

  • You want a compact FAQ to feel like a support conversation rather than a standard disclosure list.
  • Only one answer should stay open, and a short simulated reply delay fits the product tone.
  • Your app already uses shadcn-style Tailwind tokens and Motion.

Skip it if

  • Users need to scan several answers at once or compare responses side by side.
  • Your content is formal, high urgency, or task critical, where a typing simulation would add needless friction.
  • You require reduced-motion behavior out of the box; the component includes continuous dot animation and scripted transitions without its own preference handling.

Install

Installation record for ruixen-faq-chat-accordion
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

Install Motion, provide Tailwind with the foreground, background, muted, border, and muted-foreground theme tokens, add a compatible cn utility at the configured alias, and preserve client-component support. Also add a reduced-motion override if your accessibility policy 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/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

Alternatives

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