grey-haven-plugins/developer-experience/skills/api-design-standards/SKILL.md
Design RESTful APIs following Grey Haven standards - FastAPI routes, Pydantic schemas, HTTP status codes, pagination, filtering, error responses, OpenAPI docs, and multi-tenant patterns. Use when creating API endpoints, designing REST resources, implementing server functions, configuring FastAPI, writing Pydantic schemas, setting up error handling, implementing pagination, or when user mentions 'API', 'endpoint', 'REST', 'FastAPI', 'Pydantic', 'server function', 'OpenAPI', 'pagination', 'validation', 'error handling', 'rate limiting', 'CORS', or 'authentication'.
npx skillsauth add greyhaven-ai/claude-code-config api-design-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
RESTful API design for FastAPI backends and TanStack Start server functions.
Follow these standards when creating API endpoints, defining schemas, and handling errors in Grey Haven projects.
URL Patterns:
/api/v1/users (plural nouns, lowercase with hyphens)/api/v1/organizations/{org_id}/teams (hierarchical)/api/v1/getUsers (no verbs in URLs)/api/v1/user_profiles (no underscores)HTTP Verbs:
GET - Retrieve resourcesPOST - Create new resourcesPUT - Update entire resourcePATCH - Update partial resourceDELETE - Remove resourceSuccess:
200 OK - GET, PUT, PATCH requests201 Created - POST request (resource created)204 No Content - DELETE requestClient Errors:
400 Bad Request - Invalid request data401 Unauthorized - Missing/invalid authentication403 Forbidden - Insufficient permissions404 Not Found - Resource doesn't exist409 Conflict - Duplicate resource, concurrent update422 Unprocessable Entity - Validation errorsServer Errors:
500 Internal Server Error - Unhandled exception503 Service Unavailable - Database/service downAlways enforce tenant isolation:
# Extract tenant_id from JWT
repository = UserRepository(db, tenant_id=current_user.tenant_id)
# All queries automatically filtered by tenant_id
users = await repository.list() # Only returns users in this tenant
from fastapi import APIRouter, Depends, HTTPException, status
router = APIRouter(prefix="/api/v1/users", tags=["users"])
@router.post("", response_model=UserRead, status_code=status.HTTP_201_CREATED)
async def create_user(
user_data: UserCreate,
db: Session = Depends(get_db),
current_user: User = Depends(get_current_user),
) -> UserRead:
"""Create a new user in the current tenant."""
repository = UserRepository(db, tenant_id=current_user.tenant_id)
user = await repository.create(user_data)
return user
See examples/fastapi-crud.md for complete CRUD endpoints.
from pydantic import BaseModel, EmailStr, Field, ConfigDict
class UserCreate(BaseModel):
"""Schema for creating a new user."""
email: EmailStr
full_name: str = Field(..., min_length=1, max_length=255)
password: str = Field(..., min_length=8)
class UserRead(BaseModel):
"""Schema for reading user data (public fields only)."""
id: str
tenant_id: str
email: EmailStr
full_name: str
created_at: datetime
model_config = ConfigDict(from_attributes=True)
See examples/pydantic-schemas.md for validation patterns.
// app/routes/api/users.ts
import { createServerFn } from "@tanstack/start";
import { z } from "zod";
const createUserSchema = z.object({
email: z.string().email(),
fullName: z.string().min(1).max(255),
});
export const createUser = createServerFn({ method: "POST" })
.validator(createUserSchema)
.handler(async ({ data, context }) => {
const authUser = await getAuthUser(context);
// Create user with tenant isolation
});
See examples/tanstack-start.md for complete examples.
{
"error": "User with ID abc123 not found",
"status_code": 404
}
Validation errors:
{
"error": "Validation error",
"detail": [
{
"field": "email",
"message": "value is not a valid email address",
"code": "value_error.email"
}
],
"status_code": 422
}
See reference/error-handlers.md for exception handlers.
Offset-based (simple):
@router.get("", response_model=PaginatedResponse[UserRead])
async def list_users(skip: int = 0, limit: int = 100):
users = await repository.list(skip=skip, limit=limit)
total = await repository.count()
return PaginatedResponse(items=users, total=total, skip=skip, limit=limit)
Cursor-based (recommended for large datasets):
@router.get("")
async def list_users(cursor: Optional[str] = None, limit: int = 100):
users = await repository.list_cursor(cursor=cursor, limit=limit)
next_cursor = users[-1].id if len(users) == limit else None
return {"items": users, "next_cursor": next_cursor}
See examples/pagination.md for complete implementations.
Always use tenant-aware repositories:
tenant_id from JWT claimsDefine schemas for all requests/responses:
{Model}Create - Fields for creation{Model}Read - Public fields for responses{Model}Update - Optional fields for updatesFastAPI auto-generates docs:
summary, description, response_description/docs (Swagger UI) and /redoc (ReDoc)See reference/openapi.md for customization.
Protect public endpoints:
from app.core.rate_limit import rate_limit
@router.get("", dependencies=[Depends(rate_limit)])
async def list_users():
"""List users (rate limited to 100 req/min)."""
pass
See templates/rate-limiter.py for Upstash Redis implementation.
Use Doppler for allowed origins:
# NEVER hardcode origins in production!
allowed_origins = os.getenv("CORS_ALLOWED_ORIGINS", "").split(",")
app.add_middleware(
CORSMiddleware,
allow_origins=allowed_origins,
allow_credentials=True,
)
See reference/cors-rate-limiting.md for complete setup.
Use this skill when:
These API design patterns come from Grey Haven's actual templates:
cvi-backend-template (FastAPI + SQLModel + Repository Pattern)cvi-template (TanStack Start server functions)error, detail, and status_code fieldstenant_id from JWT claims for multi-tenant isolationdoppler run --config test -- pytestdevelopment
Grey Haven's comprehensive testing strategy - Vitest unit/integration/e2e for TypeScript, pytest markers for Python, >80% coverage requirement, fixture patterns, and Doppler for test environments. Use when writing tests, setting up test infrastructure, running tests, debugging test failures, improving coverage, configuring CI/CD, or when user mentions 'test', 'testing', 'pytest', 'vitest', 'coverage', 'TDD', 'test-driven development', 'unit test', 'integration test', 'e2e', 'end-to-end', 'test fixtures', 'mocking', 'test setup', 'CI testing'.
development
Comprehensive test suite generation with unit tests, integration tests, edge cases, and error handling. Use when generating tests for existing code, improving coverage, or creating systematic test suites. Triggers: 'generate tests', 'add tests', 'test coverage', 'write tests for', 'create test suite'.
development
Specialized testing for React applications using TanStack ecosystem (Query, Router, Table, Form) with Vite and Vitest. Use when testing React + TanStack apps, mocking server state, testing router, or validating query behavior. Triggers: 'TanStack testing', 'React Query testing', 'test TanStack', 'mock query', 'router test'.
development
Apply Grey Haven's TanStack ecosystem patterns - Router file-based routing, Query data fetching with staleTime, and Start server functions. Use when building React applications with TanStack Start. Triggers: 'TanStack', 'TanStack Start', 'TanStack Query', 'TanStack Router', 'React Query', 'file-based routing', 'server functions'.