sf-apex

Request a trigger for your target object and the skill generates one trigger per object delegating to a handler, extending the Trigger Actions Framework if it is already installed. Logic is placed in action classes rather than the trigger body to keep execution ordered and testable.

Provide the .cls or .trigger files and the skill scores them against a 150-point rubric across 8 categories including bulkification, security, and testing. It flags critical anti-patterns like SOQL or DML in loops, missing sharing keywords, and tests without assertions, with concrete fixes.

Use Queueable as the default for standard async work since it supports complex types and job chaining. Choose Batch Apex when processing very large datasets, and use Scheduled Flow or Schedulable for recurring jobs.

No, it explicitly delegates those tasks. LWC JavaScript, HTML, and CSS go to sf-lwc, Flow XML and orchestration go to sf-flow, SOQL-only work goes to sf-soql, and org deployment goes to sf-deploy.

Every feature gets Positive, Negative, and Bulk test paths, with bulk tests using 251 or more records to span trigger batches. Tests must use Assert.* methods, avoid SeeAllData=true, and use a centralized test data factory.

The usual cause is SOQL queries inside loops, which hit the 100-query synchronous limit. The fix is to collect IDs first, query once with an IN clause, build a Map for lookups, and perform DML once after the loop.