AdobeDocs

51 mods across 1 repository, 6 stars between them.

AdobeDocs/ff-services-docs

Cursor rule Cursor

These rules apply to all code and systems integrating with MCP (Model Context Protocol), including generated actions, scripts, and agentic behavior.

not rated 4 3mo ago A 0 tokens copy · 92% Apache-2.0

AdobeDocs/ff-services-docs

Cursor rule Cursor

USE WHEN implementing code that interacts with SQL databases, regardless of language or framework, including generated code.

not rated 4 3mo ago A 20 tokens original Apache-2.0

security-lang-c

35

AdobeDocs/ff-services-docs

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.

not rated 4 3mo ago A 497 tokens copy · 100% Apache-2.0

security-lang-cpp

36

AdobeDocs/ff-services-docs

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.

not rated 4 3mo ago A 0 tokens original Apache-2.0

security-lang-node

37

AdobeDocs/ff-services-docs

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.

not rated 4 3mo ago A 564 tokens copy · 100% Apache-2.0

AdobeDocs/ff-services-docs

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.

not rated 4 3mo ago A 0 tokens original Apache-2.0

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: