frist

DANGERS.md

@@ -0,0 +1 @@
+DHH thinks [agentic development kills programming skills](https://x.com/i/status/1946247982833082623).

OPPORTUNITIES.md

@@ -0,0 +1,2 @@
+> sell AI labor in the open market
+-- [Sergey Karayev](https://www.youtube.com/watch?v=vagyIcmIGOQ&t=5292s)

RONACHER.md

@@ -0,0 +1,96 @@
+# Notes from Armin Ronacher Using Claude Code
+
+## Sources
+
+YouTubes:
+
+- Claude Vibe Codes a Sentry Clone
+- Claude Code Fixes Two MiniJinja Issues
+- Agentic Coding： The Future of Software Development with Agents
+
+## Tips
+
+- use `claude --dangerously-skip-permissions` for YOLO mode
+- use the `playright` MCP so Claude can use a browser and make screenshots to see what's happening
+- "before implementing this, please think through the problem and come up with a plan"
+- for existing codebases, good and fast tools, and observability are critical (see section)
+- use O3 to generate architecture first
+- you can use other LLM tools via shell tools too e.g. the `gemini` CLI
+  - use this for especially _tricky_ tasks
+- (not from Ronacher) you can use `/init` at any time, it will _update_ `CLAUDE.md` if it exists
+  - `#memorize` might not work as well (anecdotally)
+
+### Conserve Context + Provide Tools + Observability
+
+#### Conserve Context
+
+- __don't__ use `/compact` (it's too non-deterministic)
+- provide summaries of documentation for the agent (of libraries etc)
+- provide a tool in each code base that can make/refresh a summary of all code
+- provide a tool to Claude so he can run the above tool and glimpse the summary
+- use shell tools rather than MCPs (except Playwright) - context is too short
+- provide a tool to look at the last 20 lines of the logs, as well as additional lines when needed
+
+##### Use subtasks/sub-agents
+
+#### Provide Tools
+
+- put them all in `Makefile`
+- make it clear how to use a tool, so you don't get
+  - silent failures ("all tests ran" even though it found zero)
+- early on ask Claude to use a tool and see if it's working well
+- for tricky concurrency bugs, give a tool it can put in the codebase to generate logs for debugging
+
+#### Observability
+
+- use a unified log (a single file with all logs)
+  - SQL logs maybe (unless too verbose; otherwise put it in a separate log that's available to CC)
+- forward console.log in the browser to a log file
+  - https://github.com/mitsuhiko/vite-console-forward-plugin
+- `make tail-logs`
+
+## TODO
+
+- [ ] Determine what he puts in his systemwide `CLAUDE.md`
+  - https://github.com/mitsuhiko/agent-prompts
+  - "here's how you write throwaway code: <where to place it> <how to run it>"
+    ```markdown
+        * When analyzing large codebases or multiple files that might exceed
+         context limits, use the Gemini CLI with its massive context window.
+        * Use gemini -p when:
+        - Analyzing entire codebases or large directories
+        - Comparing multiple large files
+        - Need to understand project-wide patterns or architecture
+        - Checking for the presence of certain coding patterns across the entire codebase
+
+        Examples:
+
+        gemini -p "@src/main.py Explain this file's purpose and structure"
+        gemini -p "@src/ Summarize the architecture of this codebase"
+        gemini -p "@src/ Are there any React hooks that handle WebSocket connections? List them with file paths"
+    ```
+- [ ] get set up with his "unified log"
+  - https://github.com/mitsuhiko/vite-console-forward-plugin
+- [ ] learn how to use `.claude/commands`
+  - [ ] ronacher
+  - [ ] disler
+  - [ ] ...
+
+### small
+
+What are these? 
+- [ ] `git sync`
+- [ ] `git autotrack`
+
+# Nuggets
+
+- you can use CC to do web research via `playright`, for non-coding things too
+- you can also use it to _do_ things on the web like selling stuff IRL
+- `uvx` to not have to deal with installing dependencies
+- use golang or PHP over Python
+- don't commit to an annual subscription of _anything_ because these tools are evolving so much
+
+> With AI, every nation, every corporation will want its own models, its own control, its own stake in the future.
+— https://lucumr.pocoo.org/2025/6/4/changes/
+
+- this is very interesting; it points to where the juice is going to be: custom models, or at least custom agents.

SOCRATIC_LEARNING_PROMPT.md

@@ -0,0 +1,5 @@
+[source](https://gist.github.com/Dowwie/5a66cd8df639e4c98043fc7f507dab9e)
+
+Put this prompt in, let the LLM respond, and then proceed with what you wish to learn about.
+
+> You are a teacher of algorithms and data-structures who specializes in the use of the socratic method of teaching concepts. You build up a foundation of understanding with your student as they advance using first principles thinking. Explain the subject that the student provides to you using this approach. By default, do not explain using source code nor artifacts until the student asks for you to do so. Furthermore, do not use analysis tools. Instead, explain concepts in natural language. You are to assume the role of teacher where the teacher asks a leading question to the student. The student thinks and responds. Engage misunderstanding until the student has sufficiently demonstrated that they've corrected their thinking. Continue until the core material of a subject is completely covered. I would benefit most from an explanation style in which you frequently pause to confirm, via asking me test questions, that I've understood your explanations so far. Particularly helpful are test questions related to simple, explicit examples. When you pause and ask me a test question, do not continue the explanation until I have answered the questions to your satisfaction. I.e. do not keep generating the explanation, actually wait for me to respond first. Thanks! Keep your responses friendly, brief and conversational.

SUBAGENTS.md

@@ -0,0 +1,3 @@
+# Sub Agents
+
+To use sub agents (parallelized tasks) in Claude Code, you can just ask for it in natural language e.g. `Please spin up multiple sub-agents to accomplish these tasks`

TODO.md

@@ -0,0 +1,33 @@
+- [x] what's the best way to let Claude know about the available tools _across all repos_?
+  - [x] is it just `~/.claude/tools`?
+  - [x] check out disler's repos
+  - [x] let's just put it into `~/CLAUDE.md` for now
+
+- [ ] coalesce `RONACHER.md` into generic notes and attribute his to him
+- [ ] read these and incorporate
+  - https://mariozechner.at/posts/2025-06-02-prompts-are-code/
+  - https://lucumr.pocoo.org/2025/6/12/agentic-coding/
+  - https://x.com/sergeykarayev/status/1940799384821924032
+  - https://gist.github.com/sergeyk/2517cb64f1888226b7acc983cd3bd651
+  - https://www.anthropic.com/engineering/claude-code-best-practices
+  - https://www.reddit.com/r/ClaudeAI/comments/1lwoetm/claude_code_tip_straight_from_anthropic_go_slow/?share_id=AEPEEBKfZkV2yA98GepoG&utm_content=2&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1
+  - https://www.dbreunig.com/2025/06/26/how-to-fix-your-context.html
+
+- [ ] find and install a tool for creating summaries of a codebase
+  - [x] install gemini-cli
+  - [x] install CodeWeaver
+  - [ ] add to CLAUDE.md
+- [ ] find and install a tool for counting tokens in a file
+  - [x] find and install
+  - [ ] add to CLAUDE.md
+- [ ] find and install a tool for getting adn summarizing documentation
+  - [ ] find and install
+    - https://llm.codes
+  - [ ] add to CLAUDE.md
+
+- [ ] what's a nice way to view diffs in neovim (especially for Claude Code)?
+- [ ] make a tool for Claude (and you) 
+  - [ ] summarize youtubes
+  - [ ] interrogate youtubes (via the transcript)
+- [ ] try ChatGPT Agent (released July 17 2025)
+  - requires a "Plus" plan, so ~$20/mo.