# Cursor Features and Practical Usage 📏 "Always validate APIs with zod" — you shouldn't have to retype that policy every prompt. Cursor's Rules give the AI persistent memory. 🏷️ Title: Persistent Instructions (Project/Team/AGENTS.md) 🔗 URL: 📘 Overview Rules provide persistent, system-level instructions to Cursor's Agent. Since LLMs don't retain memory between completions, Rules supply reusable context at the prompt level. They bundle prompts, scripts, and guidance so workflows stay reusable across a team. ⚙️ How It Works Cursor supports several kinds of Rules. ・Project Rules: `.mdc` files under `.cursor/rules`, version-controlled and scoped to your codebase. ・User Rules: global preferences defined in Cursor Settings, applied across all projects. ・Team Rules: org-wide rules managed from the dashboard (Team/Enterprise plans). ・AGENTS.md: a plain-markdown alternative in the project root or subdirectories, no frontmatter needed and nestable (more specific instructions take precedence over parent ones). Project Rule frontmatter controls behavior: `alwaysApply: true` applies to every chat, `globs` with `alwaysApply: false` auto-attaches when matching files are in context, `description` only lets the Agent apply it when relevant, and with none of these it applies only via `@`-mention. 🛠️ Practical Usage ・Scope rules to file types with globs, e.g. `src/**/*.tsx`, comma-separating multiple patterns. This auto-applies "always validate APIs with zod" whenever matching files are edited. ・Generate rules in chat with `/create-rule`, or via `Cursor Settings > Rules, Commands` → "+ Add Rule." ・Example `.mdc`: a frontmatter with `globs: src/api/**/*.ts` and `alwaysApply: false`, followed by rules like "validate every incoming payload with a zod schema" and "on failure, return 400 with a unified error shape." ・For teams, remember the application order Team Rules → Project Rules → User Rules, and enforce company-wide conventions via Team Rules. 💡 Use Cases Turn repeated policies — "validate APIs with zod," "use Conventional Commits," "structured JSON logging" — into Rules, auto-applied only to matching files via globs. Check them into Git so the whole team benefits from the same conventions. ⚠️ Caveats Keep each rule under 500 lines and split larger ones. Avoid copying style guides (use linters), and prefer referencing files over duplicating content. Target frequent patterns, not rare edge cases. Note that User Rules apply only to Agent (Chat) — not to Inline Edit, other AI features, or Cursor Tab. #Cursor# #AICoding#

# Cursor Features and Practical Usage 🧩 Tired of re-explaining the same multi-step workflow to your agent every single time? Cursor Skills let you package repeatable workflows so the agent just knows how to do them. 🏷️ Title: Reusable Workflows (SKILL.md) 🔗 URL: 📘 Overview Skills are portable, version-controlled packages that teach agents how to perform domain-specific tasks. They bundle scripts, templates, and reference material that the agent runs through its available tools. They are the evolution of Rules: agents can apply them automatically based on context, or you can invoke them explicitly as slash commands. ⚙️ How It Works Each skill is centered on a `SKILL.md` file whose leading YAML frontmatter defines its behavior. ・`name`: a lowercase identifier that must match the parent folder name (required) ・`description`: what the skill is for and when it applies; the agent reads this to decide whether to use it (required) ・`paths`: glob patterns that scope the skill to matching files (optional) ・`disable-model-invocation`: set to `true` to make it slash-only, included only when you type `/skill-name` (optional) Discovery is hierarchical: project skills live in `.cursor/skills/` (or `.agents/skills/`), and global ones in `~/.cursor/skills/`. The root is walked recursively, so nested subdirectories are found too. A skill folder can also ship `scripts/` (executable code), `references/` (docs loaded on demand), and `assets/` (templates or images). 🛠️ Practical Usage For example, in `.cursor/skills/api-endpoint/SKILL.md` set the frontmatter `name` to `api-endpoint`, a `description` of the workflow, and `paths` scoped to `src/api/**/*.ts`, then write the steps in the body (register the route, validate input with a zod schema, always add tests). If you do not want automatic invocation, add `disable-model-invocation: true` and call it explicitly by typing `/api-endpoint` in Agent chat. 💡 Use Cases In a monorepo, placing a `.cursor/skills/` folder inside each app automatically scopes those skills to files in that directory, so you can skip `paths` entirely. Share release procedures, migration scripts, or code-review checklists so the whole team works the same way. You can convert existing assets with the built-in `/migrate-to-skills` (Cursor 2.4): "Apply Intelligently" rules (`alwaysApply: false`) become skills, and slash commands become skills with `disable-model-invocation: true`. ⚠️ Caveats A skill's identity comes from the folder containing `SKILL.md`, not any parent category. The old `globs` field is deprecated; use `paths` now. `/migrate-to-skills` does not migrate `alwaysApply: true` rules or user-level rules, so those need manual handling. #Cursor# #AICoding#