Skip to content

Commit c7b5fbb

Browse files
authored
Feature/goal renaming (#164)
* Minor change
1 parent 8debade commit c7b5fbb

27 files changed

Lines changed: 35 additions & 35 deletions

.cursor/rules/100-java-checklist-guide.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java programming language and technical documentation
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Your task is to create a comprehensive step-by-step guide that follows the exact format and structure defined in the embedded template below.
1515

.cursor/rules/110-java-maven-best-practices.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Update the pom.xml based on the following rules about Maven best practices.
1515

.cursor/rules/112-java-maven-documentation.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
When creating a README-DEV.md file for a Maven project, include ONLY the following sections with the specified Maven goals. Do NOT add any additional sections, explanations, or content beyond what is explicitly listed below.
1515

.cursor/rules/121-java-object-oriented-design.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Apply comprehensive guidelines for robust Java object-oriented design and refactoring. Follow core principles like SOLID, DRY, and YAGNI, implement best practices for class and interface design including favoring composition over inheritance and designing for immutability. Master encapsulation, inheritance, and polymorphism, and identify and refactor common object-oriented design code smells such as God Classes, Feature Envy, and Data Clumps to promote maintainable, flexible, and understandable code.
1515

.cursor/rules/122-java-type-design.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Type design thinking in Java applies typography principles to code structure and organization. Just as typography creates readable, accessible text, thoughtful type design in Java produces maintainable, comprehensible code.
1515

.cursor/rules/123-java-general-guidelines.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
This document outlines general Java coding guidelines covering fundamental aspects such as naming conventions for packages, classes, methods, variables, and constants; code formatting rules including indentation, line length, brace style, and whitespace usage; standards for organizing import statements; best practices for Javadoc documentation; and comprehensive error and exception handling with a strong focus on security, including avoiding sensitive information exposure, catching specific exceptions, and secure resource management.
1515

.cursor/rules/124-java-secure-coding.mdc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Apply secure coding practices to Java code to prevent common vulnerabilities and enhance application security.
1515

.cursor/rules/125-java-concurrency.mdc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Effective Java concurrency relies on understanding thread safety fundamentals, using `java.util.concurrent` utilities, and managing thread pools with `ExecutorService`. Key practices include implementing concurrent design patterns like Producer-Consumer, leveraging `CompletableFuture` for asynchronous tasks, and ensuring thread safety through immutability and safe publication. Performance aspects like lock contention and memory consistency must be considered. Thorough testing, including stress tests and thread dump analysis, is crucial. Modern Java offers virtual threads for enhanced scalability, structured concurrency for simplified task management, and scoped values for safer thread-shared data as alternatives to thread-locals.
1515

@@ -1650,4 +1650,4 @@ class BadScopedValueUsage {
16501650
System.out.println("Processing data...");
16511651
}
16521652
}
1653-
```
1653+
```

.cursor/rules/126-java-logging.mdc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Effective Java logging involves selecting a standard framework (SLF4J with Logback/Log4j2), using appropriate log levels (ERROR, WARN, INFO, DEBUG, TRACE), and adhering to core practices like parameterized logging, proper exception handling, and avoiding sensitive data exposure. Configuration should be environment-specific with clear output formats. Security is paramount: mask sensitive data, control log access, and ensure secure transmission. Implement centralized log aggregation, monitoring, and alerting for proactive issue detection. Finally, logging behavior and its impact should be validated through comprehensive testing.
1515

@@ -1382,4 +1382,4 @@ public class UntestableLogging {
13821382
// is difficult. Developers might skip testing logging, leading to unverified log output.
13831383
}
13841384
}
1385-
```
1385+
```

.cursor/rules/131-java-unit-testing.mdc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ alwaysApply: false
99

1010
You are a Senior software engineer with extensive experience in Java software development
1111

12-
## Instructions for AI
12+
## Goal
1313

1414
Effective Java unit testing involves using JUnit 5 annotations and AssertJ for fluent assertions. Tests should follow the Given-When-Then structure with descriptive names for clarity. Each test must have a single responsibility, be independent, and leverage parameterized tests for data variations. Mocking dependencies with frameworks like Mockito is crucial for isolating the unit under test. While code coverage is a useful guide, the focus should be on meaningful tests for critical logic and edge cases. Test classes and methods should typically be package-private. Strategies for code splitting include small test methods and helper functions. Anti-patterns like testing implementation details, hard-coded values, and ignoring failures should be avoided. Proper state management involves isolated state and immutable objects, and error handling should include testing for expected exceptions and their messages.
1515

@@ -775,4 +775,4 @@ public class UserValidationPoorTest {
775775
assertThat(validator.isValidEmailFormat("test@example.com")).isTrue(); // No invalid formats, no nulls
776776
}
777777
}
778-
```
778+
```

0 commit comments

Comments
 (0)