Fable as orchestrator / reviewer, agents for implementation.
retained text
So, been trying to set up this and so far it is an epic fail for me... so much context wasted, my weekly limit is getting shattered. So, question, is there any good tutorial about how to do this kind of setup? I tried all I could to avoid large context but somehow, every time I instruct claude or want to write documentation Fable is doing it, which I just told not to and have agent do it and review only, but even then it's not always working. Not even sure it is worth it at that point... so if anyone have a good tutorial about that then another one with all the tricks to save context as much as possible, I am all ears. Hopefully a tutorial from an actual skilled and experienced dev rather than some nobodies trying to sell courses proffered. I do not get how people can one shot complex stuff while I am spending days trying to stear AI and try to make this thing work for me. Before I was just using Opus and do task by task and could last a lot longer...This is for a somehow complex app, not in scope but in bunch of physic and contracts that needs to be done on the GPU / display in HDR, to verify the accuracy and so on, and have professional output, so it's not as straightforward as "make a FPS game" and leaving it cook. I wrote some specs into MD files about what needs to be done and how... but still struggling to have speed / momentum. everything takes forever to get tested and speced right, and the app is progressing at snail pace. I try to avoid having too long convos and use /clear often, whenever I can. Something I noticed is fable constantly filling my window with updates from the agents I don't need (still not done... yeah sure, thanks for nothing) and all that jazz for example. Any help appreciated.
document fetched 2026-11-15 00:36 · canonical https://reddit.com/r/ClaudeCode/comments/1xvolje/fable_as_orchestrator_reviewer_agents_for