Vox(@Voxyz_ai):𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: once Opus 5.5 is your main model, don't let your Fable quota sit idle. Put Fable on call with /advisor. 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. 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 👇 "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. Show me the changes first. Don't edit any files yet."

2026.09.24 21:19

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: once Opus 5.5 is your main model, don't let your Fable quota sit idle. Put Fable on call with /advisor. 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. 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 👇 "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. Show me the changes first. Don't edit any files yet."

Vox@Voxyz_ai

2026.09.23 19:58

Anthropic just published a guide to using Opus 5.5. It tells you to delete "think carefully" from your prompts. You can ask Opus 5.5 to use it to review the old rules in your project. It already thinks before every reply, and it decides how much. Delete that line and replies start sooner, with no drop in quality. If your CLAUDE.md still says "take a deep breath" or "IMPORTANT: think hard," delete those too. Send this prompt and the link below to Opus 5.5 👇 "Read this guide and review my project's CLAUDE.md, AGENTS.md, skills, and saved prompts. Find three kinds of problems: lines that push you to think more, like 'think carefully' or 'take a deep breath'; rules and prompts that hand out tasks one step at a time or don't define what done looks like; and rules that make you stop for confirmation when you don't need to. For each issue, quote the original instruction, explain its impact, and suggest the smallest change needed. List any approval rules involving safety, permissions, or destructive actions separately for me to decide. Also suggest adding one rule: at the end of every long run, report under three headings: Blocked on me, Changed, Found. Show me the recommendations first. Don't modify anything yet."

1.3K

커뮤니티로 전달