01
Develop platform features
Create Apex classes and triggers, Lightning Web Components, SOQL, custom metadata, objects, fields, permissions, and supported automation.
Salesforce development and deployment
CategorySoftware Development
Salesforce Codex Skills
Salesforce Codex Skills help Codex work with metadata-driven Salesforce projects. Download the skills for Apex, Lightning Web Components, SOQL, permissions, flows, Salesforce CLI, scratch orgs, retrieval, deployment validation, test levels, code coverage, and release evidence.
SalesforceApexLWCSalesforce CLI
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete salesforce development and deployment task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A small Salesforce change can affect metadata dependencies, permissions, org-specific configuration, limits, tests, and deployment behavior far beyond the edited file.
Salesforce development moves source and metadata between local projects and authorized orgs through explicit retrieval, validation, testing, and deployment steps.
These skills keep the target org, package directories, metadata scope, security model, and rollback plan visible throughout the work.
What the downloadable skills can do
What Salesforce Codex Skills can help accomplish
02
Trace metadata dependencies
Inspect package directories, manifests, references, profiles, permission sets, API versions, namespaces, and org capabilities.
03
Test within governor limits
Write focused Apex tests, isolate data, use mocks, inspect coverage and limits, and verify LWC behavior with the project tools.
04
Prepare controlled deployments
Retrieve safely, detect conflicts, run dry runs or validation, choose test levels, review destructive changes, deploy, and collect reports.
A repeatable working process
How the salesforce development and deployment workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Identify the org and metadata scope
Confirm project structure, target alias, API version, package model, source tracking, dependencies, permissions, and release path.
02
Design for platform constraints
Account for bulk behavior, sharing, CRUD and field security, governor limits, asynchronous work, and test isolation.
03
Implement with local evidence
Change the relevant source and metadata, add tests, run static checks, and review generated or retrieved differences.
04
Validate before deployment
Use an approved validation or dry run, review tests and coverage, inspect conflicts and warnings, then hand off the exact deployment scope.
Useful across real projects
Where Salesforce Codex Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Salesforce development
Build Apex, LWC, data access, automation, metadata, tests, and local project tooling.
Org synchronization
Retrieve and compare source from scratch orgs, sandboxes, development orgs, and tracked environments.
Release pipelines
Prepare manifests, packages, validation jobs, test levels, deployment reports, and rollback information.
Security and access
Review sharing, permissions, CRUD, field-level security, secrets, integration users, and audit requirements.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create an Apex service
02Build a Lightning Web Component
03Write SOQL safely
04Add permission metadata
05Run Apex tests
06Retrieve org metadata
07Validate a Salesforce deployment
08Diagnose deployment failures
Who benefits most
Who Is This For?
These skills are designed for people who need dependable salesforce development and deployment work with a visible process.
Salesforce developers
Build platform code and metadata with limits, security, and tests in view.
Administrators working in source
Review declarative metadata, permissions, flows, and deployment effects.
Release engineers
Control org aliases, manifests, validation jobs, test levels, packages, and deployment reports.
Consulting teams
Keep client org differences, namespaces, security, and handoff evidence explicit.
Good to know:
The skills require an authorized Salesforce environment for org actions and will not expose credentials, bypass permissions, ignore conflicts, or deploy destructive changes without explicit approval.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download the Salesforce skill folder
Keep platform, metadata, security, testing, CLI, and deployment guidance together.
Install it in the Salesforce project
Repository scope lets the skill follow sfdx-project.json, package directories, manifests, and team rules.
Document environments and limits
Provide approved org aliases, API versions, packaging model, namespaces, test expectations, and deployment controls.
List safe verification commands
Add static analysis, LWC tests, Apex tests, retrieval diff, validation, deployment report, and rollback procedures.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Can the skills write Apex and Lightning Web Components?+
Yes. They cover code, metadata, tests, security, limits, and project conventions.
Will they deploy directly to production?+
Only when explicitly authorized and after the required validation, test, scope, and review controls are satisfied.
Can they choose a deployment test level?+
They can recommend and construct the correct level based on the target org, payload, release policy, and required coverage.
How do they handle permissions?+
The workflow reviews sharing, CRUD, field access, permission sets, profiles, and integration identities relevant to the change.
Can they fix metadata conflicts?+
They can compare local and org state and propose a resolution, but the owner must decide which source is authoritative.
Make the work repeatable
Give Codex a Salesforce workflow that treats metadata, limits, security, tests, and deployment evidence as one change.
Clear context. Purposeful work. Relevant checks. A result others can understand.