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 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: