sf-apexlisted

<!-- Adapted from Jaganpro/sf-skills@ff1ab74 (MIT). This file layers Brite conventions from brite-salesforce/CLAUDE.md §Apex & Automation (lines 175-196) + §Engineering Standards (lines 41-42). --> # sf-apex: Salesforce Apex Code Generation and Review (Brite edition) Use this skill when the user needs **production Apex**: new classes, triggers, selectors, services, async jobs, invocable methods, test classes, or evidence-based review of existing `.cls` / `.trigger` code. ## Brite Context Brite's Apex stance: - **Apex-first automation.** Flows are limited to screen flows and simple notifications; all business logic lives in Apex (`brite-salesforce/CLAUDE.md` §Engineering Standards line 41). - **Trigger handler dispatch.** One trigger per object delegates to a handler class. After-insert work goes through a `*AfterInsertService` interface and per-LeadSource registries — new services register themselves under the matching source list, never in the handler body directly. Canonical example: `LeadTriggerHandler` + `LeadAfterInsertService` with `webFormAfterInsertServices` / `newsletterAfterInsertServices` registries. - **Test coverage target.** 100% per class (not the 75% SF floor); 90%+ org-wide. Required for all triggers and service classes (`brite-salesforce/CLAUDE.md` §Engineering Standards line 42). - **Async defaults.** Queueable for standard async, Schedulable for recurring work, Batch only for very large record volumes. Governor-limit discipline is enforced through `BA