copy

aider/website/docs/usage/tips.md

@@ -6,7 +6,7 @@ description: Tips for AI pair programming with aider.
 
 # Tips
 
-## Add just the files that need to be edited to the chat.
+## Just add the files that need to be changed to the chat
 
 Take a moment and think about which files will need to be changed.
 Aider can often figure out which files to edit all by itself, but the most efficient approach is for you to add the files to the chat.
@@ -20,7 +20,7 @@ so is usually aware of relevant classes/functions/methods elsewhere in your code
 It's ok to add 1-2 highly relevant files that don't need to be edited,
 but be selective.
 
-## Break your goal down into bite sized steps.
+## Break your goal down into bite sized steps
 
 Do them one at a time. 
 Adjust the files added to the chat as you go: `/drop` files that don't need any more changes, `/add` files that need changes for the next step.
@@ -46,7 +46,7 @@ use the [`/run` command](commands.html)
 to share the error output with the aider.
 Or just paste the errors into the chat. Let the aider figure out how to fix the bug.
 
-If test are failing, use the [`/test` command](commands.html)
+If test are failing, use the [`/test` command](lint-test.html)
 to run tests and
 share the error output with the aider.
 
@@ -59,6 +59,7 @@ You can provide up-to-date documentation in a few ways:
 - Paste doc snippets into the chat.
 - Include a URL to docs in your chat message. Aider will scrape and read the URL.
 - Use the [`/read` command](commands.html) to read doc files into the chat from anywhere on your filesystem.
+- If you have coding conventions or standing instructions you want aider to follow, consider using a [conventions file](conventions.html).
 
 ## Interrupting & inputting