Skip to content

CLAUDE.md

Latest commit

 

History

History
53 lines (38 loc) · 3.76 KB

CLAUDE.md

File metadata and controls

53 lines (38 loc) · 3.76 KB

General

Please write a high quality, general purpose solution. Implement a solution that works correctly for all valid inputs, not just the test cases. Do not hard-code values or create solutions that only work for specific test inputs. Instead, implement the actual logic that solves the problem generally.

Focus on understanding the problem requirements and implementing the correct algorithm. Tests are there to verify correctness, not to define the solution. Provide a principled implementation that follows best practices and software design principles.

If the task is unreasonable or infeasible, or if any of the tests are incorrect, please tell me. The solution should be robust, maintainable, and extendable.

For maximum efficiency, whenever you need to perform multiple independent operations, invoke all relevant tools simultaneously rather than sequentially. After receiving tool results, carefully reflect on their quality and determine optimal next steps before proceeding. Use your thinking to plan and iterate based on this new information, and then take the best next action.

Guidelines

  • Make only high confidence suggestions when reviewing code changes.
  • Always use the latest version C#. When global.json targets .NET 8, use C# 12. When it targets .NET 9.0, use C# 13. When it uses .NET 10.0, target C# 14.
  • Never change global.json unless explicitly asked to.
  • Always prefer .IsNullOrWhiteSpace() over .IsNullOrEmpty() for strings.
  • Always prefer ArgumentException.ThrowIfNullOrWhiteSpace() over standard string parameter null checks, but only in code that targets .NET 8 or later.
  • Always prefer ArgumentNullException.ThrowIfNull() over standard object parameter null checks, but only in code that targets .NET 8 or later.
  • Always use defense-in-depth and fail-first programming to only execute a task after all the ways it could fail have been checked.
  • Don't generate interfaces for dependency injection unless ABSOLUTELY necessary.

Formatting

  • Apply code-formatting style defined in .editorconfig.
  • Prefer normal namespace declarations (NOT file-scoped) and single-line using directives.
  • Insert a newline before the opening curly brace of any code block (e.g., after if, for, while, foreach, using, try, etc.).
  • Ensure that the final return statement of a method is on its own line.
  • Organize code into groups surrounded by #regions in the following order: Fields, Properties, Constructors, Public Methods, Private Methods.
    • Region instructions should be surrounded by blank lines.
  • Members should be ordered by visibility, with public members first, followed by protected, internal, and private members.
  • Fields, properties, and methods should be ordered alphabetically within their visibility group.
  • Use pattern matching, switch expressions, range expressions, and collection initializers wherever possible.
  • Use nameof instead of string literals when referring to member names.
  • Ensure that extensive XML doc comments are created for any APIs. When applicable, include and documentation in the comments. Only tags should be on the same line as content.

Nullable Reference Types

  • Declare variables non-nullable, and check for null at entry points.
  • Always use is null or is not null instead of == null or != null.
  • Trust the C# null annotations and don't add null checks when the type system says a value cannot be null.

Testing

Guidelines

  • We use MSTest v3, Breakdance, and FluentAssertions for tests.
  • Do not emit "Act", "Arrange" or "Assert" comments.
  • Do not use any mocking in tests.
  • Copy existing style in nearby files for test method names and capitalization.
  • Always prefer .NotBeNullOrWhiteSpace() over .NotBeNullOrEmpty() for testing strings.

You can do it! Don't hold back. Give it your all.