Button group
Locked Segment
A group where the unavailable option explains itself: a padlock, a striped fill and a reason wired to the input through aria-describedby.
React + Tailwind, shadcn-compatible: press “Copy for AI” and your Cursor or Claude Code agent installs it with the shadcn CLI.
What you can change
- the options and their locked flag through options
- the initially selected option through defaultValue
- the reason text through reason and its id through reasonId
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.club/c/buttongroup-016?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
How to use
<Buttongroup016
options={[{ label: "Draft" }, { label: "Published", locked: true }]}
defaultValue="Draft"
reason="Only an editor can publish."
reasonId="status-reason"
/>A sample call. The agent installs the component itself from the registry via the “Copy for AI” link.
Settings
- Selected
defaultValue· default: Under review- Reason
reason· default: Only an editor can publish: your role lacks the right.- Accent
accent· default: theme colour- Background
background· default: theme colour
More in Button group
FAQ
- How do I add Locked Segment with Cursor or Claude Code?
- Press “Copy for AI” on this page and paste it into your agent's chat. The instruction contains the shadcn CLI install command, the dependencies and what to keep, so the agent installs this exact component instead of recreating a lookalike.
- What does Locked Segment depend on?
- No npm packages beyond React and Tailwind CSS.
- What can I change in Locked Segment?
- Adapt: the options and their locked flag through options; the initially selected option through defaultValue; the reason text through reason and its id through reasonId. Keep as installed: the local --vibeui-buttongroup-016-* palette — do not swap it for your theme tokens; the real disabled on the locked input: without it the option stays reachable from the keyboard; aria-describedby on the locked option — otherwise the reason exists for sighted users only.
- Is Locked Segment free?
- Yes. The preview is open without an account; with a free account you can copy up to 20 components a month.
For developers
npx shadcn@latest add https://vibeui.club/r/pro/buttongroup-016.jsonThis command needs a signed link: sign in and open “Component source” below — it issues a working link valid for 30 minutes. All install options
Technical notes
The component is self-contained: one file, no dependencies, its own palette in the --vibeui-buttongroup-016-* variables. It is a server component: there are no hooks, and the choice is held by radios inside a fieldset. The locked option gets a real disabled — visual "greying" without it would leave the segment clickable from the keyboard. The reason lies as a paragraph under the group and is tied to the unavailable input through aria-describedby, so it is spoken right after the option name. The unavailability is marked through three channels: pale text, a padlock glyph and a striped fill on a repeating-linear-gradient — opacity alone is not enough for low vision. The borders are collapsed, the rounded corners go to the edge ones only, and hover does not fire on a locked segment thanks to :not(:has(input:disabled)).
Tags
- buttongroup
- disabled
- a11y
- explanation
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…