@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 ## Unreleased
 
+### Preset EN translation polish (patch)
+
+- Hardened `check-preset-i18n.sh`: ±3-line keep-marker window (matches style guide), scans `.md`/`.mdc` plus hook/script suffixes; wired as hard gate via `check:preset-i18n` and `check-preset-structure` / CI.
+- Expanded `docs/PRESET-ENGLISH-STYLE.md`: canonical E4 gloss `«original» (gloss)`, stack-class bilingual policy, modality glossary (`must` over `mandatory`).
+- Normalized E4 presentation (go/java RU-first, orchestrator skip bullets, slash→paren glosses); modality wording in post-change rules/skills; shared-core code-quality native-EN polish + embed sync; types-jsdoc next Claude twin aligned to Cursor E5; trailing whitespace trimmed in `navigation-router-stack`.
+
+### English prose for all presets (minor)
+
+- Translated installable preset instruction prose from mixed EN/RU to **English** across all nine stacks (Cursor SoT + Claude twins) and `_shared/core`.
+- Paths, rule stems, agent names, CLI flags, and frontmatter keys are unchanged — prose-only; treat as **minor** when releasing.
+- Exception policy: intentional locale examples keep Cyrillic only with `<!-- i18n-keep: E4|E5|E7 -->` (see `docs/PRESET-ENGLISH-STYLE.md`).
+- Added `scripts/check-preset-i18n.sh` (soft by default; **hard** via `check:preset-i18n` / structure gate); shared-core embed drift remains gated by `check-shared-core-drift.sh`.
+- Consumers: optional `npx @bonesofspring/ai-rules init …` to refresh local wording; no required re-init for path/automation compatibility.
+- Dogfood: re-run `scripts/sync-dogfood-cursor.sh` after next (or `AI_RULES_DOGFOOD_PRESET=…`) preset edits.
+
 ### Agent artifact contracts
 
 - New shared-core schema SoT: `presets/_shared/core/agent-team/agent-artifact-contracts.md` — per-slug `artifact-manifest.json` (schema v1) as context index + completion receipts; markdown remains narrative evidence.
@@ -159,7 +174,7 @@ Cross-cutting preset packaging work (all six presets unless noted **next-only**)
 - **Skills:** `write-adr` ×6; `react-performance` ×2 (next cursor+claude only).
 - **Hooks cookbook:** `hooks/examples/` (secret-guard, format-edited, test-on-save) ×3 stacks ×2 platforms; default `hooks.json` unchanged.
 - **Dogfood:** `sync-dogfood-cursor.sh` copies root `AGENTS.md` from `REPO_AGENTS.md`; seeds `team/conventions.md` if absent.
-- **Always-on Principles** in shared `quality/code-quality-and-refactoring` (+6 adapters): compact § **Принципы** — KISS, DRY + Rule of Three, YAGNI, SOLID, CUPID, composition over inheritance, Law of Demeter hint. No smell/GoF catalogs in always-on.
+- **Always-on Principles** in shared `quality/code-quality-and-refactoring` (+6 adapters): compact § **Principles** — KISS, DRY + Rule of Three, YAGNI, SOLID, CUPID, composition over inheritance, Law of Demeter hint. No smell/GoF catalogs in always-on.
 - **Requestable `quality/design-guidance`** (+6 adapters, Cursor/Claude × next/ios-swift/go): curated Fowler smells (≤12) + GoF (≤8) + skip/avoid; globs `app/src/**/*.{ts,tsx}` / `**/*.swift` / `**/*.go`. Cross-refs in `feature-delivery-workflow` (ubiquitous language) and `code-review-mr` checklist. One-liner wiring in feature-developer / code-review / debugger (+ recommended roles).
 - **Go hexagonal preset (`go`):** Cursor + Claude twins — 32 rules (always-on: `go-app-core`, `architecture-boundaries`, `code-quality-and-refactoring`), 20 agents (`integration-test-*`, no a11y/Playwright/XCUITest), 7 skills (+ `integration-testing`), hooks/commands/team/MCP. Structure scripts `STACKS` include `go`; leakage `GO_FORBIDDEN_*` + pairwise chain forks. Install: `init cursor|claude --preset go`. Lineage markers on go `feature-delivery-workflow` / `reference-features`; go team fixtures / commands READMEs use Go gates (not xcodebuild/XCUITest copy-paste).
 - **Preset structure CI gates:** `scripts/check-preset-{twin-map,token-budget,leakage,structure}.sh` + npm scripts `check:preset-*`; GitHub Actions workflow `.github/workflows/preset-structure.yml` on `packages/ai-rules/**` PRs. Hard FAIL on twin/budget/leakage/**shared-core drift** (`AI_RULES_DRIFT_FAIL=1` in structure orchestrator).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bonesofspring/ai-rules",
-  "version": "0.2.14",
+  "version": "0.2.15",
   "description": "Presets of Cursor and Claude rules/commands for Revy Ross personal use",
   "license": "MIT",
   "author": "Revy Ross",
@@ -29,6 +29,7 @@
     "check:preset-twin-map": "bash scripts/check-preset-twin-map.sh",
     "check:preset-token-budget": "bash scripts/check-preset-token-budget.sh",
     "check:preset-leakage": "bash scripts/check-preset-leakage.sh",
+    "check:preset-i18n": "AI_RULES_I18N_FAIL=1 AI_RULES_I18N_SOFT=0 bash scripts/check-preset-i18n.sh",
     "check:shared-core-drift": "bash scripts/check-shared-core-drift.sh",
     "check:rule-eval": "node scripts/check-rule-eval.mjs"
   },

package/presets/_shared/core/agent-team/agent-team-intake.md

@@ -4,6 +4,6 @@ When the user message looks like a **work request** (implement, add, fix, refact
 
 1. Prefer **`/task <their request>`** or invoke **task-router** first.
 2. Do not jump straight to coding without router + pipeline when scope is non-trivial.
-3. Pure questions («как работает X», «объясни») — prefer agent **`codebase-analyzer`** (explain-as-is); trivial one-liners may be answered inline. Do not open `/task`.
+3. Pure questions (“how does X work”, “explain”) — prefer agent **`codebase-analyzer`** (explain-as-is); trivial one-liners may be answered inline. Do not open `/task`.
 
-Exceptions: user explicitly says «без pipeline», «просто сделай», or continues an active slug.
+Exceptions: user explicitly says “no pipeline”, “just do it”, or continues an active slug.

package/presets/_shared/core/agent-team/agent-team-orchestrator.md

@@ -2,7 +2,7 @@
 
 Parent agent = **manager**. Router plans; specialists execute. Artifacts: `.cursor/team/tasks/<slug>/` (Claude: `.claude/team/tasks/<slug>/`).
 
-Work request без `/task` — см. **agent-team-intake** (когда предлагать router вместо прямого кодинга).
+Work request without `/task` — see **agent-team-intake** (when to suggest the router instead of coding directly).
 
 ## Entry points
 
@@ -193,12 +193,12 @@ If `pipeline.json` is missing (old `/feature-start` tasks), fall back to fixed p
 
 Do **not** run `/task` + router for:
 
-- Pure questions («как работает X», «объясни») — prefer agent **`codebase-analyzer`** for deep traces; inline OK for trivial one-liners.
+- Pure questions (“how does X work”, “explain”) — prefer agent **`codebase-analyzer`** for deep traces; inline OK for trivial one-liners.
 - Typo / one-file fix / trivial config with no architecture risk.
-- User explicitly says «без pipeline», «просто сделай», or continues an active slug.
+- User explicitly says “no pipeline”, “just do it”, or continues an active slug.
 - Single-line `docs-only` with no code impact.
 
-Borderline work requests — см. **agent-team-intake**.
+Borderline work requests — see **agent-team-intake**.
 
 ## Auto-detection (optional)
 

package/presets/_shared/core/architecture/feature-delivery-workflow.md

@@ -1,18 +1,18 @@
-# Доставка фичи (сквозной порядок)
+# Feature delivery (end-to-end order)
 
-Типичная фича с данными и UI. Конкретные каталоги и rule stems — в **Stack notes** адаптера.
+Typical feature with data and UI. Concrete directories and rule stems — in the adapter **Stack notes**.
 
-## Чеклист (абстрактный порядок)
+## Checklist (abstract order)
 
-1. **Домен / типы** — сущности и контракты слоя Domain/types; public API слоя.
-2. **Транспорт / DTO** — DTO и мапперы Domain ↔ transport (не протекают в UI).
-3. **Сервисы / Data** — реализации репозиториев / API-сервисов через public клиенты стека.
-4. **Состояние** — store / ViewModel / use cases; без прямого HTTP и без DTO в UI.
-5. **UI** — тонкие views/components; данные через состояние; design-system.
-6. **Тесты** — unit на mappers / нетривиальную логику; e2e/UI по конвенции стека.
-7. **Завершение** — post-change gate стека (lint/build) + package/toolchain rules.
+1. **Domain / types** — Domain/types-layer entities and contracts; layer public API.
+2. **Transport / DTO** — DTOs and mappers Domain ↔ transport (must not leak into UI).
+3. **Services / Data** — repository / API-service implementations via the stack’s public clients.
+4. **State** — store / ViewModel / use cases; no direct HTTP and no DTOs in UI.
+5. **UI** — thin views/components; data via state; design system.
+6. **Tests** — unit for mappers / non-trivial logic; e2e/UI per stack convention.
+7. **Completion** — stack post-change gate (lint/build) + package/toolchain rules.
 
-## Поток данных (ориентир)
+## Data flow (orientation)
 
 ```mermaid
 flowchart LR
@@ -23,24 +23,24 @@ flowchart LR
   State --> UI[UI]
 ```
 
-## Частичные сценарии
+## Partial scenarios
 
-| Задача | Минимум |
-|--------|---------|
-| Только API / модель | Domain + DTO + mapper + service/repo; unit на mapper |
-| Только состояние | Протоколы/сервисы; без HTTP в UI |
-| Только UI | Существующее состояние; без DTO |
-| Только тесты | Specs по конвенции; не менять production без нужды |
+| Task | Minimum |
+|------|---------|
+| API / model only | Domain + DTO + mapper + service/repo; unit for mapper |
+| State only | Protocols/services; no HTTP in UI |
+| UI only | Existing state; no DTOs |
+| Tests only | Specs per convention; do not change production without need |
 
-## Антипаттерны (общие)
+## Anti-patterns (shared)
 
-- DTO / transport-типы в UI или presentation state.
-- Низкоуровневый HTTP / конкретный клиент из UI в обход сервиса.
-- Deep-import внутренних файлов другого модуля/фичи.
-- Нарушение границ слоёв ради краткости.
-- **Ubiquitous language:** имена и границы Domain/типов отражают предметную область фичи — не смешивать транспорт/фреймворк-термины в домен без нужды; presentation не диктует словарь модели.
-- При оценке структуры, smells или выбора паттерна — подгружать requestable **`design-guidance`** (не always-on); не копировать каталог в чеклист фичи.
+- DTO / transport types in UI or presentation state.
+- Low-level HTTP / concrete client from UI bypassing the service.
+- Deep-import of another module/feature’s internal files.
+- Breaking layer boundaries for brevity.
+- **Ubiquitous language:** Domain/type names and boundaries reflect the feature’s subject domain — do not mix transport/framework terms into the domain without need; presentation must not dictate the model vocabulary.
+- When assessing structure, smells, or pattern choice — load requestable **`design-guidance`** (not always-on); do not copy the catalog into the feature checklist.
 
-## Матрица зона → правила
+## Zone → rules matrix
 
-Заполняется в stack adapter: конкретные globs/пути и имена `.mdc` / topic `.md`.
+Filled in the stack adapter: concrete globs/paths and `.mdc` / topic `.md` names.

package/presets/_shared/core/architecture/reference-features.template.md

@@ -1,43 +1,43 @@
-# Эталонные фичи (reference features)
+# Reference features
 
-Перед реализацией найди фичу того же типа и **повтори её структуру**, не изобретая новую организацию файлов.
+Before implementing, find a feature of the same type and **mirror its structure**; do not invent a new file organization.
 
-## Таблица эталонов
+## Reference table
 
-Замени placeholders на **реальные** пути после `ai-rules init` / договорённости команды:
+Replace placeholders with **real** paths after `ai-rules init` / team agreement:
 
-| Слой | Эталон | Что копировать |
-|------|--------|----------------|
-| UI / Presentation | **TBD** | компоненты, styles/data helpers, barrel |
+| Layer | Reference | What to copy |
+|-------|-----------|--------------|
+| UI / Presentation | **TBD** | components, styles/data helpers, barrel |
 | State / ViewModel | **TBD** | slice/VM, selectors, types |
 | API / Data | **TBD** | service/repo, mappers, barrel |
 | Domain / Types | **TBD** | domain types, public export |
 | Unit tests | **TBD** | `*.spec` / XCTest naming |
 | E2E / UI tests | **TBD** | cases/plans, page objects / accessibility IDs |
 
-## Как использовать
+## How to use
 
-1. Определи затронутые слои из `decomposition.md` или задачи.
-2. Открой эталон из таблицы (после заполнения путей).
-3. Зеркаль именование, порядок файлов, паттерны импортов и тестов.
-4. Если эталона нет — выбери **самую близкую** существующую фичу того же слоя и зафиксируй выбор в handoff.
+1. Identify affected layers from `decomposition.md` or the task.
+2. Open the reference from the table (after paths are filled).
+3. Mirror naming, file order, import patterns, and tests.
+4. If there is no reference — pick the **closest** existing feature of the same layer and record the choice in the handoff.
 
 ## Living conventions
 
-После init команда ведёт **локальные** gotchas, patterns и decisions в consumer-owned store (не в shared core и не только в корневом `AGENTS.md`):
+After init the team maintains **local** gotchas, patterns, and decisions in a consumer-owned store (not in shared core and not only in root `AGENTS.md`):
 
-| Раздел | Что фиксировать |
-|--------|-----------------|
-| Gotchas | Повторяющиеся ловушки, хрупкие места, «не делай X в этом репо» |
-| Patterns | Локальные паттерны сверх эталонной таблицы |
-| Decisions | Краткие ADR-ссылки / продуктовые решения, влияющие на код |
+| Section | What to record |
+|---------|----------------|
+| Gotchas | Recurring traps, fragile spots, “do not do X in this repo” |
+| Patterns | Local patterns beyond the reference table |
+| Decisions | Short ADR links / product decisions that affect code |
 
-Указатель пути к файлу и stack-таблицы — в адаптере пресета (`team/conventions.md`). Файл **не** always-on.
+Path pointer and stack tables — in the preset adapter (`team/conventions.md`). The file is **not** always-on.
 
-## Связанные правила
+## Related rules
 
-- `code-quality-and-refactoring` — повторять паттерны, не deep-import.
-- `feature-delivery-workflow` — порядок слоёв.
-- skill `feature-delivery` — end-to-end сценарий.
+- `code-quality-and-refactoring` — repeat patterns, no deep-import.
+- `feature-delivery-workflow` — layer order.
+- skill `feature-delivery` — end-to-end scenario.
 
 > Concrete path tables, globs, and dogfood checklists live in the stack adapter **Stack notes**.

package/presets/_shared/core/meta/preset-layering.md

@@ -1,25 +1,25 @@
 # Preset layering
 
-Правила для **авторов пресетов** (`packages/ai-rules/presets/**`). Не always-on в consumer apps.
+Rules for **preset authors** (`packages/ai-rules/presets/**`). Not always-on in consumer apps.
 
-## Слои
+## Layers
 
-| Слой | Где | Что класть |
-|------|-----|------------|
-| **Core** | `presets/_shared/core/**` | Stack-agnostic prose + checklists; без frontmatter; без путей `app/**`, `Features/**`, Playwright, xcodebuild |
-| **Stack** | `presets/{cursor\|claude}/<stack>/` | Domain/tooling, always-on trio стека, stack examples в **Stack notes** |
+| Layer | Where | What to put |
+|-------|-------|-------------|
+| **Core** | `presets/_shared/core/**` | Stack-agnostic prose + checklists; no frontmatter; no paths `app/**`, `Features/**`, Playwright, xcodebuild |
+| **Stack** | `presets/{cursor\|claude}/<stack>/` | Domain/tooling, stack always-on trio, stack examples in **Stack notes** |
 | **Platform** | Cursor `.mdc` / Claude `.md` | Frontmatter (`alwaysApply`/`globs` vs `paths:`), platform-only (`BUGBOT.md`, `CLAUDE.md`) |
 
-## Куда класть новое правило
+## Where to put a new rule
 
-1. Общие принципы для всех стеков → **core** + адаптеры с `<!-- shared-core: … -->`.
-2. Только один из installable стеков (`next` / `nuxt` / `svelte` / `ios-swift` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (не в `_shared`).
-3. Только Cursor или только Claude packaging → platform artifact / frontmatter, не дублировать семантику.
+1. Shared principles for all stacks → **core** + adapters with `<!-- shared-core: … -->`.
+2. Only one of the installable stacks (`next` / `nuxt` / `svelte` / `ios-swift` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (not in `_shared`).
+3. Only Cursor or only Claude packaging → platform artifact / frontmatter; do not duplicate semantics.
 
 ## SoT
 
 - Packages path — SoT; root `.cursor/` — dogfood sync.
 - Per stack: **Cursor** `presets/cursor/<stack>/` → Claude twin same PR.
-- `_shared` **не** `--preset` и не копируется CLI `init`.
+- `_shared` is **not** a `--preset` and is not copied by CLI `init`.
 
-См. также: `preset-twin-sync`, `preset-token-budget`, `preset-pr-checklist`, `preset-no-cross-stack-leakage`.
+See also: `preset-twin-sync`, `preset-token-budget`, `preset-pr-checklist`, `preset-no-cross-stack-leakage`.

package/presets/_shared/core/meta/preset-no-cross-stack-leakage.md

@@ -1,6 +1,6 @@
 # Preset no cross-stack leakage
 
-Запрет протекания stack-specific имён, путей и handoff stems между пресетами.
+Ban leakage of stack-specific names, paths, and handoff stems across presets.
 
 ## Principles
 

package/presets/_shared/core/meta/preset-pr-checklist.md

@@ -1,15 +1,15 @@
 # Preset PR checklist
 
-Чеклист для PR, затрагивающих `packages/ai-rules/presets/**` (и dogfood `.cursor/` sync).
+Checklist for PRs that touch `packages/ai-rules/presets/**` (and dogfood `.cursor/` sync).
 
 ## Before merge
 
-- [ ] **SoT:** правки в `packages/…` (не только root `.cursor/`)
-- [ ] **Core:** если менялся `_shared/core/**` — обновлены все `<!-- shared-core: … -->` consumers (или documented intentional fork)
-- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel — см. `preset-twin-sync`)
-- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table актуален
+- [ ] **SoT:** edits in `packages/…` (not only root `.cursor/`)
+- [ ] **Core:** if `_shared/core/**` changed — all `<!-- shared-core: … -->` consumers updated (or documented intentional fork)
+- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel — see `preset-twin-sync`)
+- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table is current
 - [ ] **Token budget:** alwaysApply / session-start ≤ 3; meta rules not always-on
-- [ ] **Leakage:** нет чужих stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
+- [ ] **Leakage:** no foreign stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
 - [ ] **Twin depth:** domain ≥15 lines; thin aliases documented
 - [ ] **README:** stack `rules/README.md` core→stack mapping / catalog updated if stems added
 - [ ] **CHANGELOG / package README:** note when public preset paths or install surface change

package/presets/_shared/core/meta/preset-token-budget.md

@@ -1,17 +1,17 @@
 # Preset token budget
 
-Инварианты загрузки правил в **установленном** пресете (consumer app).
+Invariants for rule loading in an **installed** preset (consumer app).
 
 ## Hard caps
 
 | Platform | Always-on | Cap |
 |----------|-----------|-----|
 | Cursor | `alwaysApply: true` | **≤ 3** |
-| Claude | rules **without** `paths:` | **ровно 3** |
+| Claude | rules **without** `paths:` | **exactly 3** |
 
 **Claude Option A (README exclusion):** when counting Claude rules without `paths:` / session-start, **exclude `**/README.md`** (topic indexes are not session-start rules). The intended session-start trio remains **exactly 3**; body budget sums **only those 3** rules.
 
-Session-start body budget (где задокументировано): ≤140 строк суммарно (stretch ≤120).
+Session-start body budget (where documented): ≤140 lines total (stretch ≤120).
 
 ## Meta / author rules
 

package/presets/_shared/core/quality/code-quality-and-refactoring.md

@@ -1,38 +1,38 @@
-# Поддержка существующего стиля
+# Match existing style
 
-- Следовать существующим паттернам (имена, структура, типизация / DI / error handling); минимизировать стилистический шум (лишний format/rename).
-- Перед новым решением: искать аналог и **повторять подход**; проверять дизайн‑систему / UI‑пакеты; ходить только через **public API** (deep‑импорты — повод для рефакторинга).
+- Follow existing patterns (names, structure, typing / DI / error handling); avoid drive-by formatting or renames.
+- Before a new solution: find an analog and **repeat the approach**; check the design system / UI packages; go only through the **public API** (deep imports are a reason to refactor).
 
-# Принципы
+# Principles
 
-- **KISS:** самое простое изменение в паттернах репозитория.
-- **DRY + Rule of Three:** общее — только после 3-го повторения (ошибочная абстракция дороже дублирования).
-- **YAGNI:** без API, флагов, слоёв «на будущее» без текущего требования.
-- **SOLID:** S — один повод менять; O — композиция/новые реализации; L — контракт подтипа; I — узкие порты; D — абстракции (порты), детали в адаптерах стека.
-- **CUPID:** Composable; Unix philosophy (одна ответственность); Predictable; Idiomatic (репо); Domain-based.
-- **Composition over inheritance;** Law of Demeter — без цепочек `a.b.c.d`; через public API / facade.
+- **KISS:** the simplest change in the repository’s patterns.
+- **DRY + Rule of Three:** share only after the 3rd repetition (wrong abstraction costs more than duplication).
+- **YAGNI:** no APIs, flags, or “for later” layers without a current requirement.
+- **SOLID:** S — one reason to change; O — composition/new implementations; L — subtype contract; I — narrow ports; D — abstractions (ports), details in stack adapters.
+- **CUPID:** Composable; Unix philosophy (one responsibility); Predictable; Idiomatic (repo); Domain-based.
+- **Composition over inheritance;** Law of Demeter — no `a.b.c.d` chains; via public API / facade.
 
-# Рефакторинг при изменениях
+# Refactoring during changes
 
-- Лёгкий refactor OK, если меньше дублирования, выше читаемость, без ломки публичных контрактов.
-- Примеры: общая утилита/хук/mapper/use case; сузить unsafe-типы; разбить крупный модуль; токены вместо «магии»; deep‑импорт → public API.
-- Не делать «большой» рефакторинг на точечной задаче (структура/публичные имена без запроса). Крупное — минимальными шагами; код остаётся собираемым.
+- Light refactor is OK if it reduces duplication, improves readability, and does not break public contracts.
+- Examples: shared utility/hook/mapper/use case; narrow unsafe types; split a large module; tokens instead of “magic”; deep import → public API.
+- Do not do a “big” refactor on a point task (structure/public names without a request). Break large work into minimal steps; keep the repo buildable after each step.
 
-# Требование к агенту
+# Agent requirement
 
-- **Boy scout:** оставлять модуль немного лучше; не жертвовать архитектурой и слоями ради краткости.
+- **Boy scout:** leave the module a bit better; do not sacrifice architecture and layers for brevity.
 
 ## Agent discipline (anti-sycophancy)
 
 Essentials below. Full procedural set (~17 rules) → load **`anti-sycophancy-discipline`**.
 
 - Unverifiable third-party API → mark `// VERIFY: lib.symbol @ version` (or stack equivalent); never invent signatures.
-- Before «is this correct?» — ≥3 failure modes (empty, boundary, concurrency/state) or name what you could not check.
+- Before "is this correct?" — ≥3 failure modes (empty, boundary, concurrency/state) or name what you could not check.
 - Refactor without tests → propose characterization test; if declined, label `UNTESTED`.
-- Comments = WHY only when non-obvious; ban self-referential «added for issue Y».
+- Comments = WHY only when non-obvious; ban self-referential "added for issue Y".
 - Urgency/authority: name the trade-off once, then comply — no apology loops.
 - Match verification to risk; report by what was **verified**, not attempted.
 
 Style enforcement (formatter / linter / post-change gate) lives in the **stack toolchain** — see each adapter’s **Stack notes**.
 
-> Stack-specific lint gates, примеры и toolchain — в секции **Stack notes** адаптера пресета.
+> Stack-specific lint gates, examples, and toolchain — in the preset adapter **Stack notes** section.

package/presets/_shared/core/quality/design-guidance.md

@@ -1,97 +1,97 @@
 # Design guidance (smells & patterns)
 
-Словарь **code smells** (Fowler) и **design patterns** (GoF) для агентов при implement / review / debug.
+Glossary of **code smells** (Fowler) and **design patterns** (GoF) for agents during implement / review / debug.
 
-Применять только в scope задачи или MR. Лёгкий refactor — да; «большой» rewrite без явного запроса — нет.
+Apply only within the task or MR scope. Light refactor — yes; a “big” rewrite without an explicit request — no.
 
-Называть паттерн **только если** репозиторий уже так делает или это минимальный match. Иначе — extract/split/move без ярлыка GoF.
+Name a pattern **only if** the repository already does it that way or the match is minimal. Otherwise — extract/split/move without a GoF label.
 
-Не заменяет always-on Principles в `code-quality-and-refactoring` (KISS, DRY + Rule of Three, YAGNI, SOLID, CUPID, composition, Demeter).
+Does not replace always-on Principles in `code-quality-and-refactoring` (KISS, DRY + Rule of Three, YAGNI, SOLID, CUPID, composition, Demeter).
 
 ## When to load
 
-- **Feature delivery / implement** — оценка структуры модулей, границ и дублирования.
-- **Code review** — smells и pattern fit **в диффе MR**, не по всему репо.
-- **Debug** — root-cause похож на wrong abstraction, Feature Envy, Message Chains, Shotgun Surgery.
-- **Light refactor only** — улучшения в рамках boy-scout / MR scope; не расширять задачу ради каталога.
+- **Feature delivery / implement** — assess module structure, boundaries, and duplication.
+- **Code review** — smells and pattern fit **in the MR diff**, not across the whole repo.
+- **Debug** — root cause looks like wrong abstraction, Feature Envy, Message Chains, Shotgun Surgery.
+- **Light refactor only** — improvements within boy-scout / MR scope; do not expand the task for the catalog.
 
-Агенты и skills подгружают stem по one-liner wiring — не копировать этот каталог в промпт агента.
+Agents and skills load this stem via one-liner wiring — do not copy this catalog into the agent prompt.
 
 ## How to use (agent rules of thumb)
 
-1. Сначала сверить с Principles (always-on): проще ли решение, нет ли ранней абстракции, соблюдён ли public API.
-2. Затем отметить smells **в изменённых файлах** задачи/MR; предложить fix только если он укладывается в light refactor.
-3. Паттерн GoF — опциональный ярлык после того, как структура уже ясна; не начинать дизайн с выбора паттерна.
-4. Если smell и паттерн конфликтуют с границами слоёв стека — побеждают stack boundaries и existing repo patterns.
-5. Не требовать переименования «под GoF», если поведение уже корректно и читаемо.
+1. First check against Principles (always-on): is the solution simpler, is there no premature abstraction, is the public API respected.
+2. Then mark smells **in the changed files** of the task/MR; propose a fix only if it fits a light refactor.
+3. A GoF pattern is an optional label after the structure is already clear; do not start design by picking a pattern.
+4. If a smell or pattern conflicts with stack layer boundaries — stack boundaries and existing repo patterns win.
+5. Do not require renaming “for GoF” if behavior is already correct and readable.
 
 ## Code smells (Fowler, curated ≤12)
 
-Таблица: smell → detect hint → fix hint (одна линия каждый). Без механических меню рефакторинга.
+Table: smell → detect hint → fix hint (one line each). No mechanical refactoring menus.
 
 | # | Smell | Detect | Fix hint |
 |---|-------|--------|----------|
-| 1 | Duplicate Code | одинаковая логика в ≥2 местах | dedupe после Rule of Three |
-| 2 | Long Method / Long Module | единица делает слишком много | extract в рамках scope; без big rewrite |
-| 3 | Feature Envy | метод чаще трогает чужие данные, чем свои | сдвинуть логику к данным / public API |
-| 4 | Data Clumps | одни и те же группы аргументов кочуют вместе | сгруппировать в type / value object |
-| 5 | Primitive Obsession | сырые string/int вместо доменных понятий | typed ids / value objects при нужде домена |
-| 6 | Speculative Generality | неиспользуемые хуки, флаги, абстракции «на будущее» | удалить (YAGNI) |
-| 7 | Message Chains | цепочки `a.b.c.d` | Demeter; facade / public API модуля |
-| 8 | Middle Man | класс почти только прокидывает вызовы | убрать pass-through **или** оставить как boundary |
-| 9 | Divergent Change | один модуль меняется по разным причинам | split по поводам изменения |
-| 10 | Shotgun Surgery | одно смысловое изменение разъезжается по многим файлам | consolidate ответственность |
-| 11 | Inappropriate Intimacy | доступ к чужим internals / private деталям | только public API / ports / facades |
-| 12 | Refused Bequest / Parallel Inheritance | подтип игнорирует базу; зеркальные иерархии классов | composition; не плодить параллельные деревья |
-
-**Skip Fowler (не в core):** Lazy Class, Incomplete Library Class, Comments-as-smell dogma, полный каталог 70+, пошаговые recipe-меню.
-
-Приоритет при конфликте smells: Inappropriate Intimacy и Message Chains (границы модулей) > Duplicate Code (после Rule of Three) > Long Method внутри уже правильного модуля.
+| 1 | Duplicate Code | same logic in ≥2 places | dedupe after Rule of Three |
+| 2 | Long Method / Long Module | unit does too much | extract within scope; no big rewrite |
+| 3 | Feature Envy | method touches foreign data more than its own | move logic toward the data / public API |
+| 4 | Data Clumps | the same argument groups travel together | group into a type / value object |
+| 5 | Primitive Obsession | raw string/int instead of domain concepts | typed ids / value objects when the domain needs them |
+| 6 | Speculative Generality | unused hooks, flags, “for later” abstractions | remove (YAGNI) |
+| 7 | Message Chains | `a.b.c.d` chains | Demeter; facade / module public API |
+| 8 | Middle Man | class almost only forwards calls | remove pass-through **or** keep as a boundary |
+| 9 | Divergent Change | one module changes for different reasons | split by reasons to change |
+| 10 | Shotgun Surgery | one semantic change spreads across many files | consolidate responsibility |
+| 11 | Inappropriate Intimacy | access to foreign internals / private details | public API / ports / facades only |
+| 12 | Refused Bequest / Parallel Inheritance | subtype ignores base; mirrored class hierarchies | composition; do not grow parallel trees |
+
+**Skip Fowler (not in core):** Lazy Class, Incomplete Library Class, Comments-as-smell dogma, full 70+ catalog, step-by-step recipe menus.
+
+Smell conflict priority: Inappropriate Intimacy and Message Chains (module boundaries) > Duplicate Code (after Rule of Three) > Long Method inside an already correct module.
 
 ## Design patterns (GoF, curated ≤8)
 
-Suggest only when repo already uses the shape or the match is minimal. Prefer extract-function over naming Strategy ради ярлыка.
+Suggest only when repo already uses the shape or the match is minimal. Prefer extract-function over naming Strategy for the label alone.
 
-Паттерны ниже — **разрешённый минимум** для агентов; остальной GoF по умолчанию в Skip.
+Patterns below are the **allowed minimum** for agents; the rest of GoF is Skip by default.
 
 | Pattern | When to suggest | Anti-trigger |
 |---------|-----------------|--------------|
-| Strategy | взаимозаменяемые алгоритмы уже (или явно скоро) выбираются политикой | один алгоритм без ветвления политики |
-| Adapter | обернуть внешний / чужой API под локальный port | лишняя обёртка вокруг своего же API |
-| Facade | упростить multi-step subsystem за public API | facade превращается в god-object |
-| Factory Method | полиморфное создание уже принято в стиле репо | factory на каждый тривиальный `new` |
-| Decorator | аддитивное поведение без взрыва subclass-иерархий | decorator «для слоёв» без реальной нужды |
-| Observer | events / subscriptions уже есть в архитектуре | самодельный pub/sub без прецедента в репо |
-| Template Method | общий algorithm skeleton + вариативные hooks | наследование ради пары отличающихся строк |
-| Composite | дерево однородных узлов (UI/domain), как уже в репо | Composite на плоский список без иерархии |
+| Strategy | interchangeable algorithms already (or clearly soon) chosen by policy | one algorithm with no policy branching |
+| Adapter | wrap external / foreign API under a local port | extra wrapper around your own API |
+| Facade | simplify a multi-step subsystem behind a public API | facade turns into a god-object |
+| Factory Method | polymorphic creation already accepted in repo style | factory for every trivial `new` |
+| Decorator | additive behavior without exploding subclass hierarchies | decorator “for layers” with no real need |
+| Observer | events / subscriptions already exist in the architecture | homemade pub/sub with no repo precedent |
+| Template Method | shared algorithm skeleton + variable hooks | inheritance for a couple of differing lines |
+| Composite | tree of homogeneous nodes (UI/domain), as already in the repo | Composite on a flat list with no hierarchy |
 
-Если сомневаешься между двумя паттернами — выбери более простой extract/compose без имени; ярлык можно добавить на review, если репо уже так говорит.
+If unsure between two patterns — choose the simpler extract/compose without a name; the label may be added on review if the repo already speaks that way.
 
 ## Skip / avoid by default
 
 | Catalog | Skip |
 |---------|------|
 | GoF | Singleton, Abstract Factory, Flyweight, Memento, Interpreter, Visitor, Bridge, Prototype |
-| GoF (conditional) | Command, Chain of Responsibility, State — упоминать **только если** репо уже использует |
-| Fowler | всё сверх 12 smells выше |
-| DDD | Aggregates, bounded-context maps, event sourcing, CQRS — **не в core** |
-| DDD (pointer) | ubiquitous language anti-pattern — расширять в `feature-delivery-workflow`, не здесь |
-| GRASP | список Larman как отдельные правила — skip (перекрывается SOLID/CUPID) |
-| Clean Code dogma | жёсткие caps на строки функции / «ровно один assert» — skip |
+| GoF (conditional) | Command, Chain of Responsibility, State — mention **only if** the repo already uses them |
+| Fowler | everything beyond the 12 smells above |
+| DDD | Aggregates, bounded-context maps, event sourcing, CQRS — **not in core** |
+| DDD (pointer) | ubiquitous language anti-pattern — expand in `feature-delivery-workflow`, not here |
+| GRASP | Larman list as separate rules — skip (covered by SOLID/CUPID) |
+| Clean Code dogma | hard caps on function lines / “exactly one assert” — skip |
 
-Не вводить второй stem (`refactoring-smells` / `design-patterns-for-agents`) — один каталог: `design-guidance`.
+Do not introduce a second stem (`refactoring-smells` / `design-patterns-for-agents`) — one catalog: `design-guidance`.
 
 ## Out of scope for this stem
 
-- Полный GoF (23) и полный Fowler catalog.
-- Stack-specific рецепты (пути модулей, lint-команды) — только в **Stack notes** адаптера.
-- Security, a11y, perf — отдельные review-правила; здесь только структурные smells/patterns.
-- Четвёртое always-on правило — запрещено; этот stem только requestable / agent-load.
+- Full GoF (23) and full Fowler catalog.
+- Stack-specific recipes (module paths, lint commands) — only in the adapter **Stack notes**.
+- Security, a11y, perf — separate review rules; here only structural smells/patterns.
+- A fourth always-on rule — forbidden; this stem is requestable / agent-load only.
 
 ## Cross-refs
 
 - Always-on Principles: `code-quality-and-refactoring`.
-- DIP / ports vs adapters: stack `architecture-boundaries` (детали стека — в Stack notes адаптеров).
+- DIP / ports vs adapters: stack `architecture-boundaries` (stack details — in adapter Stack notes).
 - Ubiquitous language: `feature-delivery-workflow` (lineage).
 - MR checklist (smells in scope; pattern name only if repo uses it): `code-review-mr`.
 - Token / twin policy for authors: `preset-token-budget`, `preset-twin-sync` (meta, not consumer always-on).

package/presets/_shared/core/review/code-review-mr.md

@@ -15,9 +15,9 @@ On-demand rule for review flows. **Procedure and output format:** skill `code-re
 - UI conventions of the stack
 - Unit and e2e/UI test conventions
 - Post-change lint/build gate before final report
-- Design smells **in MR diff scope** — load `design-guidance`; не разворачивать полный каталог Fowler вне диффа
-- Pattern name (GoF) — только если репозиторий уже использует эту форму или match минимален
-- Principles (KISS / DRY+Ro3 / YAGNI / SOLID / CUPID) — через always-on `code-quality-and-refactoring`, не дублировать эссе в review
+- Design smells **in MR diff scope** — load `design-guidance`; do not expand the full Fowler catalog outside the diff
+- Pattern name (GoF) — only if the repository already uses that shape or the match is minimal
+- Principles (KISS / DRY+Ro3 / YAGNI / SOLID / CUPID) — via always-on `code-quality-and-refactoring`, do not duplicate the essay in review
 
 Concrete rule stems — in **Stack notes**.
 
@@ -26,7 +26,7 @@ Concrete rule stems — in **Stack notes**.
 - Focus on MR diff, not the whole repo.
 - Use local `git diff` — do not invent hosting metadata.
 - Boy scout rule: suggest fixes feasible within the MR scope.
-- No «большие рефакторинги» without an explicit request (`code-quality-and-refactoring`).
+- No “big refactors” without an explicit request (`code-quality-and-refactoring`).
 
 ## Output contract