Tool guide

Using UIVibes with Cursor

Operates inside your existing codebase — precise paths matter.

Paste workflow

The Cursorworkflow

  1. Open your project in Cursor and start a Chat or Composer session.

  2. Prefix the prompt with "Add to existing project" so Cursor treats it as an addition, not a fresh scaffold.

  3. Paste the AI Prompt tab content, including the exact `@/components/ui/` path from the prompt's Component section.

  4. Review and accept the diff — Cursor writes the file(s) straight into your tree.

Gotchas

Known gotchas

What to watch for once the prompt is in Cursor — none of these block the build, they just save a round trip.

  • Operates in existing codebases, not a blank canvas — always prefix with "Add to existing project."
  • Handles multi-file changes well in one pass (component + a usage-site update), if you ask for both.
  • Precise file paths matter — keep the `@/components/ui/` path from the prompt intact rather than letting it improvise one.

Availability

Universal, unless it isn't

universal.md is written to build cold in every supported tool, so it's the only prompt that exists for most components today.

A tool-specific variant only gets added once the universal prompt demonstrably fails in that tool — see the quickstart for what's inside a prompt either way. When a Cursor-specific variant exists for a component, its prompt tab will show it automatically; until then, the universal prompt is the one to paste.

Browse components