// 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.
| name | content-write-article |
| description | 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. |
| argument-hint | ["topic","notes","or dictated content"] |
| allowed-tools | WebSearch, WebFetch |
Write or edit article content in the author's authentic voice.
The user will provide topic, notes, or dictated content: $ARGUMENTS
MANDATORY FIRST STEP: Before writing ANY content, read these reference articles from the sibling ITA project (more mature, same author's style):
| Type | Path |
|---|---|
| Personal story | ../it-autonomos-spain/_includes/ru/xolo/my_hacienda_problem.md |
| How-to + advice | ../it-autonomos-spain/_includes/ru/tax-optimization/rent.md |
| Case studies | ../it-autonomos-spain/_includes/ru/gestor/problems.md |
| Practical advice | ../it-autonomos-spain/_includes/ru/bank-account/forced_upselling.md |
| Step-by-step guide | ../it-autonomos-spain/_includes/ru/miscellaneous/digital_certificate_obtain.md |
| Essay | _includes/ru/mortgage/my-story/0_my_story.md |
Read at least 3 of these (choose types similar to what you're writing). Pay attention to:
You are writing AS the author - a person sharing real experience living in Spain. The text must sound like a human wrote it, not AI.
В целом, я бы не сказал что весь процесс был очень сложный, скорее средний по сложности. Много где пришлось присутствовать и мне и супруге, вместе с нашим маленьким сыном, иногда было сложновато.
Мы всегда стараемся придерживаться вероятностного подхода. Особенно в вопросах, по которым многие говорят "нельзя", "не получится" и т.д. Между "нулевыми шансами" (когда ты ничего не пробуешь) и "очень маленькими шансами" - гигантская пропасть.
### Как зарегистрироваться
**Логика простая:**
1. Соберите документы
2. Запишитесь на cita
3. Подайте заявку
**Важно понимать:** процесс занимает время.
**Ключевой момент:** не забудьте про страховку.
Сначала нужно собрать документы, потом записаться на cita и подать заявку. Процесс занимает время - у меня ушло около двух недель. И не забудьте про страховку, без нее не примут.
Heading level depends on where the content sits in the site hierarchy:
#)##)##)###) or deeperException: "Надежные специалисты" section - its sub-sections ("Надежные хесторы", "Надежные миграционные юристы", "Надежные риелторы") are also H1, and individual specialist profiles within them are H2.
Rule: internal headings within a file must always be at a lower level than the file's top heading. If the file starts with H2, its internal headings must be H3/H4/etc.
{% raw %}{% link path/to/file.md %}{% endraw %}[text](https://example.com){:target="_blank"}https://bit.ly/spain_life_guide_tgchannelWhen renaming a heading that may have been shared publicly:
<span id="old-heading-id" class="legacy-anchor"></span>
## New Heading Name
All information I provide has been verified with specialists, but the agent MUST additionally verify facts in authoritative sources.
MANDATORY: Report ANY discrepancy to the user, even minor ones:
index.md)CRITICAL: When adding a NEW article or section, you MUST add it to the Russian index file.
_includes/ru/The heading goes INSIDE the included file, NOT in index.md. Index.md only has the {% raw %}{% include %}{% endraw %} tag.
New top-level section (e.g., a new category like "Транспорт"):
_includes/ru/transport/0_transport.md starting with # Транспорт (H1)index.md: {% raw %}{% include ru/transport/0_transport.md %}{% endraw %}New article within existing section (e.g., a new article under "Банки, деньги и налоги"):
_includes/ru/money-and-taxes/new_article.md starting with ## Article Title (H2){% raw %}{% include %}{% endraw %} inside the section's 0_money_and_taxes.md fileNote: Index updates for other languages (UA/EN/ES) will be done during translation phase via /content:translate-article.
CRITICAL: You MUST go through EVERY item below and show the user a verification table before presenting the article. Do not skip any items. Format: table with columns "Item | Status (✅/❌/⚠️) | Comment".
Before presenting the article, verify:
Preparation:
Style & Tone:
Structure:
Content:
Formatting:
{% link path %} format{:target="_blank"}bit.ly/spain_life_guide_tgchannelIndex:
index.md)Your response MUST include these sections in order:
Example format:
## Checklist Verification
| Item | Status | Comment |
|------|--------|---------|
| No lecturer phrases | ✅ | None found |
| No "ё" letter | ✅ | Checked |
| Facts verified | ✅ | See fact-check table |
...
## Fact-Check Results
| Claim | Status | Source |
|-------|--------|--------|
| NIE appointment required | ✅ | Extranjería official site |
...
## Proposed Content
[article or edits here]
Do NOT skip the tables - they prove you completed the checklist.
Present ONLY the Russian version and wait for approval before any translation.
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.
Translate approved Russian content to Ukrainian, English, and Spanish. Use when the user asks to translate an article or content to other languages.
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.