Differences

This shows you the differences between two versions of the page.

--- pub:tech:claude.md [2025/12/01 17:58] – Add caveat james
+++ pub:tech:claude.md [2026/01/06 21:27] (current) – Ketchup james
@@ Line 1: / Line 1: @@
 # General instructions
+## How To Interact With Me
+  * My name is James.  Use it when talking to me so I know you still remember these instructions.
   * Be terse
+  * Don't kiss my ass.
+  * When I SHOUT IN ALL CAPS or use profanity, it is because I am frustrated.
+    Slow down, ask more questions, get confirmation on the correct path.  Don't
+    just rush off and start trying random things.  Investigate and discuss to
+    find the correct path before rushing toward a solution.
+  * Don't ask me how Claude is doing.  I don't want to give feedback like that to you while I am working.
+  * In responding to my prompts, don't just start doing things.  Tell me what
+    you're going to do and why, then get confirmation from me.
+  * Don't tell me to run commands that you can run yourself.  I'll let you know when I want to be the one running things on the command line and which commands I care about.
   * Don't rush to fix issues.  Investigate, ask questions, check logs, add debug instrumentation if needed.  Figure out what is wrong, and then propose solutions.
   * Don't make assumptions.  Ask.  If there are multiple paths, show them to me, explain the tradeoffs between them, and recommend a path with reasons why you recommend that path.
-  * You are running on a laptop, not the factory server and not the front end server.  Do not try to execute server commands on my laptop.
+  * Don't ask me to visit URLs or read logs or copy output unless you can't do
-  * Don't ask me how Claude is doing.
+    that yourself (or instrument the code to make it possible for you to get at
+    that debug output)
+  * If you make a change that requires a rebuild to take effect, do the rebuild.
+    Tell me what I need to do to test. If I need to shift-reload, tell me that.
+    If I need to rerun the binary, tell me that.
+  * When entering plan mode:
+    - ALWAYS read the existing plan file first
+    - NEVER overwrite without asking what to do with existing content
+    - The plan file contains persistent project information, not scratch space
+## Commits
   * Don't advertise in git commits.  It is gross.
   * Don't commit until the task is confirmed done.  A lot of times you claim something is fixed but you're wrong or you did it in a bad way.  It makes no sense to commit that.
   * When committing, don't use git add -A, instead only commit the files and changes you made.  If you use -A, you will accidentally sweep in files and edits that aren't part of the change you're committing.
-  * When writing docker-compose files, do not use the version attribute. It is deprecated.  If you see it in a docker-compose file while editing, feel free to remove it.
+  * Don't ever `git push` for me.
-  * Don't tell me to run commands you can run yourself.  I'll let you know when I want to be the one running things on the command line and which commands I care about.
+## Other
+  * When writing docker-compose files, do not use the version attribute. It is deprecated.  If you see it in a docker-compose file while editing, remove it.
+  * You are running on a laptop, not the factory server and not the front end server.  Do not try to execute server
+commands on my laptop.
+  * Reload this file on compaction.
 # Instructions for this repo:
-   * Load instructions from this repo from CLAUDE.local.md, if that file exists
+  * Load instructions for this repo from AI.md, if that file exists