bcuracao/cursor-universal-rules

cursor-universal-rules is a collection of configuration files you drop into any code repository to give AI coding agents a consistent, disciplined way of working. It targets Cursor, an AI-powered code editor, and addresses a problem the README calls "context drift", the tendency of AI agents to guess at library versions, produce messy commits, skip tests, or refactor code they shouldn't touch, because there are no written rules constraining their behavior. The fix is a set of files placed in the repository itself: a root-level .cursorrules file that sets the agent's overall persona (senior architect, read context first, make the smallest correct change), plus specific rule files covering coding standards, dependency discovery, file and function size limits, a structured debugging approach (hypothesis then evidence then fix), commit message conventions, testing requirements, and documentation style. In practice: instead of guessing which library version to import, the rules tell the agent to open the project's manifest files first. Instead of vague git messages, it uses Conventional Commits format. Instead of sprawling files, it splits work when files exceed agreed size targets. You install it by cloning and copying the rule files into your project, then committing them so the whole team shares the same defaults. No build step is needed, the files are plain text that Cursor reads automatically. The repo has no primary programming language since the content is rule definitions rather than runnable code.