协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
testdino-audit【开发与工程】Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use the TestDino audit flow only when the user explicitly asks for a TestDino audit.
Rules:
Tool selection — use whichever audit tools the TestDino MCP server exposes:
get_audit_report and submit_audit_report are available, prefer those (the current split tools).test_audit tool is available, use it instead (it takes an action parameter).Preferred flow:
health if projectId is not known.get_audit_report with action: "context".test_audit with action: "analyze" and no score.TEST-AUDIT.md).submit_audit_report.test_audit with action: "analyze" plus score and markdownReport.get_audit_report with action: "list" or action: "get".test_audit with action: "list" or action: "get".Important: