What problem does it solve? Apex transactions fail with uncatchable LimitException errors when code exceeds Salesforce governor limits like 100 SOQL queries, 150 DML statements, 6 MB heap, or 10 seconds of CPU time, and developers often cannot tell which limit blew or how to restructure the code to stay inside it. ## Core Features & Use Cases - Complete limit reference: Full synchronous and asynchronous per-transaction, certified managed package, platform, static, and size-specific limit tables for API 67.0, plus the Limits and OrgLimits class APIs. - Bulkification patterns: Ready-to-use Apex patterns for one-DML-per-collection, query-once-map-lookup, SOQL for loops, Batch Apex with QueryLocator, and Test.startTest/stopTest limit isolation. - Symptom-to-fix playbook: A remediation guide mapping each runtime failure (SOQL 101, DML 151, heap, CPU time, callouts, stack depth, async executions) to its cause and minimum fix. - Use Case: A trigger fails in production with "Apex CPU time limit exceeded". Use this Skill to identify that nested loops are the cause, replace them with a Map-based lookup, and add a test asserting a constant query count for 200 records. ## Quick Start Ask the assistant to review my trigger handler for governor limit risks and fix any SOQL or DML inside loops.
