Skip to content
cursor.beauty
Pack

Guides

4 min read

How to install a kit

Where the files go, and how to know they loaded.

Each kit page shows a path. Trust that path.

Rules

  1. Create .cursor/rules/ at the project root if it does not exist.
  2. Save the file with the .mdc name from the kit.
  3. In Cursor, open Customize → Rules and confirm it appears.
  4. Check the frontmatter. alwaysApply: true should be rare. Globbed rules should match the files you actually edit.

Skills

  1. Create .cursor/skills/<slug>/.
  2. Save SKILL.md inside it.
  3. Start a new agent chat so the skill can be discovered.
  4. Invoke it with / if the agent does not pick it up on its own.

User-level skills can also live in ~/.cursor/skills/ if you want them in every repo.

Prompts

Copy the body. Paste into Agent. No file is required. If you want it in the repo anyway, .cursor/prompts/ is a reasonable convention — Cursor will not auto-load it like a skill.

Packs

The composer builds a zip with the right folders. Unzip at the project root so .cursor/rules merges with whatever you already have. Do not unzip a nested extra project/ folder unless you meant to.

AGENTS.md

If you only need a simple always-on note, a root AGENTS.md is enough and is portable to other tools. Use .mdc rules when you need globs or multiple files.