// Translate approved Russian content to Ukrainian, English, and Spanish. Use when the user asks to translate an article or content to other languages.
| name | content-translate-article |
| description | Translate approved Russian content to Ukrainian, English, and Spanish. Use when the user asks to translate an article or content to other languages. |
| argument-hint | ["what to translate"] |
Translate approved Russian content to Ukrainian, English, and Spanish.
The user will specify what to translate: $ARGUMENTS
STOP if any of these are not met:
Always translate FROM Russian. Never cross-translate (e.g., EN→ES).
Use Jekyll liquid tags:
{% raw %}{% link path/to/file.md %}{% endraw %}
Use standard Markdown with target attribute:
[Link text](https://example.com){:target="_blank"}
When translating content where a heading was renamed, preserve the legacy anchor:
<span id="old-heading-id" class="legacy-anchor"></span>
## New Heading Name
Copy legacy anchors exactly as they appear in the Russian source.
Use the same link for ALL language versions:
https://bit.ly/spain_life_guide_tgchannelCRITICAL: When translating partner/gestor/lawyer profiles, REORDER the "Languages" field for each site version.
Order by relevance to the audience:
DO NOT copy the same order to all versions!
_includes/ua/{same-path-as-ru}_includes/en/{same-path-as-ru}_includes/es/{same-path-as-ru}ru/{article}/index.md → ua/{article}/index.md, en/{article}/index.md, es/{article}/index.mdCRITICAL: If the Russian article was added to index.md (RU index), you MUST add it to ALL other language index files too!
Check index.md for any new includes/sections, then add the same structure to:
en/index.md - with translated heading and {% raw %}{% include en/... %}{% endraw %}ua/index.md - with translated heading and {% raw %}{% include ua/... %}{% endraw %}es/index.md - with translated heading and {% raw %}{% include es/... %}{% endraw %}This is NOT optional - all 4 index files must have identical structure.
Whenever content changes, find the <p class="last-updated"> tag in the affected page and update the date in ALL 4 language versions. Determine which page contains the translated content (index page, stand-alone article, etc.) and update accordingly.
Date formats per language:
<p class="last-updated">Последнее обновление: 24 января 2026</p><p class="last-updated">Останнє оновлення: 24 січня 2026</p><p class="last-updated">Last updated: January 24, 2026</p><p class="last-updated">Última actualización: 24 de enero de 2026</p><p class="last-updated"> tag on the affected page and update in all 4 language versionsCRITICAL: You MUST go through EVERY item below and show the user a verification table before presenting the translations. Do not skip any items. Format: table with columns "Item | Status (✅/❌/⚠️/N/A) | Comment".
Translations completed:
Language-specific rules:
Terms & formatting:
Links:
{% link path %} formatbit.ly/spain_life_guide_tgchannel for all versionsSpecial cases:
Index & dates:
<p class="last-updated"> date updated in all 4 language versions of the affected pageYour response MUST include these sections in order:
Example format:
## Checklist Verification
| Item | Status | Comment |
|------|--------|---------|
| Translated to UA | ✅ | Done |
| Translated to EN | ✅ | Done |
| Translated to ES | ✅ | Done |
| UA: no Russian words | ✅ | Checked, all Ukrainian |
| Telegram links correct | ✅ | bit.ly/spain_life_guide_tgchannel |
| Partner profile languages reordered | N/A | Not a profile translation |
| Index files updated | ✅ | Added to all 4 indexes |
| Last-updated date | ✅ | Updated on all 4 pages |
...
## Files Updated
- `_includes/ua/section/article.md` (created)
- `_includes/en/section/article.md` (created)
- `_includes/es/section/article.md` (created)
- `ua/index.md` (updated - added new section)
- `en/index.md` (updated - added new section)
- `es/index.md` (updated - added new section)
Do NOT skip the verification table - it proves you completed the checklist.
After completing translations, summarize:
Analyze an article and add relevant internal links from both SLG and ITA projects. Use when the user asks to add internal or cross-project links to an article.
Verify all claims, numbers, deadlines, and legal references in an article against official sources. Use when the user asks to fact-check or verify article content before publication.
Prepare an article for publication by running internal link addition and fact-checking in parallel. Use when the user asks to finalize, prepare, or get an article ready for publishing.
Write or edit article content in the author's authentic voice. Use when the user asks to write, create, or edit an article, blog post, or content for the Spain Life Guide site.
Run all local validation checks that don't require network access to the live site.
Verify internal links database integrity and update with new pages and anchors.