mcpField
F
fastapi-router-creator

fastapi-router-creator

github.com/first-flukeDevelopment22546 installsUpdated 4d ago
Repository

About fastapi-router-creator

A skill for developers creating maintainable FastAPI routers. It explains modular and file-based routing, with guidance on prefixes, tags, dependencies, and API versioning.

Key features

  1. 01Modular router organization
  2. 02File-based routing approach
  3. 03Router-level prefixes and tags
  4. 04Shared router dependencies
  5. 05Versioned API namespaces

Use cases

  1. 01Organizing endpoints by resource
  2. 02Applying authentication dependencies across a router
  3. 03Structuring versioned FastAPI APIs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/first-fluke/fullstack-starter --skill fastapi-router-creator

After installing, type/fastapi-router-creatorin Claude Code to confirm it loaded.

Details

From the project README

FastAPI Router Creator

This skill guides the creation of modular, organized FastAPI routers, emphasizing maintainability and scalability.

Routing Strategies

1. Modular Router Pattern (Standard)

The most common and recommended approach for FastAPI.

Structure:

src/api/v1/endpoints/
├── users.py
├── items.py
└── auth.py

Implementation:

src/api/v1/endpoints/users.py:

from fastapi import APIRouter

router = APIRouter()

@router.get("/")
async def get_users():
    ...

src/api/v1/api.py (Aggregator):

from fastapi import APIRouter
from src.api.v1.endpoints import users, items

api_router = APIRouter()
api_router.include_router(users.router, prefix="/users", tags=["users"])
api_router.include_router(items.router, prefix="/items", tags=["items"])
2. File-Based Routing (fastapi-router)

For a Next.js-like experience where file structure dictates URLs. (Requires fastapi-router library or custom walker).

Structure:

src/app/
├── api/
│   ├── users/
│   │   ├── route.py  # Handles /api/users
│   │   └── [id]/
│   │       └── route.py # Handles /api/users/{id}

Best Practices

  1. Prefixing: Use prefixes at the router include level, not inside every endpoint decorator.
  2. Tags: Use tags to group endpoints in OpenAPI docs.
  3. Dependencies: Apply dependencies (like auth) at the router level if they apply to all endpoints in that router.
    router = APIRouter(dependencies=[Depends(get_current_active_user)])
    
  4. Version: Namespace routers by API version (v1, v2).

Comments

Markdown supported