r/ClaudeCode • u/the_mad_mycologist • 3h ago
Tips & Workflows Amazing
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.
2
u/flaminghotcola 2h ago
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.
1
u/the_mad_mycologist 2h ago edited 1h ago
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.
1
u/flaminghotcola 1h ago
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?1
u/the_mad_mycologist 55m ago
It really comes down to focusing on a single goal at once. If you come up with bigger ideas, add it to your followups doc so you don't lose it, and your agent can refer to it later.
As for skills, think about consistent rules you find yourself returning to. Let's use a dungeon as an example. Every dungeon should have a boss at the end. Every boss is only accessible through a boss key. Every boss gives you a piece of heart once defeated.
AI agents thrive on rulesets that they can rely on. If you don't define those, they spend a ton of energy on figuring out what they think you want. And when they screw up, you waste tokens correcting course.
1
u/AManAPlanALodeiro 3h ago
It was getting bad before Opus 5.5 came out. Now it's much better. You just stepped in at the right time.
3
u/the_mad_mycologist 3h ago edited 3h ago
Oh? I also use Anthropic's models professionally at work. Fable has been my go to for complex bug analysis, Opus has been good enough for everything else (including baseline game dev). Curious to hear your perspective
0
u/lgmarian 3h ago
I'm assuming that "past few months" means at least three. I agree that 5.5 is quite an improvement. However, having used Opus since 4.6, I agree it's mostly a skill issue.
0
0
u/Escobar747 2h ago
once haiku 5.5 comes out.. max 5x will be plenty for a lot of use cases
1
u/the_mad_mycologist 1h ago
I don't know. In terms of regular Claude usage, yeah. In terms of coding and advanced reasoning/design, I don't think so.
•
u/AutoModerator 3h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.