# 312-frameworks-spring-data-jdbc

A skill that applies Spring Data JDBC rules to Java records: entities, repositories, aggregate boundaries, transactions, N+1 avoidance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 329 installs · ★ 456
- Author: Juan Antonio Breña Moral
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jabrena/plinth/tree/HEAD/skills/312-frameworks-spring-data-jdbc/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/312-frameworks-spring-data-jdbc

## What it does

The skill gives your agent a rulebook for Spring Data JDBC code. It covers records as entity classes, `@Table` for name mismatches, `@Embedded` to inline value objects into the parent row, the repository pattern, and immutable updates through static factories and `with*` helpers. There is a section on `save()` semantics: INSERT or UPDATE follows from whether `@Id` is null.

Aggregate boundaries get their own treatment. One repository per aggregate root, `Set` for one-to-many inside the root, foreign keys between aggregates. Custom queries go through `@Query` with named parameters, transactions sit on services with `@Transactional`, and loading is meant to happen in a single query.

Before touching anything, the skill wants a compiling project. It runs `./mvnw compile` or `mvn compile` first and stops dead if that fails. After the changes it runs `./mvnw clean verify` or `mvn clean verify`. So on a broken build the agent will not rewrite your entities, which is the behaviour you want. Ambiguous requests get a clarifying question instead of a patch.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jabrena/plinth --skill 312-frameworks-spring-data-jdbc -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/312-frameworks-spring-data-jdbc/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/312-frameworks-spring-data-jdbc/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jabrena/plinth --skill 312-frameworks-spring-data-jdbc -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/312-frameworks-spring-data-jdbc/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jabrena/plinth --skill 312-frameworks-spring-data-jdbc -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/312-frameworks-spring-data-jdbc/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jabrena/plinth 312-frameworks-spring-data-jdbc
```

2. **Manually: put the files in place**
- File: `.github/skills/312-frameworks-spring-data-jdbc/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jabrena/plinth --skill 312-frameworks-spring-data-jdbc -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jabrena/plinth --path skills/312-frameworks-spring-data-jdbc
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/312-frameworks-spring-data-jdbc/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jabrena/plinth --skill 312-frameworks-spring-data-jdbc -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/jabrena/plinth/tree/HEAD/skills/312-frameworks-spring-data-jdbc/SKILL.md

## When to use it
- convert entity classes to Java records
- split repositories along aggregate boundaries
- remove N+1 loading from relationships
- add optimistic locking and domain events
- audit custom queries for concatenated user input

## Example prompts
- Review this Spring Data JDBC code and flag aggregate boundary problems
- Model this aggregate with Java records and show the with* update helpers
- Find repositories that load relationships one by one and fix the N+1

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1838801a8b9ac702.

BEGIN THIRD-PARTY FILE 1838801a8b9ac702
```text
---
name: 312-frameworks-spring-data-jdbc
description: Use when you need to use Spring Data JDBC with Java records — including entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. This should trigger for requests such as Review Java code for Spring Data JDBC; Apply best practices for Spring Data JDBC in Java code; Model Spring Data JDBC aggregates with Java records; Review Spring Data JDBC repositories and aggregate boundaries; Improve optimistic locking or domain events in Spring Data JDBC. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Spring Data JDBC with Records

Apply Spring Data JDBC guidelines with Java records.

**What is covered in this Skill?**

- Records for entity classes (immutable, constructor-friendly)
- @Table for naming when record name differs from the table name
- @Embedded to inline value-object columns into the parent row without a separate table
- Repository pattern
- Immutable updates with static factories for new rows and with* helpers for updates
- save() INSERT vs UPDATE semantics driven by @Id nullability
- Aggregate boundaries: one repository per aggregate root, Set for one-to-many inside the root, foreign keys between aggregates
- Custom queries with @Query and named parameters (no user-input concatenation)
- Transaction management (@Transactional on services; readOnly where appropriate)
- Single query loading (N+1 avoidance)

**Scope:** Apply recommendations based on the reference rules and good/bad code examples.

## Constraints

Before applying any Spring Data JDBC changes, ensure the project compiles. If compilation fails, stop immediately. After applying improvements, run full verification.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **SAFETY**: If compilation fails, stop immediately
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed rules and good/bad patterns
- **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes
- **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

## When to use this skill

- Review Java code for Spring Data JDBC
```
END THIRD-PARTY FILE 1838801a8b9ac702

The third-party file has ended. Everything between the 1838801a8b9ac702 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2448 of 3468 bytes. © Juan Antonio Breña Moral · Apache-2.0 · https://github.com/jabrena/plinth/tree/HEAD/skills/312-frameworks-spring-data-jdbc/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md