Maximizing Efficiency with Fable until the July 7th Deadline

A couple of pointers that may be obvious, but perhaps would help a few Claude Code users to make the most of the few days Fable is available through subscriptions:

- High effort is really enough.

- Use Fable to review your most challenging code work. Have it output a detailed post-mortem.

- Then have it create implementation plans to fix each block of related issues. Have it classify them according to the proper ordering of implementation, and according to whether they can be done by Opus alone or only with Fable's supervision.

- Ask Fable to spin up an Opus subagent whenever it considers the task suitable for Opus. This will save on your Fable token use.

- When executing the plans from item 2, do not spin up a separate Opus session. Instead, ask Fable to create an Opus subagent, and ask Fable to tell that subagent to perform only tasks that it is able to evaluate and fully understand. I actually had Opus catch Fable in a mistake, which Fable (in a very endearing way) acknowledged.

- You can ask Fable to generate a HANDOFF.md file whenever it needs human interaction - for itself, or when the subagent returns. This way, if you are away from the computer, you can clear the context as soon as you return and spin up a new session based on the handoff. You will save hundreds of thousand of uncached tokens.

These are my 2-cents (written without AI, I am very proud of myself) - please feel free to pitch in.