RIPER-5
01Cursor rule Cursor
A set of strict rules for Claude 4.0 inside Cursor, a code editor based on Visual Studio Code. The rules require clear authorization before making changes to a codebase.
feishu project api mcp and agent.
This repository also configures its own agents. See what lark_agent tells them →
Cursor rule Cursor
A set of strict rules for Claude 4.0 inside Cursor, a code editor based on Visual Studio Code. The rules require clear authorization before making changes to a codebase.
Cursor rule Cursor
A set of general project rules. The supplied details do not explain what those rules contain.
Cursor rule Cursor
A general project rule covering shared development conventions, the technology used, project structure, coding principles, and response language. It comes from a Cursor rule set and is marked for removal.
Cursor rule Cursor
A set of project rules describing the required code structure.
Cursor rule Cursor
A set of project rules that records the technologies the code uses and links to their official documentation.
Cursor rule Cursor
A set of project rules for modern C++ development, covering C++17 and C++20, the standard library, and system-level programming. The supplied details do not list the individual rules.
Cursor rule Cursor
A set of project rules for writing Python code, including stated guidance on best practices and clean, efficient patterns. The supplied details do not describe the individual rules.
Cursor rule Cursor
A set of project rules for writing TypeScript code, including stated guidance on coding standards and best practices. The supplied details do not describe the individual rules.
Cursor rule Cursor
A set of Cursor editor rules for writing project documentation, including its structure, README contents, and version records.
Cursor rule Cursor
A rule for helping generate Git commit messages. Git is a tool that records changes to code in a project.
Cursor rule Cursor
A set of Git workflow rules based on Gitflow. Gitflow is a branching method that uses branches such as main or master, develop, and temporary support branches to organize changes.
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: