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

Aberta
#1,222 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
markdown, typescript

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
481
Forks
45
Merge médio
1d 13h
PRs com merge (30d)
91

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ai-driven-dev/framework

Todas as issues de ai-driven-dev/framework

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.