Cursor rule Cursor ✓ vendor
USE WHEN designing, implementing, or reviewing API security (versioning, auth, rate limits, testing).
AEM Desktop is an Electron desktop application for Adobe Experience Manager Edge Delivery Services, with development infrastructure for hot reload, updates, testing, and macOS release builds. It is used by developers building and releasing the desktop client, including signed and notarized macOS packages. Its catalogue entries provide coding-agent rules and instructions for working in this repository.
This repository also configures its own agents. See what aem-desktop tells them →
Cursor rule Cursor ✓ vendor
USE WHEN designing, implementing, or reviewing API security (versioning, auth, rate limits, testing).
Cursor rule Cursor ✓ vendor
USE WHEN implementing user authentication, login systems, session management, or access control.
Cursor rule Cursor ✓ vendor
These rules define essential practices for writing and generating secure code. They apply universally — to manual development, automated tooling, and AI-generated code. Our codebase follows a security‑first mindset: security is built in from day one.
Cursor rule Cursor ✓ vendor
USE WHEN designing, implementing, or reviewing data protection (classification, encryption, key management, privacy).
Cursor rule Cursor ✓ vendor
USE WHEN implementing error handling, logging, exception management, or security monitoring.
Cursor rule Cursor ✓ vendor
USE WHEN handling user input, database queries, command execution, or output rendering.
Cursor rule Cursor ✓ vendor
USE WHEN processing user input, form data, API requests, or data from external sources.
Cursor rule Cursor ✓ vendor
These rules apply to all code and systems integrating with MCP (Model Context Protocol), including generated actions, scripts, and agentic behavior.
Cursor rule Cursor ✓ vendor
USE WHEN rendering user data in HTML, JavaScript, SQL, URLs, or other output contexts.
Cursor rule Cursor needs its repo ✓ vendor
USE WHEN user input influences file paths or filesystem ops (join/resolve, read/write, upload/extract, list/delete, serve files).
Cursor rule Cursor ✓ vendor
USE WHEN configuring applications, managing secrets, deploying infrastructure, or setting up environments.
Cursor rule Cursor ✓ vendor
security-global-snyk from adobe/aem-desktop.
Cursor rule Cursor ✓ vendor
USE WHEN implementing code that interacts with SQL databases, regardless of language or framework, including generated code.
Cursor rule Cursor ✓ vendor
USE WHEN code that performs outbound network requests, regardless of language or framework, including generated code.
Cursor rule Cursor ✓ vendor
USE WHEN code parses or processes XML, regardless of language or framework, including generated code.
Cursor rule Cursor ✓ vendor
These rules apply to all Node.js code in the repository and aim to prevent common security risks through disciplined use of input validation, output encoding, and safe APIs.
Cursor rule Cursor ✓ vendor
USE WHEN adding, updating, or reviewing third-party dependencies, package files, or supply chain security.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: