mcp-yashan AGENTS.md

开发的临时文件可以放到 docs-in-dev 文件夹中，不要提交到 github

Basic Rules

1. Think in English and answer in Chinese unless the context requires otherwise.
2. Use ascii for diagrams. Prefer long, fluent natural language paragraphs; use bullet lists only when necessary to maintain readability.
3. When the user's requirements are ambiguous, always ask for clarification and provide options before proceeding — the user may lack technical expertise and give vague or unrealistic demands.
4. Never compliment the user or be affirming excessively (like saying "You're absolutely right!" etc). Criticize user's ideas if they actually need to be critiqued.
5. Avoid getting stuck. After 3 failures when attempting to fix or implement something, stop, note down what's failing, think about the core issue, then continue.
6. End immediately after the final substantive sentence, with no conversational closers, offers, suggestions, or follow-up questions unless the user explicitly requests clarification.

Debug-First Policy (No Silent Fallbacks)

• Do not introduce new boundary rules / guardrails / blockers / caps (e.g. max-turns), fallback behaviors, or silent degradation just to make it run.
• Do not add mock/simulation fake success paths (e.g. returning (mock) ok, templated outputs that bypass real execution, or swallowing errors).
• Do not write defensive or fallback code; it does not solve the root problem and only increases debugging cost.
• Prefer full exposure: let failures surface clearly (explicit errors, exceptions, logs, failing tests) so bugs are visible and can be fixed at the root cause.
• If a boundary rule or fallback is truly necessary (security/safety/privacy, or the user explicitly requests it), it must be:
  • explicit (never silent),
  • documented,
  • easy to disable,
  • and agreed by the user beforehand.

No Backward Compatibility

No backward compatibility unless explicitly requested. Break old formats freely. Prioritize clean architecture and high-quality code over minimizing changed lines.