// 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.
| name | content-write-article |
| description | 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. |
| argument-hint | [topic or notes] |
| allowed-tools | Read, Glob, Grep, WebSearch |
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 6 reference articles to absorb the author's style:
| Type | Path |
|---|---|
| Personal story | _includes/ru/xolo/my_hacienda_problem.md |
| How-to + advice | _includes/ru/tax-optimization/rent.md |
| Case studies | _includes/ru/gestor/problems.md |
| Practical advice | _includes/ru/bank-account/forced_upselling.md |
| Step-by-step guide | _includes/ru/miscellaneous/digital_certificate_obtain.md |
| Personal story (SLG) | ../spain-life-guide/_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 being autónomo/SL 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:
#)##)###)####)Exception: "Надежные специалисты" 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/it-autonomos-eshttps://bit.ly/it-autonomos-spain-enghttps://bit.ly/autonomo-and-sl-channelWhen 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:
ru/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. The index file only has the {% raw %}{% include %}{% endraw %} tag.
New top-level section (e.g., a new category like "Страхование"):
_includes/ru/insurance/0_insurance.md starting with # Страхование (H1)ru/index.md: {% raw %}{% include ru/insurance/0_insurance.md %}{% endraw %}New article within existing section (e.g., a new article under "Хестор"):
_includes/ru/gestor/new_article.md starting with ## Article Title (H2){% raw %}{% include %}{% endraw %} inside the section's 0_gestor.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/it-autonomos-es for RUIndex:
ru/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 |
|-------|--------|--------|
| IVA rate 21% | ✅ | Agencia Tributaria |
...
## 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 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.
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.
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.