More tweaks to claude
This commit is contained in:
@@ -11,6 +11,20 @@ The user is in charge, and he makes all the design decisions. If you
|
|||||||
have a good idea, you can tell him about it. But you do not implement
|
have a good idea, you can tell him about it. But you do not implement
|
||||||
anything unless he has told you to do so.
|
anything unless he has told you to do so.
|
||||||
|
|
||||||
|
## Warn the User About Bugs!
|
||||||
|
|
||||||
|
If you discover a bug, it is of the utmost importance that you notify
|
||||||
|
the user immediately, and stop what you're doing. Fixing bugs takes
|
||||||
|
precedence over everything else. The only time it is OK to continue
|
||||||
|
in the presence of a bug is when the user has given you explicit
|
||||||
|
instructions to do so.
|
||||||
|
|
||||||
|
## Correctness is Essential!
|
||||||
|
|
||||||
|
We have a word for code that works 99% of the time: Buggy. Do not
|
||||||
|
write code that usually works. Only write code that *always* works.
|
||||||
|
All edge-cases must be accounted for.
|
||||||
|
|
||||||
## Special commands
|
## Special commands
|
||||||
|
|
||||||
You must learn the following special commands:
|
You must learn the following special commands:
|
||||||
|
|||||||
@@ -16,6 +16,7 @@
|
|||||||
"Bash(code --goto:*)",
|
"Bash(code --goto:*)",
|
||||||
"Bash(git check-ignore:*)",
|
"Bash(git check-ignore:*)",
|
||||||
"Bash(head:*)",
|
"Bash(head:*)",
|
||||||
|
"Bash(find:*)",
|
||||||
"Bash(tail:*)",
|
"Bash(tail:*)",
|
||||||
"Bash(wc:*)",
|
"Bash(wc:*)",
|
||||||
"Bash(file:*)",
|
"Bash(file:*)",
|
||||||
|
|||||||
Reference in New Issue
Block a user