Two steps, no setup screen
Your coding agent learns where the finished sections live, then builds pages from them instead of from scratch.
01 Run this in your project
Adds the MCP server to Claude Code, Cursor or Codex.
02 Then ask for a page
Build a pricing page with three plans and a yearly toggle.
The agent picks a finished section, drops it in and matches your theme.
A centred install hero that explains itself in two numbered steps under a ruled line: run the command, copied from a rounded pill on click, then ask for a page, shown as an example prompt in a muted mono panel. Serif headline settles in word by word, one sliding-marker pill below.
An install hero that explains itself in two numbered steps under a rule: run the command on the left, and see the sentence you would type next on the right.
Upgrade to Pro
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://ui.beste.co/r/hero191?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/hero191?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/hero191.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.
The installed file exports hero191Demo alongside the block: the exact props behind the preview above. Spread it to get a working hero in one line.
import { Hero191, hero191Demo } from "@/components/beste/block/hero191";
export default function Page() {
return <Hero191 {...hero191Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Hero191 } from "@/components/beste/block/hero191";
export default function Page() {
return (
<Hero191
eyebrow="Two steps, no setup screen"
heading="Install once. Ask forever."
description="Your agent learns where the finished sections live, then builds from them."
install={{
number: "01",
title: "Run this in your project",
command: "npx your-cli@latest",
copyLabel: "Copy command",
copiedLabel: "Copied",
note: "Adds the MCP server to your agent.",
}}
ask={{ number: "02", title: "Then ask for a page", prompt: "Build a pricing page with three plans." }}
buttons={[{ label: "See what it builds", href: "/blocks" }]}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
eyebrow | string | – | Small-caps line above the headline |
heading | string | – | Headline, rendered as the page h1 through Text1 |
description | string | – | Paragraph under the headline |
install | Install | – | The first step, whose pill copies the command |
ask | Ask | – | The second step, shown as an example prompt |
buttons | ActionButton[] | [] | Pill actions centred below both steps |
className | string | – | Extra classes for the outer <section> |
type Install = {
number: string;
title: string;
command: string;
copyLabel: string;
copiedLabel: string;
note?: string;
};
type Ask = {
number: string;
title: string;
prompt: string;
note?: string;
};
type ActionButton = {
label: string;
href: string;
tone?: "primary" | "light" | "dark" | "outline";
};trigger="mount" and everything after it is offset from the word count, so the steps arrive after the last word lands.