spike(framework): make the contributor AI environment portable across supported hosts
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 12/100
- Issue-Typ
- Dokumentation
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- markdown, shell, typescript
- Bereich
- devtools
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 481
- Forks
- 45
- Ø Merge
- 1 T. 13 Std.
- Gemergte PRs (30 T.)
- 91
Entwicklungsumgebung
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus ai-driven-dev/framework
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
ai-driven-dev/framework#1311 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 79/100
ai-driven-dev/framework#1244 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
ai-driven-dev/framework#1197 ·
Maintainer antworten meist innerhalb von 1 Tag
-
refactor(aidd-context): apply the new skill template to learnEvtl. vergeben @blafourcade hat das vor 3 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
ai-driven-dev/framework#1186 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
ai-driven-dev/framework#1163 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in ai-driven-dev/framework
Ähnliche Issues
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 87/100
Maintainer antworten meist innerhalb von 1 Tag
-
🛠️ dette technique
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 61/100
betagouv/mon-entreprise#4752 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 5 Tagen
-
type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
area/providers type/feature version/v2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
anomalyco/opencode#64845 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag