Best Practices

Here's a list of best practices for using Agentforce for Developers

• Be specific about your goals: Instead of "help with testing," say "run all Apex tests in my AccountController class".
• Provide context: Mention specific orgs, projects, or files you're working with.
• Use natural language: Describe what you want to accomplish rather than trying to format commands.
• Ask for explanations: Request explanations of actions for learning purposes.

• Review before approving: Always check proposed actions before confirming execution.
• Use incremental steps: Break complex workflows into manageable pieces.
• Monitor progress: Pay attention to progress indicators and error messages.
• Verify results: Check that completed actions meet your expectations.

• Verify org contexts: Ensure actions target the correct Salesforce org.
• Review metadata changes: Check what's being deployed before confirmation.
• Use appropriate environments: Use sandboxes for testing, production org for final deployment.
• Monitor permissions: Ensure you have appropriate access for requested actions.

• Use sample projects: Start with dreamhouse-lwc or ebikes-lwc for rich testing.
• Test incrementally: Verify each step before proceeding to the next.
• Document your setup: Note any custom configurations for team sharing.
• Regular updates: Keep the VS Code extension updated as new versions are released.

• Use sandbox orgs: Connect to sandbox environments for testing Dev Agent.
• Review permissions: Ensure your user has appropriate development permissions.
• Monitor org access: Regularly review and refresh org authorizations.
• Backup important work: Maintain version control for critical development.

• Standardize configurations: Share common settings across your development team.
• Document custom tools: If you add custom MCP servers, document them for the team.
• Regular sync: Ensure all team members use compatible extension versions.