code-pair-interviews

A set of Cursor rules for solving coding problems in pair-programming interviews, with emphasis on clear structure, simple solutions, readable code, and suitable algorithms.

In plain words
What is it for?
It guides interview practice, including breaking problems into functions or classes, choosing data structures, naming code clearly, and using consistent formatting.
Why use it?
It helps prevent rushed, tangled solutions and encourages explaining the approach while keeping the implementation understandable.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/code-pair-interviews
Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules
Per session 401 This file is loaded in full into every session.
When invoked 401 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00401 $0.00401
Opus 5 $0.00200 $0.00200
Sonnet 5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 2d ago against content hash d3b6154856cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-pair-interviews scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/code-pair-interviews.mdc · 39 lines

What it actually says

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.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 39 lines · 0 tokens per session scan A d3b6154856cc

Subscribe to this mod's changes

code-pair-interviews is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 401 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.