Use the following collection of System prompts of Java to improve your Java development.
| Cursor Rule | Description | User Prompt | Notes |
|---|---|---|---|
| 000-system-prompt-list | Generate list of System Prompts for Java | User Prompt: Create a document with all System prompts for Java using @000-system-prompt-list |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 012-agile-epic | Create agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories | Interactive User Prompt: Create an agile epic using @012-agile-epic Note: The rule asks targeted questions about epic title, business value, target users, problem statement, solution overview, success criteria, key features, dependencies, risks, and documentation before generating the epic document. |
Three-phase approach: gets current date, gathers details through structured questions, then produces epic document with next steps. |
| 013-agile-feature | Create detailed feature Markdown files from an existing epic | Interactive User Prompt: Create features from my epic using @013-agile-feature Note: Add the epic file path or paste epic content. The rule analyzes the epic, clarifies scope and audience, asks per-feature questions, then generates one feature document per feature. |
Phases: current date, epic analysis and structured questions (including repeated questions per feature), then feature file generation and epic integration guidance. |
| 014-agile-user-story | Create user stories with Gherkin acceptance criteria and BDD feature files | Interactive User Prompt: Create a user story with acceptance criteria using @014-agile-user-story Note: The rule asks targeted questions about title, persona, goal, benefit, feature context, and Gherkin scenarios before generating the Markdown user story and .feature file. |
Two-phase approach: gathers details through structured questions, then produces user story and Gherkin file. |
| 040-planning-plan-mode | Create structured design plans for Cursor Plan mode (Java implementation, TDD, refactoring) | Interactive User Prompt: Create a plan for [feature/refactoring] using @040-planning-plan-mode Note: Use in Plan mode. Gathers context (specs, acceptance criteria) then produces YAML-frontmatter plan with Requirements Summary, Approach (Mermaid), Task List, Execution Instructions. |
Suitable for outside-in TDD, feature implementation, or refactoring work. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 030-architecture-adr-general | Generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes | Interactive User Prompt: Generate an ADR for the project with the cursor rule @030-architecture-adr-general Note: Add in the context the project root folder. The rule will ask questions about ADR storage location and naming convention before starting the interactive ADR generation process. Ensures project validation with Maven before proceeding. |
Interactive rule — asks questions one by one to gather all ADR information. Validates Maven project before starting, auto-increments ADR file numbering, and provides a comprehensive summary after generation. |
| 031-architecture-adr-functional-requirements | Create ADRs for functional requirements — CLI and/or REST/HTTP API; infers interface type from project context when possible | Interactive User Prompt: Generate an ADR for functional requirements with @031-architecture-adr-functional-requirements Note: Add the CLI and/or API project to context. Conversational discovery; surface discovery (CLI vs API vs both); one or two questions at a time. |
Unified functional-requirements ADR (CLI and/or REST). |
| 032-architecture-adr-non-functional-requirements | Create ADRs for non-functional requirements — document quality attributes, NFR decisions, security/performance/scalability using ISO/IEC 25010:2023 | Interactive User Prompt: Generate an ADR for non-functional requirements with @032-architecture-adr-non-functional-requirements Note: Add in the context the project. Skips irrelevant quality characteristics; dives deeper where there is uncertainty. |
NFR-focused ADR generation. |
| 033-architecture-diagrams | Generate Java project diagrams including UML sequence, class, state-machine diagrams and C4 model diagrams using a modular step-based approach | Interactive User Prompt: Generate diagrams about the project with the cursor rule @033-architecture-diagrams User Prompt: Create UML class diagrams with @033-architecture-diagrams without any question (Example) Note: Add in the context the folder to generate the diagrams. The rule will analyze the codebase and ask for user preferences before generating anything. Ensures project validation with Maven before proceeding. |
Focused on diagram generation only. I recommend to run the JBang tool jbang puml-to-png@jabrena --watch . in order to generate diagrams in PNG format on the fly |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 110-java-maven-best-practices | Analyze your pom.xml and apply Maven best practices |
User Prompt: Apply in the pom.xml the rule @110-java-maven-best-practices Note: Add in the context the pom.xml which you want to generate the documentation. User Prompt with Consultative Interactive Behaviour: Apply in the pom.xml the rule @110-java-maven-best-practices with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 111-java-maven-dependencies | Add Maven dependencies for improved code quality | Interactive User Prompt: Add essential Maven dependencies for code quality using @111-java-maven-dependencies User Prompt: Add VAVR dependency with the help of@111-java-maven-dependencies and not make any question (Example)Note: Add in the context the pom.xml which you want to enhance with quality dependencies. |
It is possible to apply the System prompt in an interactive and non interactive way. Using the interactive approach, the Software engineer will interact with the cursor rule to selectively add JSpecify, Error Prone, NullAway and VAVR dependencies based on project needs. |
| 112-java-maven-plugins | Update your pom.xml with Maven Dependencies & Plugins |
Interactive User Prompt: Improve the pom.xml using the cursor rule @112-java-maven-plugins User Prompt: Add Maven Enforcer plugin only from the rule @112-java-maven-plugins without any question (Example) Note: Add in the context the pom.xml which you want to generate the documentation. |
It is possible to apply the System prompt in an interactive and non interactive way. Using the interactive approach, the Software engineer will interact with the cursor rule to update the pom.xml. |
| 113-java-maven-documentation | Create a Maven Documentation with the file README-DEV.md |
User Prompt: Generate developer documentation with essential Maven commands using @113-java-maven-documentation Note: Add in the context the pom.xml which you want to generate the documentation. |
This cursor rule is applied automatically without any interaction with the Software engineer. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 121-java-object-oriented-design | Take another point of view with an Object Oriented Design of your development | User prompt: Improve the class/classes added in the context applying the system prompt @121-java-object-oriented-design(Example) Note: Add in the context a class/classes to improve the design. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @121-java-object-oriented-design with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 122-java-type-design | Review the Type Design in your development | User prompt: Improve the class/classes added in the context applying the system prompt @122-java-type-design (Example) Note: Add in the context a class/classes to improve the design. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @122-java-type-design with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 123-java-exception-handling | Add Exception handling | User Prompt: Improve the class/classes added in the context applying the system prompt @123-java-exception-handling (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @123-java-exception-handling with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 124-java-secure-coding | Review my code for Secure Java Coding rules | User Prompt: Improve the class/classes added in the context applying the system prompt @124-java-secure-coding (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @124-java-secure-coding with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 125-java-concurrency | Improve your code with Concurrency rules | User Prompt: Improve the class/classes added in the context applying the system prompt @125-java-concurrency (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @125-java-concurrency with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 180-java-observability-logging | Apply logging guidelines in your development | User Prompt: Improve the class/classes added in the context applying the system prompt @180-java-observability-logging (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @180-java-observability-logging with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 128-java-generics | Apply generics in a class | User Prompt: Improve the class/classes added in the context applying the system prompt @128-java-generics (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @128-java-generics with the behaviour @behaviour-consultative-interaction User Prompt with Training behaviour: Create a course about @128-java-generics.md using the behavior @behaviour-progressive-learning.md and put the course here Note: Add in the context the location to add the course. |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 130-java-testing-strategies | Apply testing strategies — RIGHT-BICEP, A-TRIP, CORRECT for boundary conditions and test quality | User Prompt: Improve tests applying testing strategies with @130-java-testing-strategies Note: Add in the context test classes or code under test. Focuses on conceptual frameworks rather than framework-specific annotations. |
Use for strategy-focused test design. For JUnit 5, AssertJ, Mockito, use @131-java-testing-unit-testing. |
| 131-java-testing-unit-testing | Apply Unit Testing best practices for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) | User Prompt: Improve the class/classes added in the context applying the system prompt @131-java-testing-unit-testing (Example) Note: Add in the context a class/classes. Project must NOT use Spring Boot, Quarkus, or Micronaut. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @131-java-testing-unit-testing with the behaviour @behaviour-consultative-interaction |
Precondition: framework-agnostic Java. For Spring Boot use @321-frameworks-spring-boot-testing-unit-tests; for Quarkus @421-frameworks-quarkus-testing-unit-tests; for Micronaut @521-frameworks-micronaut-testing-unit-tests. |
| 132-java-testing-integration-testing | Set up integration test infrastructure with WireMock (REST stubs) and generate a BaseIntegrationTest.java for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) |
Interactive User Prompt: Set up integration test infrastructure for my service using @132-java-testing-integration-testing Note: The rule will ask questions about your service's outbound HTTP dependencies before generating BaseIntegrationTest.java and starter WireMock mapping files. Project must NOT use Spring Boot, Quarkus, or Micronaut. |
Precondition: framework-agnostic Java. For Spring Boot use @322-frameworks-spring-boot-testing-integration-tests; for Quarkus @422-frameworks-quarkus-testing-integration-tests; for Micronaut @522-frameworks-micronaut-testing-integration-tests. Interactive rule — asks questions about REST topology before generating code. |
| 133-java-testing-acceptance-tests | Implement acceptance tests from a Gherkin .feature file for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — @acceptance scenarios, RestAssured, Testcontainers, WireMock | Interactive User Prompt: Implement acceptance tests from my Gherkin feature file using @133-java-testing-acceptance-tests Note: Add the .feature file to context. Project must NOT use Spring Boot, Quarkus, or Micronaut. |
Preconditions: .feature file in context; framework-agnostic Java. For Spring Boot use @323-frameworks-spring-boot-testing-acceptance-tests; for Quarkus @423-frameworks-quarkus-testing-acceptance-tests; for Micronaut @523-frameworks-micronaut-testing-acceptance-tests. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 141-java-refactoring-with-modern-features | Add Modern Java Features in your development | User Prompt: Improve the class/classes added in the context applying the system prompt @141-java-refactoring-with-modern-features (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @141-java-refactoring-with-modern-features with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 142-java-functional-programming | Add Functional Programming style in your development | User Prompt: Improve the class/classes added in the context applying the system prompt @142-java-functional-programming (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @142-java-functional-programming with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| 143-java-functional-exception-handling | Apply functional programming approaches for error handling using Optional and VAVR Either types | User Prompt: Improve the class/classes added in the context applying the system prompt @143-java-functional-exception-handling (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @143-java-functional-exception-handling with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. It promotes using Monads like Optional and Either<L,R> instead of exceptions for predictable failures. |
| 144-java-data-oriented-programming | Add Data Oriented Programming in your development | User Prompt: Improve the class/classes added in the context applying the system prompt @144-java-data-oriented-programming (Example) Note: Add in the context a class/classes. User Prompt with Consultative Interactive Behaviour: Improve the class/classes added in the context applying the system prompt @144-java-data-oriented-programming with the behaviour @behaviour-consultative-interaction |
You can use the System prompt in a purist way or add the Behaviours to customize the final behaviour. |
| Activity | Description | Prompt | Notes |
|---|---|---|---|
| 151-java-performance-jmeter | Run a performance test with Jmeter | User Prompt: Add JMeter performance testing to this project using @151-java-performance-jmeter Note: You could ask the model to create a JMeter based on a RestController/Resource. Example: Can you create a Jmeter file based on the restcontroller in the path src/test/resources/jmeter/load-test.jmx? |
This cursor rule is applied automatically without any interaction with the Software engineer. If you create a Jmeter file with the model, review the generation, sometimes it is necessary to hammer a bit. |
| Activity | Description | Prompt | Notes |
|---|---|---|---|
| 161-java-profiling-detect | Profile your development in runtime and collect evidences to be analyzed later. | Prompt: My Java application has performance issues - help me set up comprehensive profiling process using @161-java-profiling-detect and use the location YOUR-DEVELOPMENT/profiler Note: Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
Non conversational cursor rule. The Cursor rule will generate 2 scripts. One script designed to run your development with the right JVM flags for profiling and the second scripts will ask few questions about what problem do you want to solve/analyze over one particular PID. Step 1: execute ./run-with-profiler.sh --help Step2: execute ./run-jmeter.sh --help Step 3: execute ./profiler/scripts/java-profile.sh |
| 162-java-profiling-analyze | Analyze results from previous step and generate reports with the analysis results. | Prompt: Analyze the results located in YOUR-DEVELOPMENT/profiler and use the cursor rule @162-java-profiling-analyze Note: Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
Non conversational cursor rule. |
| 163-java-profiling-refactor | Refactor code based on profiling analysis findings to fix performance bottlenecks | Prompt: Apply refactoring from profiling analysis using @163-java-profiling-refactor Note: Review docs/profiling-problem-analysis-YYYYMMDD.md and docs/profiling-solutions-YYYYMMDD.md before refactoring. Replace YYYYMMDD with the analysis date. |
Step 3 of profiling workflow. Non conversational. Verifies changes with ./mvnw clean verify. |
| - | Code Refactoring from suggestions from analysis | Can you apply the solutions from @profiling-solutions-yyyymmdd.md in @/info to mitigate bottlenecks |
Make a refactoring with the notes from the analysis |
| 164-java-profiling-verify | Compare results comparing results before and after applying changes in the code | Prompt: Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule @164-java-profiling-verify Note: Put in the context the folder with the results |
This cursor rule is applied automatically without any interaction with the Software engineer. |
| Activity | Description | Prompt | Notes |
|---|---|---|---|
| 170-java-documentation | Generate Java project documentation including README.md, package-info.java files, and Javadoc using a modular step-based approach | Interactive User Prompt: Generate technical documentation about the project with the cursor rule @170-java-documentation User Prompt: Generate README.md with @170-java-documentation without any question (Example) Note: Add in the context the folder to generate the documentation. The rule will analyze existing documentation and ask for user preferences before generating anything. Ensures project validation with Maven before proceeding. |
Focused on documentation generation only. For diagrams, use @033-architecture-diagrams |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 301-frameworks-spring-boot-core | Apply Spring Boot core guidelines — @SpringBootApplication, component annotations, bean definition, @ConfigurationProperties, profiles, constructor injection | User Prompt: Improve the Spring Boot application in context using @301-frameworks-spring-boot-core Note: Add in the context the application classes or project. |
Core Spring Boot best practices. |
| 302-frameworks-spring-boot-rest | Design and improve REST APIs with Spring Boot — HTTP methods, URIs, status codes, DTOs, versioning, error handling, API documentation | User Prompt: Review and improve the REST API in context using @302-frameworks-spring-boot-rest Note: Add in the context the controllers or API classes. |
REST API design principles. |
| 311-frameworks-spring-jdbc | Programmatic JDBC with Spring — JdbcClient (Spring Framework 6.1+), JdbcTemplate for batch/streaming APIs, parameterized SQL, RowMapper, batch updates, transactions | User Prompt: Review or improve JDBC data access using @311-frameworks-spring-jdbc Note: Add in the context repository/DAO classes or SQL usage. |
Use for ad-hoc SQL and JDBC; for repository-style aggregates prefer @312-frameworks-spring-data-jdbc. |
| 312-frameworks-spring-data-jdbc | Apply Spring Data JDBC with Java records — entity design, repository pattern, immutable updates, aggregate relationships, custom queries | User Prompt: Improve the data access layer in context using @312-frameworks-spring-data-jdbc Note: Add in the context the entities, repositories, or project. |
Spring Data JDBC with records. |
| 313-frameworks-spring-db-migrations-flyway | Flyway database migrations with Spring Boot — db/migration scripts, spring.flyway.*, baseline/validate, Java migrations |
User Prompt: Add or review Flyway migrations in context using @313-frameworks-spring-db-migrations-flyway Note: Add pom.xml, application.properties, or migration SQL. |
Pairs with @311 / @312 for JDBC and Spring Data JDBC. |
| 321-frameworks-spring-boot-testing-unit-tests | Write unit tests for Spring Boot — pure Mockito for @Service/@Component, @WebMvcTest, @JsonTest | User Prompt: Add or improve unit tests in context using @321-frameworks-spring-boot-testing-unit-tests Note: Add in the context the classes to test or test classes. |
Pure unit + slice tests with Mockito. For integration tests use @322. |
| 322-frameworks-spring-boot-testing-integration-tests | Write integration tests for Spring Boot — Testcontainers, TestRestTemplate, data management, test structure | User Prompt: Add or improve integration tests in context using @322-frameworks-spring-boot-testing-integration-tests Note: Add in the context the project or test classes. |
Integration testing guidelines. |
| 323-frameworks-spring-boot-testing-acceptance-tests | Implement acceptance tests from Gherkin .feature file for Spring Boot — @acceptance scenarios, RestAssured, @SpringBootTest, Testcontainers, WireMock | Interactive User Prompt: Implement acceptance tests from my Gherkin feature file using @323-frameworks-spring-boot-testing-acceptance-tests Note: Add the .feature file to context. Project must use Spring Boot. |
Preconditions: .feature file in context; Spring Boot. For framework-agnostic Java use @133-java-testing-acceptance-tests. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 401-frameworks-quarkus-core | Apply Quarkus core guidelines — CDI beans, @ApplicationScoped, @ConfigMapping, profiles, lifecycle, extension-friendly structure | User Prompt: Improve the Quarkus application in context using @401-frameworks-quarkus-core Note: Add in the context the application classes or project. |
Core Quarkus and CDI best practices. |
| 402-frameworks-quarkus-rest | Design and improve REST APIs with Quarkus REST (JAX-RS) — resources, HTTP semantics, DTOs, validation, error mapping, OpenAPI | User Prompt: Review and improve the REST API in context using @402-frameworks-quarkus-rest Note: Add in the context the resource classes or project. |
REST on Quarkus REST / JAX-RS. |
| 411-frameworks-quarkus-jdbc | Programmatic JDBC with Quarkus — Agroal datasource, JdbcTemplate or java.sql with named parameters, transactions, records | User Prompt: Review or improve JDBC data access using @411-frameworks-quarkus-jdbc Note: Add in the context repository or SQL usage. |
Explicit SQL; no ORM. |
| 412-frameworks-quarkus-panache | Data access with Hibernate ORM Panache — repositories, active record, queries, transactions; keep persistence simple (no Spring Data JPA) | User Prompt: Improve the data access layer in context using @412-frameworks-quarkus-panache Note: Add entities, repositories, or project. |
Panache for relational data; pair with @411 for raw SQL. |
| 413-frameworks-quarkus-db-migrations-flyway | Flyway database migrations with Quarkus — quarkus-flyway, db/migration, quarkus.flyway.*, migrate-at-start |
User Prompt: Add or review Flyway migrations in context using @413-frameworks-quarkus-db-migrations-flyway Note: Add pom.xml, application.properties, or migration SQL. |
Pairs with @411 / @412 for JDBC and Panache. |
| 421-frameworks-quarkus-testing-unit-tests | Write unit tests for Quarkus — Mockito, @QuarkusTest with injection toggles, RESTAssured slices where appropriate | User Prompt: Add or improve unit tests in context using @421-frameworks-quarkus-testing-unit-tests Note: Add in the context the classes to test or test classes. |
Prefer fast tests without full bootstrap when possible. |
| 422-frameworks-quarkus-testing-integration-tests | Write integration tests for Quarkus — @QuarkusTest, Testcontainers, Dev Services, persistence and HTTP | User Prompt: Add or improve integration tests in context using @422-frameworks-quarkus-testing-integration-tests Note: Add in the context the project or test classes. |
Integration testing with real infrastructure. |
| 423-frameworks-quarkus-testing-acceptance-tests | Implement acceptance tests from Gherkin .feature file for Quarkus — @QuarkusTest, REST Assured, Testcontainers, WireMock | Interactive User Prompt: Implement acceptance tests from my Gherkin feature file using @423-frameworks-quarkus-testing-acceptance-tests Note: Add the .feature file to context. Project must use Quarkus. |
Preconditions: .feature file in context; Quarkus. For framework-agnostic Java use @133-java-testing-acceptance-tests. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 501-frameworks-micronaut-core | Apply Micronaut core guidelines — Micronaut.run, @Singleton/@Factory, @ConfigurationProperties, @Requires, scheduling, graceful shutdown | User Prompt: Improve the Micronaut application in context using @501-frameworks-micronaut-core Note: Add in the context the application classes or project. |
Core Micronaut and DI best practices. |
| 502-frameworks-micronaut-rest | Design and improve REST APIs with Micronaut — @Controller, HTTP semantics, DTOs, validation, errors, OpenAPI | User Prompt: Review and improve the REST API in context using @502-frameworks-micronaut-rest Note: Add in the context the controllers or project. |
REST on Micronaut HTTP. |
| 511-frameworks-micronaut-jdbc | Programmatic JDBC with Micronaut — pooled DataSource, PreparedStatement, text blocks, @Transactional, records, domain exceptions | User Prompt: Review or improve JDBC data access using @511-frameworks-micronaut-jdbc Note: Add in the context repository or SQL usage. |
Explicit SQL; pair with @512 for generated repositories. |
| 512-frameworks-micronaut-data | Micronaut Data — @MappedEntity, repositories, @Query, transactions, pagination, Testcontainers tests | User Prompt: Improve the data access layer in context using @512-frameworks-micronaut-data Note: Add entities, repositories, or project. |
Repository-style access; use @511 for raw JDBC. |
| 513-frameworks-micronaut-db-migrations-flyway | Flyway database migrations with Micronaut — micronaut-flyway, db/migration, flyway.datasources.* |
User Prompt: Add or review Flyway migrations in context using @513-frameworks-micronaut-db-migrations-flyway Note: Add pom.xml, application.yml, or migration SQL. |
Pairs with @511 / @512 for JDBC and Micronaut Data. |
| 521-frameworks-micronaut-testing-unit-tests | Unit tests for Micronaut — Mockito-first, @MicronautTest with @MockBean, HttpClient | User Prompt: Add or improve unit tests in context using @521-frameworks-micronaut-testing-unit-tests Note: Add in the context the classes to test or test classes. |
Fast tests without full boot when possible. |
| 522-frameworks-micronaut-testing-integration-tests | Integration tests for Micronaut — @MicronautTest, TestPropertyProvider, Testcontainers, HttpClient | User Prompt: Add or improve integration tests in context using @522-frameworks-micronaut-testing-integration-tests Note: Add in the context the project or test classes. |
Real infrastructure in tests. |
| 523-frameworks-micronaut-testing-acceptance-tests | Acceptance tests from Gherkin .feature for Micronaut — @acceptance, HttpClient, Testcontainers, WireMock | Interactive User Prompt: Implement acceptance tests from my Gherkin feature file using @523-frameworks-micronaut-testing-acceptance-tests Note: Add the .feature file to context. Project must use Micronaut. |
Preconditions: .feature in context; Micronaut. For framework-agnostic Java use @133-java-testing-acceptance-tests. |
| Cursor Rule | Description | Prompt | Notes |
|---|---|---|---|
| 200-agents-md | Generate AGENTS.md files for Java repositories using a modular step-based approach. AGENTS.md guides AI agents and contributors on project conventions, tech stack, file structure, commands, Git workflow, and boundaries | Interactive User Prompt: Generate AGENTS.md for the project with the cursor rule @200-agents-md Note: Add in the context the project root folder. The rule will ask 6 questions to understand requirements before generating. Handles existing AGENTS.md (overwrite/merge/backup). |
Focused on AGENTS.md generation only. Asks role, tech stack, file structure, commands, Git workflow, and boundaries before generating |
Note: This guide is self-contained and portable. Copy it into any Java project to get started with Cursor Rules for Java development.