Cursor

Open Project and Ensure Codebase is Indexed

Give Cursor time to scan and index the entire codebase to understand the project's context.

Open the project folder in Cursor, wait for the status bar to indicate that indexing is complete at the bottom of the screen.

For large monorepos, add a .cursorignore file to exclude the build/node_modules directory to speed up indexing.

Open Composer and Describe Change Requirements

Use Composer (Ctrl+I or Cmd+I) to clearly describe the changes needed across the entire project.

Enter a specific description such as: 'Replace all calls to the old payment API with the new SDK, keeping the existing function interface intact.'

Clearly state any files or directories that should remain unchanged if you don't want AI to modify them to avoid unintended changes.

Preview Change Plan

Check the list of files that Composer intends to edit before allowing it to apply.

Review the summary of the plan proposed by the Agent, removing unrelated files if necessary.

If the plan misses important files, provide a clearer description or directly link that file to the context.

Review Diff for Each File

Inspect each specific change that AI suggests before accepting.

Go through each diff displayed per file, click Accept for correct parts and Reject or manually adjust incorrect parts.

Prioritize reviewing logic handling payment/transaction files as these are the highest risk areas.

Run Tests and Confirm

Run the existing test suite to ensure changes do not break other functionalities.

Execute the test command in Cursor's integrated terminal, fixing any emerging errors if they occur.

Request the Agent to write additional test cases for the modified code if the project lacks sufficient tests.