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

Abierto
#1,222 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
1 d 13 h
PR fusionados (30 d)
91

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.