ChatGPT · Java · Spring Boot · Popular baseline

# ChatGPT · Java + Spring Boot  
Generated February 10, 2026  
Agent: ChatGPT  
Language: Java  
Framework: Spring Boot

## Global rules
- Start by reading existing project instructions and architecture docs before changing behavior.

- Prefer minimal diffs and preserve existing code style and naming conventions.

- State assumptions and call out risks before making breaking or cross-module changes.

- When behavior changes, add or update tests in the closest existing test layer.

- Never commit secrets, tokens, credentials, or generated private keys.

Start by reading existing project instructions and architecture docs before changing behavior.

Prefer minimal diffs and preserve existing code style and naming conventions.

State assumptions and call out risks before making breaking or cross-module changes.

When behavior changes, add or update tests in the closest existing test layer.

Never commit secrets, tokens, credentials, or generated private keys.

## Agent-specific
- State goals, constraints, and acceptance criteria before implementation.

- When generating code, prioritize readability and maintainability.

- For risky changes, propose safer alternatives and tradeoffs.

## Language-specific
- Use clear package boundaries and explicit service interfaces.

- Prefer immutable DTOs/value objects for shared contracts.

- Keep transactional boundaries explicit.

## Framework-specific
- Use clear service/repository boundaries and transactional methods.

- Keep controllers focused on input/output mapping and validation.

## Options

### Testing rules
- Require tests for changed behavior or document why tests were not added.

- Run the smallest relevant test subset first, then broaden if needed.

### Architecture rules
- Preserve module boundaries and avoid leaking internal abstractions.

- Prefer incremental refactors over large rewrites.

### Security rules
- Validate and sanitize all user-controlled input.

- Apply least-privilege defaults for data access and actions.

### Ask before changing public API
- Before changing a public API, present the impact and ask for explicit confirmation.

- If approved, document the migration path for consumers.

### Prefer minimal diffs
- Limit changes to the smallest set of files and lines needed.

- Defer unrelated cleanup to separate follow-up changes.

### Documentation rules
- Update docs/examples whenever behavior, APIs, or setup steps change.

- Add concise release notes for user-facing or breaking changes.