feat(aidd-context): make generated artifact language configurable
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 30/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- markdown, typescript
- 領域
- documentation, tooling
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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
- Skill authoring, R5, agent authoring, R4, command authoring, R3 and hook authoring, R7 currently require English.
- Rule authoring, R4 already says “English unless asked otherwise”.
- Open draft PR #1092 proposes an “unless the user asks for another language” policy for generated skills. It does not cover the other generators.
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.
- 主要語言
- TypeScript
- 星號
- 481
- 分支
- 45
- 平均合併
- 1 天 13 小時
- 30 天內合併 PR
- 91
環境準備
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
ai-driven-dev/framework 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 86/100
ai-driven-dev/framework#1311 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 79/100
ai-driven-dev/framework#1244 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
ai-driven-dev/framework#1197 ·
維護者通常 1 天內回覆
-
refactor(aidd-context): apply the new skill template to learn可能已有人在做 @blafourcade 於 3 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
ai-driven-dev/framework#1186 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
ai-driven-dev/framework#1163 · 1 則留言 ·
維護者通常 1 天內回覆
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
type: bug
難度 2/5 1-3 小時 新手友好度 78/100
nrwl/nx#37955 · 1 個 reaction ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
db-ux-design-system/core-web#8856 ·
維護者通常 1 天內回覆
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footer可能已有人在做 @wittdennis 今天認領。 未關閉priority: p3 type: bug
難度 2/5 1-3 小時 新手友好度 74/100
googleapis/release-please#2971 ·
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 87/100
維護者通常 1 天內回覆
-
🛠️ dette technique
難度 2/5 1-3 小時 新手友好度 61/100
betagouv/mon-entreprise#4752 · 1 則留言 ·
維護者通常 5 天內回覆