sf-apex: Salesforce Apex Code Generation and Review

Core Responsibilities

1. Code Generation: Create Apex classes, triggers (TAF), tests, async jobs from requirements
2. Code Review: Analyze existing Apex for best practices violations with actionable fixes
3. Validation & Scoring: Score code against 8 categories (0-150 points)
4. Deployment Integration: Validate and deploy via sf-deploy skill

Workflow (5-Phase Pattern)

Phase 1: Requirements Gathering

• Class type (Trigger, Service, Selector, Batch, Queueable, Test, Controller)
• Primary purpose (one sentence)
• Target object(s)
• Test requirements

1. Check existing code:

   Glob: **/*.cls

   ,

   Glob: **/*.trigger

2. Check for existing Trigger Actions Framework setup:

   Glob: **/*TriggerAction*.cls

3. Create TodoWrite tasks

Phase 2: Design & Template Selection

templates/trigger.trigger

templates/trigger-action.cls

templates/service.cls

templates/selector.cls

templates/batch.cls

templates/queueable.cls

templates/test-class.cls

templates/test-data-factory.cls

templates/apex-class.cls

1. Marketplace folder:

   ~/.claude/plugins/marketplaces/sf-skills/sf-apex/templates/[template]

2. Project folder:

   [project-root]/sf-apex/templates/[template]

Read: ~/.claude/plugins/marketplaces/sf-skills/sf-apex/templates/apex-class.cls

Phase 3: Code Generation/Review

1. Create class file in

   force-app/main/default/classes/

2. Apply naming conventions (see docs/naming-conventions.md)
3. Include ApexDoc comments
4. Create corresponding test class

1. Read existing code
2. Run validation against best practices
3. Generate improvement report with specific fixes

Score: XX/150 ⭐⭐⭐⭐ Rating
├─ Bulkification: XX/25
├─ Security: XX/25
├─ Testing: XX/25
├─ Architecture: XX/20
├─ Clean Code: XX/20
├─ Error Handling: XX/15
├─ Performance: XX/10
└─ Documentation: XX/10

⛔ GENERATION GUARDRAILS (MANDATORY)

"I noticed [pattern]. This will cause [problem]. Should I: A) Refactor to use [correct pattern] B) Proceed anyway (not recommended)"

for(...) { [SELECT...] }

for(...) { insert/update }

class X {

catch(e) { }

'SELECT...WHERE Name = \'' + var

@IsTest

Assert.*

Phase 4: Deployment

Skill(skill="sf-deploy", args="Deploy classes at force-app/main/default/classes/ to [target-org] with --dry-run")

Skill(skill="sf-deploy", args="Proceed with actual deployment to [target-org]")

Phase 5: Documentation & Testing Guidance

✓ Apex Code Complete: [ClassName]
  Type: [type] | API: 65.0
  Location: force-app/main/default/classes/[ClassName].cls
  Test Class: [TestClassName].cls
  Validation: PASSED (Score: XX/150)

Next Steps: Run tests, verify behavior, monitor logs

Best Practices (150-Point Scoring)

WITH USER_MODE

with sharing

Security.stripInaccessible()

!= false

Limits

• resources/bulkification-guide.md - Governor limits, collection handling
• resources/security-guide.md - CRUD/FLS, sharing, injection prevention
• resources/testing-patterns.md - Exception types, mocking, coverage
• resources/patterns-deep-dive.md - TAF, @InvocableMethod, async patterns

Trigger Actions Framework (TAF)

Quick Reference

sf package installed list

trigger AccountTrigger on Account (before insert, after insert, before update, after update, before delete, after delete, after undelete) {
    new MetadataTriggerHandler().run();
}

public class TA_Account_SetDefaults implements TriggerAction.BeforeInsert {
    public void beforeInsert(List<Account> newList) {
        for (Account acc : newList) {
            if (acc.Industry == null) {
                acc.Industry = 'Other';
            }
        }
    }
}

Trigger_Action__mdt

sf package install --package 04tKZ000000gUEFYA2 --target-org [alias] --wait 10

Async Decision Matrix

@future(callout=true)

Queueable

Batch Apex

Schedulable

Queueable Finalizer

Modern Apex Features (API 62.0)

• Null coalescing:

  value ?? defaultValue

• Safe navigation:

  record?.Field__c

• User mode:

  WITH USER_MODE

  in SOQL
• Assert class:

  Assert.areEqual()

  ,

  Assert.isTrue()

System.FinalException

Flow Integration (@InvocableMethod)

@InvocableMethod

Quick Pattern

public with sharing class RecordProcessor {

    @InvocableMethod(label='Process Record' category='Custom')
    public static List<Response> execute(List<Request> requests) {
        List<Response> responses = new List<Response>();
        for (Request req : requests) {
            Response res = new Response();
            res.isSuccess = true;
            res.processedId = req.recordId;
            responses.add(res);
        }
        return responses;
    }

    public class Request {
        @InvocableVariable(label='Record ID' required=true)
        public Id recordId;
    }

    public class Response {
        @InvocableVariable(label='Is Success')
        public Boolean isSuccess;
        @InvocableVariable(label='Processed ID')
        public Id processedId;
    }
}

templates/invocable-method.cls

• resources/patterns-deep-dive.md - Complete @InvocableMethod guide
• docs/flow-integration.md - Advanced Flow-Apex patterns
• docs/triangle-pattern.md - Flow-LWC-Apex triangle

Testing Best Practices

The 3 Test Types (PNB Pattern)

1. Positive: Happy path test
2. Negative: Error handling test
3. Bulk: 251+ records test

@IsTest
static void testPositive() {
    Account acc = new Account(Name = 'Test', Industry = 'Tech');
    insert acc;
    Assert.areEqual('Tech', [SELECT Industry FROM Account WHERE Id = :acc.Id].Industry);
}

@IsTest
static void testNegative() {
    try {
        insert new Account(); // Missing Name
        Assert.fail('Expected DmlException');
    } catch (DmlException e) {
        Assert.isTrue(e.getMessage().contains('REQUIRED_FIELD_MISSING'));
    }
}

@IsTest
static void testBulk() {
    List<Account> accounts = new List<Account>();
    for (Integer i = 0; i < 251; i++) {
        accounts.add(new Account(Name = 'Bulk ' + i));
    }
    insert accounts;
    Assert.areEqual(251, [SELECT COUNT() FROM Account]);
}

• resources/testing-patterns.md - Exception types, mocking, Test Data Factory
• docs/testing-guide.md - Complete testing reference

Common Exception Types

DmlException

QueryException

NullPointerException

ListException

LimitException

CalloutException

@IsTest
static void testExceptionHandling() {
    try {
        insert new Account(); // Missing required Name
        Assert.fail('Expected DmlException was not thrown');
    } catch (DmlException e) {
        Assert.isTrue(e.getMessage().contains('REQUIRED_FIELD_MISSING'),
            'Expected REQUIRED_FIELD_MISSING but got: ' + e.getMessage());
    }
}

LSP-Based Validation (Auto-Fix Loop)

How It Works

1. PostToolUse Hook: After every Write/Edit operation on

   .cls

   or

   .trigger

   files, the LSP hook validates syntax
2. Apex Language Server: Uses Salesforce's official

   apex-jorje-lsp.jar

   (from VS Code extension)
3. Auto-Fix Loop: If errors are found, Claude receives diagnostics and auto-fixes them (max 3 attempts)
4. Two-Layer Validation:
   • LSP Validation: Fast syntax checking (~500ms)
   • 150-Point Validation: Semantic analysis for best practices

Prerequisites

• VS Code Salesforce Extension Pack: VS Code → Extensions → "Salesforce Extension Pack"
• Java 11+: https://adoptium.net/temurin/releases/

Cross-Skill Integration

Skill(skill="sf-metadata")

Skill(skill="sf-data")

Skill(skill="sf-deploy", args="Deploy to [org]")

@AuraEnabled

Reference Documentation

Quick Guides (resources/)

Full Documentation (docs/)

best-practices.md

code-smells-guide.md

design-patterns.md

trigger-actions-framework.md

security-guide.md

testing-guide.md

naming-conventions.md

solid-principles.md

code-review-checklist.md

flow-integration.md

triangle-pattern.md

llm-anti-patterns.md

~/.claude/plugins/marketplaces/sf-skills/sf-apex/docs/

Dependencies

/plugin install github:Jaganpro/sf-skills/[skill-name]

Notes

• API Version: 62.0 required
• TAF Optional: Prefer TAF when package is installed, use standard trigger pattern as fallback
• Scoring: Block deployment if score < 67
• LSP: Optional but recommended for real-time syntax validation

License