@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/presets/cursor/java/rules/code-quality-and-refactoring.mdc

@@ -5,47 +5,48 @@ alwaysApply: true
 
 <!-- shared-core: quality/code-quality-and-refactoring.md -->
 
-# Поддержка существующего стиля
+# 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.
+
 ## Stack notes
 
-- **No UI layer in this preset** — ignore shared-core bullets about дизайн‑система / UI‑пакеты / CSS‑токены; apply public-API and boy-scout rules to Java packages/ports instead.
+- **No UI layer in this preset** — ignore shared-core bullets about design system / UI packages / CSS tokens; apply public-API and boy-scout rules to Java packages/ports instead.
 - Public API between packages: exported types in module API or explicit ports — avoid deep imports of another feature's internals.
 - Prefer checked/unchecked exceptions with clear translation at adapter edges; do not leak persistence exceptions upward.
 - Interfaces belong at **ports** (consumer side), not on every class; prefer composition over inheritance.

package/presets/cursor/java/rules/code-review-mr.mdc

@@ -22,9 +22,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**.
 
@@ -33,7 +33,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
 

package/presets/cursor/java/rules/design-guidance.mdc

@@ -9,98 +9,98 @@ alwaysApply: false
 
 # 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/cursor/java/rules/java-app-core.mdc

@@ -4,19 +4,19 @@ alwaysApply: true
 ---
 
 
-# Стек и окружение
+# Stack and environment
 
-Версии JDK, Spring Boot и зависимостей — **из `pom.xml` / `build.gradle(.kts)` целевого репозитория**. Рамка preset:
+JDK, Spring Boot, and dependency versions — **from the target repository’s `pom.xml` / `build.gradle(.kts)`**. Preset frame:
 
-- **Язык / платформа:** Java (Maven или Gradle; wrappers `./mvnw` / `./gradlew` предпочтительны).
-- **Default:** Spring Boot **hexagonal** (ports & adapters); domain не знает Spring/JPA/HTTP.
-- **Variants (documented):** plain Java, Quarkus, Micronaut, Jakarta EE — те же границы пакетов.
+- **Language / platform:** Java (Maven or Gradle; wrappers `./mvnw` / `./gradlew` preferred).
+- **Default:** Spring Boot **hexagonal** (ports & adapters); domain must not know Spring/JPA/HTTP.
+- **Variants (documented):** plain Java, Quarkus, Micronaut, Jakarta EE — same package boundaries.
 - **Layout default:** layer-first single-module; multi-module — documented variant.
-- **Тесты:** JUnit 5 + AssertJ; integration — Testcontainers; REST Assured — optional smoke.
-- **HTTP:** Spring MVC / Jakarta at the edge (примеры, не жёсткий мандат framework).
+- **Tests:** JUnit 5 + AssertJ; integration — Testcontainers; REST Assured — optional smoke.
+- **HTTP:** Spring MVC / Jakarta at the edge (examples, not a hard framework mandate).
 - **Static analysis:** discover from repo/CI — do not mandate Checkstyle/SpotBugs/Error Prone.
 
-# Структура (default: layer-first)
+# Structure (default: layer-first)
 
 ```text
 src/main/java/<base>/
@@ -30,4 +30,4 @@ src/test/java/<base>/
 
 **Feature-first variant:** `<feature>/{domain,application,adapters}` — same dependency direction.
 
-Границы — **`architecture-boundaries.mdc`**. Tooling — requestable **`java-tooling.mdc`**. После правок Java — **`post-change-test.mdc`**.
+Boundaries — **`architecture-boundaries.mdc`**. Tooling — requestable **`java-tooling.mdc`**. After Java edits — **`post-change-test.mdc`**.

package/presets/cursor/java/rules/post-change-test.mdc

@@ -8,7 +8,7 @@ globs:
 alwaysApply: false
 ---
 
-# Post-change test (requestable, mandatory after Java edits)
+# Post-change test (requestable; must after Java edits)
 
 After changing Java sources or build descriptors:
 

package/presets/cursor/java/rules/preset-layering.mdc

@@ -9,29 +9,28 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-layering.md -->
 
-
 # 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/cursor/java/rules/preset-no-cross-stack-leakage.mdc

@@ -9,10 +9,9 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-no-cross-stack-leakage.md -->
 
-
 # Preset no cross-stack leakage
 
-Запрет протекания stack-specific имён, путей и handoff stems между пресетами.
+Ban leakage of stack-specific names, paths, and handoff stems across presets.
 
 ## Principles
 

package/presets/cursor/java/rules/preset-pr-checklist.mdc

@@ -9,19 +9,18 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-pr-checklist.md -->
 
-
 # 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/cursor/java/rules/preset-token-budget.mdc

@@ -9,21 +9,20 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-token-budget.md -->
 
-
 # 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/cursor/java/rules/preset-twin-sync.mdc

@@ -9,7 +9,6 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-twin-sync.md -->
 
-
 # Preset twin sync
 
 Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.

package/presets/cursor/java/rules/technical-retro.mdc

@@ -5,12 +5,12 @@ alwaysApply: false
 
 <!-- shared-core: review/technical-retro.md -->
 
-# Техническое ретро — rule alias
+# Technical retro — rule alias
 
-Полный сценарий (включая блок **«Работа агентов»** для slug из team tasks) — в slash-команде:
+Full scenario (including the **“Agent work”** block for a slug from team tasks) lives in the slash command:
 
 **`commands/technical-retro.md`** → `/technical-retro`
 
 When a task has `metrics.json`, use the local aggregation script and state the cohort, sample size, incomplete artifacts, attribution confidence, active attempt duration, and human-gate wait separately. Do not score malformed artifacts or gate wait as agent work.
 
-Используй rule только если command недоступен. Не дублируй содержимое command в ответе — следуй command-файлу и skill `technical-retro`.
+Use this rule only if the command is unavailable. Do not duplicate the command contents in the response — follow the command file and skill `technical-retro`.

package/presets/cursor/java/team/README.md

@@ -1,6 +1,6 @@
 # Agent team artifacts (preset java)
 
-Каталог артефактов пайплайна «команда агентов» для Java backend (hexagonal / ports & adapters).
+Artifact directory for the agent-team pipeline for Java backends (hexagonal / ports & adapters).
 
 ## Layout
 

package/presets/cursor/mcp-ts/AGENTS.md

@@ -2,12 +2,12 @@
 
 **Repo-root agents:** see [`AGENTS.md`](../../AGENTS.md) at the project root (cross-tool setup, commands, security, living conventions pointers).
 
-| Задача | Куда смотреть |
-|--------|----------------|
-| Новая work-задача | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
-| Фича end-to-end | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
-| Стек и границы | `mcp-ts-app-core.mdc`, `mcp-server-boundaries.mdc` |
-| После правок TS | `post-change-test.mdc` (+ `mcp-ts-tooling.mdc`) |
+| Task | Where to look |
+|------|----------------|
+| New work request | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
+| End-to-end feature | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
+| Stack and boundaries | `mcp-ts-app-core.mdc`, `mcp-server-boundaries.mdc` |
+| After TS edits | `post-change-test.mdc` (+ `mcp-ts-tooling.mdc`) |
 | Tool/schema design | `mcp-tool-design.mdc`, `mcp-contract-testing.mdc` |
 | Code review | skill `code-review` + `code-review-mr.mdc` |
 | Security | `security-mcp.mdc` + agent `security-reviewer` |

package/presets/cursor/mcp-ts/MCP.md

@@ -1,11 +1,11 @@
 # MCP (preset `mcp-ts`, Cursor)
 
-Копируется в `.cursor/mcp.json` при `ai-rules init cursor --preset mcp-ts`.
+Copied to `.cursor/mcp.json` on `ai-rules init cursor --preset mcp-ts`.
 
 ## Servers (active in shipped config)
 
-| Name | Package | Зачем |
-|------|---------|--------|
+| Name | Package | Purpose |
+|------|---------|---------|
 | `context7` | `@upstash/context7-mcp@3.2.5` (pinned in `mcp.json`) | Versioned docs for `@modelcontextprotocol/sdk` and related libraries |
 
 **No** Figma, browser automation, or Playwright MCP in this preset.
@@ -32,6 +32,6 @@ Shipped `mcp.json` pins `@upstash/context7-mcp@<version>` so `init` does not pul
 
 Adjust `command`/`args` to the project's `bin` / `npx` entry after packaging. Prefer stdio for local Cursor/Claude use.
 
-Секреты в файл не кладём. Опционально: `CONTEXT7_API_KEY` в окружении.
+Do not put secrets in the file. Optional: `CONTEXT7_API_KEY` in the environment.
 
-После init: Settings → MCP → включить серверы. `init` перезаписывает одноимённый MCP config.
+After init: Settings → MCP → enable servers. `init` overwrites the same-named MCP config.

package/presets/cursor/mcp-ts/agents/task-router.md

@@ -17,12 +17,12 @@ You are a task router for a **TypeScript MCP server** agent team. You **do not**
 
 | intent | Signals | Default steps |
 |--------|---------|---------------|
-| `feature` | «добавь tool», «новая», «реализуй», schema/handler | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `bugfix` | «баг», «fix», «не работает», «падает» | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `review-only` | «ревью», «review MR», «проверь diff» | `security-reviewer` for threat/capability/auth/secrets diffs; **plus** parent applies skill `code-review` (write `review.md`) — no `code-reviewer` agent in Phase 1. Pure schema/style-only diffs: skip security step, parent skill only (document in `skipped`) |
-| `spike` | «исследуй», «spike», proof of concept | task-analyst → solution-architect |
-| `refactor` | «рефакторинг», «без изменения поведения» | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
-| `retro` | «ретро», «postmortem» | (orchestrator → `/technical-retro`) |
+| `feature` | "add tool", "new", "implement", schema/handler | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `bugfix` | "bug", "fix", "doesn't work", "crashes" | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `review-only` | "review", "review MR", "check diff" | `security-reviewer` for threat/capability/auth/secrets diffs; **plus** parent applies skill `code-review` (write `review.md`) — no `code-reviewer` agent in Phase 1. Pure schema/style-only diffs: skip security step, parent skill only (document in `skipped`) |
+| `spike` | "investigate", "spike", proof of concept | task-analyst → solution-architect |
+| `refactor` | "refactor", "no behavior change" | task-analyst → feature-developer → build-verifier → **security-reviewer** when [sensitive](#security-reviewer-routing); else document skip |
+| `retro` | "retro", "postmortem" | (orchestrator → `/technical-retro`) |
 
 ### Security-reviewer routing
 
@@ -38,7 +38,7 @@ Append **`security-reviewer` after `build-verifier`** for `feature` / `bugfix` /
 
 **Phase 1 available agents only:** `task-router`, `task-analyst`, `solution-architect`, `feature-developer`, `build-verifier`, `security-reviewer`.
 
-**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), `accessibility-reviewer`, `integration-test-*`, or Phase 2 `contract-test-*`. Put them in `skipped` with reason «mcp-ts Phase 1 roster».
+**Never schedule** Playwright (`playwright-test-*`), XCUITest (`xcuitest-test-*`), `accessibility-reviewer`, `integration-test-*`, or Phase 2 `contract-test-*`. Put them in `skipped` with reason "mcp-ts Phase 1 roster".
 
 ## Pipeline profiles
 

package/presets/cursor/mcp-ts/commands/README.md

@@ -1,6 +1,6 @@
 # Commands (mcp-ts)
 
-Slash-команды копируются в `.cursor/commands/` (Cursor) или `.claude/commands/` (Claude) при `ai-rules init … --preset mcp-ts`.
+Slash commands are copied to `.cursor/commands/` (Cursor) or `.claude/commands/` (Claude) on `ai-rules init … --preset mcp-ts`.
 
 | Command | Purpose |
 |---------|---------|

package/presets/cursor/mcp-ts/commands/feature-continue.md

@@ -5,15 +5,15 @@ description: Legacy alias for /task-continue that resumes a feature pipeline aft
 
 # Feature continue — legacy alias
 
-> **Предпочтительно:** `/task-continue <slug>` — то же поведение, учитывает `pipeline.json`.
+> **Preferred:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
 
-Продолжение после human gate. Полная логика — в **`task-continue.md`**.
+Continue after a human gate. Full logic lives in **`task-continue.md`**.
 
-## Кратко
+## Short version
 
-1. Прочитай `pipeline.json` (если есть) и `status.json`.
-2. Сбрось `awaitingHumanGate`; определи следующий step по `pipelineIndex`.
-3. Вызови subagent для `currentAgent`.
-4. Hook продолжит цепочку при `autoChain: true`.
+1. Read `pipeline.json` (if present) and `status.json`.
+2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
+3. Call the subagent for `currentAgent`.
+4. The hook continues the chain when `autoChain: true`.
 
-См. `task-continue.md` для деталей и таблицы handoff.
+See `task-continue.md` for details and the handoff table.