Cursor rule Cursor
A set of rules for designing REST APIs, including consistent resource names, response status codes, versioning, and error formats. REST APIs are web interfaces that programs use to exchange data.
Cursor rule Cursor
A structured way to explore a coding problem before writing code. It separates idea generation, narrowing the choices, and testing the likely weaknesses of each option.
Cursor rule Cursor
Code-style guidance for naming, function size, and comments, with the goal of making code understandable from its structure. Self-explanatory code reduces the mental effort needed to read and maintain it.
Cursor rule Cursor
A checklist for reviewing a software change before it goes live. It covers feature checks, a rollback plan for undoing the release, monitoring and alerts, and the order of database changes.
Cursor rule Cursor
Guidance for writing project and code documentation, including README files, code comments, API references, and migration instructions. A README explains how a project is used, while API documentation explains how other code can call it.
Cursor rule Cursor
A set of rules for keeping development, testing, and production environments separate and consistent. These environments are the different places where software is built, checked, and run for users.
Cursor rule Cursor
Rules for handling errors in layers, separating expected business problems from technical failures. They also cover keeping useful exceptions visible instead of silently ignoring them or adding unnecessary safeguards.
Cursor rule Cursor
A final checklist for a branch before opening a pull request, which is a request for others to review and merge code. It covers code quality, tests, commit history, the request description, and documentation.
Cursor rule Cursor
A rule for writing Git commit messages in Conventional Commits format, a shared style that labels changes such as features, fixes, and documentation.
Cursor rule Cursor
A set of rules for everyday Git work, where Git is a system for tracking code changes and collaborating with branches.
Cursor rule Cursor
A workflow for Git worktrees, which let you have several branches checked out in separate folders at the same time. You can work between branches without stashing changes or switching the current branch.
Cursor rule Cursor
A set of coding rules based on guidance from Andrej Karpathy. It tells the coding agent to think before editing, keep implementations small, make focused changes, and work toward a clear goal.
Cursor rule Cursor
A method for improving program speed by measuring performance first, finding the actual bottleneck, and then checking whether the change helped. Profiling is the process of measuring where a program spends its time or resources.
Cursor rule Cursor
Systematic PR review process with blocking/suggestion/nit severity levels.
Cursor rule Cursor
A set of rules for refactoring code, meaning changing its internal structure without changing what it does. It recommends small steps, tests first, extracting functions, and removing repeated code.
Cursor rule Cursor
A quick secure-code review checklist based on the OWASP Top 10, a widely used list of common web-application security risks. It checks input validation, authentication, injection, and exposure of sensitive data.
Cursor rule Cursor
A step-by-step method for investigating bugs, failed tests, and unexpected behaviour. It provides a structured way to narrow down the cause instead of guessing.
Cursor rule Cursor
A task-estimation rule for breaking work down to its smallest parts and estimating each part in three ways.
Cursor rule Cursor
A software development method called test-driven development, or TDD, where tests are written before the code they check.
Cursor rule Cursor
A rule set for writing an implementation plan before coding. The plan covers affected areas, broken-down steps, tests, and risks.
Skill Claude Code
: bad yaml.
Skill Claude Code
This file intentionally omits Claude Skill frontmatter with name or description.
Skill Claude Code
Review SkillOps reference repository 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: