@bonesofspring/ai-rules 0.2.1 → 0.2.3

package/presets/claude/ios-swift/rules/ui-and-accessibility/README.md

@@ -0,0 +1,11 @@
+# UI and accessibility
+
+SwiftUI Views, Design System, ViewModels, navigation. Index only — тела в topic `.md`.
+
+| File | Cursor SoT |
+|------|------------|
+| [`swiftui.md`](./swiftui.md) | `swiftui-ui.mdc` |
+| [`viewmodels.md`](./viewmodels.md) | `state-and-viewmodels.mdc` |
+| [`navigation.md`](./navigation.md) | `navigation-coordinators.mdc` |
+
+Sync: change Cursor → update Claude twin same PR. Full map: [`../README.md`](../README.md).

package/presets/claude/ios-swift/rules/ui-and-accessibility/navigation.md

@@ -0,0 +1,28 @@
+---
+description: NavigationStack, координаторы, deep links — границы Presentation
+paths:
+  - "**/Presentation/**/*Navigator*.swift"
+  - "**/Presentation/**/*Coordinator*.swift"
+  - "**/Presentation/**/*Router*.swift"
+  - "**/App/**/*App*.swift"
+  - "**/*Navigation*.swift"
+---
+
+# Навигация (iOS)
+
+## Рамка
+
+- **SwiftUI-first:** `NavigationStack` / `navigationDestination` / sheet / fullScreenCover — как в репо.
+- UIKit / coordinator — только если уже принят в модуле; не смешивать два стиля в одном Feature без причины.
+- Маршруты и deep links — **Presentation** (или App shell); Domain не знает о `NavigationPath`.
+
+## Правила
+
+- Один Feature — один явный «вход» навигации (root view / coordinator), не размазывать `NavigationLink` по Data.
+- Параметры экрана — typed (enum route / struct), не «магические» строки без реестра.
+- Deep link → route mapping централизован (App или Navigation hub); ViewModel не парсит URL напрямую.
+- Модалки: владелец presentation state — родительский VM/coordinator, не глобальный singleton без нужды.
+
+## Требование к агенту
+
+Копировать паттерн ближайшего Feature из `reference-features`. Не тащить networking в навигационный слой.

package/presets/claude/ios-swift/rules/ui-and-accessibility/swiftui.md

@@ -0,0 +1,61 @@
+---
+description: Паттерны SwiftUI, View и Design System (preset)
+paths:
+  - "**/{Presentation,DesignSystem}/**/*.swift"
+---
+
+# Общие правила View
+
+- **SwiftUI** — приоритет; UIKit — только по конвенции репо (wrapper, legacy).
+- View должна быть **тонкой**:
+  - отображает state из ViewModel;
+  - делегирует действия через методы/closures ViewModel;
+  - не содержит бизнес-логики, маппинга DTO, сетевых вызовов.
+- Перед новым кастомным контролом — искать компонент в `DesignSystem/` или существующих фичах.
+- Повторяемую UI-логику выносить в `ViewModifier`, `@ViewBuilder` helpers или subviews.
+
+# ViewModel и binding
+
+- ViewModel — `@MainActor`, `@Observable` (iOS 17+) или `ObservableObject` — как принято в проекте.
+- View читает state и вызывает **явные методы** ViewModel (`submit()`, `load()`), а не мутирует внутреннее состояние напрямую.
+- Для навигации — coordinator/router или enum route в ViewModel, не размазанные `NavigationLink` с бизнес-условиями в View.
+
+# Структура файлов
+
+Для экрана фичи:
+- `FeatureView.swift` — композиция subviews.
+- `FeatureViewModel.swift` — state + intents.
+- `FeatureView+Subviews.swift` — при большом дереве (опционально).
+- `FeatureRoute.swift` — навигация (если используется).
+
+Для компонента Design System:
+- Папка `ComponentName/`:
+  - `ComponentName.swift`
+  - `ComponentName+Preview.swift` (опционально)
+  - `ComponentNameStyle.swift` — стили/варианты (опционально)
+
+# Стили и Design System
+
+- Цвета, шрифты, отступы — из **токенов/Theme** проекта (`DesignSystem`, `Assets`, generated tokens).
+- Избегать:
+  - «магических» литералов (`.padding(17)`, `Color(red: 0.2, ...)`), если есть токены;
+  - дублирования стилей, уже закрытых примитивами.
+- `Preview` — для компонентов и экранов с mock ViewModel.
+
+# Accessibility
+
+- Интерактивные элементы: осмысленные `accessibilityLabel`, `accessibilityHint` где нужно.
+- Для UI-тестов — стабильные `accessibilityIdentifier` на ключевых элементах (согласовать с `testing/ui.md`).
+- Поддерживать Dynamic Type и контраст, не ломать layout при крупном шрифте.
+
+# Previews и локализация
+
+- Строки UI — через `String(localized:)` / `LocalizedStringKey`, не hardcoded в production без причины.
+- `#Preview` с реалистичными mock-данными; для ViewModel — stub use cases.
+
+# Требование к агенту
+
+При создании/изменении UI:
+- Следовать существующим экранам и компонентам как эталону.
+- Не импортировать Data-слой во View/ViewModel.
+- Subview выделять, когда body превышает ~40–60 строк или повторяется.

package/presets/claude/ios-swift/rules/ui-and-accessibility/viewmodels.md

@@ -0,0 +1,43 @@
+---
+description: ViewModels, состояние экрана и domain flow
+paths:
+  - "**/{Presentation,Domain}/**/*ViewModel*.swift"
+---
+
+# Общие принципы
+
+- ViewModel — **единственная точка** orchestration для экрана: load, submit, validation, navigation intents.
+- Хранить и отдавать во View **domain models** и UI-specific state (loading, error message, selected tab).
+- `@MainActor` на ViewModel; тяжёлую работу — в use case / repository (`async`), не блокировать main thread.
+- Unidirectional flow: View → intent → ViewModel → use case → state update → View.
+
+# State
+
+- Явный enum или struct для UI state где уместно:
+  - `idle`, `loading`, `loaded(Data)`, `failed(Error)` — или аналог из репо.
+- Избегать множества несинхронизированных `@Published` флагов, если один enum покрывает сценарий.
+- `@Observable` / `ObservableObject` — как в проекте; не смешивать стили в одной фиче без причины.
+
+# Use cases и repositories
+
+- ViewModel зависит от **протоколов** (`LoadOrdersUseCase`, `OrderRepository`), не от `*RepositoryImpl`.
+- Один use case — одна бизнес-операция; не раздувать ViewModel сотнями строк — выносить use cases в Domain.
+- Кэширование и offline — в repository/Data, не во ViewModel.
+
+# Side effects
+
+- Analytics, haptics, deep links — через injected services или middleware-паттерн, не hardcode синглтонов.
+- `Task` в ViewModel: отмена при `deinit` / `onDisappear` где нужно (`task(id:)`, хранение `Task?` с cancel).
+
+# Тестируемость
+
+- Инициализатор ViewModel принимает протоколы (DI); без скрытых singleton для сети/БД.
+- Бизнес-ветки покрывать unit-тестами с mock use cases.
+
+# Требование к агенту
+
+При создании ViewModel:
+- Не вызывать `URLSession` / API client напрямую.
+- Не парсить JSON и не объявлять DTO во ViewModel.
+- Именование: `FeatureViewModel`, методы — глаголы (`loadOrders()`, `submitOrder()`).
+- Следовать стилю существующих ViewModels в той же фиче.

package/presets/claude/ios-swift/skills/README.md

@@ -0,0 +1,13 @@
+# `.claude/skills` (preset ios-swift)
+
+| Skill | Назначение |
+|-------|------------|
+| `feature-delivery` | Domain → Data → VM → View → tests → post-change-build |
+| `code-review` | iOS MR checklist |
+| `unit-testing` | XCTest / Swift Testing |
+| `xcuitest-e2e` | XCUITest plan/generate/heal (← next `playwright-e2e`) |
+| `debug-investigation` | Runtime evidence before fix |
+| `ci-investigation` | iOS CI red |
+| `technical-retro` | Retro facilitation |
+
+Копируется в `.claude/skills/` при init.

package/presets/claude/ios-swift/skills/ci-investigation/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: ci-investigation
+description: Investigates failing CI checks on PRs and branches — xcodebuild, SwiftLint, unit, XCUITest — with local reproduction and minimal fixes. Use when CI is red or for ci-fix pipeline tasks.
+---
+
+# CI Investigation (iOS)
+
+## Workflow
+
+1. Identify the **first failing check** (compile, lint, unit, XCUITest, signing, SPM).
+2. Capture error output — ignore cascading failures until root cause is found.
+3. Reproduce locally with the same scheme/destination CI uses (`tooling-and-review/xcode-tooling.md`):
+   - `xcodebuild build` / `xcodebuild test`
+   - SwiftLint / SwiftFormat scripts as in repo CI
+   - affected XCUITest if UI job failed
+4. Inspect git diff for changed files related to the failure.
+5. Apply **minimal fix** — no unrelated refactors.
+
+## Artifact
+
+Write `ci-report.md` under the task slug folder (`.claude/team/tasks/<slug>/`):
+
+- Failed check name and log excerpt
+- Root cause classification
+- Fix applied (or handoff to feature-developer)
+- `resolved: true|false`
+- Validation commands and results
+
+## Handoff Rules
+
+- Config-only or one-line fixes → fix in place, re-run check.
+- Missing tests or architecture work → document and route to `feature-developer` or `qa-tester`.
+- Flaky XCUITest → prefer `xcuitest-test-healer` after ci-investigator identifies the case.
+
+## Validation
+
+Always re-run the failing command locally before marking complete. If environment blocks execution (no simulator), state the exact command and blocker.
+
+Never run yarn/`lint:js`/Playwright — wrong stack.

package/presets/claude/ios-swift/skills/code-review/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: code-review
+description: Reviews pull requests, merge requests, git diffs, and branch changes using iOS architecture, SwiftUI, networking, and testing standards. Use when the user asks for review or when code-reviewer runs in an agent pipeline.
+---
+
+# Code Review (iOS)
+
+## Inputs
+
+Use the local repository as the source of truth: `git status`, `git diff`, task artifacts under `.claude/team/tasks/<slug>/` when present, and opened files. Do not invent hosting metadata such as labels, CI status, or reviewers.
+
+## Review Order
+
+1. Understand the intent and affected Feature layers (Presentation / Domain / Data).
+2. Check correctness and regressions first.
+3. Verify architecture boundaries (`architecture/boundaries.md`): View ≠ API/DTO; ViewModel ≠ Data impl; Domain ≠ SwiftUI; Data ≠ Presentation.
+4. Check DI composition in `App/`, SPM public API (`architecture/module-public-api.md`), and no deep-imports across Features.
+5. Review Swift concurrency and conventions (`stack/swift-conventions.md`): `@MainActor`, typed errors, force unwrap.
+6. Review SwiftUI thinness, Design System usage, accessibility identifiers (`ui-and-accessibility/swiftui.md`).
+7. Check tests: unit for mapper/domain/VM (`testing/unit.md`); XCUITest for user flows (`testing/ui.md`).
+8. Report validation gaps: `xcodebuild`, SwiftLint, or relevant tests not run (`tooling-and-review/xcode-tooling.md`, `tooling-and-review/post-change-build.md`).
+
+## Output
+
+Lead with findings ordered by severity. Each finding should include the file, the problem, impact, and a concrete fix direction. If there are no findings, say so and call out remaining test or validation risk.
+
+For agent team tasks, write `.claude/team/tasks/<slug>/review.md` and set `status.json` to `completed` or `changes_requested`.

package/presets/claude/ios-swift/skills/debug-investigation/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: debug-investigation
+description: Investigates bugs, failing tests, crashes, and incorrect behavior with runtime evidence before applying minimal fixes. Use for bugfix tasks, debugger agent runs, regressions, and flaky test diagnosis.
+---
+
+# Debug Investigation (iOS)
+
+## Process
+
+1. Reproduce the issue or collect the closest available evidence: Xcode console, lldb backtrace, crash log, failing XCTest/XCUITest output, Instruments note, or user steps.
+2. Define expected vs actual behavior in one sentence.
+3. Trace the failing path through the smallest relevant Feature slice (Presentation → Domain → Data).
+4. Identify the root cause before editing. Avoid broad refactors during bugfixes.
+5. Apply the smallest fix that preserves existing architecture and public contracts.
+6. Add or update a regression XCTest when the behavior is domain/VM logic or likely to recur.
+7. Run the narrow failing check first (`xcodebuild test` for the affected target), then broader build validation if needed (`tooling-and-review/xcode-tooling.md`).
+
+## Artifacts
+
+For agent team tasks, write `.claude/team/tasks/<slug>/debug-report.md` with:
+
+- Reproduction steps or evidence source.
+- Root cause.
+- Fix scope (`fixApplied`).
+- Regression coverage.
+- Remaining risk.
+
+Update `status.json` when complete.
+
+Do not use browser/Playwright tooling — this is an Xcode stack.

package/presets/claude/ios-swift/skills/feature-delivery/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: feature-delivery
+description: Delivers iOS Swift/SwiftUI features end-to-end across Domain, Data, ViewModels, Views, tests, and post-change-build validation. Use when implementing or extending a feature, especially through /task or feature-developer.
+---
+
+# Feature Delivery (iOS)
+
+1. Read task brief, acceptance criteria, and decomposition if present.
+2. Read `architecture/feature-delivery.md` and `architecture/reference-features.md` — Domain → Data → ViewModel → View → tests; mirror the closest Feature.
+3. Wire DI in `App/` composition root; keep Views thin; keep DTOs out of ViewModels.
+4. Add or update focused XCTest for mappers / use cases / ViewModels (`testing/unit.md`).
+5. After Swift edits: **invoke** `tooling-and-review/post-change-build.md` (+ `tooling-and-review/xcode-tooling.md`). Pipeline: scoped build OK if next step is `build-verifier`.
+
+## Do / Don't
+
+- **Do** follow existing Feature folder layout and public module APIs.
+- **Do** add `accessibilityIdentifier`s for new interactive UI when UI tests are in scope.
+- **Don't** introduce TCA/SwiftData/etc. unless the repo already uses them.
+- **Don't** use yarn, Playwright, or `app/src` paths — wrong stack.
+
+## Preset packaging note
+
+When editing **ai-rules ios-swift preset** sources (agents, hooks, rules) rather than an app Feature: keep Cursor and Claude trees in sync where applicable, and **fork / verify hook handoffs** (`hooks/chain-team-phases.sh`, guard scripts, team path conventions) so Cursor (`.cursor/team`) and Claude (`.claude/team`) do not regress against each other or against the next preset templates.
+
+## Handoff
+
+Summarize by layer, validation results, and known gaps. Agent team: update `.claude/team/tasks/<slug>/status.json`.

package/presets/claude/ios-swift/skills/technical-retro/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: technical-retro
+description: Facilitates technical retrospectives for tasks, sprints, incidents, releases, and agent-team pipelines. Use when the user asks for retro, postmortem, process review, or action items after delivery.
+---
+
+# Technical Retro
+
+Same structure as next technical-retro skill. For `/task` pipelines include router, analyst, developer, **build-verifier** (xcodebuild), reviewer, QA/XCUITest, hooks, rules.
+
+Preset feedback: propose updates to `.claude/rules|agents|skills` — do not apply without approval.

package/presets/claude/ios-swift/skills/unit-testing/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: unit-testing
+description: Plans, generates, and heals XCTest / Swift Testing for mappers, use cases, and ViewModels using *Tests targets and tests-unit rules. Use for unit test planning, generation, or fixing failing unit tests.
+---
+
+# Unit Testing (iOS)
+
+## Project Layout
+
+- Unit targets: `*Tests/` colocated or parallel to Feature — **as in the Xcode project**.
+- Framework: XCTest or Swift Testing per project convention.
+- Do **not** create Jest/Vitest `*.spec.ts` files.
+
+Follow `testing/unit.md` (Cursor `.mdc` / Claude `testing/unit.md` depending on preset).
+
+## Planner
+
+Write or update `.claude/team/tasks/<slug>/unit-test-plan.md`.
+
+Each scenario needs a Russian `test` / `@Test` title (capital letter after each sentence). Cover mappers, use cases, ViewModel state branches, and mocked client/repository behavior per AC.
+
+## Generator
+
+Implement tests from `unit-test-plan.md` into the correct `*Tests` target. Reuse TestSupport / protocol mocks. Do not change production code.
+
+## Healer
+
+Fix mocks, async/MainActor timing, and fixtures — preserve business assertions. Use `unit-test-plan.md` and `brief.md` as the behavior contract.
+
+## Validation
+
+Run affected unit tests via `xcodebuild test` (`tooling-and-review/xcode-tooling.md`) when feasible. Report command, pass/fail, and remaining gaps vs plan.

package/presets/claude/ios-swift/skills/xcuitest-e2e/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: xcuitest-e2e
+description: Plans, generates, and heals XCUITest UI tests using *UITests targets, accessibility identifiers, and screen objects. Use for UI test planning, generation, or fixing flaky XCUITest.
+---
+
+# XCUITest E2E
+
+## Project Layout
+
+- UI Test target: `*UITests/` (as in the Xcode project).
+- Optional plans: `*.cases.md` if the repo uses them.
+- Screen/Page objects keyed by `accessibilityIdentifier` (`{screen}__{element}`).
+- Shared helpers: `UITestSupport/` or equivalent — follow existing patterns.
+
+Follow `testing/ui.md`. Agents: `xcuitest-test-{planner,generator,healer}`.
+
+**Never Playwright** and never `app/__tests__/e2e`.
+
+## Planner
+
+Create or update the relevant plan (`*.cases.md` or team notes). Each scenario should include title, preconditions, steps, and expected result. Cover happy path, important edge cases, validation, and error states. Russian titles with entity prefix when that is repo convention.
+
+## Generator
+
+Generate XCUITest from plans into the UITests target. Reuse screen objects. Keep test names aligned with scenario names. Prefer identifiers over coordinates.
+
+## Healer
+
+Fix waits, launch arguments, identifiers, or screen-object details without weakening business assertions. Use the matching plan / AC as the behavior contract.
+
+## Validation
+
+Run affected UI tests via `xcodebuild test` (`tooling-and-review/xcode-tooling.md`) when a simulator is available. If blocked, report the exact command and blocker.

package/presets/claude/ios-swift/team/README.md

@@ -0,0 +1,27 @@
+# Agent team artifacts (ios-swift)
+
+Каталог артефактов пайплайна «команда агентов» для iOS.
+
+## Layout
+
+```
+.claude/team/   # Claude: .claude/team/
+  active-task.json
+  fixtures/
+  tasks/<slug>/
+    pipeline.json
+    status.json
+    brief.md
+    decomposition.md
+    …
+```
+
+## Fixtures
+
+| Fixture | Notes |
+|---------|-------|
+| `feature-full.json` | Full profile; QA scope `e2e-only` = **XCUITest**; Playwright stems in `skipped` |
+| `feature-light.json` | developer → build-verifier |
+| `bugfix-standard.json` | debugger → developer (skipIf) → verifier → reviewer |
+
+**Never** schedule Playwright-only steps without skip rationale. Use `xcuitest-test-*` for UI-test-only intents.

package/presets/claude/ios-swift/team/fixtures/bugfix-standard.json

@@ -0,0 +1,33 @@
+{
+  "slug": "example-bugfix-standard",
+  "intent": "bugfix",
+  "profile": "standard",
+  "summary": "Regression fix with review",
+  "steps": [
+    {
+      "agent": "debugger",
+      "label": "Root cause"
+    },
+    {
+      "agent": "feature-developer",
+      "label": "Fix if needed",
+      "skipIf": "debugger.fixed"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "Validation gate"
+    },
+    {
+      "agent": "code-reviewer",
+      "label": "Code review"
+    }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "playwright-test-planner",
+      "reason": "iOS uses XCUITest — not in this bugfix path"
+    }
+  ]
+}

package/presets/claude/ios-swift/team/fixtures/feature-full.json

@@ -0,0 +1,48 @@
+{
+  "slug": "example-feature-full",
+  "intent": "feature",
+  "profile": "full",
+  "summary": "Multi-layer Feature with XCUITest coverage",
+  "steps": [
+    {
+      "agent": "task-analyst",
+      "label": "Clarify and decompose"
+    },
+    {
+      "agent": "feature-developer",
+      "label": "Implement + unit tests",
+      "scope": "unit-in-dev"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "xcodebuild + lint + unit smoke"
+    },
+    {
+      "agent": "code-reviewer",
+      "label": "Code review"
+    },
+    {
+      "agent": "qa-tester",
+      "label": "XCUITest",
+      "scope": "e2e-only"
+    }
+  ],
+  "humanGates": [
+    "after:task-analyst"
+  ],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "playwright-test-planner",
+      "reason": "iOS uses XCUITest — see xcuitest-test-* agents"
+    },
+    {
+      "agent": "playwright-test-generator",
+      "reason": "iOS uses XCUITest"
+    },
+    {
+      "agent": "playwright-test-healer",
+      "reason": "iOS uses XCUITest"
+    }
+  ]
+}

package/presets/claude/ios-swift/team/fixtures/feature-light.json

@@ -0,0 +1,36 @@
+{
+  "slug": "example-feature-light",
+  "intent": "feature",
+  "profile": "light",
+  "summary": "Trivial single-file Swift change with explicit AC",
+  "steps": [
+    {
+      "agent": "feature-developer",
+      "label": "Implement"
+    },
+    {
+      "agent": "build-verifier",
+      "label": "Validation gate"
+    }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    {
+      "agent": "task-analyst",
+      "reason": "Explicit AC and single-file scope"
+    },
+    {
+      "agent": "code-reviewer",
+      "reason": "Light profile"
+    },
+    {
+      "agent": "qa-tester",
+      "reason": "No XCUITest AC"
+    },
+    {
+      "agent": "playwright-test-planner",
+      "reason": "iOS uses XCUITest; not needed for light"
+    }
+  ]
+}

package/presets/claude/next/CLAUDE.md

@@ -7,8 +7,8 @@ See @rules/README.md for the full catalog and loading strategy.
 ## Conventions
 
 - **Одна тема на файл**; для больших областей — подпапки в `rules/<topic>/`.
-- **Session-start rules** — только базовые инварианты (`next-app-core`, lint, package manager, code-quality).
-- **Domain-specific rules** — YAML frontmatter `paths:` (подгружаются при работе с matching-файлами).
+- **Session-start rules** (без `paths:`) — ровно **три**: `next-app-core`, `package-manager`, `code-quality`.
+- **Domain-specific rules** — YAML frontmatter `paths:` (подгружаются при работе с matching-файлами); `post-change-lint` — requestable (**обязателен после code edits**); orchestrator и code-review — on-demand.
 - Slash-команды — в `commands/`; сценарии — в `skills/`; subagents — в `agents/`.
 
 ## Quick start
@@ -21,7 +21,7 @@ See @rules/README.md for the full catalog and loading strategy.
 | Стек и слои | `rules/stack/next-app-core.md` |
 | App Router | `rules/stack/next-app-router.md` |
 | A11y при кодинге UI | `rules/ui-and-accessibility/react-a11y-coding.md` |
-| После правок кода | `rules/tooling-and-review/post-change-lint.md` |
+| После правок кода | `rules/tooling-and-review/post-change-lint.md` (**requestable**, обязателен после edits) |
 | Валидация перед review | agent `build-verifier` |
 | Code review MR | skill `code-review` + `rules/tooling-and-review/code-review-mr.md` |
 | Техническое ретро | `commands/technical-retro.md` + skill `technical-retro` |
@@ -32,8 +32,4 @@ See @rules/README.md for the full catalog and loading strategy.
 npx @bonesofspring/ai-rules init claude --preset next
 ```
 
-Копирует `CLAUDE.md`, `rules/**`, `commands/**`, `agents/**`, `hooks/**`, `team/**`, `hooks.json`, `BUGBOT.md` и др. в `.claude/` целевого репозитория.
-
-## Pipeline routing
-
-Intent detection, profiles (`full` / `standard` / `light`), and default steps — **only** in `agents/task-router.md`. Schema and examples — `agents/README.md`.
+Копирует `CLAUDE.md`, `rules/**`, `commands/**`, `agents/**`, `hooks/**`, `team/**` и др. в `.claude/` целевого репозитория.