One taste. Genuinely different instructions.
Last updated 7 August 2026
Every dialect starts from the same taste configuration — palette, type, surface, rhythm, motion, anti-rules. What changes is how that direction is expressed for the builder receiving it: file format, primitives it already ships, constraints it needs told, and the capabilities worth using. Below is the same brief compiled twice, with only the lines each builder gets and the other does not.
140 shared lines carry the taste itself, so the design intent survives whichever tool you build in.
Lovable vs Cursor
Lovable-tuned · semantic tokens, shadcn primitives, Tailwind
- Lovable build brief
- How to use:** paste this into a fresh Lovable project as the first message.
- Stack assumed:** React + Vite + Tailwind, shadcn/ui, semantic CSS variables in `src/index.css` (or `src/styles.css` on TanStack).
- Token discipline:** never use raw colors in components — only semantic tokens (`bg-background`, `text-foreground`, `text-accent`).
- Creative direction
- Implementation constraints
- Define every color as an HSL or OKLCH CSS variable in the global stylesheet and mirror in tailwind.config.ts.
- Compose every component from shadcn/ui primitives; never re-invent Button, Input, Dialog, Card, or Tabs.
- Implement all motion through framer-motion without using bespoke CSS keyframes for state transitions.
- Maintain mobile-first responsiveness at 360, 768, and 1280 pixel breakpoints.
- Use lucide-react for iconography and sonner for toast notifications.
- Build small, focused components in src/components/ rather than large monolithic pages.
- Reference the project's llms.txt file to discover available documentation before proposing changes.
- Enable 'Execute backward incompatible database migrations' in Cloud permissions to allow dropping or renaming tables.
Cursor · .cursorrules format + file-tree expectations
- .cursorrules — generated by My Vibe Design
- Design north star
- Rules Cursor MUST follow
- Ensure your computer is plugged in and the lid is open when using 'Keep this computer awake' for remote control.
- Enable Rollouts and Security Reviewer from the Automations tab in the dashboard for Teams and Enterprise plans.
- Connect source control, deployment systems, and telemetry providers to enable automated change monitoring.
- Define custom team rules in the dashboard to ensure Security Review enforces specific architectural constraints.
- Invoke Custom Modes using the / menu and Alt+Enter to pin specific skills for the duration of a chat.
- Install necessary desktop packages on self-hosted workers to enable computer use features on Linux and Mac.
- Pair the iOS app with the desktop client and approve the pairing request to enable remote monitoring.
- Enterprise admins must manually enable Remote Control in Org settings under Security and identity.
- Use the Origin Apps plugin to plan ports of existing apps to the Origin platform.
- Latest Cursor capabilities
- Integrate with the Origin App Marketplace to connect tools for CI, security, monitoring, and deployments.
v0 vs Claude
v0.dev · React + Tailwind + shadcn, single-shot component
- v0 build brief
- How to use:** paste into v0.dev as a new generation.
- Output expected:** a single React + Tailwind + shadcn/ui composition.
- Creative direction
- Component requirements
- Use the App Router and React Server Component idioms; mark interactive leaves with 'use client'.
- Compose from shadcn/ui primitives like Button, Card, and Input rather than re-inventing them.
- Apply Tailwind utility classes only; avoid styled-components, CSS modules, or inline style props.
- Use lucide-react for icons and inline SVG for decorative ornaments.
- Design for mobile-first responsiveness and keep compositions self-contained.
- Use the slash-command menu to explicitly attach specific skills for complex logic.
- Click the compact error bar beneath the preview to debug VM dev server boot or install failures.
- Configure default chat visibility in Workspace Settings to control team access for new chats.
- Use the branch menu to fix preview, CI, or merge issues without leaving the chat.
Claude Artifacts · XML-tagged, single self-contained artifact
- <role>
- You are a senior product designer + frontend engineer. Produce a single, self-contained Claude Artifact that realises the creative brief below.
- </role>
- <creative_brief>
- </creative_brief>
- <output_contract>
- Use the computer_toolset_20260801 toolset for computer use as earlier versions like computer_20250124 are deprecated.
- Avoid using temperature, top_p, top_k, or assistant prefill with Haiku 5.5 to prevent 400 errors.
- Ensure all entries in a web tool's allowed_domains are explicitly matched within the environment's allowed_hosts.
- Set thinking.display to 'summarized' to view thinking block text, otherwise it is omitted by default.
- Include the managed-agents-2026-04-01 beta header when enabling dynamic workflows for Managed Agents.
- Return exactly ONE artifact of type application/vnd.ant.react or text/html per response.
- Ensure artifacts run standalone without external imports beyond React, Tailwind, and inlined SVGs.
- Use the effort parameter to control thinking depth as thinking cannot be disabled on 5.5 models.
Why this matters
A single Markdown blob pasted into every builder produces the average of all of them. Compiling per builder means Cursor gets rules it will keep obeying across files, Lovable gets semantic tokens and shadcn primitives, v0 gets a single-shot component brief, and Claude gets a self-contained artifact spec — from one point of view you only define once.
The full dialect set is available on Pro, and through the API and MCP server for agents.