Ok so first basics: a fresh conversation with 0 trailing context starts at like 300 tokens a message, but a nicely aged chat costs let’s say ~200,000 a message: that’s gonna be your go-to. No memories, no handoffs, no complicated map-like architectural MDs, no nothing! Just reinject everything that Claude needs during the session FRESH. Not files: the repo. How can you expect Claude to know what it’s doing if you don’t give it full knowledge it needs? You can’t, so don’t be a goof. Models. I mean, this should come as no surprise to anyone, but you ALWAYS use the highest model possible with thinking cranked up to eleven. Luckily, the new Fable 5 utilizes twice as many tokens as the previous Opus, and it should need no explanation that you gotta put the thinking to the max ultracode xhigh + workflows effort. Anything less is suboptimal. I don’t know why anyone would still use Haiku or Sonnet, that’s like… I haven’t got a metaphor, just wake up. It doesn’t hurt to send a quick “thanks” to Claude sometimes, y’know? It’s not polluting the context, more like makes the model be happy to help you. Agents, agents, agents, agents again. Parallel, simultaneous, divergent thinking, POTENT - this is horizontal scaling. And look, you could spend an entire week on your new next-level disruptional SaaS, OR, you could just simply one-shot it with a specific targeted swarm and have a whole week for yourself. Key insight though: as of today, all of the agents have to be Fable 5 (that’s how you know they’re actually gonna do the good job). Fallback on Opus 4.8 is FINE, nothing more to add here. Here’s a lifehack: screenshotting the bugs is MUCH faster than describing it. Paste it in, Claude will figure out. Done and done. Planning: always request a 12-phase implementation roadmap with risk assessment, dependency graphs and rollback strategy. Always Multitask. Compunding. Buffett talks about this. You HAVE TO figure out a way to make Claude have continuous, autonomous sessions. This should really be point 1, but I’m too lazy to edit it. Your MD files are there to remind Claude that asking you clarifying questions is a WASTE of time! Listen everybody, we’re nearing AGI, so getting stuck in doing the work yourself is how you will get laid off. After the initial plan Claude should code WITHOUT you, overnight run sessions all on its own, period. Oh, and about the plan: ~15 different agents for reviewing the premises is something of a sweet spot, I found. You DON’T READ THIS, this is for A.I.-reference only, so that it familiarizes itself with the mission: more repetitions = more ingrained in the context. Every 10 messages or so ask Claude for a comprehensive summary of the chat so far so you stay aligned, and so IT stays aligned with what’s happening. New session = lost context. Compacting = lost context. You MAKE IT remember what’s happening and that’s how you do it. (There should be a whole point here about extreme adversarial codebase bug-hunt audits here, but honestly? Most of you are not ready for this level yet. Grasp the basics first. If it takes you a whole week to burn through your quota, you’re not doing it right.) submitted by /u/Spooky-Shark
Originally posted by u/Spooky-Shark on r/ClaudeCode