spring-entity

Generate JPA entities for Spring Boot with PostgreSQL conventions.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Faouzi91/HomeFlex --skill spring-entity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-entity
Source: https://github.com/Faouzi91/HomeFlex/tree/main/.claude/skills/spring-entity
Command: npx skills add https://github.com/Faouzi91/HomeFlex --skill spring-entity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing JPA entities for Spring Boot projects often leads to inconsistent code, missed best practices (like lazy relationship loading, proper column naming, and auditing support), and avoidable bugs that require hours of debugging and refactoring.

Core Features & Use Cases

  • Production-grade entity templates: Pre-built templates that enforce Spring Boot 4, Jakarta Persistence, and PostgreSQL conventions out of the box.
  • Built-in best practice guardrails: Automatically applies lazy loading for all relationships, explicit snake_case column naming, Lombok usage restrictions, and BaseEntity inheritance for built-in auditing.
  • Use Case: When building the property management module for the HomeFlex platform, use this skill to generate consistent RoomType and Property entities that follow the project's existing domain conventions, eliminating manual boilerplate and reducing entity-related bugs.

Quick Start

Use the spring-entity skill to generate a JPA entity for a new Amenity domain object with fields for name, description, and category, following the project's existing conventions.

Frequently Asked Questions about spring-entity

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

FAQPage Schema
How do I generate Spring Boot JPA entities with production-grade conventions automatically?

The Skill generates Spring Boot JPA entities by applying pre-built templates that enforce Jakarta Persistence and PostgreSQL standards, automatically implementing lazy relationship fetching, explicit snake_case column naming, and BaseEntity auditing inheritance.

What's the best way to enforce lazy loading and proper column naming in Spring Data JPA domain models?

The best way to enforce lazy loading and proper column naming in Spring Data JPA domain models is using entity generation templates that automatically apply lazy fetching for all relationships and explicit snake_case column naming conventions.

Can I use this JPA entity generation approach with Spring Boot 4 and PostgreSQL?

Yes, this JPA entity generation approach works with Spring Boot 4 and PostgreSQL, as the templates are specifically designed to enforce Jakarta Persistence conventions and PostgreSQL database table mappings out of the box.

Why should I restrict Lombok usage when creating Hibernate entities for Spring Boot?

You should restrict Lombok usage when creating Hibernate entities to prevent runtime bugs and maintainability issues, as this Skill enforces specific Lombok usage limitations to ensure generated JPA entity code remains bug-free and consistent.

How do I add auditing support to new Spring Data JPA entities without manual boilerplate?

To add auditing support to new Spring Data JPA entities without manual boilerplate, generated entities inherit from a BaseEntity class, which the Skill automatically includes to provide built-in auditing for domain model classes.

What are common limitations of manually writing JPA entities for Spring Boot applications?

Common limitations of manually writing JPA entities include inconsistent code, missed best practices like lazy relationship loading and proper column naming, and avoidable bugs that require hours of debugging and refactoring to resolve.