Fable - Rearchitecting the Claude Code brain and operations
这条记录涉及编程工具或代码能力更新，适合开发者评估工作流变化和可复用价值。
用户利用 Fable 重新架构 Claude Code 的大脑和操作，以优化其未来的使用。他计划使用 Fable 创建知识、代理和正确的设置，并尽可能使用 Opus 和 Sonnet 来减少 Fable 的使用。具体任务包括评估现有应用程序代码并提出架构改进建议，将可重用组件转化为跨项目技能，以及创建避免重复提示的结构。…
So my limit just reset and have 2 days to use Fable with full limits. The first thing I did
Use fable to create knowledge, agents and right setup for Claude Code going forwards. Use opus and sonnet wherever possible to minimize fable usage
* Evaluate my current apps' code, suggest architecture changes for better maintainability going forwards. Should have a clear plan that Opus/Sonnet can execute
* Several projects have reusuable components (skills for analytics, deployment to app store, server deploy, etc). Make sure they are all skills that can be used across projects
* Look at areas where I had to re-prompt to fix basic mistakes. Create structures on how this can be avoided in the future
* Create a skill that automatically determines which model to use. Opus should do bulk of the planning and review. Sonnet agents should be spawned in parallel when possible to execute. Opus then reviews and commits. This should be standard for all projects unless otherwise specified. make sure all chat use this skill
* What else am I missing? What should I be using you for?
Fable spawned 20 parallel agents (was super amazing to watch) as it evaluated multiple codebases (via opus/sonnet agents), created 8 reusable components, 5 new skills + architecture recommendation for my 3 apps. Took 5 minutes and 3% of my 20xMax Fable quota.
This seems like the best use of Fable - as a grandmaster to coordinate the minions to do our bidding.