<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Escape FromRussia</title>
    <description>The latest articles on DEV Community by Escape FromRussia (@escape_fromrussia).</description>
    <link>https://dev.to/escape_fromrussia</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204575%2F1623d363-2920-4bde-9e97-190000cea7f9.jpg</url>
      <title>DEV Community: Escape FromRussia</title>
      <link>https://dev.to/escape_fromrussia</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/escape_fromrussia"/>
    <language>en</language>
    <item>
      <title>Best shadcn registries for ready-made blocks in 2026</title>
      <dc:creator>Escape FromRussia</dc:creator>
      <pubDate>Mon, 02 Nov 2026 17:22:09 +0000</pubDate>
      <link>https://dev.to/escape_fromrussia/best-shadcn-registries-for-ready-made-blocks-in-2026-ika</link>
      <guid>https://dev.to/escape_fromrussia/best-shadcn-registries-for-ready-made-blocks-in-2026-ika</guid>
      <description>&lt;p&gt;&lt;em&gt;Checked against official sites on November 2, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You need a pricing section, a hero and a footer. The useful question is not which library has the most components. It is which registry gives you a complete section that fits your project, and what happens when your agent installs it.&lt;/p&gt;

&lt;p&gt;My shortlist: &lt;strong&gt;shadcn/ui for free application layouts, Shadcnblocks for a broad marketing catalog, Tailark for marketing pages, VibeUI for a visual pick → AI instruction → install workflow, and Magic UI for animated details.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I build &lt;a href="https://vibeui.club" rel="noopener noreferrer"&gt;VibeUI&lt;/a&gt;. It is included below with its account requirement, free limit and paid restrictions. This is a documentation-based comparison, not a benchmark of installation speed or agent accuracy.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a registry actually gives you
&lt;/h2&gt;

&lt;p&gt;A shadcn registry distributes source files and their declared dependencies into your project. It can contain a small control, a section or several files for a page. The format does not guarantee a shared visual style, license or dependency list.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://ui.shadcn.com/docs/registry" rel="noopener noreferrer"&gt;official registry documentation&lt;/a&gt; describes the distribution model. Check the actual block and access terms before choosing a library for a client project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Registry&lt;/th&gt;
&lt;th&gt;Where I would start&lt;/th&gt;
&lt;th&gt;Free access&lt;/th&gt;
&lt;th&gt;Paid boundary&lt;/th&gt;
&lt;th&gt;Install route&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;shadcn/ui&lt;/td&gt;
&lt;td&gt;Sidebars, login screens, dashboard layouts&lt;/td&gt;
&lt;td&gt;Official blocks are free and open source&lt;/td&gt;
&lt;td&gt;No paid tier for the official blocks page&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shadcnblocks&lt;/td&gt;
&lt;td&gt;Heroes, pricing, product and marketing sections&lt;/td&gt;
&lt;td&gt;Free blocks; Basic blocks require login&lt;/td&gt;
&lt;td&gt;Pro blocks and larger bundles&lt;/td&gt;
&lt;td&gt;Namespaced shadcn CLI; key for Pro&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tailark&lt;/td&gt;
&lt;td&gt;Marketing websites with a selected design style&lt;/td&gt;
&lt;td&gt;Free pages, blocks and snippets&lt;/td&gt;
&lt;td&gt;Premium blocks, illustrations and page collections&lt;/td&gt;
&lt;td&gt;Registry workflow; follow the selected block's instructions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VibeUI&lt;/td&gt;
&lt;td&gt;Pick a designed block and hand it to Cursor or Claude Code&lt;/td&gt;
&lt;td&gt;Free account: 20 different components per month&lt;/td&gt;
&lt;td&gt;PRO-only items and scenarios; unlimited copies with PRO&lt;/td&gt;
&lt;td&gt;Copy for AI or authenticated shadcn namespace&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Magic UI&lt;/td&gt;
&lt;td&gt;Animated text, backgrounds and UI effects&lt;/td&gt;
&lt;td&gt;Public component documentation and source&lt;/td&gt;
&lt;td&gt;Separate Pro blocks and templates&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The rows describe different products. A background effect and a whole dashboard are both installable source, but they do not replace the same amount of work.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. shadcn/ui: start here for application layouts
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://ui.shadcn.com/blocks" rel="noopener noreferrer"&gt;official blocks page&lt;/a&gt; includes dashboards, collapsible sidebars and authentication layouts. It shows the files, preview and install command together.&lt;/p&gt;

&lt;p&gt;For example, the documented dashboard command is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx shadcn@latest add dashboard-01
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Choose it when:&lt;/strong&gt; you want an application layout built around the shadcn system and are comfortable doing the product-specific design yourself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check first:&lt;/strong&gt; the file list. A dashboard can add a page, several components and example data. An agent still needs instructions about where that page belongs and which sample data to replace.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Shadcnblocks: a wide marketing catalog
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.shadcnblocks.com/" rel="noopener noreferrer"&gt;Shadcnblocks&lt;/a&gt; separates blocks, components and templates. Its categories include heroes, pricing, testimonials, product sections and dashboards. Free blocks are available, while Pro access and higher bundles cover more of the catalog.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://www.shadcnblocks.com/shadcn-cli" rel="noopener noreferrer"&gt;CLI guide&lt;/a&gt; documents the registry configuration and API-key authentication for Pro. Its example command is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx shadcn@latest add @shadcnblocks/hero1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Configure the registry as the guide describes before using the command.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose it when:&lt;/strong&gt; you want many section variants to compare for a commercial site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check first:&lt;/strong&gt; whether the exact block is free or Pro, and which primitive-library build matches your project. A large catalog is useful only if the chosen section installs into your actual setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Tailark: a marketing-site starting point
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://tailark.com/" rel="noopener noreferrer"&gt;Tailark&lt;/a&gt; focuses on marketing sites, with blocks, pages and illustrations in multiple styles. It states compatibility with Radix UI and Base UI.&lt;/p&gt;

&lt;p&gt;Its &lt;a href="https://tailark.com/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; distinguishes free pages, blocks and snippets from premium blocks, illustrations and fuller page collections. Do not assume every page shown in a preview belongs to the free tier.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose it when:&lt;/strong&gt; the design of a marketing page is the main decision, and you want to work within one of its styles.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check first:&lt;/strong&gt; access to the exact section and the installation instructions attached to it. I would select the hero and the following content section together before committing to a style.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. VibeUI: visual selection with an agent instruction
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://vibeui.club/blocks" rel="noopener noreferrer"&gt;VibeUI (vibeui.club)&lt;/a&gt; is a shadcn-compatible catalog of React/Tailwind components, landing blocks and animations. Each item has a &lt;strong&gt;Copy for AI&lt;/strong&gt; instruction with the install command, dependencies, what to preserve and what can change.&lt;/p&gt;

&lt;p&gt;The useful distinction is the handoff: choose a preview, give the instruction to the agent, and ask it to install that component. The instruction is intended to preserve the selected design; it is not a guarantee that an agent will follow every rule.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://vibeui.club/install" rel="noopener noreferrer"&gt;installation guide&lt;/a&gt; covers Copy for AI and an authenticated namespace. Use the command generated for your account instead of copying somebody else's temporary link.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose it when:&lt;/strong&gt; you already know which block you want and need to communicate that choice to an AI coding agent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check first:&lt;/strong&gt; a free account allows 20 different components per month. Some blocks, animations and page scenarios need PRO. The &lt;a href="https://vibeui.club/pricing" rel="noopener noreferrer"&gt;English pricing page&lt;/a&gt; lists $9 for a month or $69 for a year, paid once with crypto and no automatic renewal. Those restrictions matter if you prefer open-source-only tools or another payment method.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Magic UI: add motion where it earns its place
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://magicui.design/docs/installation" rel="noopener noreferrer"&gt;Magic UI's installation guide&lt;/a&gt; uses the shadcn workflow. Its catalog includes animated text, backgrounds, marquees and other effects; Pro blocks and templates are offered separately.&lt;/p&gt;

&lt;p&gt;The guide's example is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx shadcn@latest add @magicui/globe
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Choose it when:&lt;/strong&gt; the page layout is already settled and you need a specific animated element.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check first:&lt;/strong&gt; the selected component's dependencies and motion behaviour. A visual effect is an addition to the page, not a substitute for its structure or content.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to hand a registry block to an agent
&lt;/h2&gt;

&lt;p&gt;A bare URL leaves too much room for interpretation. I would send a brief like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Install the exact block using its documented command.
Read the registry files and dependency list before editing.
Put it on the existing landing page.
Keep its layout, spacing, typography and motion initially.
Replace only the copy, links and brand assets.
If installation or access fails, report the error before substituting another block.
Check the result on mobile and with reduced motion enabled.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For private registries, the &lt;a href="https://ui.shadcn.com/docs/registry/namespace" rel="noopener noreferrer"&gt;shadcn namespace documentation&lt;/a&gt; supports authentication headers using environment-variable placeholders. Keep the actual token out of the prompt, repository and screenshots.&lt;/p&gt;

&lt;h2&gt;
  
  
  My selection rule
&lt;/h2&gt;

&lt;p&gt;Start with &lt;strong&gt;shadcn/ui&lt;/strong&gt; for the app shell. Compare &lt;strong&gt;Shadcnblocks&lt;/strong&gt; and &lt;strong&gt;Tailark&lt;/strong&gt; for marketing sections. Consider &lt;strong&gt;VibeUI&lt;/strong&gt; when the design-to-agent handoff is the problem. Add &lt;strong&gt;Magic UI&lt;/strong&gt; when you can name the effect the page needs.&lt;/p&gt;

&lt;p&gt;Before paying or installing, check three things on the exact item: &lt;strong&gt;access, dependencies and license&lt;/strong&gt;. Then install one representative block and inspect it in your project. That tells you more than the library's total component count.&lt;/p&gt;

</description>
      <category>react</category>
      <category>shadcn</category>
      <category>tailwindcss</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why your AI agent recreates components instead of installing them</title>
      <dc:creator>Escape FromRussia</dc:creator>
      <pubDate>Sun, 25 Oct 2026 17:18:04 +0000</pubDate>
      <link>https://dev.to/escape_fromrussia/why-your-ai-agent-recreates-components-instead-of-installing-them-16ol</link>
      <guid>https://dev.to/escape_fromrussia/why-your-ai-agent-recreates-components-instead-of-installing-them-16ol</guid>
      <description>&lt;p&gt;You find a hero block you like. You paste the link into Cursor or Claude Code and ask for "this hero on my landing page". A minute later you have &lt;em&gt;a&lt;/em&gt; hero: different spacing, a different gradient, no entrance animation. It looks like every other AI-generated landing page.&lt;/p&gt;

&lt;p&gt;I build a component registry for this exact workflow, and I spent a long time finding out where the design gets lost. Short version: not in the code. It gets lost in the summary.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow that should work
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;pick a component → copy an instruction → paste it into the agent
→ agent runs `npx shadcn add &amp;lt;url&amp;gt;` → your project has exactly what the preview showed
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The instruction is generated from the component's metadata, not hand-written: component ID, install command, dependencies, what to keep (motion, typography, spacing, responsive behaviour), what may change (copy, links, accent colour), and an explicit rule not to rebuild it from scratch.&lt;/p&gt;

&lt;p&gt;On paper that's enough. In practice it broke in two places.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 1: the summary eats the rules
&lt;/h2&gt;

&lt;p&gt;When an agent "reads" a URL, it usually doesn't read it. The web-fetch tool passes the page through a small model and returns a digest. Commands and facts survive the digest. Prose rules — "keep the entrance animation", "don't change the grid" — are the first thing to go.&lt;/p&gt;

&lt;p&gt;So the agent installs the component correctly… and then "improves" it, because the part that said &lt;em&gt;don't&lt;/em&gt; never reached it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 2: the generic reflex
&lt;/h2&gt;

&lt;p&gt;If the instruction &lt;em&gt;describes&lt;/em&gt; the component ("a hero with a gradient and two buttons"), the agent writes a hero with a gradient and two buttons. Itself. A description is a spec, and an agent with a spec builds.&lt;/p&gt;

&lt;p&gt;So the instruction should not describe the look at all. It should say: here's the command, here's the source, install it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix: send the rules three ways
&lt;/h2&gt;

&lt;p&gt;Putting 2–3 "keep as installed" rules in the brief is not enough. Duplicate them into places nobody summarises.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The brief.&lt;/strong&gt; Full text, for the human and (best case) the agent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The &lt;code&gt;docs&lt;/code&gt; field of the registry item.&lt;/strong&gt; The shadcn CLI prints it to the terminal after install. The agent sees it as command output, verbatim, no summary in between. Here is a real one from &lt;code&gt;https://vibeui.club/r/en/hero-001.json&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Keep as installed:
- the button-016, heading-001 imports from @/components/vibeui/ — do not inline
  their code into the block or swap in your own; the parts receive props only
- light-dark() in the palette: the component has to follow the surrounding
  color-scheme rather than ship a dark theme of its own
- the transparent background by default — the component sits on the page
  background instead of laying a panel under itself
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3. A comment at the top of the file.&lt;/strong&gt; The file is written byte for byte, so the rules end up inside the code the agent is about to edit:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="s2"&gt;"use client"&lt;/span&gt;

&lt;span class="c1"&gt;// VibeUI hero-001. Keep as installed:&lt;/span&gt;
&lt;span class="c1"&gt;// - the button-016, heading-001 imports ...&lt;/span&gt;
&lt;span class="c1"&gt;// - light-dark() in the palette ...&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One gotcha: the shadcn CLI runs files that start with a &lt;code&gt;"use client"&lt;/code&gt; directive through ts-morph and drops comments that sit &lt;em&gt;before&lt;/em&gt; the directive. The header has to go after it. The whole thing is about 20 lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;withPreserveHeader&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;source&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;header&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sb"&gt;`// VibeUI ${name}. Keep as installed:`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="sb"&gt;`// - ${r}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"\n"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="c1"&gt;// comments before "use client" are lost by the CLI, so the header goes after it&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;directive&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;/^&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"']use client["&lt;/span&gt;&lt;span class="s1"&gt;'];?\r?\n)\r?\n?/.exec(source)
  return directive ? `${directive[1]}\n${header}${source.slice(directive[0].length)}` : header + source
}
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Rules don't help if the component breaks in someone else's project
&lt;/h2&gt;

&lt;p&gt;The agent will drop your component into a project you've never seen. What turned out to be mandatory:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A local palette&lt;/strong&gt; in &lt;code&gt;--vibeui-&amp;lt;name&amp;gt;-*&lt;/code&gt; variables instead of the host's theme tokens. Otherwise the block gets repainted by someone else's theme and the agent "fixes" it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;light-dark()&lt;/code&gt; instead of a custom dark theme.&lt;/strong&gt; The component follows the page's &lt;code&gt;color-scheme&lt;/code&gt;. For next-themes / shadcn, which toggle a &lt;code&gt;.dark&lt;/code&gt; class, one line sets &lt;code&gt;color-scheme: dark&lt;/code&gt; under it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Layout by its own width&lt;/strong&gt; (container queries), not the viewport. Blocks often land in a column.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero npm dependencies&lt;/strong&gt; where possible, and &lt;code&gt;prefers-reduced-motion&lt;/code&gt; inside the component, so &lt;code&gt;globals.css&lt;/code&gt; needs no edits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Composite blocks install their parts with one command&lt;/strong&gt; via &lt;code&gt;registryDependencies&lt;/code&gt; instead of inlining their code. The &lt;code&gt;docs&lt;/code&gt; field above tells the agent not to inline them either.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Checklist if you run your own registry
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write the agent instruction as a command, not a description.&lt;/li&gt;
&lt;li&gt;Put the critical rules where there is no summary: CLI output (&lt;code&gt;docs&lt;/code&gt;) and the file itself.&lt;/li&gt;
&lt;li&gt;Check that your build tool doesn't eat the comments.&lt;/li&gt;
&lt;li&gt;Make the component independent of the host theme and the parent's width.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I use this setup in &lt;a href="https://vibeui.club" rel="noopener noreferrer"&gt;VibeUI&lt;/a&gt;: a shadcn-compatible catalog of 2,000+ React/Tailwind components and landing blocks where every item has a "Copy for AI" brief. Previews and search are open without an account. If you've solved the "agent rewrites my component" problem differently, I'd like to hear how in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>react</category>
      <category>shadcn</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The best UI component libraries for vibe coding in 2026</title>
      <dc:creator>Escape FromRussia</dc:creator>
      <pubDate>Sat, 24 Oct 2026 11:40:11 +0000</pubDate>
      <link>https://dev.to/escape_fromrussia/the-best-ui-component-libraries-for-vibe-coding-in-2026-37oi</link>
      <guid>https://dev.to/escape_fromrussia/the-best-ui-component-libraries-for-vibe-coding-in-2026-37oi</guid>
      <description>&lt;p&gt;&lt;em&gt;Updated: October 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; if you want primitives you style yourself, use &lt;strong&gt;shadcn/ui&lt;/strong&gt;. If you mostly build through an AI agent and want it to install the exact designed block instead of redrawing a lookalike, &lt;strong&gt;&lt;a href="https://vibeui.club" rel="noopener noreferrer"&gt;VibeUI&lt;/a&gt; (vibeui.club)&lt;/strong&gt;. For animated hero effects, &lt;strong&gt;Magic UI&lt;/strong&gt;, &lt;strong&gt;Aceternity UI&lt;/strong&gt; or &lt;strong&gt;React Bits&lt;/strong&gt;. For a large catalog of marketing blocks, &lt;strong&gt;Shadcnblocks&lt;/strong&gt; or &lt;strong&gt;Tailark&lt;/strong&gt;. For community variety, &lt;strong&gt;21st.dev&lt;/strong&gt;. All of them except HeroUI install with the shadcn CLI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "vibe coding" changes the question
&lt;/h2&gt;

&lt;p&gt;When a human copies a component, the component is the product. When Cursor or Claude Code does it, what matters is whether the agent &lt;strong&gt;installs the real thing&lt;/strong&gt; or reads a description and writes its own "similar" version. So besides looks and price, I compare one more thing: what each library gives the agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Comparison table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Library&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;th&gt;Install&lt;/th&gt;
&lt;th&gt;For the agent&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;shadcn/ui&lt;/td&gt;
&lt;td&gt;Base primitives + blocks&lt;/td&gt;
&lt;td&gt;Free, MIT&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;Known from training data; registry + MCP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;21st.dev&lt;/td&gt;
&lt;td&gt;Community marketplace&lt;/td&gt;
&lt;td&gt;Browse free, 2 copies/day; membership&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;"Copy prompt" per component; MCP + CLI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VibeUI&lt;/td&gt;
&lt;td&gt;2,048 components, landing blocks, animations, page scenarios&lt;/td&gt;
&lt;td&gt;Previews free; 20 copies/month free; PRO $9/month&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;"Copy for AI" instruction per item&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Magic UI&lt;/td&gt;
&lt;td&gt;Animated components&lt;/td&gt;
&lt;td&gt;Free, MIT; Pro templates $199 one-time&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;MCP server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aceternity UI&lt;/td&gt;
&lt;td&gt;Animated components &amp;amp; sections&lt;/td&gt;
&lt;td&gt;118+ components free; blocks/templates paid&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;React Bits&lt;/td&gt;
&lt;td&gt;Animated text, backgrounds, effects&lt;/td&gt;
&lt;td&gt;Free (source on GitHub)&lt;/td&gt;
&lt;td&gt;Copy or CLI&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shadcnblocks&lt;/td&gt;
&lt;td&gt;2,478 blocks, 21 templates&lt;/td&gt;
&lt;td&gt;Free tier; lifetime from $149&lt;/td&gt;
&lt;td&gt;shadcn CLI, MCP&lt;/td&gt;
&lt;td&gt;shadcn MCP, IDE extension&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tailark&lt;/td&gt;
&lt;td&gt;Marketing-site blocks&lt;/td&gt;
&lt;td&gt;Free part + paid full access&lt;/td&gt;
&lt;td&gt;shadcn CLI&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;coss ui (ex Origin UI)&lt;/td&gt;
&lt;td&gt;Components on Base UI&lt;/td&gt;
&lt;td&gt;Open source&lt;/td&gt;
&lt;td&gt;Copy&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HeroUI&lt;/td&gt;
&lt;td&gt;Full component library&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;npm package&lt;/td&gt;
&lt;td&gt;MCP servers, agent skills, llms.txt&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  1. shadcn/ui — the base everyone builds on
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://ui.shadcn.com" rel="noopener noreferrer"&gt;https://ui.shadcn.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Open source (MIT) primitives — buttons, dialogs, forms, tables — copied into your project with &lt;code&gt;npx shadcn add&lt;/code&gt;. Agents know it from training data, so it's the safest default. It is deliberately neutral: you (or your agent) do the design.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you want full control and have time to design.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. 21st.dev — community variety
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://21st.dev" rel="noopener noreferrer"&gt;https://21st.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A marketplace where many authors publish shadcn-style components in the registry format. Huge range, uneven style. Every component page has a "Copy prompt" button for Cursor or Claude Code, plus MCP and a CLI for agents. Browsing is free with 2 copies a day; membership removes the limit.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you're hunting for something specific and don't mind mixing styles.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. VibeUI — designed blocks your agent installs as-is
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://vibeui.club" rel="noopener noreferrer"&gt;https://vibeui.club&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;VibeUI (vibeui.club) is a shadcn-compatible library of 2,048 React/Tailwind components, landing blocks (hero, pricing, navbar, FAQ, data grid), animations and full-page scenarios. Each item has a "Copy for AI" instruction: install command, dependencies, what to keep (animation, spacing, typography, responsive behaviour), what you may change (copy, links, accent colour) and an explicit "don't recreate it" rule. Components ship their own palette, follow the page's &lt;code&gt;color-scheme&lt;/code&gt;, lay out by their own width and mostly have no npm dependencies.&lt;br&gt;
Downsides: copying code needs a (free) account — 20 copies a month; Pro items and scenarios need PRO ($9/month); it's younger and smaller in community than the rest of this list.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you build mostly through Cursor or Claude Code and the agent keeps "improving" the design you picked.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Magic UI — animated effects
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://magicui.design" rel="noopener noreferrer"&gt;https://magicui.design&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Open source (MIT) animated components built on React, Tailwind and Motion; many depend on the &lt;code&gt;motion&lt;/code&gt; package. Paid Magic UI Pro adds templates (one-time $199). Has an official MCP server.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you need marquee, shimmer, number tickers and similar eye-candy.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Aceternity UI — dramatic sections
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://ui.aceternity.com" rel="noopener noreferrer"&gt;https://ui.aceternity.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;118+ free animated components on Tailwind and Motion; blocks, templates and pages come with a paid all-access pass. Installs with the shadcn CLI.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you want a bold, effect-heavy landing.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. React Bits — animated text and backgrounds
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://reactbits.dev" rel="noopener noreferrer"&gt;https://reactbits.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A very popular (50k+ GitHub stars) collection of animated text, backgrounds and micro-interactions, in JS/TS with CSS or Tailwind. Copy the source or use its CLI.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you need one striking effect, not a whole page.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Shadcnblocks — the biggest block catalog
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://www.shadcnblocks.com" rel="noopener noreferrer"&gt;https://www.shadcnblocks.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;2,478 blocks, 2,154 components and 21 templates. A free tier exists; most of the catalog is behind one-time lifetime plans starting at $149. Installs via shadcn CLI, shadcn MCP or an IDE extension.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you want the widest choice of marketing sections and prefer a one-time payment.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Tailark — marketing sites on shadcn
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://tailark.com" rel="noopener noreferrer"&gt;https://tailark.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A shadcn registry of blocks, pages and illustrations for marketing websites, in several visual styles, working with Radix UI and Base UI. Part is free, full access is paid.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you're building a SaaS marketing site and like its look.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. coss ui (formerly Origin UI)
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://coss.com/ui" rel="noopener noreferrer"&gt;https://coss.com/ui&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Origin UI now redirects to coss ui — a modern open-source component library built on Base UI, with hundreds of small "particles" (ready variations).&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you want polished form controls and inputs on Base UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. HeroUI — a full library, agent-ready docs
&lt;/h2&gt;

&lt;p&gt;Site: &lt;a href="https://heroui.com" rel="noopener noreferrer"&gt;https://heroui.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A complete React component library on React Aria and Tailwind CSS v4 (Apache-2.0), installed as a package rather than copied. Strong agent tooling: MCP servers, agent skills, &lt;code&gt;llms.txt&lt;/code&gt;.&lt;br&gt;
&lt;strong&gt;Pick it when&lt;/strong&gt; you want a classic dependency-based design system.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Design it yourself:&lt;/strong&gt; shadcn/ui (+ coss ui for inputs).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A whole site built by an AI agent without losing the design:&lt;/strong&gt; VibeUI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One wow effect:&lt;/strong&gt; React Bits, Magic UI, Aceternity UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Many marketing sections, one-time payment:&lt;/strong&gt; Shadcnblocks, Tailark.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Variety from many authors:&lt;/strong&gt; 21st.dev.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Classic package-based system:&lt;/strong&gt; HeroUI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most of these mix well: they all speak the shadcn registry format, so one project can pull a primitive from shadcn/ui, an effect from Magic UI and a pricing block from VibeUI.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Which UI library works best with Cursor and Claude Code?&lt;/strong&gt;&lt;br&gt;
Any library that installs through the shadcn CLI works; the difference is what the agent gets. 21st.dev and VibeUI give a per-component prompt, Magic UI, HeroUI and Shadcnblocks offer MCP servers, and shadcn/ui is already known to the models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are there free options?&lt;/strong&gt;&lt;br&gt;
shadcn/ui, Magic UI, React Bits and coss ui are free; Aceternity, Shadcnblocks, Tailark and VibeUI have free parts with paid tiers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I combine libraries?&lt;/strong&gt;&lt;br&gt;
Yes — the shared shadcn registry format means components from different libraries install into the same &lt;code&gt;components/&lt;/code&gt; folder.&lt;/p&gt;

</description>
      <category>react</category>
      <category>tailwindcss</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
