Reindexing rules

Author: jabrena

…rsor/rules/151-java-profiling-detect.mdc …rsor/rules/161-java-profiling-detect.mdc.cursor/rules/151-java-profiling-detect.mdc renamed to .cursor/rules/161-java-profiling-detect.mdc .cursor/rules/151-java-profiling-detect.mdc renamed to .cursor/rules/161-java-profiling-detect.mdc

@@ -49,10 +49,10 @@ Use the following process to improve the java development in some areas if requi
 
 | Activity | Description | Prompt | Notes |
 |----------|------|--------|-------|
-| [151-java-profiling-detect](.cursor/rules/151-java-profiling-detect.mdc) | Measure problems | `My Java application has performance issues - help me set up comprehensive profiling process using @151-java-profiling-detect.mdc and use the location YOUR-DEVELOPMENT/profiler` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
-| [152-java-profiling-analyze](.cursor/rules/152-java-profiling-analyze.mdc) | Analyze results | `Analyze the results located in YOUR-DEVELOPMENT/profiler and use the cursor rule @152-java-profiling-analyze` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
+| [161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.mdc) | Measure problems | `My Java application has performance issues - help me set up comprehensive profiling process using @151-java-profiling-detect.mdc and use the location YOUR-DEVELOPMENT/profiler` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
+| [162-java-profiling-analyze](.cursor/rules/162-java-profiling-analyze.mdc) | Analyze results | `Analyze the results located in YOUR-DEVELOPMENT/profiler and use the cursor rule @152-java-profiling-analyze` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
 | - | 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 |
-| [154-java-profiling-compare](.cursor/rules/152-java-profiling-compare.mdc) | Analyze results | `Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule 154-java-profiling-compare.mdc` | Put in the context the folder with the results |
+| [164-java-profiling-compare](.cursor/rules/162-java-profiling-compare.mdc) | Analyze results | `Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule 154-java-profiling-compare.mdc` | Put in the context the folder with the results |
 
 ## Reference Table: Java Cursor Rules
 
@@ -70,10 +70,9 @@ Use the following process to improve the java development in some areas if requi
 | Modern Java Features | @141-java-refactoring-with-modern-features | Refactoring with modern Java (Java 8+) features |
 | Functional Programming | @142-java-functional-programming | Applying functional programming in Java |
 | Data Oriented Programming | @143-java-data-oriented-programming | Data-oriented programming style in Java |
-| Java Profiling | @151-java-profiling-detect | Generate profiling data |
-| Java Profiling | @152-java-profiling-analyze | Analyze profiling data |
-| Java Profiling | @154-java-profiling-compare | Compare results after refactoring |
-| SQL Guidelines | @500-sql | SQL development best practices |
+| Java Profiling | @161-java-profiling-detect | Generate profiling data |
+| Java Profiling | @162-java-profiling-analyze | Analyze profiling data |
+| Java Profiling | @164-java-profiling-compare | Compare results after refactoring |
 
 ## Tips & Best Practices
 

…sor/rules/152-java-profiling-analyze.mdc …sor/rules/162-java-profiling-analyze.mdc.cursor/rules/152-java-profiling-analyze.mdc renamed to .cursor/rules/162-java-profiling-analyze.mdc .cursor/rules/152-java-profiling-analyze.mdc renamed to .cursor/rules/162-java-profiling-analyze.mdc

@@ -61,10 +61,10 @@ Using the Cursor rules is straightforward: simply `drag and drop` the cursor rul
 
 | Activity | Description | Prompt | Notes |
 |----------|------|--------|-------|
-| [151-java-profiling-detect](.cursor/rules/151-java-profiling-detect.mdc) | Measure problems | `My Java application has performance issues - help me set up comprehensive profiling process using @151-java-profiling-detect.mdc and use the location YOUR-DEVELOPMENT/profiler` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
-| [152-java-profiling-analyze](.cursor/rules/152-java-profiling-analyze.mdc) | Analyze results | `Analyze the results located in YOUR-DEVELOPMENT/profiler and use the cursor rule @152-java-profiling-analyze` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
+| [161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.mdc) | Measure problems | `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` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
+| [162-java-profiling-analyze](.cursor/rules/162-java-profiling-analyze.mdc) | Analyze results | `Analyze the results located in YOUR-DEVELOPMENT/profiler and use the cursor rule @162-java-profiling-analyze` | Replace YOUR-DEVELOPMENT with your actual development path. Example: examples/spring-boot-memory-leak-demo/profiler |
 | - | 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 |
-| [154-java-profiling-compare](.cursor/rules/152-java-profiling-compare.mdc) | Analyze results | `Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule 154-java-profiling-compare.mdc` | Put in the context the folder with the results |
+| [164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.mdc) | Analyze results | `Review if the problems was solved with last refactoring using the reports located in @/results with the cursor rule 154-java-profiling-compare.mdc` | Put in the context the folder with the results |
 
 ## Getting started
 
@@ -139,3 +139,5 @@ If you have new ideas to improve any of the current Cursor rules or add a new on
 - https://github.com/jabrena/plantuml-to-png-cli
 - https://github.com/jabrena/setup-cli
 - https://github.com/jabrena/jbang-catalog
+
+Powered by [Cursor](https://www.cursor.com/)