You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,24 +40,24 @@ Using the Cursor rules is straightforward: simply `drag and drop` the cursor rul
40
40
41
41
| Cursor Rule | Description | Prompt | Notes |
42
42
|-------------|-------------|--------|-------|
43
-
|[123-java-general-guidelines](.cursor/rules/123-java-general-guidelines.mdc)|General Java Guidelines|**Prompt:**`Review my code for general Java best practices using the cursor rule @123-java-general-guidelines`**Note:** Add a package in the context. | Non conversational cursor rule. |
44
-
|[124-java-secure-coding](.cursor/rules/124-java-secure-coding.mdc)| Secure Java Coding |**Prompt:**`Check my code for security issues using the cursor rule @124-java-secure-coding`**Note:** Add a package in the context. | Non conversational cursor rule. |
45
-
|[125-java-concurrency](.cursor/rules/125-java-concurrency.mdc)| Concurrency |**Prompt:**`Review my code for concurrency best practices using the cursor rule @125-java-concurrency`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | Non conversational cursor rule. |
46
-
|[126-java-logging](.cursor/rules/126-java-logging.mdc)|Logging Guidelines|**Prompt:**`Help me improve logging using the cursor rule @126-java-logging`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
43
+
|[123-java-general-guidelines](.cursor/rules/123-java-general-guidelines.mdc)|Apply general purpose Java guidelines|**Prompt:**`Review my code for general Java best practices using the cursor rule @123-java-general-guidelines`**Note:** Add a package in the context. | Non conversational cursor rule. |
44
+
|[124-java-secure-coding](.cursor/rules/124-java-secure-coding.mdc)|Review your coide with Secure Java Coding rules|**Prompt:**`Check my code for security issues using the cursor rule @124-java-secure-coding`**Note:** Add a package in the context. | Non conversational cursor rule. |
45
+
|[125-java-concurrency](.cursor/rules/125-java-concurrency.mdc)|Improve your code with Concurrency rules|**Prompt:**`Review my code for concurrency best practices using the cursor rule @125-java-concurrency`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | Non conversational cursor rule. |
46
+
|[126-java-logging](.cursor/rules/126-java-logging.mdc)|Apply logging guidelines in your development|**Prompt:**`Help me improve logging using the cursor rule @126-java-logging`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
47
47
48
48
### Testing rules
49
49
50
50
| Cursor Rule | Description | Prompt | Notes |
51
51
|-------------|-------------|--------|-------|
52
-
|[131-java-unit-testing](.cursor/rules/131-java-unit-testing.mdc)| Unit Testing |**Prompt:**`Can improve the unit tests using the cursor rule @131-java-unit-testing`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
52
+
|[131-java-unit-testing](.cursor/rules/131-java-unit-testing.mdc)|Apply Unit Testing best practices|**Prompt:**`Can improve the unit tests using the cursor rule @131-java-unit-testing`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
53
53
54
54
### Refactoring rules
55
55
56
56
| Cursor Rule | Description | Prompt | Notes |
57
57
|-------------|-------------|--------|-------|
58
-
|[141-java-refactoring-with-modern-features](.cursor/rules/141-java-refactoring-with-modern-features.mdc)| Add Modern Java Features |**Prompt:**`Refactor my code to use modern Java features using the cursor rule @141-java-refactoring-with-modern-features`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | Non conversational cursor rule. |
59
-
|[142-java-functional-programming](.cursor/rules/142-java-functional-programming.mdc)| Functional Programming |**Prompt:**`Refactor my code to use functional programming using the cursor rule @142-java-functional-programming`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
60
-
|[143-java-data-oriented-programming](.cursor/rules/143-java-data-oriented-programming.mdc)| Data Oriented Programming|**Prompt:**`Refactor my code to use data oriented programming using the cursor rule @143-java-data-oriented-programming`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
58
+
|[141-java-refactoring-with-modern-features](.cursor/rules/141-java-refactoring-with-modern-features.mdc)| Add Modern Java Features in your development |**Prompt:**`Refactor my code to use modern Java features using the cursor rule @141-java-refactoring-with-modern-features`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | Non conversational cursor rule. |
59
+
|[142-java-functional-programming](.cursor/rules/142-java-functional-programming.mdc)|Add Functional Programming style in your development|**Prompt:**`Refactor my code to use functional programming using the cursor rule @142-java-functional-programming`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
60
+
|[143-java-data-oriented-programming](.cursor/rules/143-java-data-oriented-programming.mdc)|Add Data Oriented Programmin in your development|**Prompt:**`Refactor my code to use data oriented programming using the cursor rule @143-java-data-oriented-programming`**Note:** Add a class or package which consider that it could bye improved by the cursor rule. | This cursor rule is applied automatically without any interaction with the Software engineer. |
61
61
62
62
### Performance rule (Jmeter)
63
63
@@ -69,10 +69,10 @@ Using the Cursor rules is straightforward: simply `drag and drop` the cursor rul
69
69
70
70
| Activity | Description | Prompt | Notes |
71
71
|----------|-------------|--------|-------|
72
-
|[161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.mdc)|Measure problems|**Prompt:**`My Java application has performance issues - help me set up comprehensive profiling process using @161-java-profiling-detect.mdc 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. |
73
-
|[162-java-profiling-analyze](.cursor/rules/162-java-profiling-analyze.mdc)| Analyze results from previous step generating reports with the analysis.|**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. |
74
-
| - | Code Refactoring |`Can you apply the solutions from @profiling-solutions-yyyymmdd.md in @/info to mitigate bottlenecks`| Make a refactoring with the notes from the analysis |
75
-
|[164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.mdc)|Analyze results |**Prompt:**`Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule 154-java-profiling-compare.mdc`**Note:** Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
72
+
|[161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.mdc)|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.mdc 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. |
73
+
|[162-java-profiling-analyze](.cursor/rules/162-java-profiling-analyze.mdc)| 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. |
74
+
| - | 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 |
75
+
|[164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.mdc)|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 154-java-profiling-compare.mdc`**Note:** Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
0 commit comments