What problem does it solve? Writing Salesforce Apex that survives deployment requires juggling sharing keywords, user-mode versus system-mode access, bulkification, trigger frameworks, and partial-success DML handling — and API 67.0 changed the defaults, invalidating older patterns like WITH SECURITY_ENFORCED. This Skill encodes those rules so generated or reviewed Apex is secure, bulkified, and gate-compliant from the start. ## Core Features & Use Cases - Security-correct Apex by default: Enforces explicit sharing declarations (with/without/inherited sharing) and explicit access modes (WITH USER_MODE, insert as user, AccessLevel) aligned with API 67.0 behavior changes. - Trigger framework and bulkification patterns: Provides a runnable one-trigger-per-object handler framework with recursion guards, bypass registry, and map-driven bulkified idioms that eliminate SOQL/DML in loops. - Enterprise layering and integration surfaces: Includes dependency-free Selector, Domain, Service, and Unit of Work implementations plus @AuraEnabled(cacheable=true) contracts for LWC and @RestResource services. - Use Case: When asked to add a second trigger to an object or refactor a class flagged by vf-check analyzer for ApexSharingViolations, the Skill restructures the code into a single trigger with a declared handler class and user-mode queries. ## Quick Start Ask the assistant to create or review an Apex class or trigger under force-app, for example to build a bulkified Case escalation service with a trigger handler and explicit sharing.
