---
schema_version: "1"
id: b4d99e13dffaea197cc7751362e003d525517b42e63ac7827269f761b73ef44e
title: Best Practices
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/einsteinfordevs/guides/files/einstein-bestpractices.md
canonical_url: https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/einstein-bestpractices.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b102bf112e8d2e6542a82a123fe271735f9ac73807d5eeed5a54403ac9e2e8db
products:
  - Agentforce Vibes Developer Guide (Deprecated)
  - salesforcedx
---
# Best Practices

Here's a list of best practices for using Agentforce Vibes Extension

### Write Effective Requests

- **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.

### Manage Tool Execution

- **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.

### Security Considerations

- **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.

### Initial Setup

- **Use sample projects**: Start with [dreamhouse-lwc](https://github.com/trailheadapps/dreamhouse-lwc) or [ebikes-lwc](https://github.com/trailheadapps/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.

### Security Considerations

- **Use sandbox orgs**: Connect to sandbox environments for testing Agentforce.
- **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.

### Team Setup

- **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.