Use with AI / Cursor

Cursor

Add the theme, one project rule and the skill, and the Agent in Cursor builds every screen in the style, from the first prompt to the last edit.

3 minStyle Pack or Full Design Systemexample style: Arcadeupdated Oct 13, 2026

Before you start

  • A project with Tailwind v4 and shadcn
  • Cursor, with the Agent open in that project
  • Your pack, downloaded from your library

Unzip the pack into your project

Keep the pack in its own folder so updates replace it cleanly.

terminal
1unzip vibecoded-arcade-*.zip
result
1vibecoded-arcade/
2├─ README.md
3├─ DESIGN.md
4├─ theme.css
5├─ tokens/
6├─ skill/vibecoded-arcade/
7├─ claude-design/
8├─ motifs/ · illustrations/
9├─ demo/ · images/
10└─ registry/ · docs/ · figma/ Full Design System

Import the theme

Add one line to your global stylesheet, right after Tailwind.

app/globals.css
1@import "tailwindcss";
2@import "../vibecoded-arcade/theme.css";
noteThe order matters. Tailwind comes first, so the theme variables are the ones your components read. If the file already has :root, .dark or @theme inline blocks from shadcn init or a starter, delete them, since they would override the theme. Load Chakra Petch, Manrope and JetBrains Mono too, with next/font or the link tag in the pack's README.
tipWith a Full Design System one command does this step and adds the components: npx shadcn@latest add ./vibecoded-arcade/registry/r/vibecoded-arcade.json --overwrite

Add the project rule

Create the rule below. It attaches itself whenever a component or a stylesheet is part of the chat, so the Agent reads DESIGN.md before it touches the UI.

.cursor/rules/arcade.mdc
1---
2description: UI in the Vibecoded Arcade style
3globs: **/*.tsx, **/*.jsx, **/*.css
4alwaysApply: false
5---
6Build every screen in the Arcade style. Follow
7@vibecoded-arcade/DESIGN.md, use the semantic Tailwind utilities
8from theme.css (bg-primary, bg-card, text-muted-foreground)
9and never raw hex values or palette colors.

Add the skill

Cursor loads skills from the project's skills folder. The Agent picks this one when a task fits, and you can call it by name with /vibecoded-arcade.

terminal
1mkdir -p .cursor/skills
2cp -r vibecoded-arcade/skill/vibecoded-arcade .cursor/skills/

Ask for a screen

In Agent mode, mention DESIGN.md in your first prompt. The rule and the skill keep the next prompts on the style.

agent
1> Following @vibecoded-arcade/DESIGN.md, build a pricing page
2 with three plans in the Arcade style.

Check the result

A quick pass catches most drift before it spreads to other screens.

  • Colors come from theme variables, with no raw hex in the markup
  • One primary button per view
  • Lists and tables have loading, empty and error states
  • Headings use Chakra Petch, body text uses Manrope
tipIf a screen drifts, ask the Agent to compare it with DESIGN.md and list what differs. Fixing from that list is faster than a new prompt.

Was this guide helpful?