java-spring

Name: java-spring
Availability: InStock
Author: Violet

Enforce Java/Spring Boot conventions for Violet services with Maven builds.

Updated Aug 27, 2026

Search Tags:#rest #java #mongodb #maven #spring-boot #api-patterns #snake_case

Ready to run

npx skills add https://github.com/violetio/violet-ai-plugins --skill java-spring-violetio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: java-spring
Source: https://github.com/violetio/violet-ai-plugins/tree/main/plugins/v-java-spring/skills/java-spring
Command: npx skills add https://github.com/violetio/violet-ai-plugins --skill java-spring-violetio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Java/Spring Boot conventions to accelerate Violet service development and ensure consistency across teams.

Core Features & Use Cases

Framework & Version: Spring Boot 3.2.x with Java 21
Project Structure: Standard layout under src/main/java/io/drizzl/platform/{service}/ with modules for config, temporal, service, repository, web, model, and platform-specific integrations
Data & Serialization: Snake_case naming via Jackson; MongoDB (Spring Data MongoDB) or PostgreSQL (Spring Data JPA)
API & Patterns: Always use path parameters for database queries; standard Violet endpoint pattern
MongoDB & Jackson: Use @Document, @Field, and Snake_case naming
Build & Run: Maven-based build, run with mvn clean install spring-boot:run

Quick Start

Configure a Violet Java Spring service by following the conventions above:

Create a Spring Boot 3.2.x project using Java 21 and Maven
Use the folder structure under src/main/java/io/drizzl/platform/{service}/
Implement REST endpoints using the standard Violet endpoint pattern and path variables for DB queries

Frequently Asked Questions about java-spring

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

FAQPage Schema

How do I structure a Spring Boot REST API with MongoDB and snake_case serialization?▼

Structure your Spring Boot 3.2.x project under src/main/java/io/drizzl/platform/{service}/ with modules for config, repository, web, and model. Use @Document and @Field annotations for MongoDB entities, configure Jackson for snake_case naming via property-naming-strategy, and implement REST endpoints with path parameters for database queries to match Violet conventions.

What Java version and Maven setup do Violet Spring services require?▼

Violet Spring services require Java 21 and Spring Boot 3.2.x with Maven-based builds. Build and run using mvn clean install spring-boot:run. This standardized stack ensures consistency across Violet services handling REST endpoints, MongoDB or PostgreSQL persistence, and snake_case serialization.

How do I enforce Spring Boot conventions for REST endpoints and data access?▼

Always use path parameters for database queries rather than query strings. Implement proper null-safety checks for nested fields, apply CreatedDate and LastModifiedDate timestamps on domain models, and follow the standard Violet endpoint pattern. These conventions ensure security and consistency across REST APIs and data access layers.

Can I use this Skill with both MongoDB and PostgreSQL?▼

Yes, Violet Spring conventions support both MongoDB (via Spring Data MongoDB with @Document annotations) and PostgreSQL (via Spring Data JPA). Choose your persistence layer based on project requirements; both follow the same project structure, snake_case serialization rules, and REST endpoint patterns.

What timestamp and null-safety patterns do I need for Violet Spring models?▼

Add @CreatedDate and @LastModifiedDate annotations to domain models for automatic temporal tracking. Implement null-safety checks for nested object fields to prevent NullPointerException errors. These patterns satisfy Violet's technical requirements for data integrity and audit trails across services.

Why does Violet use snake_case serialization in Spring Boot APIs?▼

Snake_case serialization via Jackson ensures consistent field naming across Violet services and external API contracts. This standardization improves interoperability between services, simplifies client integration, and aligns with Violet platform conventions for REST API design and MongoDB document fields.