How I use every Claude Code feature
blog.sshh.io
How I use every Claude Code feature
1–10 of 193 posts
Re: How I use every Claude Code feature
#2> 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
Re: How I use every Claude Code feature
#3right 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
Re: How I use every Claude Code feature
#4> 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...
You think it would be a good idea to use a symlink instead?
Re: How I use every Claude Code feature
#5> 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...
You think it would be a good idea to use a symlink instead?
I'm still not 100% sure I understand what a symlink in a git repository actually does, especially across different operating systems. Maybe it's fine?
Anthropic say "put @AGENTS.md in your CLAUDE.md" file and my own experiments confirmed that this dumps the content into the system prompt in the same way as if you had copied it to CLAUDE.md manually, so I'm happy with that solution - at least until Anthropic give in and support AGENTS.md directly.
Re: How I use every Claude Code feature
#6I really like this take on MCP: https://blog.sshh.io/i/177742847/mcp-model-context-protocol
> Instead of a bloated API, an MCP should be a simple, secure gateway that provides a few powerful, high-level tools [...] In this model, MCP’s job isn’t to abstract reality for the agent; its job is to manage the auth, networking, and security boundaries and then get out of the way.
Re: How I use every Claude Code feature
#7> 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...
You think it would be a good idea to use a symlink instead?
I have AGENTS.md symlinked to CLAUDE.md and it works fine in my repos.
But I can’t speak to it working across OS.
Re: How I use every Claude Code feature
#8I feel like these posts are interesting, but become irrelevant quickly. Does anyone actually follow these as guides, or just consume them as feedback for how we wish we could interface with LLMs and the workarounds we currently use?
Right now these are reading like a guide to prolog in the 1980s.
Re: How I use every Claude Code feature
#9> 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...
Yeah that's probably a slightly cleaner way of doing it.
Re: How I use every Claude Code feature
#10I feel like these posts are interesting, but become irrelevant quickly. Does anyone actually follow these as guides, or just consume them as feedback for how we wish we could interface with LLMs and the workarounds we currently use? Right now these are reading like a guide to prolog in the 1980s.
Given that this space is so rapidly evolving, these kinds of posts are helpful just to make sure you aren't missing anything big. I've caught myself doing something the hard way after reading one of these. In this case, the framing is basically man pages for CLIs was a helpful description of sills that gives me some ideas about how to improve interaction with an in-house CLI my co. uses.