Does this work with Maven?
Yes. Choose Maven in the generator and replace the Gradle commands with mvn verify, mvn test and so on.
A Spring Boot service in Java, built with Gradle. The rules keep an agent on constructor injection, explicit transactions and Flyway migrations, and give it the exact Gradle tasks that verify a change.
# AGENTS.md
Project: spring-service. A Spring Boot REST service in Java with Spring Data JPA and PostgreSQL.
This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.
## Stack
- Language: Java
- Framework: Spring Boot
- Database: PostgreSQL
- Hosting: AWS
- Tests: JUnit 5
- Package manager: Gradle
## Commands
Run these from the repository root.
- Install dependencies: `./gradlew dependencies`
- Run locally: `./gradlew bootRun`
- Build: `./gradlew build`
- Run all tests: `./gradlew test`
- Run one test file: `./gradlew test --tests "com.example.orders.OrderServiceTest"`
- Lint: `./gradlew spotlessCheck`
- Format: `./gradlew spotlessApply`
## Project layout
- `src/main/java/com/example/<feature>/`: Feature packages: controller, service, repository, entities, DTOs
- `src/main/resources/application.yml`: Configuration (no secrets)
- `src/main/resources/db/migration/`: Flyway migrations V<n>__description.sql
- `src/test/java/`: JUnit 5 tests
## Code style
- Indent with 4 spaces. Never tabs.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Prefer small pure functions and immutable data; keep side effects at the edges (handlers, jobs, I/O modules).
- Never swallow an error. Handle it where you can act on it, or rethrow it with context about what failed.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- For a bug fix or behavior change, first write or update a test that fails, then make it pass.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Ask before creating, editing or running database migrations, and never edit a migration that has already been applied.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
## Product constraints
- Validate all input at the boundary, use parameterized queries only, and treat every external payload as untrusted.
- Changes must be backward compatible across a rolling deploy: old and new code run side by side, so migrations and API changes go in safe steps.
## Project-specific notes
- Use constructor injection with final fields; never `@Autowired` on fields.
- Controllers accept and return DTOs (records), never JPA entities.
- Validate request bodies with `@Valid` and Bean Validation annotations.
- Put `@Transactional` on service methods that write, not on controllers or repositories.
- Schema changes are new Flyway files `V<next>__<description>.sql`; never edit an applied migration. `spring.jpa.hibernate.ddl-auto` stays `validate`.
- Secrets come from environment variables or a secret manager referenced in `application.yml`, never literal values.
- Slice tests (`@WebMvcTest`, `@DataJpaTest`) for controllers and repositories; full `@SpringBootTest` only for integration tests.
## Project phase
This project is in active development. Follow the patterns that already exist; consistency beats novelty.
# CLAUDE.md
@AGENTS.md
## Claude Code
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
# GEMINI.md
@./AGENTS.md
## Gemini CLI
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
# Copilot instructions
Project: spring-service. A Spring Boot REST service in Java with Spring Data JPA and PostgreSQL.
The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.
## Stack
- Language: Java
- Framework: Spring Boot
- Database: PostgreSQL
- Hosting: AWS
- Tests: JUnit 5
- Package manager: Gradle
## Commands
- Install dependencies: `./gradlew dependencies`
- Run locally: `./gradlew bootRun`
- Build: `./gradlew build`
- Run all tests: `./gradlew test`
- Run one test file: `./gradlew test --tests "com.example.orders.OrderServiceTest"`
- Lint: `./gradlew spotlessCheck`
- Format: `./gradlew spotlessApply`
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- For a bug fix or behavior change, first write or update a test that fails, then make it pass.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Ask before creating, editing or running database migrations, and never edit a migration that has already been applied.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---
# Project rules
The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.
Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.
Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).
These are the exact files the generator writes for this preset. Change any command or rule in the generator and download your own set.
The preset describes a a Spring Boot REST service in Java with Spring Data JPA and PostgreSQL. Its AGENTS.md is 50 non-empty lines with 7 exact commands, 4 key directories, and 7 stack-specific rules on top of the shared working rules.
./gradlew dependencies, ./gradlew bootRun, ./gradlew build, ./gradlew test, ./gradlew test --tests "com.example.orders.OrderServiceTest", ./gradlew spotlessCheck, ./gradlew spotlessApply.src/main/java/com/example/<feature>/, src/main/resources/application.yml, src/main/resources/db/migration/, src/test/java/.It makes classes impossible to construct in a plain unit test and hides how many collaborators a class really has. Constructor injection is the Spring team recommendation and makes the code honest.
Returning JPA entities couples the API to the schema, can trigger lazy-loading errors during serialization, and may expose fields you never meant to publish.
Letting Hibernate alter the schema at startup works on a laptop and causes drift and data loss in production. Flyway makes changes explicit and ordered.
Agents default to @SpringBootTest for everything, which starts the whole context and makes the test suite slow enough that nobody runs it.
@Autowired on fields.@Valid and Bean Validation annotations.@Transactional on service methods that write, not on controllers or repositories.V<next>__<description>.sql; never edit an applied migration. spring.jpa.hibernate.ddl-auto stays validate.application.yml, never literal values.@WebMvcTest, @DataJpaTest) for controllers and repositories; full @SpringBootTest only for integration tests.Want different commands or rules? Load this preset into the generator, change anything, and download your own set.
AGENTS.md is read directly by Codex, Cursor, Windsurf, Cline, Zed and Jules, and by GitHub Copilot's cloud agent, code review and CLI. Claude Code reads it through the generated CLAUDE.md, and Gemini CLI through GEMINI.md. See the compatibility table for details, last verified 2026-11-13.
All presets are on the stacks page.
Yes. Choose Maven in the generator and replace the Gradle commands with mvn verify, mvn test and so on.
Most rules apply. Choose Kotlin as the language and add any Kotlin-specific conventions, such as data classes for DTOs, to the notes.
The Java compiler type-checks as part of ./gradlew build, so a separate command is not needed.
Yes. Copy them into any project, commercial or not, without attribution. They are a starting point: adjust the commands and rules to match your repository.
You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.