How to use SKILL.md files with Cursor

how cursor reads skills

Cursor loads SKILL.md files automatically

When you open a project in Cursor, it scans for SKILL.md files in your project directory. Any it finds are loaded into the model's context before your first message — the same way Claude Code handles them. You don't need to configure anything or paste the content manually.

The standard location is your project root:

.
├── src/
├── package.json
└── SKILL.md        ← Cursor reads this automatically

For skills that apply to a specific subdirectory — a backend service inside a monorepo, for instance — you can place the SKILL.md in that subdirectory. Cursor will pick it up when you're working in that context.

installing a skill

Three ways to get a skill into your project

1. Copy from theskills.directory. Click any skill on theskills.directory, hit Copy, paste the content into a SKILL.md file in your project root. Done in 30 seconds.

2. Install via the CLI. If you have Node.js installed, the skillsadd command fetches and installs a skill directly from GitHub:

npx skillsadd anthropics/skills/frontend-design

This drops the SKILL.md into your current directory. Open Cursor and it's already loaded.

3. Use multiple skills together. You can have more than one skill in a project. Cursor merges them all. The easiest way to install a set of complementary skills is to use a stack — a curated collection built to work together.

cursor-specific tips

What works best in Cursor

Skills that encode structural rules tend to have the most impact in Cursor — things like component architecture, file naming conventions, and which libraries to use. Cursor is generating entire files, not just inline completions, so high-level structural guidance shapes more of the output.

Skills that encode quality bars — accessibility standards, performance constraints, design system rules — work well because Cursor is making many small decisions in parallel. Without a skill, it defaults to the average of its training data. With a skill, it defaults to your standard.

recommended skills

The skills that make the biggest difference in Cursor

Based on copy counts and community feedback, these are the skills Cursor users install most:

• Frontend Design — Anthropic's production design principles. Cursor generates a lot of UI — this stops it defaulting to generic layouts and generic component choices.
• Vercel React Best Practices — 69 explicit rules from Vercel's engineering team. Prevents Cursor from mixing App Router and Pages Router patterns, using deprecated APIs, or picking the wrong rendering strategy.
• Next.js Best Practices — Covers routing, error handling, and data fetching patterns that Cursor gets wrong without explicit guidance.
• shadcn/ui — The official shadcn skill. If your project uses shadcn, this ensures Cursor uses the correct component API instead of inventing its own patterns.
• Systematic Debugging — Four-phase debugging methodology. Stops Cursor from patching symptoms without finding root causes.

team workflows

Committing skills to version control

The real advantage of SKILL.md files is that they live in your repo. Commit them alongside your code and every developer on your team — Cursor user or not — benefits from the same conventions automatically. A new hire opens the project and Cursor already knows your standards.

For teams that use both Cursor and Claude Code, a single SKILL.md in the repo root works for both. You write it once. It applies everywhere.

# Commit your skills with the project
git add SKILL.md
git commit -m "add frontend-design skill"

# Or for multiple skills
git add *.md
git commit -m "add vercel-react and shadcn skills"