feat(aidd-context): make generated artifact language configurable

Offen
#1,222 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
markdown, typescript

Rechercherichtung

Start with the rule generator's language rule in plugins/aidd-context/skills/05-rule-generate/references/rule-authoring.md (R4, "English unless asked otherwise"), then compare the English-only rules in the skill, agent, command and hook authoring references (R5, R4, R3, R7). Done means an explicit French request applies to natural-language text in all five generators, English stays the default, and generation and validation tests pass for both languages. The open design question is which content stays language-neutral, so check with maintainers before writing code.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Problem

The authoring contracts for generated skills, agents, commands and hooks require English, even when a user requests another language. The rule generator already allows another language when requested. This leaves multilingual teams with inconsistent output, and the contracts do not explain whether English is required for compatibility or is a convention.

Scope

  • Let users request the natural language for generated artifact text across skills, agents, commands, hooks and rules.
  • Keep English as the default.
  • Define which content is natural language and which must retain the target tool's required names, keys, markers, placeholders and executable syntax.
  • Document the language policy and its compatibility boundary.

Acceptance criteria

  • English remains the default.
  • An explicit language request applies consistently to natural-language content from all five generators.
  • Required technical identifiers, structure and executable content remain compatible with their target tools.
  • Documentation explains how language selection works and what stays language-neutral.
  • Generation and validation cover English and French; existing English behavior remains valid.

Prior art in this repo

Out of scope

  • Translating AIDD's own source files.
  • Translating technical identifiers or executable code.
  • A persistent project-level language setting; this proposal covers an explicit request during generation.
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.