cursor-desktop-guide

Guide for using Cursor desktop features including AGENTS.md, Rules, Skills, Commands, Subagents, MCP, and Hooks. Use when the user asks about Cursor configuration, features, or how to set up the IDE environment.

16 stars

Best use case

cursor-desktop-guide is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Guide for using Cursor desktop features including AGENTS.md, Rules, Skills, Commands, Subagents, MCP, and Hooks. Use when the user asks about Cursor configuration, features, or how to set up the IDE environment.

Teams using cursor-desktop-guide should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cursor-desktop-guide/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/documentation/cursor-desktop-guide/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/cursor-desktop-guide/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How cursor-desktop-guide Compares

Feature / Agentcursor-desktop-guideStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Guide for using Cursor desktop features including AGENTS.md, Rules, Skills, Commands, Subagents, MCP, and Hooks. Use when the user asks about Cursor configuration, features, or how to set up the IDE environment.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Cursor Desktop Guide

## Context Architecture

Understand the priority of context loading to effectively manage the agent's knowledge:

1. **Team Rules** (Highest priority)
2. **Project Rules** (`.cursor/rules/`)
3. **User Rules** (Cursor Settings)
4. **AGENTS.md** (Project root and subdirectories)
5. **Skills** (Automatically discovered)

## Core Components

### AGENTS.md

- **Purpose**: Global instructions and context for the project.
- **Best Practice**: Keep compact (<100 lines). Use nested `AGENTS.md` for subdirectories.
- **Location**: Project root (`AGENTS.md`) or subdirectories (e.g., `projects/foo/AGENTS.md`).

### Project Rules (`.cursor/rules/`)

- **Purpose**: Specific, versioned rules.
- **Format**: `.md` or `.mdc` (with YAML frontmatter).
- **Types**:
  - **Always Apply**: `alwaysApply: true`
  - **Apply Intelligently**: `alwaysApply: false` (Agent decides based on description)
  - **Apply to Specific Files**: `globs: ["pattern"]`
  - **Apply Manually**: `@rule-name` mention

### Skills (`.cursor/skills/`)

- **Purpose**: Portable, versioned packages for domain-specific workflows.
- **Structure**: Directory with `SKILL.md`, `scripts/`, `assets/`, `references/`.
- **Usage**: Multi-step workflows requiring resources or scripts.

### Commands (`.cursor/commands/`)

- **Purpose**: One-off actions triggered by `/command` in chat.
- **Format**: Simple Markdown files.

### Subagents

- **Purpose**: Isolated AI assistants for heavy tasks or parallel execution.
- **Usage**: Use `Task` tool.
- **When to use**: Context isolation needed, parallel work, or specialized long-running tasks.
- **Cost**: Each subagent has its own context window (token overhead).

### MCP Servers & Integrations

- **Local**: Use MCP for stateful connections (e.g., Slack) or CLI tools via `Shell` for request-response (e.g., Jira, GitLab).
- **Cloud Agents**: Not used in this system (require remote repo).

### Hooks (`.cursor/hooks.json`)

- **Purpose**: Scripts triggered on agent events (e.g., `preToolUse`, `afterFileEdit`).
- **Types**: Command-based (shell script) or Prompt-based (LLM evaluation).

## Best Practices

1. **AGENTS.md** is the entry point, not an encyclopedia.
2. Use **Rules** with globs for file formats (e.g., ADRs).
3. Use **Skills** for complex workflows (reviews, reports).
4. Use **Commands** for simple rituals (`/morning`).
5. Use **Subagents** only when context isolation is strictly necessary.
6. Use **`.cursorignore`** to exclude archives and cache from Semantic Search.
7. Use **Max Mode** (1M tokens) for heavy workflows.

## References

- Full documentation: [references/REFERENCE.md](references/REFERENCE.md)
- Online up-to-date documentation: [https://www.cursor.com/docs](https://www.cursor.com/docs)

Related Skills

nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file-cursorrules

16
from diegosouzapw/awesome-omni-skill

Apply for nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file. --- description: Best practices for using Tailwind CSS in Next.js 15 and React 19 applications, including responsive design, custom configurations, and performance optimization. globs: app/**/*

Creating Cursor Rules

16
from diegosouzapw/awesome-omni-skill

Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples

assessment-guide

16
from diegosouzapw/awesome-omni-skill

Comprehensive guide for skill assessment, career evaluation, learning paths, knowledge testing, and professional development. Use when assessing technical skills, planning learning journeys, or evaluating career progress.

angular-typescript-cursorrules-prompt-file-cursorrules

16
from diegosouzapw/awesome-omni-skill

Apply for angular-typescript-cursorrules-prompt-file. --- description: General rules for Angular components, focusing on code quality, performance, and maintainability. globs: **/*.component.ts

Onboarding Guide Generator

16
from diegosouzapw/awesome-omni-skill

Generate onboarding guides for new team members based on project structure

documentation-guidelines

16
from diegosouzapw/awesome-omni-skill

Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.

developer-guidelines

16
from diegosouzapw/awesome-omni-skill

Guidelines for the Developer role: strict adherence, no unsolicited refactoring, documentation, security.

artifact-guidelines

16
from diegosouzapw/awesome-omni-skill

Guidelines for writing reports, organizing files, and generating code artifacts

android-service-account-guide

16
from diegosouzapw/awesome-omni-skill

Step-by-step guide for creating Google Cloud service account for Play Store API access

alto-dev-guide

16
from diegosouzapw/awesome-omni-skill

Use when developing ALTO itself - editing devenv.nix, hooks/*.py, agents/*.md, or checking Claude Code hook/agent syntax. Reference guide with documentation URLs and patterns.

devops-guide

16
from diegosouzapw/awesome-omni-skill

Comprehensive DevOps and infrastructure guide covering Docker, Kubernetes, AWS, Terraform, CI/CD pipelines, Linux, and cloud deployment strategies. Use when setting up infrastructure, automation, or deployment systems.

web-design-guidelines

16
from diegosouzapw/awesome-omni-skill

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".