Code Pair Interviews

Install

Downloads the file at commit b044f956f021 into .cursor/rules/.

To remove it later:

Context cost: ≈504 tokens when used.

Rules file

---
description: "Cursor rules for code pair interviews development with integration."
globs: **/*
alwaysApply: false
---
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_cost` instead of `calc`.
-   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.

Copy file

Security

Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan