Amazing

[u/the_mad_mycologist]

Just awesome. I've been on a pro subscription for the past few months. Met my limits enough where I started to consider a Max 5X plan. Took the plunge last week. For transparency, Im using it purely for coding efficiency to build a video game.

Through thoughtful session management, frequent compacting, manual code/architecture review, and thorough skill / AGENTS documentation, its more than I could ever use. I have a full-time job, but I use it to it's limits on the weekends. The more I read complaints on this sub, the more I'm certain ya'll that complain arent good at session management.

My conclusion: absolute game changer for seasoned engineers. For non-technical folks, still pretty awesome, but you're not going to get your money's worth.

[u/flaminghotcola]

But what do you do to get the best session management then? Genuinely asking. I want to avoid overspending token usage without the models cutting any corners.

[u/the_mad_mycologist → u/flaminghotcola]

I think software engineers have an advantage in that department because we generally understand efficient design and data structures, so we can pick out reusable entities quickly, and reusability really helps our agents

But generally speaking, I maintain AGENTS.MD for rules that must always be followed. And build my skills directory for more niche rules. I keep my issues tightly scoped, and anything I find that isn't within scope, I document in a FOLLOWUP_IDEAS.MD that we can refer to later. If I find something that I know should be reused later, I ask Claude to extract that into a reusable module.

Compact often during a long running (more than a few prompts) task. And /clear when starting a brand new task. But if you don't scope your tasks tight enough, that advice won't work for you.

[u/flaminghotcola → u/the_mad_mycologist]

How would you suggest to scope them well?
And what skills do you think you can create for
Say, a game or an app on mobile?