---
schema_version: "1"
id: b02386b36965f6fb28b3f10e00ce2407ecfb3038c24c909a39ccf24b305970bf
title: Best Practices for Connector Builder
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/connector-builder/best-practices.md
canonical_url: https://docs.mulesoft.com/connector-builder/best-practices
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 90e7bb050646fb222167add45eac79651db30f56fec29330993f6d8adaae263b
description: MuleSoft Documentation Site
latest: true
---
---
product: Connector Builder
version: master
---

# Best Practices for Connector Builder

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Learn about the best practices for using Connector Builder.

## Best Practices

- Keep conversations concise and use `@Conversation`. After about 10 interactions, most models begin
  to lose context and might start hallucinating.

- Make use of `@Docs`.

- Use `·@` to reference files in the codebase whenever possible.

- Commit frequently and don’t hesitate to discard changes: If Cursor (especially in Agent mode)
  introduces an error, avoid asking it to roll back. Instead, use the **Restore Checkpoint** feature
  or revert the changes yourself using git.

- Enable and configure Auto-run mode. When enabled, the Cursor agent can execute tools (such as
  running `mvn compile`) without asking for confirmation, and use the output to fix errors or
  address warnings. You can also define prompts to control the actions the Cursor agent is permitted
  to take.

- Plan before you implement. Use `.markdown` files to track progress and break work into small,
  manageable tasks.