Skip to content

An open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作

:memo: Prefer existing workflows when evaluating implementation requests https://github.com/siyuan-note/siyuan/issues/20696

Daniel5bb41ffbdb1b
diff --git a/AGENTS.md b/AGENTS.md
index c71f3b7d2d..adb30d6987 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -17,8 +17,8 @@ SiYuan repository guide. Module path `github.com/siyuan-note/siyuan`, license AG
Before implementing a requirement, evaluate its premise and approach with effort proportional to its complexity and risk
1. **Check compliance first:** For major features, review applicable compliance requirements, licensing terms, privacy risks, and costs before technical design
-2. **Check the premise and existing capabilities:** Inspect the relevant implementation, settings, shortcuts, APIs, or plugin capabilities, and reproduce reported behavior when feasible. Check applicable repository rules, encrypted notebook compatibility, the `.sy` format, and API contracts. Distinguish the user's goal and acceptance criteria from a suggested implementation; evaluate whether that implementation addresses the underlying problem. State any limits to verification
-3. **Choose an appropriate approach:** Prefer the smallest sufficient change consistent with existing practices and compatibility requirements. Consider whether an existing capability or a documentation correction already satisfies the need, including the option of making no code change
+2. **Check the premise and existing capabilities:** Inspect the relevant implementation, settings, code snippets, shortcuts, APIs, or plugin capabilities, and reproduce reported behavior when feasible. Check applicable repository rules, encrypted notebook compatibility, the `.sy` format, and API contracts. Distinguish the user's goal and acceptance criteria from a suggested implementation; a named implementation form (for example, a JS script) does not remove this evaluation step. Evaluate whether that implementation addresses the underlying problem, respect explicit user constraints, and state any limits to verification
+3. **Choose an appropriate approach:** Prefer the smallest sufficient change consistent with existing practices and compatibility requirements. Consider whether an existing capability or a documentation correction already satisfies the need, including the option of making no code change. Compare user effort, persistence, reversibility, and maintenance when choosing among suitable approaches. For styling-only workarounds, consider CSS snippets with built-in enable/disable controls before JavaScript that injects styles. Explain how to enable, disable, or undo the chosen solution when relevant
4. **Briefly report before editing:** State the conclusion, key evidence, and remaining uncertainty in a progress update before the first change. Discuss alternatives only when they involve meaningful tradeoffs; simple tasks need only a short explanation
5. **Ask only when a decision is needed:** If the premise is false or implementation is unwarranted, explain the evidence and ask how to proceed unless the user's existing instructions already resolve the next step. Ask before changing the agreed goal or scope, or making an unresolved product, priority, or compatibility tradeoff. Do not silently narrow or broaden the task
6. **Otherwise proceed directly:** When the requirement is reasonable, implement it without another confirmation round. Choosing a different implementation that meets the agreed goal and acceptance criteria does not itself require approval