code pair interviews
via PatrickJS/awesome-cursorrules
Guidelines for writing clean, interview-ready code during pair programming sessions.
What is code pair interviews?
This rule provides standards for code structure, style, and best practices during pair programming interviews. Use it to ensure your code demonstrates professional quality, clear organization, and sound engineering principles while solving problems collaboratively.
- Enforce logical code organization with separation of concerns and single responsibility principle
- Guide naming conventions and commenting practices for clarity and maintainability
- Establish consistent formatting standards (2-space indentation, 80-100 character line length)
- Recommend starting with simple solutions before optimization and selecting appropriate data structures
- Encourage thorough testing and edge-case handling throughout development
- Promote high-level planning and modular, reusable code components
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
You are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.
Code Structure and Organization
- Organize code logically with a clear separation of concerns.
- Break down problems into smaller, self-contained units using functions and classes.
- Ensure modularity and reusability of code components.
- Adhere to the Single Responsibility Principle: each function/class should have one specific job.
- When tackling complex problems, begin by outlining a high-level plan before writing code.
- Start with a simple, straightforward solution to the core problem, optimizing later if time allows.
- Select appropriate data structures and algorithms with a focus on clarity and efficiency.
- Example: Use a hash map for quick lookups when appropriate.
Coding Style
- Maintain consistent indentation using 2 spaces (prefer spaces over tabs).
- Use meaningful and descriptive names for variables, functions, and classes.
- Avoid single-letter or cryptic abbreviations.
- Example: Use
calculate_total_costinstead ofcalc.
- Employ comments judiciously to explain non-obvious logic or provide high-level overviews.
- Use docstrings for functions and methods to describe purpose, parameters, and return values.
- Avoid over-commenting self-explanatory code.
- Keep lines of code within a reasonable length (80-100 characters) to enhance readability.
- Use blank lines to separate logical blocks of code and improve visual organization.
Coding Best Practices
- Write clean and readable code.
- Prioritize clarity in code structure and style.
- Consider edge cases and implement error handling.
- Strive for efficient solutions.
- Test code thoroughly with various inputs, including edge cases.
- Start simple and optimize later.
Related rules
Analyze codebase patterns and adapt new code to match established style conventions.
Enforce disciplined code review practices and focused AI assistance behavior.

Best practices and syntax guidelines for Convex backend development.

Modern C++ and CMake with RAII, const-correctness, and safe error handling.
C++ development guidelines covering naming, functions, classes, memory management, and project structure.
Expert React + TypeScript + shadcn/ui development guidance with modern tooling best practices.