From 4667c9339ee5951345651e008bc5e6dd719ed33d Mon Sep 17 00:00:00 2001 From: Michele Cereda Date: Mon, 2 Mar 2026 02:38:14 +0100 Subject: [PATCH] chore(kb/ai): review and expand notes --- knowledge base/ai/claude/claude code.md | 71 +++++++++++++++++++++++-- 1 file changed, 67 insertions(+), 4 deletions(-) diff --git a/knowledge base/ai/claude/claude code.md b/knowledge base/ai/claude/claude code.md index b25286c..16e31fa 100644 --- a/knowledge base/ai/claude/claude code.md +++ b/knowledge base/ai/claude/claude code.md @@ -15,6 +15,13 @@ Works in a terminal, IDE, browser, and as a desktop app. ## TL;DR +Claude can run in multiple shell sessions.
+Prefer using git worktrees to isolate sessions in the same repository. + +Fully multimodal.
+Can access and understand images and other file types.
+Can use tools, and do it in parallel. + _Normally_: - Tied to Anthropic's Claude models (Sonnet and Opus). @@ -45,9 +52,61 @@ flowchart LR Supports a plugin system for extending its capabilities. -Sends Statsig telemetry data by default.
+Sends Statsig telemetry data by default. Includes operational metrics (latency, reliability, usage patterns).
Disable it by setting the `DISABLE_TELEMETRY` environment variable to `1`. +Gives better results when asked to make a plan before writing code, and when tries multiple times (iterates).
+Common workflows: + +- Explore, plan, ask for confirmation, write code, commit. + +
+ Example + + > Figure out the root cause for issue \#43, then propose possible fixes.
+ > Let me choose an approach before you write code.
+ > Ultrathink. + +
+ +- Write tests, commit, write code, iterate, commit, push, create a PR. + +
+ Example + + > Write tests for @utils/markdown.ts to make sure links render properly.
+ > Note these tests will not pass yet since links are not yet implemented.
+ > Commit.
+ > Update the code to make the tests pass.
+ > Commit. Push. PR. + +
+ +- Write code, screenshot the result, track progress, iterate. + +
+ Example + + > Implement \[mock.png], then screenshot it with Puppeteer and iterate until it looks like the mock.
+ > Write down notes for yourself at every iteration. Think hard. + +
+ +Hit `esc` once to stop Claude.
+This action is usually safe. Claude will then resume or make things differently, but will have a context. + +Prefer using Sonnet for quicker, smaller tasks (e.g. as sub-agent, greenfield coding, app initialization).
+Consider using Opus for broader, longer, higher-level tasks (e.g. planning, refactoring, orchestrating sub-agents). + +Use memory and context files (`CLAUDE.md`) to instruct Claude Code on commands, style guidelines, and give it _key_ +context. Try to keep them small. + +Consider allowing specific tools to reduce interruption and avoid fatigue due to too many requests.
+Prefer using CLI tools over MCP servers. + +Make sure to use `/clear` or `/compact` regularly to allow Claude to maintain focus on the conversation.
+Or make it create notes to self and restart it once the context goes above a threshold (usually best at 60%). +
Setup @@ -69,7 +128,9 @@ claude "fix the build error" # Run a one-off task, then exit. claude -p 'Hi! Are you there?' -claude -p "explain this function" +claude -p "explain the function in @someFunction.ts" +claude -p 'What did I do this week?' --allowedTools 'Bash(git log:*)' --output-format 'json' +cat 'minutes.md' | claude -p "summarize this" # Resume the most recent conversation that happened in the current directory claude -c @@ -119,12 +180,12 @@ claude plugin update 'gitlab@claude-plugins-official' From within Claude Code: ```plaintext -/mcp +/mcp manage MCP servers ```
-
+
Real world use cases ```sh @@ -477,6 +538,7 @@ Claude Code version: `v2.1.41`.
- [Documentation] - [pffigueiredo/claude-code-sheet.md] +- [Mastering Claude Code in 30 minutes] by Boris Cherny, Anthropic [Agent Skills]: https://agentskills.io/