paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule instructs the AI not to suggest updates or changes to files when there are no actual modifications needed. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule prevents the AI from suggesting whitespace changes. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule instructs the AI to preserve existing code and functionalities, avoiding unnecessary removal of code. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule ensures the AI provides links to the real files instead of placeholder names like x.md. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule requires the AI to provide all edits in a single chunk, avoiding multiple-step instructions for the same file. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule ensures that the AI always verifies information before presenting it, avoiding assumptions and speculation. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule enforces code writing standards relevant to different languages. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule dictates how comments should be used within the codebase to enhance understanding and avoid clutter. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule enforces encapsulating nested conditionals into functions to improve clarity. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule enforces the Don't Repeat Yourself principle to avoid code duplication and improve maintainability. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule enforces the single responsibility principle, ensuring functions are short and focused. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule applies to all files in the project and enforces general principles of clean code, readability, and maintainability. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: This rule focuses on using meaningful and descriptive names for variables, functions, and classes throughout the project. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: General rule for backend development expertise across the project. globs: /.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: Best practices when interacting with databases in backend Go code. globs: /db//.go.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: Specific guidelines for implementing gRPC services in Go. globs: /grpc//.go.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
description: Rule for handling Protocol Buffer definition files in the project. globs: /.proto.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
General rules for Go API development using the net/http package, focusing on code quality, security, and best practices.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
This rule ensures proper error handling, status codes, and JSON response formatting in Go API development.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
This rule emphasizes security, scalability, and maintainability best practices in Go API development.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
This rule enforces the use of Go's standard library for API development, focusing on idiomatic and efficient code.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
This rule focuses on the initial planning stage for Go API development, emphasizing detailed step-by-step thinking and pseudocode.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
Rules for maintaining a consistent file structure within individual element directories.
paulpham157/paul-s-cursor-rules
Cursor rule Cursor
This applies to most files in the project. Enforces developer-friendly practices and documentation.
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: