Improving the article

Author: jabrena

.cursor/rules/100-java-cursor-rules-list.md

@@ -81,7 +81,7 @@ Use the following collection of System prompts of Java to improve your Java deve
 | [161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.md) | 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](.cursor/rules/162-java-profiling-analyze.md) | 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. |
 | - | 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-compare](.cursor/rules/164-java-profiling-compare.md) | 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` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
+| [164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.md) | 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-compare` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
 
 ## Documentation rules
 

CURSOR-RULES-JAVA.md

@@ -63,7 +63,7 @@ Use the following collection of System prompts of Java to improve your Java deve
 | [161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.md) | 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](.cursor/rules/162-java-profiling-analyze.md) | 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. |
 | - | 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-compare](.cursor/rules/164-java-profiling-compare.md) | 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` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
+| [164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.md) | 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-compare` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
 
 ## Documentation rules
 

docs/blog/2025/09/release-0.11.0.html

@@ -160,6 +160,8 @@ <h2> Why decouple Pure System prompts from specialized behaviors?</h2>
 <li><a href="https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-consultative-interaction.md"><code>@behaviour-consultative-interaction</code></a></li>
 <li><a href="https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-progressive-learning.md"><code>@behaviour-progressive-learning</code></a></li>
 </ul>
+<p>Using specialized behaviours like <code>@behaviour-progressive-learning</code> in a Creative way in your repositories could increase <code>the collective ownership</code> and spread easily the <code>Code Standards</code>implemented in the code.</p>
+<p><a href="http://www.extremeprogramming.org/"><img src="/cursor-rules-java/images/xp.png" alt="" /></a></p>
 <hr />
 <p>After this design change applied into the different system prompts, you can use them in your <code>Data pipelines</code> for different use cases such as <code>automatic coding</code>, <code>code refactoring</code>, <code>continuous profiling</code>, and more.</p>
 <p><img src="/cursor-rules-java/images/data-pipeline-workflow.png" alt="" /></p>
@@ -176,7 +178,14 @@ <h2>New UML state machine diagrams for better understanding in complex dependenc
 <h2>Profiling improvements</h2>
 <p>In this release, the script <code>profile-java-process.sh</code>, included in  <code>@161-java-profiling-detect</code>, was updated to include the latest release (v4.1) of the popular profiling tool <code>Async-profiler</code>. In addition, the script added new <code>JFR</code> options available in <code>Java 25</code> and earlier.</p>
 <p><img src="/cursor-rules-java/images/0.11.0-profiling-menu.png" alt="" /></p>
-<p>In recent months, I have been inspired by the work of outstanding engineers in this field: <a href="https://x.com/forked_franz">Francesco Nigro</a>, <a href="https://x.com/jerrinot">Jaromir Hamala</a>, and <a href="https://x.com/parttimen3rd">Johannes Bechberger</a>. I highly recommend following them.</p>
+<p>In recent months, I have been inspired by the work of outstanding engineers in this field: <a href="https://x.com/forked_franz">Francesco Nigro</a>, <a href="https://x.com/jerrinot">Jaromir Hamala</a>, <a href="https://x.com/parttimen3rd">Johannes Bechberger</a> &amp; <a href="https://x.com/brendangregg">Brendan Gregg</a>. I highly recommend following them.</p>
+<p>If you are interested in the Profiling model <code>Detect, Analyze, Refactor &amp; Compare</code> implemented with the following set of System prompts:</p>
+<ul>
+<li><code>@161-java-profiling-detect</code></li>
+<li><code>@162-java-profiling-analyze</code></li>
+<li><code>@164-java-profiling-compare</code></li>
+</ul>
+<p>You could review the course about <a href="https://jabrena.github.io/cursor-rules-java/courses/profile-memory-leak/index.html">Detecting memory leaks with System prompts</a>.</p>
 <h2>A new website</h2>
 <p>In recent releases, the project published an article summarizing its evolution and shared it across channels like Twitter, Reddit, and LinkedIn. To unify the source of truth, and leveraging <a href="https://docs.github.com/es/pages">GitHub Pages</a>, the project now has <a href="https://jabrena.github.io/cursor-rules-java/index.html">a dedicated website</a>.</p>
 <p>The website includes information about releases, technical articles you can apply in your projects, and courses.</p>

docs/feed.xml

@@ -2,7 +2,7 @@
 <feed xmlns='http://www.w3.org/2005/Atom' xml:lang='en'>
   <id>https://jabrena.github.io/cursor-rules-java/</id>
   <title>Cursor Rules for Java</title>
-  <updated>2025-09-27T20:38:34+0200</updated>
+  <updated>2025-09-27T23:47:26+0200</updated>
   <link rel="alternate" type="text/html" href="https://jabrena.github.io/cursor-rules-java/" />
   <link rel='self' type='application/atom+xml' href='https://jabrena.github.io/cursor-rules-java//feed.xml' />
   <entry>

docs/images/xp.png

@@ -100,10 +100,15 @@ With this evolution, software engineers now can combine pure system prompts and
 - [`@behaviour-consultative-interaction`](https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-consultative-interaction.md)
 - [`@behaviour-progressive-learning`](https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-progressive-learning.md)
 
+Using specialized behaviours like `@behaviour-progressive-learning` in a Creative way in your repositories could increase `the collective ownership` and spread easily the `Code Standards`implemented in the code.
+
+[![](/cursor-rules-java/images/xp.png)](http://www.extremeprogramming.org/)
+
 ---
 
 After this design change applied into the different system prompts, you can use them in your `Data pipelines` for different use cases such as `automatic coding`, `code refactoring`, `continuous profiling`, and more.
 
+
 ![](/cursor-rules-java/images/data-pipeline-workflow.png)
 
 ## New UML state machine diagrams for better understanding in complex dependencies.
@@ -131,7 +136,15 @@ In this release, the script `profile-java-process.sh`, included in  `@161-java-p
 
 ![](/cursor-rules-java/images/0.11.0-profiling-menu.png)
 
-In recent months, I have been inspired by the work of outstanding engineers in this field: [Francesco Nigro](https://x.com/forked_franz), [Jaromir Hamala](https://x.com/jerrinot), and [Johannes Bechberger](https://x.com/parttimen3rd). I highly recommend following them.
+In recent months, I have been inspired by the work of outstanding engineers in this field: [Francesco Nigro](https://x.com/forked_franz), [Jaromir Hamala](https://x.com/jerrinot), [Johannes Bechberger](https://x.com/parttimen3rd) & [Brendan Gregg](https://x.com/brendangregg). I highly recommend following them.
+
+If you are interested in the Profiling model `Detect, Analyze, Refactor & Compare` implemented with the following set of System prompts:
+
+- `@161-java-profiling-detect`
+- `@162-java-profiling-analyze`
+- `@164-java-profiling-compare`
+
+You could review the course about [Detecting memory leaks with System prompts](https://jabrena.github.io/cursor-rules-java/courses/profile-memory-leak/index.html).
 
 ## A new website
 

site-generator/assets/images/xp.png

@@ -64,7 +64,7 @@ Use the following collection of System prompts of Java to improve your Java deve
 | [161-java-profiling-detect](.cursor/rules/161-java-profiling-detect.md) | 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](.cursor/rules/162-java-profiling-analyze.md) | 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. |
 | - | 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-compare](.cursor/rules/164-java-profiling-compare.md) | 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` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
+| [164-java-profiling-compare](.cursor/rules/164-java-profiling-compare.md) | 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-compare` **Note:**  Put in the context the folder with the results | This cursor rule is applied automatically without any interaction with the Software engineer. |
 
 ## Documentation rules