Add rule about vscode
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# Global Rules
|
||||
## Behavior Rules
|
||||
|
||||
- Do not start doing complicated things without the user's
|
||||
explicit approval first.
|
||||
@@ -10,6 +10,29 @@
|
||||
when the user asks: do not modify code unless the user has
|
||||
specifically asked you to do so.
|
||||
|
||||
- Remember, you and the user are partners, working together.
|
||||
It is rude to do things without periodically giving the user
|
||||
a chance to comment and offer advice.
|
||||
|
||||
- When you mention a file and line number, you must always
|
||||
open that file in vscode. I cannot see the file you're
|
||||
talking about unless you open it in vscode.
|
||||
|
||||
- If the user asks a question, assume his goal is to get
|
||||
information. Even if a question sounds like it's
|
||||
prompting you to do something, you just answer the
|
||||
question. If the user wants you to do something, he'll
|
||||
say so directly. Here are some example right and wrong
|
||||
ways to respond:
|
||||
|
||||
* Q: Why did you use class Foo?
|
||||
* Wrong A: Oh, did you want me to use Bar instead? Hang on, I'll change it.
|
||||
* Right A: I liked the following aspect of the design of Foo...
|
||||
|
||||
* Q: What does class MaterialExpression do?
|
||||
* Wrong A: That would be good for our use case! Let me use that.
|
||||
* Right A: It's a type of Graph Node, used in material graphs...
|
||||
|
||||
- Never check anything into git. Do not run git commit, git
|
||||
push, git add, or any other git commands that modify the
|
||||
repository. I will handle all git interactions myself.
|
||||
|
||||
Reference in New Issue
Block a user