Claude Code 子代理上线前 20 项质检清单与成本策略

来源摘录

Vox@Voxyz_ai原内容发布于 2026年9月27日

Claude Code tip: before you ship a vibe-coded site, have Opus 5.5 send out 𝟱 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟮𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then fix them all in one pass: Consistent design → Write a DESIGN.md first, and make every color, font size, spacing and corner radius follow it → Keep the palette restrained and the type hierarchy clear → Make every button, card and input of the same kind look alike → Too flat? Add emphasis. Too crowded? Cut → Keep text readable on both dark and light backgrounds On mobile → No sideways scrolling, and nothing spilling off the screen → Add a mobile menu → Make buttons big enough to tap → Keep the layout intact when the text is enlarged Every state → Give loading, empty and error states a proper screen → Give every button feedback, with its own hover, pressed and disabled look → Show form errors right where they happen, plus submitting, success and failure messages → Add transitions to modals, dropdowns and tab switches Use it like a real user → Click through the core flows, like sign-up and checkout, from start to finish → Find buttons that do nothing and links that are broken → Make sure the whole thing works with just a keyboard Before launch → Say what you do in one line on the home page → Give each page one main button you want people to click → Give every page a title, a description and a favicon → Delete all placeholder text For effort, follow Anthropic's cost guide from yesterday: medium is for well-scoped daily work. The default medium is enough for these 20 fixes; raise it for the harder ones. Thariq tested it: turning effort up mostly buys more verification and edge-case testing. Send this whole post to Claude Code. If you need to, add this line at the end 👇 "Send one subagent per group to check it without editing anything. Then fix everything yourself from their lists, so no two agents edit the same file. If a group is more complex, raise that subagent's effort. Show me the list of issues first, don't change anything until I confirm, and when you're done, give me before-and-after screenshots."

Anthropic just published its 𝗳𝘂𝗹𝗹 𝗰𝗼𝘀𝘁 𝗴𝘂𝗶𝗱𝗲 for Opus 5.5. You can ask Opus 5.5 to use it to review your Claude Code setup. At the same effort level, Opus 5.5 thinks more per turn than Opus 5, most of all at xhigh and max. Thinking is billed as output, and an output token costs 𝟭𝟬𝟬 𝘁𝗶𝗺𝗲𝘀 𝗮 𝗰𝗮𝗰𝗵𝗲 𝗿𝗲𝗮𝗱. So don't carry over the level you set for Opus 5. Start at medium, and save xhigh and max for work where you've measured a gain. Send this prompt to Opus 5.5 👇 "Read this guide: https://t.co/8RHkfmiKjM Then review my Claude Code setup against it: my user and project settings, the subagents in ~/.claude/agents and .claude/agents, CLAUDE.md, and the MCP servers I have connected. Find three kinds of problems: 1. A default effort that doesn't fit the work. Use the guide's ladder: low for mechanical edits, medium for well-scoped daily work, high when medium stalls, and xhigh or max only for work where a gain was measured. Flag a default of xhigh or max, or a level I picked for Opus 5. Then look at this project's code and recent commits and tell me which kinds of work here fit which level. 2. Subagents that only search, read logs or run tests but set no model, so they run on my main model. 3. Setup that makes every turn cost more: MCP servers I don't use, or a CLAUDE.md well over 200 lines. For each issue, quote the setting or line, explain what it costs, and suggest the smallest change. Also tell me which three things to check in /usage at the end of a task. Show me the recommendations first. Don't change anything yet."
— @Voxyz_ai（Vox）的引用原文

深度解析

是什么：一条 Claude Code 实战技巧推文串：上线“氛围编码”出的网站前，让 Opus 5.5 派出 5 个子代理，按 20 项清单（视觉一致性、移动端、状态覆盖、真实用户走查、上线检查）分组只读巡检，再由主代理汇总清单、经确认后一次性修复，避免多代理改同一文件，并要求输出前后截图验收。

核心方法：把 QA 按领域拆成互不重叠的分组，用“读改分离”编排消除写冲突，是典型的多代理并行工程模式。被引用的成本线程与 claude.dev 官方文章给出理论支撑：任务成本由轮数、缓存读、输出 token 和模型共同决定；每轮会重发全部上下文，思考按输出计费，而输出价是缓存读的 100 倍，所以 effort 是最贵的旋钮。Opus 5.5 默认 medium 足以覆盖这 20 项修复，更高档位主要换来更多验证与边界测试。

设计维度：清单前四组实质是一份 UI/UX 质量标准——先写 DESIGN.md 约束颜色、字号、间距与圆角，统一同类组件，覆盖 loading/empty/error 与 hover/pressed/disabled 状态，保证无横向滚动、足够触控面积、文字放大后布局不破及全键盘可用。

边界与风险：清单偏表层质检，不能替代真实可用性测试；成本数字来自官方示例，需用 /usage 实测校准；先读后改的流程会拉长反馈周期，小改动未必划算。

来源摘录

Vox@Voxyz_ai原内容发布于 2026年9月27日

Claude Code tip: before you ship a vibe-coded site, have Opus 5.5 send out 𝟱 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟮𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then fix them all in one pass: Consistent design → Write a DESIGN.md first, and make every color, font size, spacing and corner radius follow it → Keep the palette restrained and the type hierarchy clear → Make every button, card and input of the same kind look alike → Too flat? Add emphasis. Too crowded? Cut → Keep text readable on both dark and light backgrounds On mobile → No sideways scrolling, and nothing spilling off the screen → Add a mobile menu → Make buttons big enough to tap → Keep the layout intact when the text is enlarged Every state → Give loading, empty and error states a proper screen → Give every button feedback, with its own hover, pressed and disabled look → Show form errors right where they happen, plus submitting, success and failure messages → Add transitions to modals, dropdowns and tab switches Use it like a real user → Click through the core flows, like sign-up and checkout, from start to finish → Find buttons that do nothing and links that are broken → Make sure the whole thing works with just a keyboard Before launch → Say what you do in one line on the home page → Give each page one main button you want people to click → Give every page a title, a description and a favicon → Delete all placeholder text For effort, follow Anthropic's cost guide from yesterday: medium is for well-scoped daily work. The default medium is enough for these 20 fixes; raise it for the harder ones. Thariq tested it: turning effort up mostly buys more verification and edge-case testing. Send this whole post to Claude Code. If you need to, add this line at the end 👇 "Send one subagent per group to check it without editing anything. Then fix everything yourself from their lists, so no two agents edit the same file. If a group is more complex, raise that subagent's effort. Show me the list of issues first, don't change anything until I confirm, and when you're done, give me before-and-after screenshots."

Anthropic just published its 𝗳𝘂𝗹𝗹 𝗰𝗼𝘀𝘁 𝗴𝘂𝗶𝗱𝗲 for Opus 5.5. You can ask Opus 5.5 to use it to review your Claude Code setup. At the same effort level, Opus 5.5 thinks more per turn than Opus 5, most of all at xhigh and max. Thinking is billed as output, and an output token costs 𝟭𝟬𝟬 𝘁𝗶𝗺𝗲𝘀 𝗮 𝗰𝗮𝗰𝗵𝗲 𝗿𝗲𝗮𝗱. So don't carry over the level you set for Opus 5. Start at medium, and save xhigh and max for work where you've measured a gain. Send this prompt to Opus 5.5 👇 "Read this guide: https://t.co/8RHkfmiKjM Then review my Claude Code setup against it: my user and project settings, the subagents in ~/.claude/agents and .claude/agents, CLAUDE.md, and the MCP servers I have connected. Find three kinds of problems: 1. A default effort that doesn't fit the work. Use the guide's ladder: low for mechanical edits, medium for well-scoped daily work, high when medium stalls, and xhigh or max only for work where a gain was measured. Flag a default of xhigh or max, or a level I picked for Opus 5. Then look at this project's code and recent commits and tell me which kinds of work here fit which level. 2. Subagents that only search, read logs or run tests but set no model, so they run on my main model. 3. Setup that makes every turn cost more: MCP servers I don't use, or a CLAUDE.md well over 200 lines. For each issue, quote the setting or line, explain what it costs, and suggest the smallest change. Also tell me which three things to check in /usage at the end of a task. Show me the recommendations first. Don't change anything yet."
— @Voxyz_ai（Vox）的引用原文

深度解析