pr-rules
25Cursor rule Cursor
PR title, body, and Jira-link conventions for this repo.
Cursor rule Cursor
PR title, body, and Jira-link conventions for this repo.
Cursor rule Cursor
USE WHEN designing, implementing, or reviewing API security (versioning, auth, rate limits, testing).
Cursor rule Cursor
USE WHEN implementing user authentication, login systems, session management, or access control.
Cursor rule Cursor
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
USE WHEN you wish to test the currently implemented logic for dangers and insecure flows.
Cursor rule Cursor
USE WHEN designing, implementing, or reviewing data protection (classification, encryption, key management, privacy).
Cursor rule Cursor
USE WHEN adding, updating, or reviewing third-party dependencies, package files, or supply chain security.
Cursor rule Cursor
USE WHEN implementing error handling, logging, exception management, or security monitoring.
Cursor rule Cursor
USE WHEN handling user input, database queries, command execution, or output rendering.
Cursor rule Cursor
USE WHEN processing user input, form data, API requests, or data from external sources.
Cursor rule Cursor
These rules apply to all code and systems integrating with MCP (Model Context Protocol), including generated actions, scripts, and agentic behavior.
Cursor rule Cursor
USE WHEN rendering user data in HTML, JavaScript, SQL, URLs, or other output contexts.
Cursor rule Cursor
USE WHEN user input influences file paths or filesystem ops (join/resolve, read/write, upload/extract, list/delete, serve files).
Cursor rule Cursor
USE WHEN configuring applications, managing secrets, deploying infrastructure, or setting up environments.
Cursor rule Cursor
security-global-snyk from AdobeDocs/ff-services-docs.
Cursor rule Cursor
USE WHEN implementing code that interacts with SQL databases, regardless of language or framework, including generated code.
Cursor rule Cursor
USE WHEN code that performs outbound network requests, regardless of language or framework, including generated code.
Cursor rule Cursor
USE WHEN code parses or processes XML, regardless of language or framework, including generated code.
Cursor rule Cursor
Cursor rule "security-lang-c" from AdobeDocs/ff-services-docs, covering secure c development, 1. avoid unsafe functions, 2. always validate input lengths, 3. initialize all pointers and memory and 4. check all memory allocations.
Cursor rule Cursor
These rules apply to all C++ source and header files in the repository and aim to prevent memory corruption, resource leaks, undefined behavior, and security vulnerabilities through modern C++ best practices.
Cursor rule Cursor
Cursor rule "security-lang-node" from AdobeDocs/ff-services-docs, covering secure node.js development, 1. do not use user input in file paths or commands, 2. avoid eval, function, and vm on dynamic input, 3. avoid synchronous childprocess and shell execution and 4. use environment variables for secrets.
Cursor rule Cursor
These rules apply to all Python code in the repository and aim to prevent common security risks through disciplined handling of input validation, output encoding, safe execution, secure configuration, and dependency hygiene.
Skill Claude CodeCodexCursor
Audits an OpenAPI JSON spec (Redocly lint, OpenAPI version, FFS style guide, copy rules). Read-only — no file edits. Use when the user invokes /api-eval or asks to evaluate or audit an API spec.
Skill Claude CodeCodexCursor
Fixes Redocly lint errors and api-ref-structure.mdc inconsistencies on an OpenAPI JSON spec. Use when the user invokes /api-fix or asks to fix API lint or structure issues. Does not apply FFS style guide or copy fixes.