Create, update, and organize English Markdown documentation in Anyo, including how-to guides, knowledge, decisions, component READMEs, and agreed tasks. Use for documentation work rather than unrelated code changes.
Configure and verify Anyo's Python distribution and prepare requested releases. Use for pyproject metadata, dependency constraints and extras, package resources, wheel and source builds, installation checks, versioning, and publishing workflows.
Implement or review Anyo's Python library code and public APIs. Use for function and class contracts, type annotations, extension interfaces, exceptions, resource ownership, and compatibility changes. Package placement is covered by anyo-structure.
Keep Anyo's root README short and write simple, example-led how-to guides in docs/wiki. Use when editing the README or wiki, moving usage documentation, or deciding where user-facing instructions belong.
Structure Anyo as a Python library. Use when adding or moving Python modules, assigning capability ownership, changing public imports or component dependencies, or reviewing package organization. Covers the src layout, module boundaries, integrations, tests,…
Design, implement, and run tests for Anyo's Python library behavior. Use for regression coverage, public contracts, fake agents and providers, integration boundaries, failure handling, and asynchronous tests. Distribution build verification is covered by…