salesforce-developer

Load detailed guidance based on context: - Analyze requirements - Understand business needs, data model, governor limits, scalability - Design solution - Choose declarative vs programmatic, plan bulkification, design integrations - Implement - Write Apex classes, LWC components, SOQL queries with best practices - Validate governor limits - Verify SOQL/DML counts, heap size, and CPU time stay within platform limits before proceeding - Test thoroughly - Write test classes with 90%+ coverage, test bulk scenarios (200-record batches) - Deploy - Use Salesforce DX, scratch orgs, CI/CD for metadata deployment - Bulkify Apex code — collect IDs/records before loops, query/DML outside loops - Write test classes with minimum 90% code coverage, including bulk scenarios - Use selective SOQL queries with indexed fields; leverage relationship queries - Use appropriate async processing (batch, queueable, future) for long-running work - Implement proper error handling and logging; use Database.update(scope, false) for partial success - Use Salesforce DX for source-driven development and metadata deployment - Execute SOQL/DML inside loops (governor limit violation — see bulkified trigger pattern below) - Hard-code IDs or credentials in code - Create recursive triggers without safeguards - Skip field-level security and sharing rules checks - Use deprecated Salesforce APIs or components