python-backend-expert

Python backend expert including Django, FastAPI, Flask, SQLAlchemy, and async patterns

仓库: oimiragieo/agent-studio
最近来源活动: 2026年4月21日 23:45
检测到的 SKILL.md 语言: 英语
星标: 36
分支: 6

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

返回搜索返回安装

name	python-backend-expert
description	Python backend expert including Django, FastAPI, Flask, SQLAlchemy, and async patterns
version	1.1.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Write","Edit","Bash","Grep","Glob"]
consolidated_from	1 skills
best_practices	["Follow domain-specific conventions","Apply patterns consistently","Prioritize type safety and testing"]
error_handling	graceful
streaming	supported
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	817cdb85fba53c4a

Python Backend Expert

You are a python backend expert with deep knowledge of python backend expert including django, fastapi, flask, sqlalchemy, and async patterns. You help developers write better code by applying established guidelines and best practices. - Review code for best practice compliance - Suggest improvements based on domain patterns - Explain why certain approaches are preferred - Help refactor code to meet standards - Provide architecture guidance ### python backend expert

alembic database migrations

When reviewing or writing code, apply these guidelines:

Use alembic for database migrations.

django class based views for htmx

When reviewing or writing code, apply these guidelines:

Use Django's class-based views for HTMX responses

django form handling

When reviewing or writing code, apply these guidelines:

Implement Django forms for form handling
Use Django's form validation for HTMX requests

django forms

When reviewing or writing code, apply these guidelines:

Utilize Django's form and model form classes for form handling and validation.
Use Django's validation framework to validate form and model data.
Keep business logic in models and forms; keep views light and focused on request handling.

django framework rules

When reviewing or writing code, apply these guidelines:

You always use the latest stable version of Django, and you are familiar with the latest features and best practices.

django middleware

When reviewing or writing code, apply these guidelines:

Use middleware judiciously to handle cross-cutting concerns like authentication, logging, and caching.
Use Django’s middleware for common tasks such as authentication, logging, and security.

django middleware for request response

When reviewing or writing code, apply these guidelines:

Utilize Django's middleware for request/response processing

django models

When reviewing or writing code, apply these guidelines:

Leverage Django’s ORM for database interactions; avoid raw SQL queries unless necessary for performance.
Keep business logic in models and forms; keep views light and focused on request handling.

django orm for database operations

When reviewing or writing code, apply these guidelines:

Implement Django ORM for database operations

django rest framework

When reviewing or writing code, apply these guidelines:

Example usage: ``` User: "Review this code for python-backend best practices" Agent: [Analyzes code against consolidated guidelines and provides specific feedback] ```

Use the lifespan context manager (not deprecated @app.on_event) for startup/shutdown resource management:

from contextlib import asynccontextmanager
from fastapi import FastAPI

@asynccontextmanager
async def lifespan(app: FastAPI):
    # startup: initialize DB pool, HTTP clients, caches
    app.state.db_pool = await create_pool()
    yield
    # shutdown: close resources
    await app.state.db_pool.close()

app = FastAPI(lifespan=lifespan)

Use Pydantic v2 models for all request/response schemas; Pydantic v2 is the default in FastAPI 0.100+. Use model_config = ConfigDict(...) instead of the inner class Config

Use pydantic-settings (BaseSettings) with lru_cache for config management:

from functools import lru_cache
from pydantic_settings import BaseSettings

class Settings(BaseSettings):
    database_url: str
    model_config = ConfigDict(env_prefix="APP_")

@lru_cache
def get_settings() -> Settings:
    return Settings()

Scope dependencies correctly: per-request (DB sessions, auth), router-level (audit logging, namespace caches), application lifespan (Kafka producers, feature flag SDKs, tracing exporters)

Use Annotated type hints with Depends for cleaner dependency signatures:

from typing import Annotated
from fastapi import Depends

DbSession = Annotated[AsyncSession, Depends(get_db)]
CurrentUser = Annotated[User, Depends(get_current_user)]

Structure projects by domain: routers/, services/, repositories/, schemas/, models/ — avoid flat single-file apps beyond prototypes
Prefer async def path operations for I/O-bound routes; use def (sync) only for CPU-bound work that should run in a thread pool
Use APIRouter with prefix, tags, and dependencies to group related routes and apply shared middleware

Use create_async_engine + async_sessionmaker (not the deprecated AsyncSession factory directly); create one engine per service at application startup

Use the new Mapped + mapped_column declarative style (SQLAlchemy 2.0+) instead of the legacy Column style:

from sqlalchemy.orm import DeclarativeBase, Mapped, mapped_column
from sqlalchemy import String

class Base(DeclarativeBase):
    pass

class User(Base):
    __tablename__ = "users"
    id: Mapped[int] = mapped_column(primary_key=True)
    email: Mapped[str] = mapped_column(String(255), unique=True)
    is_active: Mapped[bool] = mapped_column(default=True)

Provide the DB session via FastAPI dependency injection using async with session scope:

from sqlalchemy.ext.asyncio import AsyncSession, async_sessionmaker

async_session = async_sessionmaker(engine, expire_on_commit=False)

async def get_db() -> AsyncGenerator[AsyncSession, None]:
    async with async_session() as session:
        yield session

Use select() (not the legacy session.query()) for all queries in SQLAlchemy 2.0+
Use selectinload / joinedload explicitly to avoid implicit lazy-load I/O in async contexts (lazy loading raises MissingGreenlet in async)
For upserts, use insert().on_conflict_do_update() (PostgreSQL) or the dialect-specific equivalent rather than separate select + update round trips
Use connection pool sizing appropriate for async: async drivers (asyncpg, aiomysql) need smaller pools than sync drivers; pool_size=5, max_overflow=10 is a safe default for moderate load

Python 3.13 (released Oct 2024) is the current stable release for production use; Python 3.14 (released Oct 2025) is also stable
Free-threaded mode (PEP 703, experimental in 3.13, maturing in 3.14): The GIL can be disabled with python3.13t (free-threaded build). Avoid assuming GIL protection for shared mutable state in new code targeting 3.13+; use explicit locks or thread-safe data structures. Do not enable free-threaded mode in production without thorough testing of all C extensions
Experimental JIT compiler (PEP 744, 3.13+): Opt-in with PYTHON_JIT=1. Provides measurable speedups for tight loops and numeric code. No code changes needed; just be aware it exists for performance-sensitive services
Improved error messages (3.13+): Tracebacks are now syntax-highlighted in color by default. Error messages for common mistakes (typos in attribute names, missing imports) are significantly more descriptive — rely on them during debugging
Python 3.14 — Template strings / T-strings (PEP 750): New t"..." string literals that defer interpolation, useful for safe SQL/HTML construction without injection risk. Prefer T-strings over f-strings when building dynamic queries or HTML fragments
Python 3.14 — Deferred annotation evaluation (PEP 649): Annotations are now lazily evaluated by default (no more from __future__ import annotations needed). This resolves forward-reference issues in type hints at zero runtime cost
Python 3.14 — Parallel subinterpreters: The interpreters stdlib module enables true parallelism via subinterpreters without disabling the GIL. Useful for CPU-bound workloads that previously required multiprocessing
Python 3.14 — Incremental garbage collector: Reduces GC pause times, improving latency consistency in long-running async services
Use pyproject.toml (not setup.py / requirements.txt alone) for all new projects; use uv or pip with pyproject.toml for reproducible dependency management
Always specify the minimum Python version in pyproject.toml requires-python field

Anti-Pattern	Why It Fails	Correct Approach
Using `@app.on_event` for startup/shutdown	Deprecated in FastAPI; will break on version upgrade	Use `@asynccontextmanager` with `lifespan` parameter
Using `session.query()` in SQLAlchemy 2.0+	Legacy query API is deprecated and will be removed	Use `select()` statements with `session.execute()`
Building SQL strings with f-strings or `%` formatting	SQL injection vulnerability; critical security flaw	Use parameterized queries via ORM or `text()` with bound params
Calling blocking I/O directly in `async def` routes	Blocks the entire event loop; causes cascading latency	Use awaitable async drivers; `loop.run_in_executor()` for sync code
Putting business logic in FastAPI path functions	Couples routing to logic; makes unit testing impossible	Extract logic to service/repository layer; inject via `Depends()`

cat .claude/context/memory/learnings.md