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

Aperta
#1,222 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown, typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
1g 13h
PR unite (30g)
91

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.