gpupixel / rules

We split this cpp-develop.mdc into the rules it gives an agent

26 rules. About 0 are common, 20 are distinctive, and 6 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈20

  Distinctive · estimate

  This author's own choices. Worth a look.

• 6

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Write concise, idiomatic C++ code with accurate examples.

   line 12
2. Distinctive:

   Follow modern C++ conventions and best practices.

   line 13
3. Distinctive:

   Use object-oriented, procedural, or functional programming patterns as appropriate.

   line 14
4. Distinctive:

   Use descriptive variable and method names (e.g., 'is_user_signed_in', 'CalculateTotal()').

   line 16
5. Distinctive:

   Use PascalCase for class and methods names.

   line 20
6. Very specific:

   Use SCREAMING_SNAKE_CASE for constants and macros.

   line 21
7. Distinctive:

   Use namespaces to organize code logically.

   line 22
8. Distinctive:

   Use Google C++ Style Guide.

   line 23
9. Distinctive:

   Prefer modern C++ features (e.g., auto, range-based loops, smart pointers).

   line 26
10. Very specific:

    Use std::unique_ptr and std::shared_ptr for memory management.

    line 27
11. Very specific:

    Use constexpr and const to optimize compile-time computations.

    line 28
12. Distinctive:

    Follow a consistent coding style, such as Google C++ Style Guide.

    line 31
13. Distinctive:

    Place braces on the same line for control structures and methods.

    line 32
14. Distinctive:

    Use clear and consistent commenting practices.

    line 33
15. Very specific:

    Use exceptions for error handling (e.g., std::runtime_error, std::invalid_argument).

    line 36
16. Distinctive:

    Use RAII for resource management to avoid memory leaks.

    line 37
17. Distinctive:

    Avoid unnecessary heap allocations.

    line 41
18. Very specific:

    Use std::move to enable move semantics and avoid copies.

    line 42
19. Distinctive:

    Use smart pointers over raw pointers for better memory safety.

    line 47
20. Distinctive:

    Avoid global variables; use singletons sparingly.

    line 48
21. Very specific:

    Use enum class for strongly typed enumerations.

    line 49
22. Distinctive:

    Use templates and metaprogramming judiciously for generic solutions.

    line 51
23. Distinctive:

    Write clear comments for classes, methods, and critical logic.

    line 54
24. Distinctive:

    Use Doxygen for generating API documentation.

    line 55
25. Distinctive:

    Document assumptions, constraints, and expected behavior of code.

    line 56
26. Distinctive:

    Follow the official ISO C++ standards and guidelines for best practices in modern C++ development.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.