spring-boot-rest-api-standards
Comprehensive REST API design standards and best practices for Spring Boot applications.
Works with
0
total installs
0
this week
194
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
194
stars
What it does
Covers resource-based URL design, HTTP method conventions, status codes, DTOs, validation, and error handling with global exception strategies
Includes pagination, filtering, sorting, security headers, CORS policies, and HATEOAS implementation patterns
Provides constructor injection, immutable DTO patterns, transaction management, and logging best practices with code examples
Enforces API vers
Installation Guide
How to use spring-boot-rest-api-standards on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
spring-boot-rest-api-standards
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches spring-boot-rest-api-standards from giuseppe-trisciuoglio/developer-kit and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate spring-boot-rest-api-standards. Access via /spring-boot-rest-api-standards in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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:
-
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
-
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)
-
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
-
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
-
Implement Validation
- Use
@Validannotation on@RequestBodyparameters - Apply validation constraints (
@NotBlank,@Email,@Size, etc.) - Handle validation errors with
MethodArgumentNotValidException
- Use
-
Set Up Error Handling
- Use
@RestControllerAdvicefor global exception handling - Return standardized error responses with status, error, message, and timestamp
- Use
ResponseStatusExceptionfor specific HTTP status codes
- Use
-
Configure Pagination
- Use Pageable for large datasets
- Include page, size, sort parameters
- Return metadata with total elements, totalPages, etc.
-
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) {
ErrorResponse error List & Monetize Your Skill
Submit your Claude Code skill and start earning
Get started →Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
tailwind-css-patterns
16giuseppe-trisciuoglio/developer-kit
nextjs-code-review
8giuseppe-trisciuoglio/developer-kit
rest-api-design
7aj-geddes/useful-ai-prompts
drizzle-orm-patterns
6giuseppe-trisciuoglio/developer-kit
java-coding-standards
10affaan-m/everything-claude-code
typescript-best-practices
96jwynia/agent-skills
Reviews
- SShikha Mishra★★★★★Dec 16, 2024
Keeps context tight: spring-boot-rest-api-standards is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSofia Gill★★★★★Dec 12, 2024
spring-boot-rest-api-standards is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNaina Park★★★★★Nov 19, 2024
I recommend spring-boot-rest-api-standards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- SSakshi Patil★★★★★Nov 15, 2024
I recommend spring-boot-rest-api-standards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- RRahul Santra★★★★★Nov 7, 2024
spring-boot-rest-api-standards has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CCarlos Yang★★★★★Nov 3, 2024
Solid pick for teams standardizing on skills: spring-boot-rest-api-standards is focused, and the summary matches what you get after install.
- PPratham Ware★★★★★Oct 26, 2024
Solid pick for teams standardizing on skills: spring-boot-rest-api-standards is focused, and the summary matches what you get after install.
- NNaina Haddad★★★★★Oct 22, 2024
spring-boot-rest-api-standards has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CCarlos Chen★★★★★Oct 10, 2024
Useful defaults in spring-boot-rest-api-standards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- CChaitanya Patil★★★★★Oct 6, 2024
Useful defaults in spring-boot-rest-api-standards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 35
Discussion
Comments — not star reviews- No comments yet — start the thread.