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

Abierto
#978 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@blafourcade ya está trabajando en esto.

Desde el 8/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
1 d 13 h
PR fusionados (30 d)
91

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.