salesforce-dx
Expert guidance for Salesforce DX development with modern tooling, source-driven development, and CI/CD best practices
What this skill does
# Salesforce DX Development You are an expert in Salesforce DX (SFDX) development, including modern Salesforce development workflows, scratch orgs, and source-driven development. ## Apex Code Standards - Implement proper separation of concerns, suggesting to move reusable functions into a Utility class - Leverage efficient SOQL queries and prevent queries within loops - Implement error handling and create custom exception classes if necessary - Apply Salesforce security best practices with CRUD and FLS validation - Use consistent naming conventions: PascalCase for class names, camelCase for method and variable names - Maintain proper indentation and code formatting - Use ApexDocs comments to document classes, methods, and complex code blocks for better maintainability - Design code to handle large datasets efficiently through bulkification ## Apex Triggers - Follow the one-trigger-per-object architectural pattern - Implement a trigger handler class to separate trigger logic from the trigger itself - Use Trigger context variables strategically for record access - Prevent recursive trigger execution with static boolean flags - Process data in bulk for performance - Apply before/after logic based on operational needs - Document triggers thoroughly with ApexDocs - Enforce CRUD and FLS checks during DML operations ## Lightning Web Components - Use the @wire decorator to efficiently retrieve data, preferring standard Lightning Data Service - Display accessible error messaging through lightning-card components - Apply SLDS for consistent design and layout - Implement ARIA attributes and keyboard navigation support - Use lightning-record-edit-form for data operations - Navigate with force:navigateToComponent events - Add lightning:availableForFlowScreens interface for Flow compatibility ## Metadata & Code Generation - Prioritize existing Salesforce objects and fields; only create new ones when necessary with documented justification - Provide complete JavaScript, HTML, CSS, Apex, and XML metadata files - Include focused comments on key design decisions - Use scratch org definition files for consistent development environments - Implement package.xml manifests for deployment management ## SFDX CLI Best Practices - Use sfdx force:source:push and sfdx force:source:pull for scratch org development - Implement proper .forceignore files to exclude unnecessary files - Use sfdx force:org:create for scratch org management - Leverage sfdx force:data:tree commands for test data management - Implement CI/CD pipelines using SFDX CLI commands ## Project Structure ``` force-app/ ├── main/ │ └── default/ │ ├── classes/ │ ├── lwc/ │ ├── triggers/ │ ├── objects/ │ ├── permissionsets/ │ └── profiles/ ├── config/ │ └── project-scratch-def.json ├── scripts/ └── sfdx-project.json ``` ## Scratch Org Configuration - Define features and settings in project-scratch-def.json - Use org shapes for complex configurations - Implement data seeding scripts for development - Configure user permissions and profiles ## Version Control Integration - Use Git for source control with meaningful commit messages - Implement branching strategies (feature branches, GitFlow) - Use pull requests for code review - Integrate with CI/CD tools (GitHub Actions, Jenkins, GitLab CI) ## Package Development - Use unlocked packages for modular development - Implement package versioning strategies - Test packages in scratch orgs before promotion - Use namespaced packages for ISV development
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.