spring-mvc-webflux-api-builder

Generate Kotlin Spring HTTP API files with DTOs, controllers, and web tests.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/yalishevant/kotlin-backend-agent-skills --skill spring-mvc-webflux-api-builder-yalishevant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-mvc-webflux-api-builder
Source: https://github.com/yalishevant/kotlin-backend-agent-skills/tree/main/.agents/skills/spring-mvc-webflux-api-builder
Command: npx skills add https://github.com/yalishevant/kotlin-backend-agent-skills --skill spring-mvc-webflux-api-builder-yalishevant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and generate Kotlin Spring HTTP APIs with correct controller signatures, DTOs, validation, serialization assumptions, error handling, and web tests. Use when building or changing REST endpoints, choosing between MVC and WebFlux, modeling request and response payloads, standardizing error responses, or avoiding Kotlin-specific validation and Jackson mistakes.

Core Features & Use Cases

  • Provide clear endpoint contracts, DTO boundaries, and consistent error handling.
  • Generate skeletons for controllers, services, mappers, validations, and tests aligned to project conventions.
  • Use case: When you need to switch a module between MVC and WebFlux or update DTOs across endpoints.

Quick Start

Provide a complete Kotlin Spring endpoint blueprint with request/response DTOs, controller signatures, and a focused web-layer test.

Frequently Asked Questions about spring-mvc-webflux-api-builder

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

FAQPage Schema
How do I generate Kotlin Spring API layers with correct DTOs and validation?

Generate Kotlin Spring API layers by defining endpoint contracts, request and response DTO boundaries, validation, and error models. This produces compilable controllers, services, mappers, exception handling, and focused web-layer tests aligned to project conventions.

When should I use Spring WebFlux versus MVC for my Kotlin REST endpoints?

Choosing between Spring WebFlux and MVC depends on your module's concurrency requirements. The generation process identifies the correct stack for your module and confirms project conventions before producing the endpoint contract and associated files.

What is the best way to standardize error handling and API contracts in a Spring WebFlux project?

Standardize error handling by defining a consistent error model alongside your endpoint contract. This generates exception handling code and response DTOs that align with your project conventions, preventing Kotlin-specific Jackson and validation mistakes.

Does this approach generate web-layer tests for Kotlin Spring controllers?

Yes, generating Kotlin Spring controllers includes producing a focused web-layer test. The output provides an end-to-end, compilable set of files covering controller signatures, service boundaries, and tests to verify the endpoint contract.

How do I avoid Kotlin-specific validation and Jackson serialization mistakes in Spring?

Avoid Kotlin validation and Jackson mistakes by defining clear DTO boundaries and validation rules upfront. The generated skeleton ensures serialization assumptions and validation annotations are correctly applied across request and response payloads.