feat: Add translations table to translate and check prompts

Author: MoritzWeber0

.opencode/command/check.md

@@ -10,3 +10,4 @@ Check the page $ARGUMENTS for errors. When no language is provided, check all la
 - Content differs between the different languages. The content should always be the same.
 - The page structure doesn't follow the archetype defined in `archetypes`
 - Anchors of internal links are not matching the referenced and translated title
+- Keywords are not translated as defined in the translations table in `AGENTS.md`

.opencode/command/translate.md

@@ -10,7 +10,7 @@ Follow these rules:
 
 - Do not modify the meaning of content. Translate as 1:1 where possible.
 - Use names of the translation language for cities (e.g., Köln in German, "Cologne" in English and "eau de Cologne" in French).
-- Enforce the Glossary defined in `AGENTS.md`.
+- Enforce the glossary and translations as defined in `AGENTS.md`.
 - Do not translate the keys of the front matter section, the keys of shortcodes or partials.
 - Use the corresponding archetype (defined in `archetypes`) as base for the translated page.
 - Update anchors of internal links to the corresponding section in the target language.

AGENTS.md

@@ -3,10 +3,10 @@
 ## Content Guidelines
 
 - Content MUST support all three languages (en, de, fr)
-- ALWAYS align the content with the corresponding base (defined in `archetypes`)
 - NEVER change the meaning of content when translating. Always translate as 1:1.
-- ALWAYS create new content pages with `hugo new {base}/{name}` where base can be `country`, `operator` or `booking`.
+- ALWAYS align the content with the corresponding base (defined in `archetypes`)
 - ALWAYS use the exact translations for headlines (defined in `archetypes`)
+- ALWAYS create new content pages with `hugo new {base}/{name}` where base can be `country`, `operator` or `booking`.
 
 ### Glossary