project-guidance
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAgent guidance
Agent 指导
Read existing instructions and inspect only the areas relevant to the requested change.
- Enable only the requested workflows. Preserve existing paths, policies, and languages; migrate files or change global configuration only when requested.
- Keep AGENTS.md to actionable repository constraints and conditional links. Include rules that affect agent decisions, not generic advice or facts easily found in code.
- Keep one source per rule. Remove duplication, contradictions, and obsolete references without losing intentional constraints.
- Load detailed references only for the task that needs them. Do not route agents through several indexes or require reading every skill.
- For a new layout, keep AGENTS.md at the root and create only needed references under .agents/docs/, .agents/adr/, or .agents/todo/.
- Require correcting inaccurate guidance, not producing text after every edit. Add an ADR only when its rationale has lasting value, and a task only when work needs tracking.
- Define agent-content and human-documentation languages separately when needed. An English skill does not impose English output on every project.
- Keep task history and procedures out of AGENTS.md. Use specialized skills only for the artifacts needed; do not enable them all as a side effect.
- Check changed paths and links. Do not add explanatory files or usage tutorials unless requested.
阅读现有说明,并且仅检查与所请求更改相关的区域。
- 仅启用所请求的工作流。保留现有路径、策略和语言;仅在明确要求时迁移文件或更改全局配置。
- 将 AGENTS.md 保持为可执行的仓库约束和条件链接。应包含会影响 Agent 决策的规则,而不是通用建议或代码中容易找到的事实。
- 每条规则仅保留一个来源。在不丢失有意约束的情况下,删除重复内容、矛盾和过时引用。
- 仅为需要相关详细参考的任务加载它们。不要让 Agent 层层经过多个索引,也不要要求其阅读每个 skill。
- 对于新布局,将 AGENTS.md 保留在根目录,并且仅在 .agents/docs/、.agents/adr/ 或 .agents/todo/ 下创建确有需要的引用文件。
- 要求修正不准确的指导,而不是在每次编辑后都生成说明文字。仅当决策理由具有长期价值时才添加 ADR,仅当工作需要跟踪时才添加任务。
- 必要时,分别定义 Agent 内容和人类文档的语言。英文 skill 并不意味着所有项目都必须使用英文输出。
- 不要将任务历史和操作流程放入 AGENTS.md。仅针对需要生成的产物使用专门的 skill;不要因附带影响而启用全部 skill。
- 检查发生更改的路径和链接。除非明确要求,否则不要添加解释文件或使用教程。