python-standards

Python coding standards for Amplifier modules require complete type hints for functions and classes, async execution using asyncio.gather for I/O operations, structured ToolResult-based error reporting, and dependency management with uv.

To make Python code compliant, enforce complete type hints for functions and classes, use asyncio.gather for async I/O parallel work, and return structured ToolResult-based errors to keep tools responsive and maintainable.

Yes, Amplifier development requires using uv for dependency management and ruff for formatting to prevent formatting drift, enforce code quality, and align modules with accepted repository conventions.

The best way to handle error reporting in Amplifier Python tools is returning structured ToolResult-based errors, which promotes reliability and maintainability while enabling protocol-level testing.

You should use async execution in Python modules for Amplifier projects when performing I/O operations or parallel work, utilizing asyncio.gather to keep tools responsive and avoid blocking.

Yes, Amplifier Python modules support testing at the protocol level to ensure maintainability and reliability, aligning implementation and testing with accepted repository conventions.