vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-mist-faqs-2

faqminimal-flat

A client-side FAQ section shipped as a shadcn registry block. It renders hard-coded questions in a responsive Tailwind grid, uses Next.js Link for the support prompt, and imports accordion primitives through the local component alias. Its registry also depends on Tailark's Mist accordion item.

Specimen
Harness screenshot of tailark-mist-faqs-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-faqs-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-faqs-2 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 tailark-mist-faqs-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal57.8 KB (123.2 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 909ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-accordion" from "<sandbox>re-aa26eff4d2a6/src/components/ui/accordion.tsx".

Verdict

Do not adopt it unchanged: the build fails because the registry resolves the Mist accordion dependency to a missing endpoint. It needs a shadcn-style setup and a working local accordion implementation before its rendering or accessibility can be verified.

Use it if

  • You already use Next.js, Tailwind theme tokens, and shadcn-style component aliases.
  • You want a compact FAQ section with single-item, collapsible accordion behavior.
  • You are willing to repair or replace the unresolved Mist accordion dependency before adoption.

Skip it if

  • You need a registry item that installs and builds without manual dependency repair.
  • Your project does not use Next.js or shadcn-style local UI primitives.
  • Your FAQ content must come from a CMS or data API without modifying the component.
  • You need verified runtime or accessibility behavior, since the failed build prevented mounting.

Install

Installation record for tailark-mist-faqs-2
Declared dependenciesclsx, tailwind-merge
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

A non-shadcn project must add compatible accordion primitives, recreate the component alias, provide Tailwind utilities and semantic theme tokens, and replace Next.js Link if the app uses another router. The broken Tailark registry dependency must be bypassed or corrected.

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/tailark/blocks
License
MIT
Record published
2026-08-15

Alternatives

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