Merge branch 'main' into faster-load

1 files changed, 40 insertions, 0 deletions

diff --git a/docs/docs/how-to-use-continue.md b/docs/docs/how-to-use-continue.md
index 96c44228..66de7ee9 100644
--- a/docs/docs/how-to-use-continue.md
+++ b/docs/docs/how-to-use-continue.md
@@ -29,42 +29,82 @@ Here are tasks that Continue excels at helping you complete:
 
 Continue works well in situations where find and replace does not work (i.e. “/edit change all of these to be like that”)
 
+Examples
+- "/edit Use 'Union' instead of a vertical bar here"
+- “/edit Make this use more descriptive variable names”
+
 ### Writing files from scratch
 
 Continue can help you get started building React components, Python scripts, Shell scripts, Makefiles, Unit tests, etc.
 
+Examples
+- “/edit write a python script to get Posthog events"
+- “/edit add a React component for syntax highlighted code"
+
 ### Creating projects from scratch
 
 Continue can go even further. For example, it can help build the scaffolding for a Python package, which includes a typer cli app to sort the arguments and print them back out.
 
+Examples
+- “/edit use this schema to write me a SQL query that gets recently churned users”
+- “/edit create a shell script to back up my home dir to /tmp/"
+
 ### Fix highlighted code
 
 After selecting a code section, try to refactor it with Continue (e.g “/edit change the function to work like this”, “/edit do this everywhere”)
 
+Examples
+- “/edit migrate this digital ocean terraform file into one that works for GCP”
+- “/edit rewrite this function to be async”
+
 ### Ask about highlighted code or an entire file
 
 If you don't understand how some code works, highlight it and ask "how does this code work?"
 
+Examples
+- “where in the page should I be making this request to the backend?”
+- “how can I communicate between these iframes?”
+
 ### Ask about errors
 
 Continue can also help explain errors and offer possible solutions. You will need to copy and paste the error text into the text input though.
 
+Examples
+- “explain this error to me in human understandable way”
+- "what are some ideas for how I might solve this problem?"
+
 ### Figure out what shell command to run
 
 Instead of switching windows and getting distracted, you can ask things like "How do I find running process on port 8000?"
 
+Examples
+- "what is the load_dotenv library name?"
+- "how do I find running process on port 8000?"
+
 ### Ask single-turn open-ended questions
 
 Instead of leaving your IDE, you can ask open-ended questions that you don't expect to turn into multi-turn conversations.
 
+Examples
+- “how can I set up a Prisma schema that cascades deletes?”
+- "what is the difference between dense and sparse embeddings?"
+
 ### Editing small existing files
 
 You can highlight an entire file and ask Continue to improve it as long as the file is not too large.
 
+Examples
+- “/edit here is a connector for postgres, now write one for kafka”
+- "/edit Rewrite this API call to grab all pages"
+
 ### Tasks with a few steps
 
 There are many more tasks that Continue can help you complete. Typically, these will be tasks that don't involve too many steps to complete.
 
+Examples
+- “/edit make an IAM policy that creates a user with read-only access to S3”
+- “/edit change this plot into a bar chart in this dashboard component”
+
 ## When to not use Continue
 
 Here are tasks that Continue is **not** helpful with today: