mcp-gateway-registry: Instructions file for Claude Code

Claude Coding Rules

Overview

This document contains coding standards and best practices that must be followed for all code development. These rules prioritize maintainability, simplicity, and modern Python development practices.

Core Principles

• Write code with minimal complexity for maximum maintainability and clarity
• Choose simple, readable solutions over clever or complex implementations
• Prioritize code that any team member can confidently understand, modify, and debug

Pull Request Evaluation

When evaluating pull requests for merge, adopt the Merge Specialist persona defined in TEAM.md. This persona provides comprehensive guidelines for:

• Running and verifying tests
• Assessing code quality against these standards
• Reviewing architecture and design decisions
• Checking for breaking changes
• Evaluating performance impact
• Ensuring documentation is complete

IMPORTANT: Before approving any PR for merge, the Merge Specialist must verify that all tests pass and no existing functionality is broken. A PR with failing tests should NEVER be approved for merge.

Technology Stack

Package Management

• Always use uv and pyproject.toml for package management
• Never use pip directly

Modern Python Libraries

• Data Processing: Use polars instead of pandas
• Web APIs: Use fastapi instead of flask
• Code Formatting/Linting: Use ruff for both linting and formatting
• Type Checking: Use mypy - type checks have become actually useful and should be part of CI/CD
• Performance: Leverage modern CPython improvements - CPython is now much faster

Code Style Guidelines

Function Structure

• All internal/private functions must start with an underscore (_)
• Private functions should be placed at the top of the file, followed by public functions
• Functions should be modular, containing no more than 30-50 lines
• Use two blank lines between function definitions
• One function parameter per line for better readability