English | Русский

Localization Strategy

Approach

TAUSIK uses directory-based localization: docs/en/ (English) + docs/ru/ (Russian).

• Main language for GitHub: English (README.md)
• Each localized file has a language switcher linking to the other version
• All documentation is fully localized (EN + RU)

Structure

README.md          ← English (main)
README.ru.md       ← Russian

docs/
├── en/            ← English docs (~45 files: quickstart, workflow, skills,
│                    hooks, cli, mcp, architecture, adding-new-ide,
│                    vendor-skills, senar-compliance-matrix, i18n-strategy,
│                    brain-*, skill-*, plan-*, cost-telemetry, environment,
│                    permissions, security, etc.)
├── ru/            ← Russian docs (~44 files; mirrors en/ minus a few EN-only
│                    docs like plan-review/plan-stacks/skill-spec/skill-patterns,
│                    plus RU-only agent-contract.md)
├── en/research/   ← Technical research notes (localized — paired with ru/research/)
├── ru/research/
└── README.md      ← Navigation hub (bilingual)

What's localized

Location	RU	EN	Notes
README.md / README.ru.md	✓	✓ (main)	Entry point for GitHub
docs/en/ + docs/ru/	✓	✓	All user docs fully localized

What's NOT localized

• CLAUDE.md — project-internal instructions, follows user's language preference
• CHANGELOG.md — historical record, stays in original language
• Skills (SKILL.md) — agent instructions, English frontmatter + Russian content
• CLI help text — stays in Russian (follows user locale)
• Code comments — English
• docs/research/ — technical notes/research, original language

How to add a new language

1. Create docs/{lang}/ directory
2. Copy files from docs/en/, translate prose content
3. Add language switcher to all files: [English](../en/file.md) | [Язык](../lang/file.md) (example, replace lang with your language code)
4. Keep all code blocks, paths, and technical terms as-is
5. Update docs/README.md navigation hub