Prompt of the day:

/wait-what questions did you have for me

Great for when the agent has gone off on its own for hours and has random questions scattered through its context window.

holy sh*t. Official Anthropic tip for Claude Code: stop burning Opus 5.5 context on tasks Haiku 5.5 can swarm, while Sonnet 5.5 builds

put the architect on call with /advisor

claude --advisor opus --subagents haiku

Sonnet 5.5 drives the primary session on high effort, writing diffs and running test suites
Haiku 5.5 subagents swarm the repo in parallel at 340 tok/s, handling file discovery and spec docs lookup
Opus 5.5 stays on call in the background as the advisor, only stepping in at three critical moments:

→ before a plan locks: does the implementation plan miss auth invariants or schema contracts?
→ when a test breaks twice: are we fixing the root cause or falling into a recursive rabbit hole?
→ before calling done: did the full diff introduce hidden regressions or break pre-flight rules?

Opus 5.5 reviews. Sonnet 5.5 builds. Haiku 5.5 swarms

Jev engineering runs the identical pattern one layer down: mechanical decisions that need no reasoning (which file to open, which tool to invoke, retry or abort) execute in 16ms, so the frontier models only wake up when execution paths actually diverge

Plan on high. Delegate on medium. Keep Opus on call.

- the full advisor setup
> Opus 5.5 on call reads full session history and catches deep architectural traps
> Sonnet 5.5 lead drives edits, writes core logic, and executes test harnesses
> Haiku 5.5 subagents swarm AST parsing, grep scans, and API docs in parallel
> JEV micro-fork layer resolves 1,500+ mechanical routing branches in under 16ms
> advisor stays completely silent on routine bash execution to protect context

paste the setup and this prompt into Claude Code below:

"Configure my Claude Code workspace for hierarchical advisor orchestration:

1. Audit ~/.claude/settings.json and project config for model roles fitting lead, subagents, and advisor:
> Pin main session model: sonnet with effortLevel: high for primary execution
> Pin subagents model: haiku with effortLevel: medium for parallel file discovery and docs retrieval
> Pin advisor model: opus on call for strategic review

2. Enable the advisor tool in ~/.claude/settings.json:
> Set advisorModel to claude-opus-5-5
> Enable subagent parallel dispatcher pool (3x workers)

3. Configure automatic advisor consultation checkpoints in ~/.claude/CLAUDE.md:
> Consult /advisor opus before finalizing multi-file architecture plans
> Automatically summon /advisor opus when the same test or compiler error fails twice
> Enforce advisor diff contract audit before declaring tasks complete or staging git commits

4. Constrain subagent scopes:
> Haiku subagents return structured AST summaries and docs snippets only without modifying main session context

Show every configuration diff first. Do not apply edits until confirmed"

↳
https://t.co/gvAWk6KbDn

我非常建议大家在每个阶段完成后调用/writing-for-agent和/retro

可能有人从没有管过自己的AGENT.md，里面塞了一大堆中间状态都不知道…这些玩意每轮都会进入AI的上下文，不但耗token还会误导它的工作

或者是文档之间各说各的，有的还没有引用跳转，整个文档系统让AI用得很难受

/retro搭配/writing-for-agent使用可以有奇效！

它们会用渐进式披露原则检查你的README.md和AGENT.md文件，把详细信息用导航的形式放到专用的文档里，把无用的中间过程全部删掉，保持AI的上下文文件清爽

Prompt of the day:

/retro read my last 10 coding agent sessions and find ways to make my repo easier to navigate. Find where agents take too long to find relevant information, or rely on out-of-date docs.

Improving navigability is such an underrated way to save tokens.

Claude Coders: Run this prompt for Opus 5.5 *NOW*.

'/doctor prompt-audit'

Different from a viral post I had earlier this week because it prioritizes stale paths, obsolete commands, and conflicting instructions.

感觉现在 GPT 和 Claude 吐的东西真是又臭又长，刚看到大佬在全局 CLAUDE.md 添加了：

“始终使用 ASD-STE100 简化技术英语进行交流。始终读取 CONTEXT.md 文件，并使用其中定义的通用语言。”

那么，有没有更适合中文场景的提示词呢🤔