// Translate approved Russian content to Ukrainian, English, and Spanish. Use when user asks to translate an article or content to other languages, or after an article has been approved in Russian.
| name | content-translate-article |
| description | Translate approved Russian content to Ukrainian, English, and Spanish. Use when user asks to translate an article or content to other languages, or after an article has been approved in Russian. |
| argument-hint | [article path or topic] |
| allowed-tools | Read, Glob, Grep |
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.
CRITICAL: Use correct Telegram link for each language:
https://bit.ly/it-autonomos-eshttps://bit.ly/it-autonomos-eshttps://bit.ly/it-autonomos-spain-enghttps://bit.ly/it-autonomos-spain-enghttps://bit.ly/autonomo-and-sl-channelCRITICAL: 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 ru/index.md, you MUST add it to ALL other language index files too!
Check ru/index.md for any new includes/sections, then add the same structure to:
index.md (EN - default) - 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.
Update on ALL 4 index pages when content changes:
<p class="last-updated">Last updated: February 7, 2026</p><p class="last-updated">Последнее обновление: 7 февраля 2026</p><p class="last-updated">Останнє оновлення: 7 лютого 2026</p><p class="last-updated">Última actualización: 7 de febrero de 2026</p>CRITICAL: 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 %} formatSpecial cases:
Index & dates:
Your 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 | ✅ | RU/UA: bit.ly/it-autonomos-es, EN/ES: bit.ly/it-autonomos-spain-eng |
| 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)
- `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 article and automatically insert relevant internal and external links from both ITA and SLG projects. Use when user asks to add links to an article or improve article cross-linking.
Perform thorough fact-checking of an article against authoritative official sources. Use when user asks to verify facts, check article accuracy, or validate claims before publication.
Prepare article for publication by running all pre-publication checks (internal links + fact-check) in parallel. Use when user asks to finalize, prepare for publication, or do final checks on an article.
Write or edit article content in the author's authentic voice. Use when writing new articles, editing existing content, or when user provides notes/dictated content to turn into an article about being autónomo or SL in Spain.
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/anchors.