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

Offen
#978 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@blafourcade arbeitet bereits daran.

Seit 08.10.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
91

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.