Apex Core

Workflow

1. Identify execution context: synchronous, Queueable, Batchable, Scheduled, trigger, invocable, REST/SOAP, or UI-facing Apex.
2. Identify transaction boundaries and expected record volume.
3. Identify data access and security requirements before writing code.
4. Prefer simple, explicit Apex over unnecessary abstraction.
5. Keep methods cohesive and side effects obvious.
6. Handle expected business failures explicitly; do not swallow exceptions.
7. Avoid hard-coded IDs, field names, URLs, credentials, or org-specific assumptions unless the requirement explicitly calls for them.
8. For behavior that varies by Salesforce/API version, verify the target API version and current official documentation.

Coding rules