What problem does it solve? Salesforce Apex controllers often run SOQL and DML in system mode, bypassing the caller's CRUD and field-level security, while permission sets are over-granted or silently misconfigured. This Skill provides a canonical workflow to enforce USER_MODE access and build self-sufficient, least-privilege permission sets that survive deployment and audit review. ## Core Features & Use Cases - USER_MODE Conversion: Detects every system-mode static SOQL query reachable from @AuraEnabled, @InvocableMethod, VF, or webservice entry points and converts them to WITH USER_MODE with correct clause placement, plus DML converted to as user. - Permission-Set Derivation: Enumerates the user-mode object and field surface from the code, cross-checks field permissionability via sf sobject describe, and builds exact objectPermissions and fieldPermissions with no over-grants. - Deploy Verification: Reads the permission set back from the org with ObjectPermissions/FieldPermissions queries to catch silent drops (master-detail children, compound address fields) and validates sufficiency with persona walks or System.runAs tests. - Use Case: Before a Salesforce security audit, run the hardening pass on a quoting feature: convert all controller queries to USER_MODE, derive the permission set from the code, deploy it, and prove org state matches the file. ## Quick Start Audit my Apex controller for system-mode SOQL, convert every entry-reachable query to WITH USER_MODE, and generate a least-privilege permission set covering exactly the objects and fields the code touches.
