vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-mist-content-1

cardminimal-flat

A client-side React content section that pairs marketing copy with decorative code-list and scheduling-toolbar illustrations. It ships as a shadcn registry block and expects Tailwind theme tokens, a cn utility, Lucide icons, plus Tailark button and toggle-group registry components.

Specimen
Harness screenshot of tailark-mist-content-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-content-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-content-1 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-content-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal41.5 KB (106.9 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 786ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-1d0574375e4d/src/cut/components/content-1.tsx".

Verdict

Do not adopt it unchanged: the build fails because the mist-button registry dependency resolves to a missing resource. It also needs a shadcn-style setup. Teams needing a dependable drop-in component should avoid it until the registry reference is fixed or the dependency is replaced locally.

Use it if

  • You want a responsive feature narrative with contrasting text and product-interface illustrations.
  • Your app already follows shadcn conventions and you are willing to repair or replace the unresolved Tailark registry dependencies.
  • You need a static product-marketing section whose copy and mock controls can be adapted in source.

Skip it if

  • You need a registry block that installs and builds without repairing dependency references.
  • Your design system does not provide shadcn-style theme tokens, utility aliases, buttons, and toggle groups.
  • You need the illustrated controls to perform real editing or scheduling actions rather than serve as presentation.

Install

Installation record for tailark-mist-content-1
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 Tailwind-compatible theme tokens and utilities, a cn helper, Lucide React icons, and local button and accessible toggle-group primitives. Replace the broken Tailark button registry reference before attempting the build.

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