api-create

Generate API endpoints with Controller, UseCase, DTO, Service, and Repository layers from domain models.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/hyxklee/AI-DEV-ToolKit --skill api-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-create
Source: https://github.com/hyxklee/AI-DEV-ToolKit/tree/main/claude/skills/api-create
Command: npx skills add https://github.com/hyxklee/AI-DEV-ToolKit --skill api-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent API scaffolding from domain models to accelerate backend development and reduce boilerplate.

Core Features & Use Cases

  • Automated generation of Controller, UseCase, DTO, Service, and Repository layers from domain definitions.
  • Support for Java and Kotlin implementations with domain-driven design patterns.
  • OpenAPI-ready controllers with validation and transactional boundaries.

Quick Start

Provide a domain model and run the API endpoint generator to scaffold a complete API layer.

Frequently Asked Questions about api-create

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

FAQPage Schema
How do I generate API scaffolding from a domain model in Java or Kotlin?

To generate API scaffolding from a domain model, provide your domain definitions to the generator. It automatically creates Controller, UseCase, DTO, Service, and Repository layers for your Java or Kotlin clean architecture project.

Can I auto-generate OpenAPI annotations and validation for my API endpoints?

Yes, you can auto-generate OpenAPI-ready controllers with built-in validation and transactional boundaries. The generator structures these annotations directly into the presentation layer during code generation.

What is the best way to scaffold a clean architecture API across presentation, application, and domain layers?

The best way to scaffold a clean architecture API is to define your domain model first. The generator then maps this model across presentation, application, and domain layers to ensure scalable and structured code boundaries.

Does this API scaffolding tool support domain-driven design patterns for backend development?

Yes, this API scaffolding tool supports domain-driven design patterns. It reduces backend boilerplate by translating domain definitions directly into structured UseCase and Service implementations for Java and Kotlin projects.

When do I need to generate API layers from domain models instead of writing them manually?

You need to generate API layers from domain models when accelerating backend development and reducing boilerplate are priorities. It ensures consistent scaffolding across multiple endpoints without manual coding errors.