Spring endpoint

Skill vaibhavsaxena022/skills/spring-endpoint

AI-agent skills for software engineering — works with Claude Code, Codex, Cursor

Install

npx -y skills add vaibhavsaxena022/skills --skill spring-endpoint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scaffold a clean Spring Boot REST endpoint — controller, service, DTOs, and validation — following the project's existing layered conventions. Use when adding a new REST endpoint or resource to a Spring Boot project.

SKILL.md

1.5 KB, 258 tokens by cl100k_base, as published. Nobody here has run it

Spring Boot Endpoint

Create a new REST endpoint that matches the project's existing structure.

Steps

Inspect first. Read the codebase to learn its conventions: package layout, controller/service style, DTO/mapper pattern, error handling, and validation approach. Match them — do not introduce a new pattern.
Build the layers:
- Controller — thin. Map request → service call → response. Correct HTTP verb + status code (201 for create, 204 for delete). @Valid on request bodies.
- Service — the business logic. Put @Transactional on write operations.
- DTOs — separate request and response types (records preferred). Never expose entities directly.
- Validation — bean-validation annotations (@NotNull, @Size, …) on the request DTO.
Return errors through the project's existing exception handler — don't add a new one.

Rules

Constructor injection, never field injection.
Keep controllers free of business logic.
Add only what the endpoint needs — nothing speculative.
If the project has a mapper (MapStruct, manual), use it; don't hand-roll a new style.

Gives 0 of the 12 instructions most apis services skills give in 258 tokens

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

use plural nouns for resource namesin 41 of 424, across 32 files
use cursor-based pagination for large datasetsin 35 of 424, across 20 files
include rate limit headers in responsesin 25 of 424, across 13 files
Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
version APIs in the URL pathin 19 of 424, across 9 files
use semantic HTTP status codesin 18 of 424, across 8 files
verify webhook signaturesin 18 of 424, across 11 files
use query parameters for filteringin 17 of 424, across 6 files
use async database operationsin 14 of 424, across 7 files
wrap successful responses in a data fieldin 13 of 424, across 3 files
prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

annotate request bodies with @Valid
annotate write operations with @Transactional
put validation annotations on the request DTO
return errors via the existing exception handler
use constructor injection
use the project's existing mapper pattern

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.