Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Build a working mental model from the code. Explain entry points, data flow, ownership, boundaries, and non-obvious behavior. Use why when the user wants historical motivation.
Treat one module or symbol as simple. Treat a flow across several modules or services as complex.
For a simple question, inspect and explain inline.
For a complex question, divide the system into two to four non-overlapping slices. If the host supports subagents and the user permits them, assign each slice to a read-only subagent using the parent model. Use different available models only for an explicitly requested multi-model critique. If delegation is unavailable or forbidden, inspect the slices inline in the same order.
Each slice must:
Use references/explorer-prompt.md for delegated exploration and references/explainer-prompt.md for synthesis.
Reconcile the slices into one account. Resolve contradictions by reading the code. Do not paste raw exploration reports.
Use only the sections the question needs:
Explain the system before judging it. When permitted, ask two or more read-only critics to assess the same explanation and source files independently. Prefer different available model families when the host supports model selection. Otherwise perform one inline critique against the same rubric.
Read references/critique-rubric.md and references/critic-prompt.md. Classify each finding:
Present the explanation first. Then present the critique and cite the files that support each finding.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
中文简介正在准备中。当前显示原文说明。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
中文简介正在准备中。当前显示原文说明。
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
中文简介正在准备中。当前显示原文说明。
Use when the user asks to restate or explain the last message in plain, jargon-free language.
中文简介正在准备中。当前显示原文说明。
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
中文简介正在准备中。当前显示原文说明。
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
中文简介正在准备中。当前显示原文说明。