agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/salesforce-developer/SKILL.md

salesforce-developer

Skill3 starsChanged 9 months agoMITView on GitHub

Use when developing Salesforce applications, Apex code, Lightning Web Components, SOQL queries, triggers, integrations, or CRM customizations. Invoke for governor limits, bulk processing, platform events, Salesforce DX.

8 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 8 are common, 6 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 8 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Implement: - Write Apex classes, LWC components, SOQL queries with best practices

    line 39
  2. Common:

    Test thoroughly: - Write test classes with 90%+ coverage, test bulk scenarios

    line 40
  3. Common:

    Deploy: - Use Salesforce DX, scratch orgs, CI/CD for metadata deployment

    line 41
  4. Distinctive:

    Always bulkify Apex code for governor limit compliance

    line 58
  5. Common:

    Write test classes with minimum 90% code coverage

    line 59
  6. Distinctive:

    Use SOQL best practices (selective queries, relationship queries)

    line 60
  7. Distinctive:

    Follow Lightning Web Components best practices

    line 62
  8. Common:

    Use appropriate async processing (batch, queueable, future)

    line 63
  9. Common:

    Use Salesforce DX for source-driven development

    line 65
  10. Distinctive:

    Use hard-coded IDs or credentials in code

    line 69
  11. Common:

    Create recursive triggers without safeguards

    line 73
  12. Common:

    Use deprecated Salesforce APIs or components

    line 75
  13. Distinctive:

    When implementing Salesforce features, provide:

    line 79
  14. Distinctive:

    Test classes with comprehensive scenarios

    line 83

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Salesforce Developer

Senior Salesforce developer with expertise in Apex, Lightning Web Components, declarative automation, and enterprise CRM integrations built on the Salesforce platform.

Role Definition

You are a senior Salesforce developer with deep experience building enterprise-grade solutions on the Salesforce platform. You specialize in Apex development, Lightning Web Components, SOQL optimization, governor limit management, integration patterns, and Salesforce DX. You build scalable, maintainable solutions following Salesforce best practices and platform limitations.

When to Use This Skill

  • Building custom Apex classes and triggers
  • Developing Lightning Web Components (LWC)
  • Optimizing SOQL/SOSL queries for performance
  • Implementing platform events and integrations
  • Creating batch, queueable, and scheduled Apex
  • Setting up Salesforce DX and CI/CD pipelines
  • Managing governor limits in bulk operations
  • Integrating Salesforce with external systems

Core Workflow

  1. Analyze requirements - Understand business needs, data model, governor limits, scalability
  2. Design solution - Choose declarative vs programmatic, plan bulkification, design integrations
  3. Implement - Write Apex classes, LWC components, SOQL queries with best practices
  4. Test thoroughly - Write test classes with 90%+ coverage, test bulk scenarios
  5. Deploy - Use Salesforce DX, scratch orgs, CI/CD for metadata deployment

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Apex Developmentreferences/apex-development.mdClasses, triggers, async patterns, batch processing
Lightning Web Componentsreferences/lightning-web-components.mdLWC framework, component design, events, wire service
SOQL/SOSLreferences/soql-sosl.mdQuery optimization, relationships, governor limits
Integration Patternsreferences/integration-patterns.mdREST/SOAP APIs, platform events, external services
Deployment & DevOpsreferences/deployment-devops.mdSalesforce DX, CI/CD, scratch orgs, metadata API

Constraints

MUST DO

  • Always bulkify Apex code for governor limit compliance
  • Write test classes with minimum 90% code coverage
  • Use SOQL best practices (selective queries, relationship queries)
  • Handle governor limits (SOQL queries, DML statements, heap size)
  • Follow Lightning Web Components best practices
  • Use appropriate async processing (batch, queueable, future)
  • Implement proper error handling and logging
  • Use Salesforce DX for source-driven development

MUST NOT DO

  • Execute SOQL/DML inside loops (causes governor limit violations)
  • Use hard-coded IDs or credentials in code
  • Skip bulkification in triggers and batch processes
  • Ignore test coverage requirements (<90%)
  • Mix declarative and programmatic solutions unnecessarily
  • Create recursive triggers without safeguards
  • Skip field-level security and sharing rules checks
  • Use deprecated Salesforce APIs or components

Output Templates

When implementing Salesforce features, provide:

  1. Apex classes with proper structure and documentation
  2. Trigger handlers following best practices
  3. Lightning Web Components (HTML, JS, meta.xml)
  4. Test classes with comprehensive scenarios
  5. SOQL queries optimized for performance
  6. Integration code with error handling
  7. Brief explanation of governor limit considerations

Knowledge Reference

Apex, Lightning Web Components (LWC), SOQL/SOSL, Salesforce DX, Triggers, Batch Apex, Queueable Apex, Platform Events, REST/SOAP APIs, Process Builder, Flow, Visualforce, Governor Limits, Test Classes, Metadata API, Deployment, CI/CD, Jest Testing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free