Enshittification needs its Moore's law.
How I use every Claude Code feature
31–40 of 193 posts
Re: How I use every Claude Code feature
#32Earlier quoted context omitted.
This one is already out of date. The bit on the top about allocating space in CLAUDE.md for each tool is largely a waste of tokens these days. Use the skills feature.
It's a balance and we use both. Skills doesn't totally deprecate documenting things in CLAUDE.md but agree that a lot of these can be defined as skills instead. Skill frontmatter also still sits in the global context so it's not really a token optimization either.
The skill lets you compress the amount loaded to just the briefest description, with the “where do I go to get more info” being implicit. You should use a SKILL.md for evry added tool. At which point, putting instructions in CLAIDE.md becomes redundant and confusing to the LLM.
Re: How I use every Claude Code feature
#33Earlier quoted context omitted.
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.
Confirm on a new clone that if you modify a file that the other is updated.
I thought git by default treats symlinks simply as file copies when cloning new.
Ie git may not be aware of the symlink.
Re: How I use every Claude Code feature
#34Earlier quoted context omitted.
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.
Confirm on a new clone that if you modify a file that the other is updated. I thought git by default treats symlinks simply as file copies when cloning new. Ie git may not be aware of the symlink.
git very much supports symlinks. Although depending on the system config it might not create actual symlinks on Windows.
Re: How I use every Claude Code feature
#35Why are so many still using CC and not Codex
CC has better agent tools and is faster. The ability to switch from plan mode to execution mode and back is huge. Toggling thinking also. And of course they are innovating all of these agentic features like MCP, sub-agents, skills, etc...
Codex writes higher quality code, but is slower and less feature rich. I imagine this will change within months. The jury is still out. Exciting times!
Re: How I use every Claude Code feature
#36> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be.
Are the CLI-based agents better (much better?) than the Cursor app? Why?
I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____."
I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying. "Fix login.ts lines 148-160, it's broken like this ___"
Re: How I use every Claude Code feature
#37[dead]
Re: How I use every Claude Code feature
#38Why are so many still using CC and not Codex
If you have no modifications or customization of Claude code then it comes down to a preference for proactivity (codex) or a bit more restraint.
If you are using literally any of Claude Code’s features the experience isn’t close, and regardless of model preference (Claude is my least favorite model by far) you should probably use Claude code. It’s just a much more extensible product for teams.
Re: How I use every Claude Code feature
#39> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…
They all have optional ide integration, e.g Claude knows the active vscode tab and highlighted lines.
Re: How I use every Claude Code feature
#40Blog posts like this would really benefit from specific examples. While I can get some mileage out of these tools for greenfield projects, I'm actually shocked that this has proven useful with projects of any substantial size or complexity. I'm very curious to understand the context where such tools are paying off.