docs(framework): define verified tool compatibility and tool onboarding

未關閉
#978 2 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@blafourcade 已經在處理了。

開始於 2026年10月8日。

評估

這個 Issue 還沒有評估資料。

描述

Problem

I wanted to add /quick, a command, not a skill, across all supported tools, with this agreed wording:

Answer here in the chat. No web search unless needed. Do not create or modify files. Under 150 words. State uncertainty explicitly. Never guess.

The generator's support table excludes Codex and omits Kilo; all current builds skip commands. We need an explicit support contract: no silent failure for a capability advertised as supported.

Scope

  • Root COMPATIBILITY.md: Claude Code, Cursor, GitHub Copilot, Codex, OpenCode, Kilo Code; VS Code separately as an IDE, through its installed assistant. Include every subsequently registered tool.
  • Cover instructions/memory, skills, agents, rules, commands, MCP and hooks per event. Separate generation, build/install, discovery and execution.
  • Document native/adapted support, limitations, unsupported cases and verification evidence: paths, invocation, prerequisites, scope, tested version/platform and date.
  • Distinguish CLI/IDE and project/user scope. Current distributions: marketplace + flat for Claude/Cursor/Copilot/Codex; flat only for OpenCode/Kilo.
  • Tool-addition guide in cli/ARCHITECTURE.md; CI completeness check; links from README, CONTRIBUTING and existing .github/SUPPORT.md; reconcile contradictory claims.

Acceptance criteria

  • Every registered tool/capability/mode has an explicit support status; unverified cases are identified.
  • Every verified claim has runtime evidence; advertised support never relies only on generated files.
  • Every identified incompatibility links to a corrective issue or an explicit upstream limitation.
  • A contributor can add a tool using the guide; CI catches omitted compatibility coverage.

Prior art in this repo

Out of scope

Implementing /quick, adding tools, or duplicating existing fixes. SUPPORT.md remains the help entrypoint. Vendor limitations must be documented, not hidden behind a universal-support claim.

主要語言
TypeScript
星號
481
分支
45
平均合併
1 天 13 小時
30 天內合併 PR
91

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。