> Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
npx skills add https://github.com/microsoft/agent-framework --skill python-development
Every .py file must start with:
# Copyright (c) Microsoft. All rights reserved.
Type | None instead of Optional[Type]from __future__ import annotations to enable postponed evaluationT for TypeVar names: ChatResponseT = TypeVar("ChatResponseT", bound=ChatResponse)Mapping instead of MutableMapping for read-only input parameters# type: ignore[...] over unnecessary casts, or isinstance checks, when these are internally called and executed methodsBut make sure the ignore is specific for both mypy and pyright so that we don't miss other mistakes
agent_framework* modules when intentional; use a targeted# pyright: ignore[reportPrivateUsage] instead of making the helper public just to satisfy pyright.
casts, or clearer annotations over adding runtime overhead without a design benefit.
*) for optional parametersdef create_agent(name: str, tool_mode: Literal['auto', 'required', 'none'] | ChatToolMode) -> Agent:
if isinstance(tool_mode, str):
tool_mode = ChatToolMode(tool_mode)
next_handler instead of next)**kwargs unless needed for subclass extensibility; prefer named parametersUse Google-style docstrings for all public APIs:
def equal(arg1: str, arg2: str) -> bool:
"""Compares two strings and returns True if they are the same.
Args:
arg1: The first string to compare.
arg2: The second string to compare.
Returns:
True if the strings are the same, False otherwise.
Raises:
ValueError: If one of the strings is empty.
"""
Keyword Args when applicable# Core
from agent_framework import Agent, Message, tool
# Components
from agent_framework.observability import enable_sensitive_telemetry
# Connectors (lazy-loaded)
from agent_framework.openai import OpenAIChatClient
from agent_framework.foundry import FoundryChatClient
In __init__.py files that define package-level public APIs, use direct re-export imports plus an explicit
__all__. Avoid identity aliases like from ._agents import Agent as Agent, and avoid
from module import *.
Do not define __all__ in internal non-__init__.py modules. Exception: modules intentionally exposed as a
public import surface (for example, agent_framework.observability) should define __all__.
__all__ = ["Agent", "Message", "ChatResponse"]
from ._agents import Agent
from ._types import Message, ChatResponse
Special case: the root agent_framework/__init__.py uses lazy runtime exports. For root public API changes:
_LAZY_MODULE_EXPORTS and keep _LAZY_EXPORTS derived from it.__all__ synchronized; it is still required for from agent_framework import *.agent_framework/__init__.pyi so pyright, mypy, and editors see the typed surface.__getattr__; avoid root-levelspecial-case branches for individual deprecated exports.
.pyi stubs because they mark re-exported names for type checkers; avoid themin runtime .py modules unless there is a specific compatibility reason.
match/case on .type attribute over isinstance() in hot paths_prepare_<object>_for_<purpose> for methods that prepare data for external services_parse_<object>_from_<source> for methods that process data from external servicesGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take microsoft/python-development from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.