Skip to content
Development
Skill

/spring-boot-rest-api-standards

Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.

From plugin
developer-kit
345116 skills44 agents35 commands2 MCP
Install
$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-rest-api-standards --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/spring-boot-rest-api-standards

Context preview

The summary Claude sees to decide when to auto-load this skill.

Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.

SKILL.md

spring-boot-rest-api-standards.SKILL.md
name: spring-boot-rest-api-standards
description: Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Spring Boot REST API Standards

Overview

REST API design standards for Spring Boot covering URL design, HTTP methods, status codes, DTOs, validation, error handling, pagination, and security headers.

When to Use

  • Creating REST endpoints and API routes
  • Designing DTOs and API contracts
  • Implementing error handling and validation
  • Setting up pagination and filtering
  • Configuring security headers and CORS
  • Reviewing REST API architecture

Instructions

To Build RESTful API Endpoints

Follow these steps to create well-designed REST API endpoints:

1. **Design Resource-Based URLs**

  • Use plural nouns for resource names
  • Follow REST conventions: GET /users, POST /users, PUT /users/{id}
  • Avoid action-based URLs like /getUserList

2. **Implement Proper HTTP Methods**

  • GET: Retrieve resources (safe, idempotent)
  • POST: Create resources (not idempotent)
  • PUT: Replace entire resources (idempotent)
  • PATCH: Partial updates (not idempotent)
  • DELETE: Remove resources (idempotent)

3. **Use Appropriate Status Codes**

  • 200 OK: Successful GET/PUT/PATCH
  • 201 Created: Successful POST with Location header
  • 204 No Content: Successful DELETE
  • 400 Bad Request: Invalid request data
  • 404 Not Found: Resource doesn't exist
  • 409 Conflict: Duplicate resource
  • 500 Internal Server Error: Unexpected errors

4. **Create Request/Response DTOs**

  • Separate API contracts from domain entities
  • Use Java records or Lombok `@Data`/`@Value`
  • Apply Jakarta validation annotations
  • Keep DTOs immutable when possible

5. **Implement Validation**

  • Use `@Valid` annotation on `@RequestBody` parameters
  • Apply validation constraints (`@NotBlank`, `@Email`, `@Size`, etc.)
  • Handle validation errors with `MethodArgumentNotValidException`

6. **Set Up Error Handling**

  • Use `@RestControllerAdvice` for global exception handling
  • Return standardized error responses with status, error, message, and timestamp
  • Use `ResponseStatusException` for specific HTTP status codes

7. **Configure Pagination**

  • Use Pageable for large datasets
  • Include page, size, sort parameters
  • Return metadata with total elements, totalPages, etc.

8. **Add Security Headers**

  • Configure CORS policies
  • Set content security policy
  • Include X-Frame-Options, X-Content-Type-Options

**Validation checkpoints:**

  • After step 1-2: Verify URL structure follows REST conventions (/users not /getUsers)
  • After step 3: Test each endpoint returns correct status codes
  • After step 4-5: Validate DTOs with curl or HTTPie before proceeding
  • After step 6: Confirm error responses match standardized format

Examples

Basic CRUD Controller

@RestController
@RequestMapping("/v1/users")
@RequiredArgsConstructor
@Slf4j
public class UserController {
    private final UserService userService;

    @GetMapping
    public ResponseEntity<Page<UserResponse>> getAllUsers(
            @RequestParam(defaultValue = "0") int page,
            @RequestParam(defaultValue = "10") int pageSize) {
        log.debug("Fetching users page {} size {}", page, pageSize);
        Page<UserResponse> users = userService.getAll(page, pageSize);
        return ResponseEntity.ok(users);
    }

    @GetMapping("/{id}")
    public ResponseEntity<UserResponse> getUserById(@PathVariable Long id) {
        return ResponseEntity.ok(userService.getById(id));
    }

    @PostMapping
    public ResponseEntity<UserResponse> createUser(@Valid @RequestBody CreateUserRequest request) {
        UserResponse created = userService.create(request);
        return ResponseEntity.status(HttpStatus.CREATED).body(created);
    }

    @PutMapping("/{id}")
    public ResponseEntity<UserResponse> updateUser(
            @PathVariable Long id,
            @Valid @RequestBody UpdateUserRequest request) {
        return ResponseEntity.ok(userService.update(id, request));
    }

    @DeleteMapping("/{id}")
    public ResponseEntity<Void> deleteUser(@PathVariable Long id) {
        userService.delete(id);
        return ResponseEntity.noContent().build();
    }
}

Request/Response DTOs

// Request DTO
@Data
@NoArgsConstructor
@AllArgsConstructor
public class CreateUserRequest {
    @NotBlank(message = "User name cannot be blank")
    private String name;

    @Email(message = "Valid email required")
    private String email;
}

// Response DTO
@Data
@NoArgsConstructor
@AllArgsConstructor
public class UserResponse {
    private Long id;
    private String name;
    private String email;
    private LocalDateTime createdAt;
}

Global Exception Handler

@RestControllerAdvice
@Slf4j
public class GlobalExceptionHandler {

    @ExceptionHandler(MethodArgumentNotValidException.class)
    public ResponseEntity<ErrorResponse> handleValidationException(
            MethodArgumentNotValidException ex, WebRequest request) {
        String errors = ex.getBindingResult().getFieldErrors().stream()
                .map(f -> f.getField() + ": " + f.getDefaultMessage())
                .collect(Collectors.joining(", "));

        ErrorResponse errorResponse = new ErrorResponse(
                HttpStatus.BAD_REQUEST.value(),
                "Validation Error",
                "Validation failed: " + errors,
                request.getDescription(false).replaceFirst("uri=", "")
        );
        return new ResponseEntity<>(errorResponse, HttpStatus.BAD_REQUEST);
    }

    @ExceptionHandler(ResponseStatusException.class)
    public ResponseEntity<ErrorResponse> handleResponseStatusException(
            ResponseStatusException ex, WebRequest request) {
        Erro
Read more
Ships withdeveloper-kit

Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI.

Get the whole plugin

Other skills on developer-kit.