Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A few thoughts on this:

- I wouldn’t outsource my brain to CC when it comes to checking CC’s output. Very mixed results in my experience, and it might discourage further exploration/thinking if you’ve already performed the checklist CC has given you (satisficing).

- Slash commands are the idiomatic way to memoize often used prompts, I wonder why author put them in CLAUDE.md?

- I’m also a bit skeptical that, aside from strict rules CC needs to follow, the encouragements/enchantments for writing good code author put in CLAUDE.md really work. But who knows.

- I DO like the caveats section at the end a lot. This is probably the most important piece of the article, when it comes to large codebases. Never just accept the first draft. Review everything with high suspicion and bend the output to your own style and taste. Otherwise, you‘re pushing legacy code.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: