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

オープン
#978 コメント 2 件 リアクション 0 件 担当者 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時間
マージ済み PR(30日)
91

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。