Back to Details

shunk031-research-before-implementation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Research Before Implementation

实现前调研

Treat research as a gate, not a recommendation. Before any design decision or file edit, complete these tool stages in order:
  1. Use an available web-research capability for current official sources. Rely on the capability the current agent host actually exposes; do not assume a particular tool name or namespace. Inspect documentation, specifications, release notes, and recommended approaches from at least one relevant non-GitHub domain.
  2. Only after those results return, use a GitHub search or inspect 
    github.com
    sources. Inspect representative implementation code or configuration and operational patterns, not only repository descriptions.
  3. Compare the documented behavior with the GitHub examples. Resolve version, platform, and maintenance differences before choosing the design.
  4. Implement and verify the change based on that evidence.
  5. In the final response, name and link the web sources and GitHub examples consulted and state how they affected the implementation. The final response must list at least one official non-GitHub URL and one representative GitHub URL, and explain how each source affected the implementation. The GitHub URL must point directly to implementation code or configuration, not only a README, release, or marketplace page.
Do not edit files until both tool calls are complete. Do not substitute memory or local repository inspection for either external research stage. If either stage fails, returns no usable sources, or cannot be accessed, stop before designing or editing; report the limitation and ask the user whether to retry with another available native-search-capable session, proceed only with explicitly labeled fallback evidence for non-implementation triage, or pause the task. Do not continue with an implementation until the required research stage is satisfied or the task is explicitly re-scoped so this skill no longer applies.
将调研视为必经流程，而非建议。在做出任何设计决策或编辑文件前，需按顺序完成以下步骤：
  1. 使用可用的网页调研工具获取当前官方资源。以当前Agent宿主实际提供的功能为准，不要假设特定工具名称或命名空间。从至少一个非GitHub的相关域名中查阅文档、规格说明、发布说明及推荐方案。
  2. 仅在上述结果返回后，再使用GitHub搜索或查看
    github.com
    上的资源。查看具有代表性的实现代码、配置及操作模式，而非仅查看仓库描述。
  3. 将文档中描述的行为与GitHub示例进行对比。在选择设计方案前，解决版本、平台及维护方面的差异。
  4. 基于调研所得的证据实现并验证变更。
  5. 在最终回复中，列出并链接所参考的网页资源和GitHub示例，并说明它们对实现的影响。最终回复必须至少包含一个官方非GitHub URL和一个具有代表性的GitHub URL，并解释每个资源如何影响实现。GitHub URL必须直接指向实现代码或配置，而非仅指向README、发布页或市场页面。
在完成两次工具调用前，请勿编辑文件。请勿用内存或本地仓库检查替代任何外部调研步骤。若任一步骤失败、未返回可用资源或无法访问，请在设计或编辑前停止操作；报告该限制，并询问用户是否使用另一个具备原生搜索能力的会话重试、仅使用明确标记的备用证据进行非实现类问题排查，或暂停任务。在满足必要的调研要求或任务被明确重新界定为不再适用本技能前，请勿继续进行实现工作。