@bonesofspring/ai-rules 0.2.13 → 0.2.15

package/presets/claude/java/rules/tooling-and-review/preset-no-cross-stack-leakage.md

@@ -11,11 +11,13 @@ paths:
 
 # Preset no cross-stack leakage
 
-Запрет протекания stack-specific имён, путей и handoff stems между пресетами.
+Ban leakage of stack-specific names, paths, and handoff stems across presets.
 
 ## Principles
 
 - `next` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `nuxt` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `svelte` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
 - `ios-swift` must not ship Playwright handoffs or Next lint recipes as required commands.
 - `go` / `java` / `php-hexagonal` / `php-laravel` / `mcp-ts` must not ship Playwright, XCUITest, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
 - `mcp-ts` must not ship Go tool commands (`go test`, `go vet`, `golangci-lint`) or `integration-test-*` agents as required delivery gates.
@@ -36,6 +38,18 @@ Required instead: `xcuitest-test-*` stems; build-verifier mentions `xcodebuild`
 - `xcuitest-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Next app work
 
+## Forbidden in nuxt hooks/agents (FAIL when present as required)
+
+- `xcuitest-test-` as handoff stems
+- Requiring `xcodebuild` / SwiftLint as the default post-change gate for Nuxt app work
+- Frontend profile mirrors `next`: Playwright / `lint:js` / `lint:css` allowed
+
+## Forbidden in svelte hooks/agents (FAIL when present as required)
+
+- `xcuitest-test-` as handoff stems
+- Requiring `xcodebuild` / SwiftLint as the default post-change gate for SvelteKit app work
+- Frontend profile mirrors `next` / `nuxt`: Playwright / `lint:js` / `lint:css` allowed
+
 ## Forbidden in go / java / php-hexagonal / php-laravel hooks/agents (FAIL)
 
 Shared backend-stack bans (`go`, `java`, `php-hexagonal`, and `php-laravel`):
@@ -66,4 +80,4 @@ Required instead: package-manager–discovered typecheck/test (`mcp-ts-tooling`,
 
 ## Chain fork
 
-`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `ios-swift`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).
+`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `nuxt`, `svelte`, `ios-swift`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).

package/presets/claude/java/rules/tooling-and-review/preset-pr-checklist.md

@@ -11,16 +11,16 @@ paths:
 
 # 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, 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/claude/java/rules/tooling-and-review/preset-token-budget.md

@@ -11,18 +11,18 @@ paths:
 
 # 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/claude/java/rules/tooling-and-review/preset-twin-sync.md

@@ -18,6 +18,8 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 | Stack | Cursor SoT | Claude derive | Mapping table |
 |-------|------------|---------------|---------------|
 | `next` | `presets/cursor/next/rules/*.mdc` | `presets/claude/next/rules/<topic>/` | **Required** in `claude/next/rules/README.md` |
+| `nuxt` | `presets/cursor/nuxt/rules/*.mdc` | `presets/claude/nuxt/rules/<topic>/` | **Required** in `claude/nuxt/rules/README.md` |
+| `svelte` | `presets/cursor/svelte/rules/*.mdc` | `presets/claude/svelte/rules/<topic>/` | **Required** in `claude/svelte/rules/README.md` |
 | `ios-swift` | `presets/cursor/ios-swift/rules/*.mdc` | `presets/claude/ios-swift/rules/<topic>/` | Keep in `claude/ios-swift/rules/README.md` |
 | `go` | `presets/cursor/go/rules/*.mdc` | `presets/claude/go/rules/<topic>/` | Keep in `claude/go/rules/README.md` |
 | `java` | `presets/cursor/java/rules/*.mdc` | `presets/claude/java/rules/<topic>/` | Keep in `claude/java/rules/README.md` |
@@ -40,6 +42,8 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 ## Severity (build-verifier)
 
 - **next:** missing Claude twin for a changed Cursor rule → **FAIL** (mapping table required).
+- **nuxt:** missing Claude twin for a changed Cursor rule → **FAIL** (mapping table required).
+- **svelte:** missing Claude twin for a changed Cursor rule → **FAIL** (mapping table required).
 - **ios-swift:** missing Claude twin for a changed Cursor rule → **FAIL**.
 - **go:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift; mapping table required).
 - **java:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go; mapping table required).

package/presets/claude/java/rules/tooling-and-review/technical-retro.md

@@ -11,12 +11,12 @@ paths:
 
 <!-- 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/claude/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/claude/mcp-ts/MCP.md

@@ -1,11 +1,11 @@
 # MCP (preset `mcp-ts`, Claude)
 
-Копируется в **корень проекта** как `.mcp.json` при `ai-rules init claude --preset mcp-ts`.
+Copied to the **project root** as `.mcp.json` on `ai-rules init claude --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 pu
 
 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/claude/mcp-ts/agents/build-verifier.md

@@ -33,7 +33,7 @@ Document PASS/FAIL in `validation-report.md`. Soft leakage output:
 - **Negation** of forbidden stems in agents → suppressed (INFO count). **Not** a merge blocker.
 - **WARN** only for non-negation packaging mentions in this verifier (and rare chain-skip WARNs). Do not treat INFO/WARN counts as FAIL.
 
-1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java|mcp-ts|php-hexagonal`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
+1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|nuxt|svelte|ios-swift|go|java|mcp-ts|php-hexagonal|php-laravel`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
 2. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
 3. **Forbidden agent filenames** (Playwright / XCUITest / integration-test / accessibility-reviewer / contract-test): must be absent → **FAIL** via `check:preset-leakage`.
 4. **Rule eval (WARN):** optional maintainer smoke — not part of default `check:preset-structure`.

package/presets/claude/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/claude/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/claude/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.

package/presets/claude/mcp-ts/commands/feature-start.md

@@ -5,29 +5,29 @@ description: Legacy analyst-only feature intake. Prefer /task for new work becau
 
 # Feature start — legacy (analyst only)
 
-> **Предпочтительно:** `/task <описание>` — router выберет роли и порядок автоматически.
+> **Preferred:** `/task <description>` — the router picks roles and order automatically.
 
-Запуск **фазы анализа** без router. Родительский агент действует как оркестратор (см. `agent-team-orchestrator.mdc`).
+Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `rules/tooling-and-review/agent-team-orchestrator.md`).
 
-## Что делать
+## What to do
 
-1. Извлеки описание задачи из аргументов команды (всё после `/feature-start`).
-2. Сгенерируй **slug** (kebab-case, до 48 символов) из заголовка задачи.
-3. Создай `.cursor/team/tasks/<slug>/` если его ещё нет — через **Write** артефакта (не Shell `mkdir`).
-4. Запиши `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Опционально: минимальный `pipeline.json` с фиксированными steps (analyst → developer → reviewer → qa-tester).
-6. Вызови subagent **task-analyst** (Task tool) с полным описанием задачи и путём к артефактам.
-7. Дождись завершения аналитика. **Не вызывай developer** на этом этапе.
+1. Extract the task description from command arguments (everything after `/feature-start`).
+2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
+3. Create `.claude/team/tasks/<slug>/` if it does not exist yet — via Write / Edit (not Shell `mkdir`).
+4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+5. Optionally: minimal `pipeline.json` with fixed steps (analyst → developer → reviewer → qa-tester).
+6. Invoke subagent **task-analyst** with the full task description and artifact paths.
+7. Wait for the analyst to finish. **Do not invoke developer** at this stage.
 
 ## Human gate
 
-После аналитика:
+After the analyst:
 
-- Покажи пользователю ссылки на `brief.md` и `decomposition.md`.
-- Попроси проверить и утвердить или прислать правки.
-- Для продолжения: `/task-continue <slug>` или `/feature-continue <slug>`.
+- Show the user links to `brief.md` and `decomposition.md`.
+- Ask them to review and approve or send edits.
+- To continue: `/task-continue <slug>` or `/feature-continue <slug>`.
 
-## Если slug уже существует
+## If slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или continue.
-- Если задача в работе — спроси, продолжать или начать новый slug.
+- If `status.json` is `awaiting_approval` — offer review or continue.
+- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/mcp-ts/commands/task-continue.md

@@ -3,25 +3,25 @@ name: task-continue
 description: Continue an agent-team task after a human gate, pause, or review changes request using pipeline.json and status.json.
 ---
 
-# Task continue — после human gate или паузы
+# Task continue — after human gate or pause
 
-Продолжение пайплайна из `pipeline.json`. Алиас по смыслу: `/feature-continue`.
+Resume the pipeline from `pipeline.json`. Semantic alias: `/feature-continue`.
 
-## Аргументы
+## Arguments
 
-`<slug>` — идентификатор задачи.
+`<slug>` — task identifier.
 
 ## Preconditions
 
-1. Прочитай `.claude/team/tasks/<slug>/pipeline.json` и `status.json`.
-2. Продолжай если:
-   - `awaitingHumanGate: true` или `state: awaiting_approval`, **или**
-   - `state: changes_requested` (после review), **или**
-   - задача прервана и нужно возобновить с `pipelineIndex`.
+1. Read `.claude/team/tasks/<slug>/pipeline.json` and `status.json`.
+2. Continue if:
+   - `awaitingHumanGate: true` or `state: awaiting_approval`, **or**
+   - `state: changes_requested` (after review), **or**
+   - the task was interrupted and must resume from `pipelineIndex`.
 
-## Алгоритм
+## Algorithm
 
-1. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+1. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
 2. **Human gate resume** (`awaitingHumanGate` / `awaiting_approval`):
    1. **Do not** manually increment `pipelineIndex` or invent `currentAgent` first.
    2. Close the gate + activate the next attempt via the **installed** hook (single authority for ledger + status):
@@ -36,10 +36,10 @@ printf '%s\n' '{"status":"completed","action":"end_human_gate","activateNext":tr
 4. **Other resume**: restore `pipelineIndex` / `currentAgent` from status and invoke that agent.
 5. After the invoked agent completes, `chain-team-phases.sh` on `subagentStop` continues the chain when `autoChain: true`.
 
-## Артефакты для handoff
+## Artifacts for handoff
 
-| Agent | Прочитать |
-|-------|-----------|
+| Agent | Read |
+|-------|------|
 | feature-developer | brief.md, decomposition.md, validation-report.md (if retry), review.md (if retry), architecture.md |
 | build-verifier | git diff, decomposition.md |
 | code-reviewer | brief.md, validation-report.md, git diff |

package/presets/claude/mcp-ts/commands/task.md

@@ -3,52 +3,52 @@ name: task
 description: Route a natural-language task through the agent-team pipeline: task-router, pipeline.json, and the first planned specialist.
 ---
 
-# Task — единая точка входа (router + pipeline)
+# Task — unified entry point (router + pipeline)
 
-Главная команда для постановки задачи. Родительский агент = оркестратор (`agent-team-orchestrator.mdc`). Intake для work-запросов без `/task` — `agent-team-intake.mdc`.
+Main command for submitting work in Claude Code. Parent agent = orchestrator (`rules/tooling-and-review/agent-team-orchestrator.md`). Intake — `rules/tooling-and-review/agent-team-intake.md`.
 
-## Аргументы
+## Arguments
 
-Всё после `/task` — описание задачи на естественном языке.
+Everything after `/task` is the task description in natural language.
 
-Примеры:
+Examples:
 
-- `/task Добавить MCP tool list_resources`
-- `/task Handler падает при пустом body — пофикси`
-- `/task Project tests падают локально после правки schema — bugfix + build-verifier`
-- `/task Миграция на новый SDK / package`
-- `/task Покрой unit-тестами handler echo`
-- `/task Напиши changelog для релиза tool`
-- `/task Сделай ревью моих изменений в src/tools`
-- `/task Напиши contract/unit tests для tool schema`
+- `/task Add MCP tool list_resources`
+- `/task Handler crashes on empty body — fix it`
+- `/task Project tests fail locally after schema change — bugfix + build-verifier`
+- `/task Migrate to a new SDK / package`
+- `/task Cover handler echo with unit tests`
+- `/task Write changelog for tool release`
+- `/task Review my changes in src/tools`
+- `/task Write contract/unit tests for tool schema`
 
-## Алгоритм
+## Procedure
 
-1. **Slug** — kebab-case из описания (≤48 символов). Создай `.cursor/team/tasks/<slug>/` через **Write** (например placeholder `pipeline.json` или пустой marker) — runtime/hook владеет `status.json` — **не** через Shell `mkdir` (песочница → `Operation not permitted`).
-2. **Router** — вызови subagent **task-router** с описанием задачи и путём к slug.
-3. **План** — покажи пользователю таблицу из `pipeline.json`: intent, steps, skipped, humanGates.
-4. **Intent retro** — если `intent === "retro"`, выполни `/technical-retro` и **остановись**.
-5. **Старт** — после router:
-   - подтверди `pipeline.json` и `active-task.json`;
-   - **не** пиши lifecycle-поля `status.json` / `metrics.json` сам — их владеет orchestration runtime/hook (см. **agent-artifact-contracts**). Если `status.json` отсутствует, допустим только минимальный bootstrap (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **не** увеличивай `pipelineIndex` вручную;
-   - вызови subagent для `pipeline.steps[0].agent` (slug, пути к артефактам, scope).
-6. **После каждого агента** — дождись hook handoff / reconciliation terminal receipt → `status.state`; не запускай следующий шаг, пока `status.json` не отражает handoff (или пока нет `followup_message` от hook).
-7. **Human gate** — если после текущего шага есть gate в `humanGates` (`after:<agent>`), после завершения агента **остановись** и попроси `/task-continue <slug>` (или `/feature-continue <slug>`).
+1. **Slug** — kebab-case from the description (≤48 characters). Create `.claude/team/tasks/<slug>/` via Write / Edit; runtime/hook owns `status.json` — **do not** rely on Shell `mkdir` as the only way to create the directory.
+2. **Router** — invoke subagent **task-router** with the task description and slug path.
+3. **Plan** — show the user the table from `pipeline.json`: intent, steps, skipped, humanGates.
+4. **Intent retro** — if `intent === "retro"`, run `/technical-retro` and **stop**.
+5. **Start** — after router:
+   - confirm `pipeline.json` and `active-task.json`;
+   - **do not** write lifecycle fields in `status.json` / `metrics.json` yourself — orchestration runtime/hook owns them (see **agent-artifact-contracts**). If `status.json` is missing, only minimal bootstrap is allowed (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **do not** increment `pipelineIndex` manually;
+   - invoke subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
+6. **After each agent** — wait for hook handoff / reconciliation terminal receipt → `status.state`; do not start the next step until `status.json` reflects handoff (or until hook returns `followup_message`).
+7. **Human gate** — if there is a gate in `humanGates` after the current step (`after:<agent>`), **stop** after the agent finishes and ask for `/task-continue <slug>` (or `/feature-continue <slug>`).
 
-## Не делать
+## Do not
 
-- Не вызывать developer до router и (если в pipeline) analyst/architect.
-- Не hardcode порядок ролей — только `pipeline.json`.
-- Не пропускать human gate без явного continue.
+- Invoke developer before router and (if in pipeline) analyst/architect.
+- Hardcode role order — only `pipeline.json`.
+- Skip human gate without explicit continue.
 
-## Если slug занят
+## If slug is taken
 
-- `awaitingHumanGate` / `state: awaiting_approval` → предложи ревью артефактов или `/task-continue <slug>`.
-- `in_progress` → спроси: продолжить или новый slug.
+- `awaitingHumanGate` / `state: awaiting_approval` → offer artifact review or `/task-continue <slug>`.
+- `in_progress` → ask: continue or new slug.
 
 ## Legacy
 
-`/feature-start` и `/feature-continue` остаются совместимыми; для новых задач предпочитай `/task`.
+`/feature-start` and `/feature-continue` remain compatible; for new tasks prefer `/task`.
 
 ## Metrics
 

package/presets/claude/mcp-ts/commands/technical-retro.md

@@ -3,82 +3,82 @@ name: technical-retro
 description: Facilitate a technical retrospective for a period, incident, release, or completed agent-team task slug.
 ---
 
-# Техническое ретро
+# Technical retrospective
 
-Агент выступает как **нейтральный фасилитатор технической ретроспективы**, а не как ревьюер кода или оценщик людей. **Phase 1:** следуй этому command-файлу (skill `technical-retro` — Phase 2, не обязателен).
+The agent acts as a **neutral facilitator of a technical retrospective**, not as a code reviewer or people evaluator. **Phase 1:** follow this command file (skill `technical-retro` is Phase 2, optional).
 
-## Когда включать
+## When to use
 
-- Пользователь просит: «ретро», «техническое ретро», «разбор спринта/итерации», «action items после релиза».
-- После завершения пайплайна команды агентов (`/feature-start` → `/feature-continue`).
-- Есть контекст: период, тема (релиз, инцидент), slug задачи, заметки.
+- User asks: "retro", "technical retro", "sprint/iteration review", "action items after release".
+- After completing the agent-team pipeline (`/feature-start` → `/feature-continue`).
+- Context available: period, topic (release, incident), task slug, notes.
 
-## Входные данные (собрать, не выдумывать)
+## Inputs (gather; do not invent)
 
-Запросить при нехватке:
+Request when missing:
 
-- **Период и фокус**.
-- **Slug задачи** (если ретро по работе команды агентов).
-- **Участники/роли** (если важно).
-- **Ограничения**: время, формат (async vs синхрон).
+- **Period and focus**.
+- **Task slug** (if retro is about agent-team work).
+- **Participants/roles** (if relevant).
+- **Constraints**: time, format (async vs sync).
 
-### Артефакты команды агентов (если есть slug)
+### Agent-team artifacts (if slug present)
 
-Прочитать из репозитория:
+Read from the repository:
 
-- `.cursor/team/tasks/<slug>/pipeline.json`
-- `.cursor/team/tasks/<slug>/brief.md`
-- `.cursor/team/tasks/<slug>/decomposition.md`
-- `.cursor/team/tasks/<slug>/status.json`
-- Git diff / `git status` для изменённых файлов
+- `.claude/team/tasks/<slug>/pipeline.json`
+- `.claude/team/tasks/<slug>/brief.md`
+- `.claude/team/tasks/<slug>/decomposition.md`
+- `.claude/team/tasks/<slug>/status.json`
+- Git diff / `git status` for changed files
 
-Не приписывать факты, которых нет в артефактах, diff или сообщении пользователя.
+Do not attribute facts not present in artifacts, diff, or the user's message.
 
-## Принципы фасилитации
+## Facilitation principles
 
-- **Безопасность**: процесс и система, не «виноватые».
-- **Конкретика**: от абстракций к наблюдаемым событиям.
-- **Баланс**: позитив и зоны роста.
-- **Action items**: владелец и срок у каждого.
-- **Не смешивать с code review** — развести блоки, если запросили оба.
+- **Safety**: process and system, not "blame".
+- **Specificity**: from abstractions to observable events.
+- **Balance**: positives and growth areas.
+- **Action items**: owner and deadline for each.
+- **Do not mix with code review** — separate blocks if both were requested.
 
-## Структура сессии (по умолчанию)
+## Default session structure
 
-1. **Цель и рамки**.
-2. **Сбор фактов**: хорошо / мешало / сюрпризы.
-3. **Группировка тем** (3–7).
-4. **Корневые причины** для 1–2 болезненных тем.
-5. **Эксперименты** (1–3 изменения процесса).
-6. **Action items**: что / владелец / до когда / критерий успеха.
+1. **Goal and scope**.
+2. **Fact gathering**: went well / blocked / surprises.
+3. **Theme grouping** (3–7).
+4. **Root causes** for 1–2 painful themes.
+5. **Experiments** (1–3 process changes).
+6. **Action items**: what / owner / by when / success criteria.
 
-## Блок «Работа агентов» (обязателен при slug)
+## "Agent work" block (required when slug present)
 
-Если ретро связано с пайплайном `/feature-start`:
+If retro is tied to a `/feature-start` pipeline:
 
-| Вопрос | Что фиксировать |
-|--------|-----------------|
-| Router | Ошибка intent, лишние/пропущенные steps в pipeline |
-| Аналитик | Ошибки в assumptions, пропущенные AC, лишние/недостающие таски |
-| Декомпозиция | Неполное покрытие слоёв, неверный порядок, blocked-зависимости |
-| Developer | Scope creep, пропущенные правила, lint/type gaps |
-| Reviewer | Пропущенные дефекты, false positives, качество чеклиста |
-| QA | Покрытие AC тестами, flakiness, пробелы в e2e планах |
+| Question | What to capture |
+|----------|-----------------|
+| Router | Intent error, extra/missing pipeline steps |
+| Analyst | Assumption errors, missed AC, extra/missing tasks |
+| Decomposition | Incomplete layer coverage, wrong order, blocked dependencies |
+| Developer | Scope creep, missed rules, typecheck/test gaps |
+| Reviewer | Missed defects, false positives, checklist quality |
+| QA | AC test coverage, flakiness, contract/unit plan gaps |
 
-**Action items** в этом блоке — на улучшение **промптов, subagents и rules** (не только кода).
+**Action items** in this block — improve **prompts, subagents, and rules** (not only code).
 
-## Формат ответа
+## Response format
 
-- Шапка: период, фокус, slug (если есть), допущения.
-- Повестка по этапам.
-- Блок **«Работа агентов»** (если применимо).
-- Темы — буллеты; спорное — **вопросы команде**.
-- **Action items** в конце.
+- Header: period, focus, slug (if any), assumptions.
+- Agenda by stage.
+- **"Agent work"** block (if applicable).
+- Themes — bullets; disputed points — **questions for the team**.
+- **Action items** at the end.
 
-## Ограничения
+## Constraints
 
-- Не приписывать цитаты и факты без входа.
-- Не выдавать HR‑рекомендации.
-- Если просят только шаблон — **шаблон повестки** без выдуманного контента.
+- Do not attribute quotes or facts without input.
+- No HR recommendations.
+- If only a template is requested — **agenda template** without invented content.
 
 ### Metrics evidence
 

package/presets/claude/mcp-ts/rules/architecture/mcp-server-boundaries.md

@@ -2,7 +2,7 @@
 description: MCP server module boundaries: registration, handler, capability, lifecycle
 ---
 
-# Границы MCP-сервера
+# MCP server boundaries
 
 Dependency direction:
 
@@ -22,7 +22,7 @@ MCP client → transport/entry → registration → schema + handler → scoped
 - auth/config/env → `mcp-auth-secrets` + `security-mcp`
 - After `*.ts` edits → `post-change-test` (+ `mcp-ts-tooling`)
 
-# Требование к агенту
+# Agent requirement
 
 - Keep registration, validation, and handlers separable — avoid a monolithic `index.ts`.
 - Prefer least privilege for every tool capability.