mcp: Instructions file for GitHub Copilot

Python Coding Conventions

Python Instructions

• Write clear and concise comments for each function using Google Pydoc style.
• Ensure functions have descriptive names and include type hints.
• Provide docstrings following PEP 257 conventions.
• Use the typing module for type annotations (e.g., List[str], Dict[str, int]).
• Break down complex functions into smaller, more manageable functions.

General Instructions

• Always prioritize readability and clarity.
• For algorithm-related code, include explanations of the approach used.
• Write code with good maintainability practices, including comments on why certain design decisions were made.
• Handle edge cases and write clear exception handling.
• For libraries or external dependencies, mention their usage and purpose in comments.
• Use consistent naming conventions and follow language-specific best practices.
• Write concise, efficient, and idiomatic code that is also easily understandable.

Code Style and Formatting

• Follow the PEP 8 style guide for Python.
• Maintain proper indentation (use 4 spaces for each level of indentation).
• Ensure lines do not exceed 79 characters.
• Place function and class docstrings immediately after the def or class keyword.
• Use blank lines to separate functions, classes, and code blocks where appropriate.
• Imports always go on top of the file, never just randomly in a function or code block.

Edge Cases and Testing

• Always include test cases for critical paths of the application.
• Account for common edge cases like empty inputs, invalid data types, and large datasets.
• Include comments for edge cases and the expected behavior in those cases.
• Write unit tests for functions and document them with docstrings explaining the test cases.

Proper Documentation

• use google style doc guidelines for docstrings
• do not include types because the function signature already has them
• include the title on the first line of the docstring after the """
• one empty line between the title and the description
• make examples in the docstring if it is intended to be used a lot in different ways