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

Ouverte
#978 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@blafourcade y travaille déjà.

Depuis le 8/10/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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.

Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 13 h
PR mergées (30 j)
91

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.