For people who ship UI with Claude Code · Cursor · v0
Design it once.
AI builds it exactly.
UIPrompt is a visual component editor that writes spec-grade prompts with exact values, state diffs, theme-aware tokens, and accessibility rules. The UI your AI builds is the UI you designed.
Free playground · No signup
You are implementing a UI component in this codebase. Match the project's existing component conventions for file placement and exports. Implement the component below as a React component styled with Tailwind CSS. Where Tailwind has no utility for an exact value, use arbitrary values (e.g. `rounded-[8px]`). Follow this spec exactly; every value is intentional. Do not substitute your own design taste, do not round values, and do not add visual features the spec does not mention. ## Component: Button ### Default state - Background: #18181B - Text color: #FAFAFA - Corner radius: 8px - Padding: 10px vertical, 16px horizontal - Border: none - Font size: 14px (line-height: 1.25) - Font weight: 500 - Shadow: none - Transition: background-color 150ms ease-out ## Implementation rules - **Visible focus ring**: Style keyboard focus with `:focus-visible` (never bare `:focus`): a 2px outline offset 2px from the element, using a high-contrast color. Never remove focus outlines without an equally visible replacement. - **Respect reduced motion**: Wrap all transitions/animations in `@media (prefers-reduced-motion: no-preference)` or disable them under `prefers-reduced-motion: reduce`. Motion must be an enhancement, never a requirement. - **Transition only listed properties**: Transition exactly the properties listed in the spec; never use `transition: all`. Keep durations as specified; do not add extra animated properties. - **Minimum hit target**: Ensure the interactive hit target is at least 44×44px. If the visual element is smaller, extend the clickable area with padding or a pseudo-element without changing the visual size. - **Disabled state**: For the disabled state: set `cursor: not-allowed` on a wrapper (disabled elements don't fire pointer events), reduce opacity to ~50% unless the spec overrides colors explicitly, and suppress all hover/active effects. - **Font smoothing on dark fills**: When rendering light text on a dark background, apply `-webkit-font-smoothing: antialiased` and `-moz-osx-font-smoothing: grayscale` to avoid overly bold-looking text. - **Text contrast**: Text must meet WCAG AA contrast (4.5:1 against its background; 3:1 for text ≥18.66px bold). If a specified color pair falls short, keep the spec colors but flag the contrast issue in a code comment. - **No hover layout shift**: Hover/focus styles must not change the element's layout size. If a border appears on interaction, reserve its space with a transparent border in the default state.
drag anything ↑ and watch the prompt rewrite itself
Adjectives gamble. Specs land.
✕What most people prompt
"make me a nice modern button, something clean that pops"
Eight visual decisions left to chance. The result looks fine, in someone else's app. Then the correction loop starts.
✓What UIPrompt writes for you
- Corner radius: 8px
- Transition: background-color 150ms ease-out
- Hover state: background #1D4ED8
Every value pinned. States as diffs. First try lands.
Twelve components. Every state. Real CSS.
These previews are rendered by the same engine that writes your prompts: hover, focus, disabled, light and dark. More types ship with every release.
Blind-tested: 11 of 11 CSS properties, identical.
We gave an AI only the generated prompt. It never saw the design. The implementation matched every measured property: colors, radius, padding, shadow, all three transition values. Read the full experiment.
Rules AI always forgets, included when relevant
- :focus-visible ring
- prefers-reduced-motion
- 44px hit target
- WCAG AA contrast
- no transition: all
- no hover layout shift
Buy once. Own it forever.
$39
one-time launch price, regular $59
- ✓ Unlimited components & tokens
- ✓ AI Design System Pack export
- ✓ Full prompt export, 3 target tools
- ✓ All future component types
- ✓ 14-day money-back guarantee
Frequently asked
- Why prompts instead of exporting code?
- Code exports go stale the moment they meet your codebase. A precise prompt lets your AI tool implement the design in your stack, your conventions, your naming, while keeping every visual value exact.
- Which AI tools are supported?
- Prompts are tuned for Claude Code, Cursor, and v0, and work with any capable coding assistant. You can switch the target tool with one click.
- What do free accounts get?
- Free accounts keep 3 saved components and full single-component prompts, free forever. One $39 purchase (regular $59) unlocks unlimited components and the AI Design System Pack export. Nothing is ever deleted.
- Can it export my whole design system at once?
- Yes. Switch the prompt scope to System and you get one prompt covering every component, shared tokens (with light and dark values), and de-duplicated rules, so your AI builds the whole library consistently.
- Can I share my designs?
- Every workspace can become a public read-only link: a live gallery with theme toggle and the full prompt. Anyone can remix it into their own playground with one click.
- Can I get a refund?
- Yes. 14-day money-back guarantee, no questions asked.