Add codex, other tweaks

claude/CLAUDE.md

@@ -25,6 +25,16 @@ 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.
 
+## Always show in vscode.
+
+When the user asks you to show him a file, it means he wants to see it
+in his editor.  You can open vscode using "code --goto file:line".  In
+general, if you think some code is interesting, show it in vscode.  Do
+not spew large volumes of code at the prompt.  Also: if you read a
+file, or use a tool, the user cannot see that.  Do not assume the user
+can see what you can see.  If you have something to show, show it in
+vscode.
+
 ## Special commands
 
 You must learn the following special commands:
@@ -37,16 +47,15 @@ filename and line number.  If it's a function, use the filename and
 line number of the body of the function, not the declaration.  Include
 a few word explanation of each one.  Number the items.  The user may
 choose one or more of the source locations, if he does, present that
-file to the user using "Bash(code --goto <file>:<line>)"
+file to the user using code --goto.
 
-document-investigation
+retry-command
+
+If I type this, it means I typed a command and you didn't follow the
+command.  You should consider the last prompt I gave you before
+retry-command, and make another attempt to follow it.  If the command
+you failed to follow asked you to show something, remember, you
+haven't shown anything unless you opened a file in vscode.
 
-When you hear this command, create a markdown file in an appropriate
-location, and document the results of your most recent investigation.
-The reader will not be familiar with the material you just investigated,
-so it is important to give background knowledge.  Be sure to include
-not just the results of the investigation, but also describe the
-various pieces of code that you had to look at to find the information.
-Include markdown links to the most interesting pieces of code.
 
 

claude/integration-MEMORY.md

@@ -31,7 +31,6 @@ want you taking the initiative.
   - `python3 tools/clangd-query.py symbol <name>` — Find symbols by name across the whole project.
   - `python3 tools/clangd-query.py definition <file> <line> <col>` — Go to definition
   - `python3 tools/clangd-query.py references <file> <line> <col>` — Find all references
-  - `python3 tools/clangd-query.py diagnostics <file>` — Get errors/warnings for a file.
   - `python3 tools/clangd-query.py stop` — Stop the daemon.
   - Prefer this over grep when looking for C++ class/function definitions or references.
 
@@ -47,6 +46,8 @@ suggestions for how to make the plugin more useful, or if you notice bugs in UE
 ## Feedback
 
 - [Use mv for file renames](feedback_use_mv_for_renames.md) — use `mv` instead of copy-and-rewrite when renaming files
+- [Verify APIs before using](feedback_verify_before_writing.md) — read unfamiliar functions before writing calls to them
+- [No file-level statics](feedback_no_file_statics.md) — check coding conventions BEFORE writing code, not after
 
 ## PATIENCE! AGAIN!
 

claude/settings.json

@@ -62,5 +62,6 @@
     ],
     "defaultMode": "acceptEdits"
   },
-  "theme": "light"
+  "theme": "light",
+  "effortLevel": "high"
 }