> Finally, we keep this file synced with an AGENTS.md file to maintain compatibility with other AI IDEs that our engineers might be using. I researched this the other day, the recommended (by Anthropic) way to do this is to have a CLAUDE.md with a single line in it: @AGENTS.md Then keep your actual content in the other file: https://docs.claude.com/en/docs/claude-code/claude-code-on-t...
How I use every Claude Code feature
131–140 of 193 posts
Re: How I use every Claude Code feature
#132Crazy how fast Claude Code is evolving, every week there’s something new to learn, and it just keeps getting better.
Nothing crazy about it, judging by how much CPU and memory it uses. Now, if it managed to grow features without bringing my M4 Mac with 64GB of ram to a crawl... that's be magic .
Re: How I use every Claude Code feature
#133Earlier quoted context omitted.
I have the same instinctive response to reading AI generated stuff, but I'm coming to a more moderate position where I'm trying to judge the content on the content itself. For example, in a post like this, it doesn't bother me at all because it's still an extremely useful reference, and the author clearly read through, organized, and edited the output. This is a good example of usage of AI in my opinion. The people w…
Not worried about hallucinations?
Re: How I use every Claude Code feature
#134right on. i usually just tell it "hey go update this function to do [x]" in horribly misspelled english and then yell at it until it does it right
Sometimes I write with Claude in English and German mixed with really bad typos and it’s amazing how well it works.
I suggest everyone who can to try the voice mode. https://getvoicemode.com/
Re: How I use every Claude Code feature
#135"Claude Code isn’t just an interactive CLI; it’s also a powerful SDK for building entirely new agents—..." Em dash and "it's not X, it's Y" in one sentence. Tired of reading posts written by AI. Feels disrespectful to your readers
Didn’t realize you were forced to read this?
> Feels disrespectful to your readers
I didn’t feel disrespected—I felt so respected I read the whole thing.
Re: How I use every Claude Code feature
#136I use claude code every day, and havent had a chance to dig super deep into skills, but even though ive read a lot of people describe them and say they're the best thing so far, I still dont get them. Theyre things the agent chooses to call right? They have different permissions? is it a tool call with different permissions and more context? I have yet to see a single post give an actual real-world concrete example o…
The prerequisite thought here is that you're using CC to invoke CLI tools. So now you need to get CC to understand _how_ to do that for various tools in a way that's context efficient, because otherwise you're relying on either potentially outdated knowledge that Claude has built in (leading to errors b/c CC doesn't know about recent versions) or chucking the entirety of a man page into your default context (ineffice…
Re: How I use every Claude Code feature
#137Re: How I use every Claude Code feature
#138Earlier quoted context omitted.
Claude is just better at coding than cursor. Really, the interface isn't a meaningful part of it. I also like cmd-L, but claude just does better at writing code. ...also, it's nice that Anthropic is just focusing on making cool stuff (like skills), while the folk from cursor are... I dunno. Whatever it is they're doing with cursor 2.0 :shrug:
Cursor can use the Claude Sonnet and Claude Opus LLMs, so I would expect output to be quite similar in that respect. The agentic part of the equation is improving on both sides all the time.
Re: How I use every Claude Code feature
#139Earlier quoted context omitted.
This is one thing I think they need to get in-line with, and rename CLAUDE.md to AGENTS.md to follow convention.
To be fair, I think Anthropic/Claude started doing CLAUDE.md before AGENTS.md was a thing.
Re: How I use every Claude Code feature
#140I really enjoyed reading this. One thought I had on the issue of paths in Claude.md My concern with hardcoding paths inside a doc, it will likely become outdated as the codebase evolves. One solution would be to script it and have it run pre commit to regenerate the Claude.md with the new paths. There probably is potential for even more dev tooling that 1. Ensure reference paths are always correct, 2. Enforces standa…
We have a linter that checks for this to help mitigate