Claude Code 技巧：让 Opus 5.5 主跑，Fable 做顾问
𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: once Opus 5.5 is your main model, don't let your Fable quota si…
提供了极具实操价值的 Claude Code 多 Agent 协作工作流，包含具体的配置步骤和 Prompt，结构清晰且可直接复用。
𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: once Opus 5.5 is your main model, don't let your Fable quota sit idle. Put Fable on call with /advisor.
𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 提示：一旦 Opus 5.5 成为你的主力模型，不要让 Fable 的配额闲置。通过 /advisor 让 Fable 随时待命。
Run /advisor fable and Claude Code gets 𝗮𝗻 𝗮𝗱𝘃𝗶𝘀𝗼𝗿 𝗼𝗻 𝘁𝗵𝗲 𝘀𝗶𝗱𝗲𝗹𝗶𝗻𝗲𝘀. Opus 5.5 keeps doing the work and usually calls Fable in at three moments: → Before committing to a plan: is it right? → When the same error keeps coming back: am I heading the wrong way? → Before saying "done": did I miss anything? Fable reads the whole session and gives advice. Opus still writes the code.
运行 /advisor fable，Claude Code 就会获得一个 𝗦𝗶𝗱𝗲𝗹𝗶𝗻𝗲 𝗔𝗱𝘃𝗶𝘀𝗼𝗿（场边顾问）。Opus 5.5 继续执行工作，通常会在三个时刻调用 Fable： → 在承诺执行计划之前：这个计划对吗？ → 当同一个错误反复出现时：我是否走错了方向？ → 在宣布“完成”之前：是否有遗漏之处？ Fable 会阅读整个会话并提供建议。代码仍由 Opus 编写。
The tree is the full setup. Opus 5.5 on high runs the main session. Three subagents on medium split the rest: one reads code, one edits and runs tests, one looks up docs. Fable waits on the sidelines. Hand the tree and this prompt to Claude Code to set it up 👇
该树状结构代表完整的配置。高配模式下的 Opus 5.5 运行主会话。三个中配模式的子代理分担其余任务：一个负责阅读代码，一个负责编辑和运行测试，一个负责查阅文档。Fable 在场边待命。将此树状结构和此提示词交给 Claude Code 以进行设置 👇
"Set up my Claude Code to match this tree: 1. For the three subagents, reuse fitting ones from ~/.claude/agents and .claude/agents, and propose new ones only for missing roles. Set each to model: opus and effort: medium. Leave any subagent that already sets a different model alone, and list it. 2. Set the main session's default effort to high with effortLevel in ~/.claude/settings.json. 3. Check for environment variables that turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, or DISABLE_TELEMETRY and anything else that stops flag fetching) and for CLAUDE_CODE_EFFORT_LEVEL, which overrides every subagent's effort. Report them; don't change them. 4. Add one rule to ~/.claude/CLAUDE.md: ask the advisor before committing to a big plan, when the same error shows up a second time, and before calling a long task done.
"按照以下树状结构配置我的 Claude Code： 1. 对于这三个子代理，请从 ~/.claude/agents 和 .claude/agents 中复用合适的代理，仅针对缺失的角色提出新的代理。将每个新代理设置为 model: opus 且 effort: medium。保留任何已设置不同模型的现有子代理不变，并将其列出。 2. 在 ~/.claude/settings.json 中将主会话的默认 effortLevel 设置为 high。 3. 检查是否存在关闭顾问的环境变量（CLAUDE_CODE_DISABLE_ADVISOR_TOOL，或 DISABLE_TELEMETRY 以及任何其他阻止标志获取的变量），以及会覆盖所有子代理 effort 的 CLAUDE_CODE_EFFORT_LEVEL。报告这些变量；不要修改它们。 4. 在 ~/.claude/CLAUDE.md 中添加一条规则：在承诺执行大型计划前、同一错误第二次出现时、以及在调用长时间任务完成前，询问顾问。"
Show me the changes first. Don't edit any files yet."
先向我展示更改内容。暂时不要编辑任何文件。"
https://code.claude.com/docs/en/advisor
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力