spike(framework): make the contributor AI environment portable across supported hosts
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- markdown, shell, typescript
- Área
- devtools
Línea de trabajo
This is a design spike, not a code change: start from the inventory table and the cli/.claude/rules/00-architecture/0-hexagonal.md and cli/.claude/skills/tools/SKILL.md files it cites, plus scripts/check-hosts.cjs and scripts/dev-sync.sh. Done means a versioned inventory, a host compatibility matrix with reproduction commands, and a recommendation covering scoping, user-owned files, and bootstrap risks, all agreed with maintainers before any PR.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
AIDD's own contributor AI environment is partly Claude Code-specific. Contributors modifying ai-driven-dev/framework with Codex, Kilo Code, OpenCode, or other supported hosts may not receive the same project guidance, architecture rules, skills, and automatic feedback as Claude Code users.
This concerns contributing to the framework itself, not the AIDD plugins distributed to downstream projects.
Static inventory of next at commit 8d67ae942fd61e36daca9b1f28a25ad065ca26c9:
| Contributor resource | Current state | Portability question |
|---|---|---|
Root .claude/rules/ |
3 rules | No automatic Codex discovery established |
cli/.claude/rules/ |
12 CLI architecture and development rules | No equivalent project-level Codex projection found |
cli/.claude/skills/ |
5 skills: distribution, framework, test, tools, translate |
No cli/.agents/skills/ equivalent in the tracked tree |
Root .claude/skills/release-video/ |
1 skill | Symlink under .agents/skills/; live discovery still needs verification |
Root .claude/hooks/ |
PostToolUse and WorktreeCreate hooks |
No equivalent host behavior demonstrated |
cli/CLAUDE.md |
CLI-specific guidance and memory imports | No corresponding cli/AGENTS.md |
Root CLAUDE.md and AGENTS.md |
Overlapping contributor instructions | Effective precedence and drift need evaluation |
Biome, architecture tests, Lefthook, and CI already enforce many constraints independently of the assistant. However, catching a violation after generation is not equivalent to making the architectural rules available during implementation.
make setup, make reload, and make check-hosts provide multi-host developer tooling, but their current checks do not establish contributor-rule and workflow parity. These are static findings, not proof of a runtime failure for every host.
Scope
- Inventory all contributor-owned instructions, rules, skills, hooks, scripts, and referenced assets, including nested
cli/resources. Classify ownership, repository scope, and mandatory versus optional behavior. - Verify native discovery, instruction precedence, path-scoped rule applicability, skill invocation, supporting-reference resolution, and hook behavior across Claude Code, Codex, Kilo Code, and other supported hosts where feasible. Report tested versions and unsupported cases.
- Map each rule to existing deterministic checks (Biome, architecture tests, Lefthook, CI), separating agent-time guidance gaps from already enforced invariants.
- Compare a minimal shared-file/host-projection approach with an optional framework-contributor plugin (provisional name
aidd-contributor) using existing AIDD CLI translation, distribution, and installation capabilities. - Build a narrow proof of concept using the
toolscontributor skill and representative CLI architecture rules; test discovery, applicability, reference paths, and repository-scoped behavior. - Recommend the smallest justified follow-up, preserving a bootstrap path that works even when the AIDD CLI or plugin installation cannot run.
Acceptance criteria
- A versioned inventory identifies contributor resources, owners, scopes, and current host entry points, including the 15 rules, 6 skills, and 2 hooks in this baseline.
- A host compatibility matrix records observed discovery, rule applicability, skill invocation, reference resolution, and hooks, with reproduction commands, host versions, and explicit uncertainty.
- Documented portability gaps distinguish missing agent-time guidance from deterministic constraints already enforced elsewhere.
- A reproducible POC compares shared/native projections against the proposed contributor plugin, without assuming either architecture must win.
- The recommendation addresses repository scoping, user-owned file preservation, updates, duplicate prevention, host-specific hooks, and bootstrap/dependency-cycle risks.
- Contributors retain a functional baseline through
AGENTS.md,CONTRIBUTING.md,make,pnpm, and local tests without relying on the new plugin. - The outcome names the smallest necessary follow-up implementation work, if any.
Prior art in this repo
- Root contributor rules and CLI-specific rules, including CLI hexagonal architecture rules.
- CLI contributor skills, including tools/SKILL.md; release-video skill.
- CLI-local CLAUDE.md, root CLAUDE.md and root AGENTS.md.
- Claude-specific hook setup, dev-sync.sh, check-hosts.cjs, Lefthook, and CI validation.
- #929 defines the broader portability boundary; #978 covers declared host compatibility; #245 covers local contributor testing; #916 covers portable agents; #914 covers Kilo-native generation. This investigation focuses only on the framework's own contributor environment.
Out of scope
- Changing end-user plugin behavior or replacing the framework's canonical Claude-format source.
- Assuming the dedicated contributor plugin is already the chosen implementation.
- Forcing hosts to expose identical hook mechanisms.
- Installing repository-specific contributor rules globally in unrelated projects.
- Removing deterministic architecture gates, automatically migrating user-owned files, or introducing a second independent translation engine.
- Implementing a full migration or opening a PR before maintainers agree on the proposed direction.
- Lenguaje dominante
- TypeScript
- Estrellas
- 481
- Forks
- 45
- Merge medio
- 1 d 13 h
- PR fusionados (30 d)
- 91
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ai-driven-dev/framework
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
ai-driven-dev/framework#1311 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
ai-driven-dev/framework#1244 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ai-driven-dev/framework#1197 ·
Los mantenedores suelen responder en 1 día
-
refactor(aidd-context): apply the new skill template to learnPosiblemente ocupada @blafourcade la tomó hace 3 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ai-driven-dev/framework#1186 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
ai-driven-dev/framework#1163 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de ai-driven-dev/framework
Issues similares
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPosiblemente ocupada @pcbeingused333 la tomó hoy. AbiertoBug db: d1-sqlite Payload OSS
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
payloadcms/payload#19766 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
device-management-toolkit/sample-web-ui#3711 ·
Los mantenedores suelen responder en 1 día
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/kibana#306401 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
agentes-chat/agentes-chat#927 ·
Los mantenedores suelen responder en 1 día
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPosiblemente ocupada @seenimohamed la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ardia-browser/ardia#2769 ·
Los mantenedores suelen responder en 1 día