Refactoring about Output format

jabrena · jabrena · commit 147a326a85e3 · 2025-07-08T09:05:55.000+02:00
diff --git a/.cursor/rules/100-java-checklist-guide.mdc b/.cursor/rules/100-java-checklist-guide.mdc
@@ -26,7 +26,7 @@ Create a markdown file named `CURSOR-RULES-JAVA.md` with the following exact str
 - **ONLY** use the exact wording and structure from the template
 - If a cursor rule exists in the workspace but is not in the template, **DO NOT** include it
 
-## Output Requirements
+## Output Format
 
 - Generate the complete markdown file following the embedded template exactly
 - Use proper markdown formatting with headers, code blocks, tables, and checklists
diff --git a/.cursor/rules/110-java-maven-best-practices.mdc b/.cursor/rules/110-java-maven-best-practices.mdc
@@ -584,7 +584,7 @@ Description: Define all dependency and plugin versions in the `<properties>` sec
 </project>
 
 ```
-## Output Requirements
+## Output Format
 
 - Update the file pom.xml if something is not correct
 - verify changes with the command: `mvn validate`
diff --git a/.cursor/rules/112-java-maven-documentation.mdc b/.cursor/rules/112-java-maven-documentation.mdc
@@ -24,7 +24,7 @@ Create a markdown file named `README-DEV.md` with the following exact structure:
 - **ONLY** use the exact wording and structure from the template
 - If a cursor rule exists in the workspace but is not in the template, **DO NOT** include it
 
-## Output Requirements
+## Output Format
 
 - Generate the complete markdown file following the embedded template exactly
 - Use proper markdown formatting with headers, code blocks, tables, and checklists
diff --git a/.cursor/rules/121-java-object-oriented-design.mdc b/.cursor/rules/121-java-object-oriented-design.mdc
@@ -2466,8 +2466,8 @@ public class FileManager {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply object-oriented design principles to improve code quality and maintainability
 - Refactor code to follow SOLID principles and eliminate design smells
-- Verify code changes compile and pass tests
+- Verify code changes compile and pass tests
diff --git a/.cursor/rules/122-java-type-design.mdc b/.cursor/rules/122-java-type-design.mdc
@@ -851,7 +851,7 @@ class BadProductService {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply type design principles to improve code quality and maintainability
 - Create type-safe wrappers for domain-specific types
diff --git a/.cursor/rules/123-java-general-guidelines.mdc b/.cursor/rules/123-java-general-guidelines.mdc
@@ -328,8 +328,8 @@ public class UnsafeFileProcessor {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply the Java general guidelines to improve code quality and maintainability
 - Follow naming conventions, formatting rules, and documentation standards
-- Implement comprehensive error handling with security considerations
+- Implement comprehensive error handling with security considerations
diff --git a/generator/src/main/resources/cursor-rules.xsl b/generator/src/main/resources/cursor-rules.xsl
@@ -122,7 +122,7 @@ Description: </xsl:text>        <xsl:value-of select="normalize-space(example-de
     <!-- Output format section template -->
     <xsl:template match="output-format">
         <xsl:text>
-## Output Requirements
+## Output Format
 
 </xsl:text>
         <xsl:for-each select="output-format-list/output-format-item">
diff --git a/generator/src/test/resources/100-java-checklist-guide.mdc b/generator/src/test/resources/100-java-checklist-guide.mdc
@@ -26,7 +26,7 @@ Create a markdown file named `CURSOR-RULES-JAVA.md` with the following exact str
 - **ONLY** use the exact wording and structure from the template
 - If a cursor rule exists in the workspace but is not in the template, **DO NOT** include it
 
-## Output Requirements
+## Output Format
 
 - Generate the complete markdown file following the embedded template exactly
 - Use proper markdown formatting with headers, code blocks, tables, and checklists
diff --git a/generator/src/test/resources/110-java-maven-best-practices.mdc b/generator/src/test/resources/110-java-maven-best-practices.mdc
@@ -584,7 +584,7 @@ Description: Define all dependency and plugin versions in the `<properties>` sec
 </project>
 
 ```
-## Output Requirements
+## Output Format
 
 - Update the file pom.xml if something is not correct
 - verify changes with the command: `mvn validate`
diff --git a/generator/src/test/resources/112-java-maven-documentation.mdc b/generator/src/test/resources/112-java-maven-documentation.mdc
@@ -24,7 +24,7 @@ Create a markdown file named `README-DEV.md` with the following exact structure:
 - **ONLY** use the exact wording and structure from the template
 - If a cursor rule exists in the workspace but is not in the template, **DO NOT** include it
 
-## Output Requirements
+## Output Format
 
 - Generate the complete markdown file following the embedded template exactly
 - Use proper markdown formatting with headers, code blocks, tables, and checklists
diff --git a/generator/src/test/resources/121-java-object-oriented-design.mdc b/generator/src/test/resources/121-java-object-oriented-design.mdc
@@ -2466,8 +2466,8 @@ public class FileManager {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply object-oriented design principles to improve code quality and maintainability
 - Refactor code to follow SOLID principles and eliminate design smells
-- Verify code changes compile and pass tests
+- Verify code changes compile and pass tests
diff --git a/generator/src/test/resources/122-java-type-design.mdc b/generator/src/test/resources/122-java-type-design.mdc
@@ -851,7 +851,7 @@ class BadProductService {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply type design principles to improve code quality and maintainability
 - Create type-safe wrappers for domain-specific types
diff --git a/generator/src/test/resources/123-java-general-guidelines.mdc b/generator/src/test/resources/123-java-general-guidelines.mdc
@@ -328,8 +328,8 @@ public class UnsafeFileProcessor {
     }
 }
 ```
-## Output Requirements
+## Output Format
 
 - Apply the Java general guidelines to improve code quality and maintainability
 - Follow naming conventions, formatting rules, and documentation standards
-- Implement comprehensive error handling with security considerations
+- Implement comprehensive error handling with security considerations

Original file line number	Diff line number	Diff line change
`@@ -2466,8 +2466,8 @@ public class FileManager {`
`2466`	`2466`	`}`
`2467`	`2467`	`}`
`2468`	`2468`	```
`2469`		`-## Output Requirements`
	`2469`	`+## Output Format`
`2470`	`2470`
`2471`	`2471`	`- Apply object-oriented design principles to improve code quality and maintainability`
`2472`	`2472`	`- Refactor code to follow SOLID principles and eliminate design smells`
`2473`		`-- Verify code changes compile and pass tests`
	`2473`	`+- Verify code changes compile and pass tests`
Original file line number	Diff line number	Diff line change
`@@ -851,7 +851,7 @@ class BadProductService {`
`851`	`851`	`}`
`852`	`852`	`}`
`853`	`853`	```
`854`		`-## Output Requirements`
	`854`	`+## Output Format`
`855`	`855`
`856`	`856`	`- Apply type design principles to improve code quality and maintainability`
`857`	`857`	`- Create type-safe wrappers for domain-specific types`
Original file line number	Diff line number	Diff line change
`@@ -328,8 +328,8 @@ public class UnsafeFileProcessor {`
`328`	`328`	`}`
`329`	`329`	`}`
`330`	`330`	```
`331`		`-## Output Requirements`
	`331`	`+## Output Format`
`332`	`332`
`333`	`333`	`- Apply the Java general guidelines to improve code quality and maintainability`
`334`	`334`	`- Follow naming conventions, formatting rules, and documentation standards`
`335`		`-- Implement comprehensive error handling with security considerations`
	`335`	`+- Implement comprehensive error handling with security considerations`