@bonesofspring/ai-rules 0.2.14 → 0.2.15

package/presets/claude/ios-swift/rules/stack/ios-app-core.md

@@ -1,20 +1,20 @@
 ---
-description: Базовые принципы, стек и структура iOS приложения на Swift (preset)
+description: Core principles, stack, and structure for an iOS Swift app (preset)
 ---
 
-# Стек и окружение
+# Stack and environment
 
-Версии — **из Xcode / Package.swift / конфигов репо**. Рамка: Swift, iOS; SwiftUI приоритет (UIKit где принято); Xcode + SPM/CocoaPods как в репо; `async`/`await`, `@MainActor`; XCTest/Swift Testing + XCUITest; сеть — `URLSession`/`Codable`; UI — токены `DesignSystem/`; наблюдаемость — только если уже в проекте.
+Versions come **from Xcode / Package.swift / repo configs**. Frame: Swift, iOS; SwiftUI preferred (UIKit where the repo already uses it); Xcode + SPM/CocoaPods as in the repo; `async`/`await`, `@MainActor`; XCTest/Swift Testing + XCUITest; networking — `URLSession`/`Codable`; UI — `DesignSystem/` tokens; observability — only if already in the project.
 
-# Структура проекта
+# Project structure
 
-Feature-first или слои сверху (как в репо): `App/` (composition root), `Features/<Name>/` (Presentation / Domain / Data), `Core/`, `DesignSystem/`, `Tests/`. Новые файлы — рядом с аналогами. Границы/DI — **`architecture/boundaries.md`**.
+Feature-first or top-level layers (as in the repo): `App/` (composition root), `Features/<Name>/` (Presentation / Domain / Data), `Core/`, `DesignSystem/`, `Tests/`. Place new files next to analogs. Boundaries/DI — **`architecture/boundaries.md`**.
 
-# Swift и качество
+# Swift and quality
 
-API Design Guidelines + SwiftLint/SwiftFormat репо; без `!`/`try!` в production; `guard` / typed errors; паттерны соседних файлов.
+API Design Guidelines + the repo’s SwiftLint/SwiftFormat; no `!`/`try!` in production; `guard` / typed errors; follow neighboring-file patterns.
 
-# Работа агента
+# Agent work
 
-- Слой → паттерн соседей; без `URLSession` во View и DTO во ViewModel (`architecture/boundaries.md`).
-- Фичи: `architecture/feature-delivery.md`; после Swift — **вызвать** `tooling-and-review/post-change-build.md`; toolchain — `tooling-and-review/xcode-tooling.md`.
+- Layer → neighbor patterns; no `URLSession` in Views and no DTOs in ViewModels (`architecture/boundaries.md`).
+- Features: `architecture/feature-delivery.md`; after Swift edits — **invoke** `tooling-and-review/post-change-build.md`; toolchain — `tooling-and-review/xcode-tooling.md`.

package/presets/claude/ios-swift/rules/stack/swift-conventions.md

@@ -7,28 +7,28 @@ paths:
 # Naming and API design
 
 - Types: `UpperCamelCase`; methods, properties, enum cases: `lowerCamelCase`.
-- Protocols, описывающие capability: `-able`, `-ing`, или `Protocol` суффикс — как в репо.
-- Избегать аббревиатур в именах, кроме общепринятых (URL, ID, HTTP).
+- Protocols that describe a capability: `-able`, `-ing`, or `Protocol` suffix — as in the repo.
+- Avoid abbreviations in names except common ones (URL, ID, HTTP).
 
 # Optionals and errors
 
 ```swift
-// ❌ Плохо
+// ❌ Bad
 let name = user!.name
 
-// ✅ Хорошо
+// ✅ Good
 guard let name = user?.name else { return }
 ```
 
-- `throws` + typed errors вместо `Result` там, где так принято в слое; быть консistent внутри модуля.
-- `guard` для early exit; не вкладывать глубокие `if let` pyramids.
+- `throws` + typed errors instead of `Result` where that is the layer convention; stay consistent within a module.
+- `guard` for early exit; do not nest deep `if let` pyramids.
 
 # Concurrency
 
 - UI types — `@MainActor`.
-- Shared mutable state — `actor` или isolation через queue; document thread expectations.
-- `Task { }` в ViewModel: учитывать cancellation; `[weak self]` в escaping closures при retain cycles (default when capturing `self` in escaping work).
-- Prefer `async/await` over completion handlers для нового кода.
+- Shared mutable state — `actor` or isolation via a queue; document thread expectations.
+- `Task { }` in ViewModel: account for cancellation; `[weak self]` in escaping closures when retain cycles are possible (default when capturing `self` in escaping work).
+- Prefer `async/await` over completion handlers for new code.
 
 ## Anti-hallucination (Swift / concurrency)
 
@@ -42,20 +42,20 @@ guard let name = user?.name else { return }
 
 # Access control
 
-- Минимально необходимый уровень: `private` / `fileprivate` по умолчанию для implementation details.
-- Public API фичи — явные types и protocols; не экспортировать DTO наружу модуля.
+- Minimum necessary level: `private` / `fileprivate` by default for implementation details.
+- Feature public API — explicit types and protocols; do not export DTOs outside the module.
 
 # Value semantics
 
-- Предпочитать `struct` для models и state где нет identity semantics.
-- `class` — когда нужен identity, inheritance, или Objective-C interop.
+- Prefer `struct` for models and state where there is no identity semantics.
+- `class` — when identity, inheritance, or Objective-C interop is required.
 
 # Extensions
 
-- Группировать extensions по типу; не складывать unrelated helpers в один `Extensions.swift` без структуры.
-- Protocol extensions для shared default behavior.
+- Group extensions by type; do not dump unrelated helpers into one unstructured `Extensions.swift`.
+- Protocol extensions for shared default behavior.
 
-# Требование к агенту
+# Agent requirement
 
 - Style gate: **SwiftLint** (and SwiftFormat when configured) — prefer fixing lint over prose style essays; `// swiftlint:disable` only with an explicit reason.
-- Новый код — Swift Concurrency-ready (`Sendable` где требует компилятор/линтер проекта).
+- New code — Swift Concurrency-ready (`Sendable` where the project compiler/linter requires it).

package/presets/claude/ios-swift/rules/testing/README.md

@@ -1,6 +1,6 @@
 # Testing
 
-Unit (XCTest / Swift Testing) и UI (XCUITest). Index only — тела в topic `.md`.
+Unit (XCTest / Swift Testing) and UI (XCUITest). Index only — bodies live in topic `.md` files.
 
 | File | Cursor SoT |
 |------|------------|

package/presets/claude/ios-swift/rules/testing/ui.md

@@ -1,43 +1,43 @@
 ---
-description: UI-тесты XCUITest и accessibility identifiers
+description: XCUITest UI tests and accessibility identifiers
 paths:
   - "**/*UITests/**/*.swift"
 ---
 
-# Структура UI-тестов
+# UI test structure
 
-- UI Test target: `*UITests/` — сценарии пользовательских потоков.
-- Page Object (или Screen Object) — класс на экран: селекторы + действия (`LoginScreen`, `OrderHistoryScreen`).
-- Общие хелперы — `UITestSupport/`, base classes, launch arguments.
+- UI Test target: `*UITests/` — end-user flow scenarios.
+- Page Object (or Screen Object) — one class per screen: selectors + actions (`LoginScreen`, `OrderHistoryScreen`).
+- Shared helpers — `UITestSupport/`, base classes, launch arguments.
 
-# Селекторы и стабильность
+# Selectors and stability
 
-- **Приоритет:** `accessibilityIdentifier` для ключевых элементов; затем label/trait где устойчиво.
-- Идентификаторы согласовать с Presentation-слоем (`ui-and-accessibility/swiftui.md`): `{screen}__{element}`.
-  - Пример: `order-history__submit-button`, `login__email-field`.
-- Избегать привязки к абсолютным координатам и хрупким XPath-подобным цепочкам.
+- **Priority:** `accessibilityIdentifier` for key elements; then label/trait where stable.
+- Align identifiers with the Presentation layer (`ui-and-accessibility/swiftui.md`): `{screen}__{element}`.
+  - Example: `order-history__submit-button`, `login__email-field`.
+- Avoid absolute coordinates and brittle XPath-like chains.
 
-# Сценарии и именование
+# Scenarios and naming
 
-- Названия тестов — **на русском**, с префиксом сущности:
-  - `OH-001 Отображается список заказов` (префикс — первые буквы сущности, номер — три цифры).
-- Один тест — один пользовательский сценарий; не объединять несвязанные проверки.
+- Test names — **in the product locale** (Russian when UI copy is Russian), with an entity prefix:
+  <!-- i18n-keep: E5 -->
+  - `OH-001 Отображается список заказов` (prefix — entity initials, number — three digits).
+- One test — one user scenario; do not combine unrelated checks.
 
-# Launch и окружение
+# Launch and environment
 
-- `-UITesting`, mock server URL, сброс state — через `launchArguments` / `launchEnvironment`, как в репо.
-- Не зависеть от прод-backend в CI; использовать staging/mock.
+- `-UITesting`, mock server URL, state reset — via `launchArguments` / `launchEnvironment`, as in the repo.
+- Do not depend on production backend in CI; use staging/mock.
 
-# Синхронизация с UI
+# Sync with UI
 
-- При изменении UI обновлять identifiers в View и селекторы в page objects.
-- Не ослаблять assertions против бизнес-ожиданий ради «зелёного» CI.
+- When UI changes, update identifiers in Views and selectors in page objects.
+- Do not weaken assertions against business expectations just to keep CI green.
 
-# Требование к агенту
+# Agent requirement
 
-При добавлении UI-тестов:
-- Переиспользовать page objects, не дублировать query в каждом тесте.
-- Добавлять `accessibilityIdentifier` в SwiftUI через `.accessibilityIdentifier(...)` для новых интерактивных элементов.
-- Следовать существующим UITest files как эталону.
-
-- Планирование / генерация / heal — agents `xcuitest-test-{planner,generator,healer}` и skill `xcuitest-e2e` (не Playwright).
+When adding UI tests:
+- Reuse page objects; do not duplicate queries in every test.
+- Add `accessibilityIdentifier` in SwiftUI via `.accessibilityIdentifier(...)` for new interactive elements.
+- Follow existing UITest files as the reference.
+- Planning / generation / heal — agents `xcuitest-test-{planner,generator,healer}` and skill `xcuitest-e2e` (not Playwright).

package/presets/claude/ios-swift/rules/testing/unit.md

@@ -1,41 +1,41 @@
 ---
-description: Unit и integration тесты (XCTest / Swift Testing)
+description: Unit and integration tests (XCTest / Swift Testing)
 paths:
   - "**/*Tests/**/*.swift"
 ---
 
-# Общие правила тестирования
+# General testing rules
 
-- **Framework** — XCTest или Swift Testing, как в проекте.
-- Цель: проверять **поведение и бизнес-правила**, не детали реализации и private API.
-- Именование:
-  - `test` / `@Test` descriptions и `XCTContext` — **на русском**, как понятные бизнес-фразы.
-  - Описания **с заглавной буквы**.
+- **Framework** — XCTest or Swift Testing, as in the project.
+- Goal: verify **behavior and business rules**, not implementation details and private API.
+- Naming:
+  - `test` / `@Test` descriptions and `XCTContext` — **in the product locale** (Russian when UI copy is Russian), as clear business phrases.
+  - Descriptions **start with a capital letter**.
 
-# ViewModel и use case
+# ViewModel and use case
 
-- Mock протоколов repositories / use cases; не поднимать реальную сеть.
-- Проверять переходы state: loading → success/failure, validation errors, edge cases.
-- `@MainActor` ViewModel тестировать с `@MainActor` test methods или `await MainActor.run`.
+- Mock repository / use case protocols; do not hit the real network.
+- Assert state transitions: loading → success/failure, validation errors, edge cases.
+- Test `@MainActor` ViewModels with `@MainActor` test methods or `await MainActor.run`.
 
-# Mappers и domain
+# Mappers and domain
 
-- Mapper functions — unit-тесты с таблицами кейсов: nil fields, empty arrays, граничные значения.
-- Regression на бизнес-правила (скидки, статусы, форматирование дат).
+- Mapper functions — unit tests with case tables: nil fields, empty arrays, boundary values.
+- Regressions on business rules (discounts, statuses, date formatting).
 
-# Изоляция
+# Isolation
 
-- Не мокать то, что является предметом теста (например, сам mapper при тесте mapper).
-- Fixtures — в `TestSupport/`, `Mocks/` или рядом по конвенции репо; не дублировать большие JSON inline без нужды.
+- Do not mock the subject under test (e.g. the mapper itself when testing the mapper).
+- Fixtures — in `TestSupport/`, `Mocks/`, or colocated per repo convention; do not inline large JSON without need.
 
-# Структура файлов
+# File structure
 
-- `FeatureViewModelTests.swift`, `OrderMapperTests.swift` — суффикс `Tests` в имени типа/файла по стилю Xcode.
-- Не создавать глубокую вложенность `Tests/Tests/`; следовать target structure проекта.
+- `FeatureViewModelTests.swift`, `OrderMapperTests.swift` — `Tests` suffix on type/file name per Xcode style.
+- Do not create deep `Tests/Tests/` nesting; follow the project target structure.
 
-# Требование к агенту
+# Agent requirement
 
-При добавлении тестов:
-- Копировать паттерны из существующих test files в репо.
-- Добавлять тесты для новых веток логики и регрессий.
-- Использовать DTO fixtures из Data layer и domain types из Domain, не дублировать типы в тестах.
+When adding tests:
+- Copy patterns from existing test files in the repo.
+- Add tests for new logic branches and regressions.
+- Use DTO fixtures from the Data layer and domain types from Domain; do not duplicate types in tests.

package/presets/claude/ios-swift/rules/tooling-and-review/README.md

@@ -1,6 +1,6 @@
 # Tooling and review
 
-Качество, review, build, security, agent-team, retro. Index only — тела в topic `.md`.
+Quality, review, build, security, agent-team, retro. Index only — bodies live in topic `.md` files.
 
 | File | Cursor SoT |
 |------|------------|
@@ -9,8 +9,11 @@
 | [`post-change-build.md`](./post-change-build.md) | `post-change-build.mdc` |
 | [`xcode-tooling.md`](./xcode-tooling.md) | `xcode-tooling.mdc` |
 | [`security-ios.md`](./security-ios.md) | `security-ios.mdc` |
-| [`agent-team-intake.md`](./agent-team-intake.md) | `agent-team-intake.mdc` |
 | [`agent-team-orchestrator.md`](./agent-team-orchestrator.md) | `agent-team-orchestrator.mdc` |
+| [`agent-team-intake.md`](./agent-team-intake.md) | `agent-team-intake.mdc` |
 | [`technical-retro.md`](./technical-retro.md) | `technical-retro.mdc` |
+| [`design-guidance.md`](./design-guidance.md) | `design-guidance.mdc` |
+| [`anti-sycophancy-discipline.md`](./anti-sycophancy-discipline.md) | `anti-sycophancy-discipline.mdc` |
+| `preset-*.md` | `preset-*.mdc` |
 
 Sync: change Cursor → update Claude twin same PR. Full map: [`../README.md`](../README.md).

package/presets/claude/ios-swift/rules/tooling-and-review/agent-team-intake.md

@@ -13,6 +13,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/claude/ios-swift/rules/tooling-and-review/agent-team-orchestrator.md

@@ -8,12 +8,11 @@ paths:
 
 <!-- shared-core: agent-team/agent-team-orchestrator.md -->
 
-
 # Agent team orchestrator
 
 Parent agent = **manager**. Router plans; specialists execute. Artifacts: `.claude/team/tasks/<slug>/`.
 
-Work request без `/task` — см. **`tooling-and-review/agent-team-intake.md`**.
+Work request without `/task` — see **`tooling-and-review/agent-team-intake.md`**.
 
 ## Entry points
 
@@ -25,15 +24,41 @@ Work request без `/task` — см. **`tooling-and-review/agent-team-intake.md
 | `/feature-continue <slug>` | Alias of task-continue |
 | `/technical-retro [slug]` | Retro with agent team block |
 
-## Roles (iOS)
-
-Same stems as Cursor ios-swift agents. **Never Playwright** — use `xcuitest-test-{planner,generator,healer}`. `build-verifier` runs xcodebuild + SwiftLint/Format + unit smoke.
+## Stack notes
+
+### Roles (iOS)
+
+| Agent | Prod writes | Typical intent |
+|-------|-------------|----------------|
+| `task-router` | no (team) | Every `/task` |
+| `task-analyst` | no | feature, refactor, test-only, a11y, docs, migration |
+| `solution-architect` | no | spike, cross-layer Feature |
+| `migration-specialist` | no | Xcode/SPM/iOS upgrades |
+| `api-contract-reviewer` | no | OpenAPI / Swift codegen contracts |
+| `debugger` | minimal | bugfix |
+| `ci-investigator` | minimal CI | ci-fix |
+| `feature-developer` | yes | feature, bugfix, refactor, migration, a11y |
+| `build-verifier` | no | xcodebuild + SwiftLint/Format + unit smoke; preset-structure for preset PRs |
+| `accessibility-reviewer` | no | VoiceOver / Dynamic Type |
+| `performance-auditor` | no | launch / Instruments |
+| `code-reviewer` | no | most pipelines, review-only |
+| `security-reviewer` | no | Keychain, ATS, PII |
+| `qa-tester` | tests | feature, bugfix, test-only |
+| `unit-test-planner` / `generator` / `healer` | tests | unit-only |
+| `xcuitest-test-planner` / `generator` / `healer` | UI tests | e2e-only (XCUITest) |
+| `tech-writer` | docs | docs-only |
+
+**Never use Playwright stems** in this preset — substitute XCUITest trio. Document Playwright skips when copying next templates.
+
+**Cursor frontmatter:** all team agents use `readonly: false` (team writes). Production restrictions live in prompt bodies.
 
 Full prompts: `.claude/agents/*.md`. Artifact conventions: `.claude/team/README.md`; schema SoT: **agent-artifact-contracts**.
 
+When editing `packages/ai-rules/presets/**`, follow **`tooling-and-review/preset-pr-checklist.md`** (+ twin-sync / layering / token-budget / leakage meta-rules).
+
 ## Dynamic pipeline
 
-**Source of truth:** `pipeline.json` → `steps[]`.
+**Source of truth for order:** `pipeline.json` → `steps[]`. Never hardcode analyst → dev → review → QA when `pipeline.json` exists.
 
 New pipelines retain top-level `profile` and include `routingDecision` with `complexity`, `riskFlags`, non-empty `routingReasons`, `estimatedWorkPackages`, and `openDecisionCount`. The stack `task-router` owns heuristics; this metadata is auditable evidence and does not change hook semantics.
 
@@ -43,7 +68,7 @@ Use the local `metrics.json` ledger described by **agent-task-metrics**: the orc
 
 ## Artifact context index and receipts
 
-Each slug has one `artifact-manifest.json`: `.cursor/team/tasks/<slug>/` or `.claude/team/tasks/<slug>/`. Schema SoT: **agent-artifact-contracts**.
+Each slug has one `artifact-manifest.json`: `.claude/team/tasks/<slug>/` or `.cursor/team/tasks/<slug>/`. Schema SoT: **agent-artifact-contracts**.
 
 - Read the manifest before broad prior-artifact discovery. Each step receives authoritative input entry IDs, owns named output entry IDs, and finishes with one terminal receipt linked to AC/task IDs.
 - Markdown remains detailed evidence; the manifest records producer, status, authoritative paths, timestamps, outcome, and evidence paths.
@@ -72,26 +97,31 @@ On each `subagentStop`, the hook reconciles `status.state` from the completing p
 
 ## Rules (strict)
 
-1. **`/task` always starts with task-router**.
+1. **`/task` always starts with task-router** (unless user skips with documented pipeline).
 2. Read `pipeline.json` before every subagent invocation.
-3. One role per invocation — except parallel steps.
-4. **Never** skip `humanGates` without continue/approval.
-5. Persist handoffs under `.claude/team/tasks/<slug>/` by writing files (not Shell-only `mkdir`).
-6. On `validation_failed`: developer → build-verifier.
-7. When complete, suggest `/technical-retro <slug>`.
+3. One role per Task call — except parallel steps.
+4. **Never** skip `humanGates` without `/task-continue` or explicit approval.
+5. Persist handoffs to disk under `.claude/team/tasks/<slug>/` via **Write** (not Shell `mkdir`).
+6. On `changes_requested`: developer → same reviewer.
+7. On `validation_failed`: developer → build-verifier.
+8. When all steps complete, suggest `/technical-retro <slug>`.
+9. If `autoChain: false`, do not rely on hook.
 
-## Model when invoking
+## Model when invoking (Task)
 
 Honor optional `steps[i].model` (`cheap` \| `standard` \| `strong`); else agent frontmatter (matrix in `agents/README.md`).
 
-- `cheap` → Agent `haiku` (or frontmatter `fast`).
-- `standard` → omit / `sonnet` / inherit.
-- `strong` → `opus`.
+- `cheap` → Task `model: "fast"` when accepted.
+- `standard` → omit Task model.
+- `strong` → never pass `fast`; use agent pin `claude-opus-4-8[effort=high]` / parent Max.
 
-## Skip pipeline when
+## Team artifact I/O (Cursor Shell sandbox)
+
+- Create/update `.claude/team/tasks/<slug>/**` with the **Write** tool. Do **not** bootstrap slug dirs with Shell `mkdir -p` — sandbox → `Operation not permitted` (esp. macOS Desktop/Documents + TCC).
+- If Shell must touch team paths and fails with EPERM, retry with `required_permissions: ["all"]`.
 
-Pure questions («как работает X») — prefer **`codebase-analyzer`**; trivial one-file; user «без pipeline»; docs-only one-liner.
+## Skip pipeline when
 
-## Preset authoring
+- Pure questions (“how does X work?”) — prefer **`codebase-analyzer`**; typo / one-file trivial fix; user “no pipeline”; single-line docs-only.
 
-When editing `packages/ai-rules/presets/**`, follow **`tooling-and-review/preset-pr-checklist.md`** (+ twin-sync / layering / token-budget / leakage).
+Borderline — **`tooling-and-review/agent-team-intake.md`**.

package/presets/claude/ios-swift/rules/tooling-and-review/code-quality.md

@@ -1,51 +1,52 @@
 ---
-description: Поддержка и улучшение качества кода и архитектуры iOS
+description: Maintain and improve iOS code quality and architecture
 ---
 
 <!-- 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
 
-- Перед новым UI‑контролом проверять DesignSystem и существующие компоненты.
-- Public API: протоколы и facades между фичами.
-- Допустимые примеры: общий mapper/validation; заменить force unwrap; разбить перегруженный ViewModel на use cases; design tokens вместо magic numbers/colors; убрать прямую зависимость View от Data в пользу протокола.
-- Post-change gate: **`post-change-build.mdc`** + `xcode-tooling.mdc` (не yarn lint).
+- Before adding a new UI control, check DesignSystem and existing components.
+- Public API: protocols and facades between features.
+- Acceptable examples: shared mapper/validation; replace force unwrap; split an overloaded ViewModel into use cases; design tokens instead of magic numbers/colors; remove a direct View→Data dependency in favor of a protocol.
+- Post-change gate: **`tooling-and-review/post-change-build.md`** + `tooling-and-review/xcode-tooling.md` (not yarn lint).
 - Style: **SwiftLint** (+ SwiftFormat when configured) — authoritative style gate; do not duplicate linter rules in prose.

package/presets/claude/ios-swift/rules/tooling-and-review/code-review.md

@@ -1,5 +1,5 @@
 ---
-description: Требования к code review для iOS merge requests. Use when reviewing MR/diff/PR, evaluating a branch, or when the user asks for code review.
+description: Code review requirements for iOS merge requests. Use when reviewing MR/diff/PR, evaluating a branch, or when the user asks for code review.
 paths:
   - .claude/commands/**/*
   - .claude/team/**/*
@@ -26,9 +26,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**.
 
@@ -37,7 +37,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
 
@@ -50,38 +50,39 @@ Procedure details live in skill `code-review`. Required shape:
 
 ## Stack notes
 
-On-demand правило для review-потоков (не always-on).
-
-- **Когда применять**
-  - Запросы: «проведи ревью», «оцени MR/ветку/дифф», «посмотри изменения».
-  - Опираться на локальный репозиторий: ветка, `git diff`, открытые файлы.
-
-- **Что обязан проверить агент**
-  - **Архитектура и слои** (`architecture/boundaries.md`, `stack/ios-app-core.md`):
-    - View не вызывает API и не знает DTO.
-    - ViewModel не зависит от Data-реализаций напрямую.
-    - Domain не импортирует SwiftUI/UIKit.
-    - Data не тянет Presentation.
-  - **Зависимости и модули**:
-    - DI через протоколы; composition root в App.
-    - Нет deep-import между фичами.
-    - Файлы в правильных слоях (`Presentation`, `Domain`, `Data`, `DesignSystem`).
-  - **Swift и concurrency** (`stack/swift-conventions.md`):
-    - `@MainActor` на UI; нет необоснованных force unwrap.
-    - Typed errors; корректная отмена Task где нужно.
+On-demand rule for review flows (not always-on).
+
+- **When to apply**
+  - Requests: “review this”, “evaluate the MR/branch/diff”, “look at the changes”.
+  - Rely on the local repository: branch, `git diff`, open files.
+
+- **What the agent must check**
+  - **Architecture and layers** (`architecture/boundaries.md`, `stack/ios-app-core.md`):
+    - View does not call APIs and does not know DTOs.
+    - ViewModel does not depend on Data implementations directly.
+    - Domain does not import SwiftUI/UIKit.
+    - Data does not pull Presentation.
+  - **Dependencies and modules**:
+    - DI via protocols; composition root in App.
+    - No deep-import between features.
+    - Files in the correct layers (`Presentation`, `Domain`, `Data`, `DesignSystem`).
+  - **Swift and concurrency** (`stack/swift-conventions.md`):
+    - `@MainActor` on UI; no unjustified force unwraps.
+    - Typed errors; correct Task cancellation where needed.
   - **UI** (`ui-and-accessibility/swiftui.md`):
-    - Тонкие Views; Design System tokens; accessibility identifiers для тестируемых элементов.
-  - **Сеть и data** (`api-and-data/networking.md`):
-    - DTO отделены от domain; mappers покрывают edge cases.
-  - **Тесты**:
-    - Нетривиальная логика — unit (`testing/unit.md`); пользовательские потоки — UI (`testing/ui.md`).
-    - Указать, какие тесты добавить или обновить.
-
-- **Глубина и формат**
-  - Фокус на **диффе MR**, не на всём проекте.
-  - Следовать **Output contract** выше (`path:line`, severity, verdict).
-  - Без «больших рефакторингов» без запроса (`tooling-and-review/code-quality.md`).
-
-- **Ограничения**
-  - Не выдумывать метаданные CI/MR с хостинга без локальных данных.
-  - Boy scout rule в рамках MR.
+    - Thin Views; Design System tokens; accessibility identifiers for testable elements.
+  - **Networking and data** (`api-and-data/networking.md`):
+    - DTOs separated from domain; mappers cover edge cases.
+  - **Tests**:
+    - Non-trivial logic — unit (`testing/unit.md`); user flows — UI (`testing/ui.md`).
+    - State which tests to add or update.
+
+- **Depth and format**
+  - Focus on the **MR diff**, not the whole project.
+  - Overview first (MR goal, risks), then concrete comments with file and a fix suggestion matching repo patterns.
+  - No “big refactors” without a request (`tooling-and-review/code-quality.md`).
+
+- **Constraints**
+  - Do not invent CI/MR hosting metadata without local data.
+  - Boy scout rule within the MR.
+  - BUGBOT automated review — see root `BUGBOT.md` (Cursor).