python-api-endpoint-creator

Generate FastAPI endpoints with Router, Service, and Repository layers.

96|9|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/c0x12c/ai-toolkit --skill python-api-endpoint-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-api-endpoint-creator
Source: https://github.com/c0x12c/ai-toolkit/tree/main/toolkit/skills/python-api-endpoint-creator
Command: npx skills add https://github.com/c0x12c/ai-toolkit --skill python-api-endpoint-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates complete FastAPI endpoints following a strict layered architecture (Router → Service → Repository), enabling rapid scaffolding of new API endpoints, CRUD operations, and domain modules.

Core Features & Use Cases

  • Automated scaffolding of Router → Service → Repository → Tests for new domain entities.
  • Enforces a clean layered architecture with thin routers, expressive services, and soft-delete repositories.
  • Provides templates and guidance to implement schemas, models, dependencies, and tests across the full stack.

Quick Start

Scaffold a new domain endpoint using the provided templates to generate Router, Service, Repository, and Tests.

Frequently Asked Questions about python-api-endpoint-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold FastAPI endpoints with a clean layered architecture?

Scaffolding FastAPI endpoints with a layered architecture generates complete Router, Service, and Repository modules for new domain entities. This enforces thin routers, expressive services, and soft-delete repositories to standardize API structure.

What's the best way to structure FastAPI CRUD operations and domain modules?

Structuring FastAPI CRUD operations uses a Router → Service → Repository pattern to separate routing, business logic, and data access. This approach produces standardized templates for schemas, models, dependencies, and tests across the full stack.

Does FastAPI scaffolding support async endpoints and standardized error handling?

FastAPI scaffolding supports async endpoints and standardized error handling within the generated Router and Service layers. It applies these patterns automatically to ensure consistent asynchronous API behavior and soft-delete logic.

Can I generate tests and schemas when creating a new FastAPI domain module?

Generating tests and schemas is included when creating a new FastAPI domain module. The scaffolding process produces templates for the full stack, ensuring that models, dependencies, and tests are created alongside the Router, Service, and Repository.

Why use a repository pattern for FastAPI scaffolding instead of direct database calls?

Using a repository pattern for FastAPI scaffolding isolates data access logic from the service layer, enforcing clean separation of concerns. This yields expressive services and thin routers while standardizing soft-delete logic across domain modules.

When should I avoid automated FastAPI scaffolding for new endpoints?

Avoid automated FastAPI scaffolding when your project requires a single-file architecture or lacks distinct domain entities. The strict Router → Service → Repository layering is designed for scalable CRUD operations and may be excessive for simple microservices.