One taste. Genuinely different instructions.

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.
• Request Lovable to reuse the signed-in user identity instead of adding a login page for internal tools.

Cursor · .cursorrules format + file-tree expectations

• .cursorrules — generated by My Vibe Design
• Design north star
• Rules Cursor MUST follow
• Select an Optimization Mode in Auto mode to manage the cost-intelligence tradeoff.
• Use /side or /btw to initiate context-aware tangents without disrupting the primary agent.
• Explicitly select between Cloud, Local, or Remote environments using the 'Run on' picker.
• Enable Remote Control in the Dashboard for Teams and Enterprise plans to use mobile features.
• Configure Team MCP servers in the Integrations dashboard to distribute them to members.
• Propose file changes as a diff plan before editing code when adding new features.
• Use the install command for pre-session environment setup and the start command for fresh services.
• Review agent status updates in the mobile Inbox to redirect execution early.
• Use the iPad split-screen view to keep file diffs open next to active agent chats.
• Enable Builds in the Cloud Agents dashboard to ensure agents boot into ready environments.
• Latest Cursor capabilities

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.
• Utilize the Vercel Sandbox for data-heavy processing and terminal-based file management.
• Use Cmd/Ctrl + Enter to send or interrupt responses and Cmd/Ctrl + Up/Down to step through queued prompts.
• Latest v0 capabilities

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>
• 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 Lucide-react SVGs.
• Avoid using `localStorage`, `sessionStorage`, or third-party `fetch` calls unless explicitly requested.
• Use semantic Tailwind utilities and a `:root` token block for styling instead of hardcoded hex values.
• Wrap the entire user interface in a single root component named `App`.
• Do not disable thinking when using Opus 5 at effort levels higher than 'high' to avoid 400 errors.
• Budget long-running logic to fit within the 90-second per-cell code execution time limit.
• Ensure path_prefix for memory store operations ends with a forward slash and matches whole segments.