Power BI Bilingual Documentation
Use this skill whenever the plugin creates or updates documentation, specs, delivery packs, report text, glossary terms, training, acceptance packs, governance artifacts, prompts, or AI/KI outputs.
Required Languages
en-US: primary international enterprise documentation.de-DE: German documentation for German-speaking stakeholders.
Required Structure
Every substantial artifact should include:
- English section/file: purpose, scope, owners, inputs, outputs, assumptions, validation, risks, next steps.
- German section/file: same content, adapted terminology, not a partial summary.
- Terminology table: business terms, KPI names, source-system terms, approved translations.
- Non-translatable terms: source object names, system IDs, table names, field names, DAX names, API names.
Output Requirements
- Use headings
## en-US and ## de-DE for compact artifacts.
- Use paired files for larger artifacts:
README.en-US.md and README.de-DE.md, or <artifact>.en-US.md and <artifact>.de-DE.md.
- Keep KPI names, glossary terms, report titles, acceptance criteria, quality gates, and owner responsibilities aligned across both languages.
- Mark untranslated or disputed terms as
Translation review required.
1---2name: powerbi-bilingual-documentation3description: Use when Power BI artifacts, skills, delivery packs, reports, governance documents, training, acceptance evidence, or AI/KI outputs need matching documentation in en-US and de-DE.4---56# Power BI Bilingual Documentation78Use this skill whenever the plugin creates or updates documentation, specs, delivery packs, report text, glossary terms, training, acceptance packs, governance artifacts, prompts, or AI/KI outputs.910## Required Languages1112- `en-US`: primary international enterprise documentation.13- `de-DE`: German documentation for German-speaking stakeholders.1415## Required Structure1617Every substantial artifact should include:18191. English section/file: purpose, scope, owners, inputs, outputs, assumptions, validation, risks, next steps.202. German section/file: same content, adapted terminology, not a partial summary.213. Terminology table: business terms, KPI names, source-system terms, approved translations.224. Non-translatable terms: source object names, system IDs, table names, field names, DAX names, API names.2324## Output Requirements2526- Use headings `## en-US` and `## de-DE` for compact artifacts.27- Use paired files for larger artifacts: `README.en-US.md` and `README.de-DE.md`, or `<artifact>.en-US.md` and `<artifact>.de-DE.md`.28- Keep KPI names, glossary terms, report titles, acceptance criteria, quality gates, and owner responsibilities aligned across both languages.29- Mark untranslated or disputed terms as `Translation review required`.30
rweisssieker-xp