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

It does make a big difference in the sense that the less you tell it about things that aren't relevant to it's task, the better it performs.

This has been found in all sorts of variations, and is accepted. It's not just my word, it's the standard understanding. But also, it's true in my experience.

You also limit the session work when you are offloading to agents, which are calling skills. So it does do that as well.

But that's what we're talking about, having agents do things in smaller chunks. Maybe I didn't explain that clearly enough?

It's just a complex topic. It's hard to cover everything. But yet, that's part of the idea. We're making context very specific to the task, and cutting things up into smaller chunks with dedicated context windows only for that task.

I almost completely ignore Claude.md - there are very few rules I want every subtask to know about.

the main system is for cordination, of the many agents with their own dedicated Claude.mds which call their own skills with their own dedicated instructions.

It's like Russian dolls. Now, I do use much, much MUCH larger Agent mds than anyone else. I've been doing this for 10 months, and I believe it's the correct way to do it.

I intend to write a blog post on it, it's a topic in it's own part.

Even your small Claude.md - I would have in several files. The Typescript agent is the only one that needs to know about the Typescript details. This is the kind of thing I mean.



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

Search: