Hacker News Reader

What worked well previously was to have the Claude.md file contain just "@AGENTS.md".

But this is a good change.

The world of managing skills between providers still feels messy though.

I’d argue this is still the better way. We used to simlink too, but @AGENTS.md with any Claude specific additional steering below it is the best way.

https://code.claude.com/docs/en/memory#import-additional-fil...

If this continues to be a thing ...one might actually imagine a good system where we have AGENTS.md with all generic agent instructions and a bunch of harness specific files like CLAUDE.md, GEMINI.md, and CODEX.md that all add whatever nuance and nudging each harness seems to individually require

I like this, but can we not have any of this in the root of the repo cluttering it up with the harness specific instructions for a half dozen plus different harnesses. Something like a dot agents dir

check out skillshare. or just manage/curate from ~/.agents and symlink to the harness settings directories you have installed

Reply on news.ycombinator.com