@bonesofspring/ai-rules 0.2.13 → 0.2.15

package/presets/claude/next/CLAUDE.md

@@ -1,6 +1,6 @@
 # Next.js stack — project instructions
 
-Краткая точка входа для Claude Code. Подробные правила — модульные файлы под `rules/` (подпапки по темам).
+Short Claude Code entry point. Detailed rules — modular files under `rules/` (topic subfolders).
 
 **Repo-root agents:** see [`AGENTS.md`](../../AGENTS.md) at the project root (cross-tool setup, commands, security, living conventions pointers).
 
@@ -8,27 +8,27 @@ See @rules/README.md for the full catalog and loading strategy.
 
 ## Conventions
 
-- **Одна тема на файл**; для больших областей — подпапки в `rules/<topic>/`.
-- **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/`.
+- **One topic per file**; for large areas — subfolders under `rules/<topic>/`.
+- **Session-start rules** (no `paths:`) — exactly **three**: `next-app-core`, `package-manager`, `code-quality`.
+- **Domain-specific rules** — YAML frontmatter `paths:` (loaded when matching files are in play); `post-change-lint` — requestable (**required after code edits**); orchestrator and code-review — on-demand.
+- Slash commands — in `commands/`; scenarios — in `skills/`; subagents — in `agents/`.
 
 ## Quick start
 
-| Задача | Куда смотреть |
-|--------|----------------|
-| Любая новая work-задача | `commands/task.md` + `rules/tooling-and-review/agent-team-orchestrator.md` |
-| Новая фича end-to-end | skill `feature-delivery` + `rules/architecture/feature-delivery-workflow.md` |
-| Эталонные фичи | `rules/architecture/reference-features.md` (заполнить TBD в репо) |
-| Стек и слои | `rules/stack/next-app-core.md` |
+| Task | Where to look |
+|------|----------------|
+| Any new work task | `commands/task.md` + `rules/tooling-and-review/agent-team-orchestrator.md` |
+| New end-to-end feature | skill `feature-delivery` + `rules/architecture/feature-delivery-workflow.md` |
+| Reference features | `rules/architecture/reference-features.md` (fill TBD in the repo) |
+| Stack and layers | `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` (**requestable**, обязателен после edits) |
-| Валидация перед review | agent `build-verifier` |
+| A11y while coding UI | `rules/ui-and-accessibility/react-a11y-coding.md` |
+| After code edits | `rules/tooling-and-review/post-change-lint.md` (**requestable**, required after edits) |
+| Validation before review | agent `build-verifier` |
 | Code review MR | skill `code-review` + `rules/tooling-and-review/code-review-mr.md` |
 | Security (auth/forms/env) | `rules/tooling-and-review/security-next.md` + agent `security-reviewer` |
-| Как работает X | agent `codebase-analyzer` (explain-as-is; без `/task`) |
-| Техническое ретро | `commands/technical-retro.md` + skill `technical-retro` |
+| How X works | agent `codebase-analyzer` (explain-as-is; without `/task`) |
+| Technical retro | `commands/technical-retro.md` + skill `technical-retro` |
 
 ## Install
 
@@ -36,4 +36,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/**`, `MCP.md` в `.claude/`, плюс `mcp.json` → **`.mcp.json`** и `REPO_AGENTS.md` → корневой **`AGENTS.md`**. Skills: `write-adr`, `react-performance` (on-demand).
+Copies `CLAUDE.md`, `rules/**`, `commands/**`, `agents/**`, `hooks/**`, `team/**`, `MCP.md` into `.claude/`, plus `mcp.json` → **`.mcp.json`** and `REPO_AGENTS.md` → root **`AGENTS.md`**. Skills: `write-adr`, `react-performance` (on-demand).

package/presets/claude/next/MCP.md

@@ -1,16 +1,16 @@
 # MCP (preset `next`, Claude Code)
 
-Копируется в **корень проекта** как `.mcp.json` при `ai-rules init claude --preset next` (не в `.claude/` — так устроен project scope Claude Code).
+Copied to the **project root** as `.mcp.json` on `ai-rules init claude --preset next` (not under `.claude/` — that is how Claude Code project scope works).
 
 ## Servers
 
-| Name | Package | Зачем |
-|------|---------|--------|
-| `context7` | `@upstash/context7-mcp` | Актуальная документация Next/React/TS |
-| `playwright-test` | `@playwright/mcp` | Browser MCP; имя сервера совпадает с `mcp__playwright-test__*` в agents |
+| Name | Package | Purpose |
+|------|---------|---------|
+| `context7` | `@upstash/context7-mcp` | Up-to-date Next/React/TS docs |
+| `playwright-test` | `@playwright/mcp` | Browser MCP; server name matches `mcp__playwright-test__*` in agents |
 | `chrome-devtools` | `chrome-devtools-mcp` | Live DOM/network/performance |
-| `figma` | remote `https://mcp.figma.com/mcp` | Design context → код; OAuth при первом подключении |
+| `figma` | remote `https://mcp.figma.com/mcp` | Design context → code; OAuth on first connect |
 
-Секреты не коммитим. Опционально: `CONTEXT7_API_KEY`. Figma — OAuth (токен в файл не пишем). После clone/init Claude Code попросит approve project MCP (`/mcp`).
+Do not commit secrets. Optional: `CONTEXT7_API_KEY`. Figma — OAuth (do not write the token to a file). After clone/init Claude Code will ask to approve project MCP (`/mcp`).
 
-Для полного Playwright Test Agents loop (`planner_*` / `generator_*` / `test_*`) дополнительно: `npx playwright init-agents --loop=claude` в приложении с `@playwright/test`.
+For the full Playwright Test Agents loop (`planner_*` / `generator_*` / `test_*`) additionally: `npx playwright init-agents --loop=claude` in an app with `@playwright/test`.

package/presets/claude/next/README.md

@@ -1,37 +1,37 @@
 # Preset `next` (Claude Code)
 
-Структура отличается от пресета Cursor: здесь повторяется типичный **layout проекта Claude Code** под `.claude/`, а не плоский список `.mdc` в `rules/`.
+Layout differs from the Cursor preset: here the typical **Claude Code project layout** under `.claude/` is mirrored, not a flat `.mdc` list in `rules/`.
 
-| В пресете | Куда копирует `ai-rules init claude --preset next` |
-|-----------|-----------------------------------------------------|
-| `CLAUDE.md` | `.claude/CLAUDE.md` (точка входа, грузится в начале сессии) |
-| `rules/**` | `.claude/rules/**` (рекурсивно: подпапки по темам, см. [документацию](https://code.claude.com/docs/en/memory#organize-rules-with-clauderules)) |
+| In the preset | Where `ai-rules init claude --preset next` copies |
+|---------------|---------------------------------------------------|
+| `CLAUDE.md` | `.claude/CLAUDE.md` (entry point, loaded at session start) |
+| `rules/**` | `.claude/rules/**` (recursive: topic subfolders; see [docs](https://code.claude.com/docs/en/memory#organize-rules-with-clauderules)) |
 | `commands/**` | `.claude/commands/**` |
-| `skills/**` | `.claude/skills/**` (если папка есть) |
-| `agents/**` | `.claude/agents/**` (если папка есть) |
-| `hooks/**` | `.claude/hooks/**` (если папка есть) |
-| `team/**` | `.claude/team/**` (шаблон артефактов agent team) |
-| `mcp.json` | **`.mcp.json`** в корне проекта (Claude project MCP) |
+| `skills/**` | `.claude/skills/**` (if present) |
+| `agents/**` | `.claude/agents/**` (if present) |
+| `hooks/**` | `.claude/hooks/**` (if present) |
+| `team/**` | `.claude/team/**` (agent-team artifact template) |
+| `mcp.json` | **`.mcp.json`** at project root (Claude project MCP) |
 | `MCP.md` | `.claude/MCP.md` |
 
-Файлы правил — обычный Markdown с опциональным YAML frontmatter (`paths:` для скоупа по путям), не формат `.mdc` Cursor.
+Rule files are ordinary Markdown with optional YAML frontmatter (`paths:` for path scope), not Cursor `.mdc`.
 
 ## Preset taxonomy & contributing
 
 - **Layers:** Core → Stack → Platform — [`../../_shared/README.md`](../../_shared/README.md)
 - **Contribution guide:** [`../../docs/PRESET-CONTRIBUTION.md`](../../docs/PRESET-CONTRIBUTION.md)
-- **Cursor SoT:** `presets/cursor/next/` — этот пресет derived twin; правки Cursor first, same PR
+- **Cursor SoT:** `presets/cursor/next/` — this preset is the derived twin; edit Cursor first, same PR
 - **Cursor→Claude map + core table:** [`rules/README.md`](./rules/README.md)
 - **Author meta:** `tooling-and-review/preset-*.md` (`paths:` on `packages/ai-rules/presets/**` only)
 
 ## Agent team workflow
 
-Cursor-пресет и Claude-пресет используют один и тот же смысловой workflow:
+The Cursor and Claude presets share the same workflow intent:
 
 - `/task <desc>` → `task-router` → `pipeline.json`;
-- `/task-continue <slug>` → продолжение после human gate;
-- `.claude/agents/*.md` → **22** ролей: planning (router, analyst, architect, migration, api-contract), analysis (`codebase-analyzer`), implementation (debugger, ci-investigator, developer), review (code, a11y, security, perf), testing (QA, unit trio, playwright trio), docs (tech-writer), build (build-verifier);
-- `.claude/team/tasks/<slug>/` → handoff-артефакты (`brief.md`, `decomposition.md`, `review.md`, `migration-plan.md`, `ci-report.md`, `status.json`, …).
+- `/task-continue <slug>` → continue after a human gate;
+- `.claude/agents/*.md` → **22** roles: planning (router, analyst, architect, migration, api-contract), analysis (`codebase-analyzer`), implementation (debugger, ci-investigator, developer), review (code, a11y, security, perf), testing (QA, unit trio, playwright trio), docs (tech-writer), build (build-verifier);
+- `.claude/team/tasks/<slug>/` → handoff artifacts (`brief.md`, `decomposition.md`, `review.md`, `migration-plan.md`, `ci-report.md`, `status.json`, …).
 
 ## Cross-tool root AGENTS
 

package/presets/claude/next/agents/README.md

@@ -1,44 +1,44 @@
 # `.claude/agents` (preset next)
 
-Специализированные подагенты (personas) — по [документации Claude Code](https://code.claude.com/docs), если используете их в проекте.
+Specialized subagents (personas) — per [Claude Code documentation](https://code.claude.com/docs), when used in the project.
 
 ## Planning and routing
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | Router | `task-router.md` | no |
-| Аналитик | `task-analyst.md` | no |
-| Архитектор | `solution-architect.md` | no |
+| Analyst | `task-analyst.md` | no |
+| Architect | `solution-architect.md` | no |
 | Migration planner | `migration-specialist.md` | no |
 | API contract reviewer | `api-contract-reviewer.md` | no |
 
 ## Analysis (on-demand)
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | Codebase analyzer | `codebase-analyzer.md` | no (explain-as-is only) |
 
 ## Implementation and CI
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | Debugger | `debugger.md` | minimal fix only |
 | CI investigator | `ci-investigator.md` | minimal CI fix only |
 | Build verifier | `build-verifier.md` | no |
-| Разработчик | `feature-developer.md` | yes |
+| Developer | `feature-developer.md` | yes |
 
 ## Review specialists
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
-| Ревьюер | `code-reviewer.md` | no |
+| Reviewer | `code-reviewer.md` | no |
 | A11y reviewer | `accessibility-reviewer.md` | no |
 | Security reviewer | `security-reviewer.md` | no |
 | Performance auditor | `performance-auditor.md` | no |
 
 ## Testing
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | QA | `qa-tester.md` | tests only |
 | Unit planner | `unit-test-planner.md` | no |
@@ -50,15 +50,15 @@
 
 ## Documentation
 
-| Agent | Файл | Production-код |
+| Agent | File | Production code |
 |-------|------|----------------|
 | Tech writer | `tech-writer.md` | docs only |
 
-Папка копируется в `.claude/agents/` при `ai-rules init claude --preset next`.
+The folder is copied to `.claude/agents/` on `ai-rules init claude --preset next`.
 
 ## Model matrix (frontmatter `model`)
 
-SoT по умолчанию — YAML `model` в каждом agent-файле. Опциональный `steps[].model` (`cheap` \| `standard` \| `strong`) переопределяет тир на шаге (см. `task-router.md`, `tooling-and-review/agent-team-orchestrator.md`).
+Default SoT — YAML `model` in each agent file. Optional `steps[].model` (`cheap` \| `standard` \| `strong`) overrides tier per step (see `task-router.md`, `tooling-and-review/agent-team-orchestrator.md`).
 
 | Tier | Default frontmatter | Agents |
 |------|---------------------|--------|
@@ -72,15 +72,15 @@ SoT по умолчанию — YAML `model` в каждом agent-файле.
 - Resolution order (Claude Code): env `CLAUDE_CODE_SUBAGENT_MODEL` → per-invocation `model` → frontmatter → parent session.
 - Never put `strong` on `build-verifier` / `tech-writer` / `task-router`.
 
-## Оркестрация
+## Orchestration
 
-| Command | Назначение |
+| Command | Purpose |
 |---------|------------|
-| `/task <desc>` | Router → dynamic pipeline → первый agent |
-| `/task-continue <slug>` | После human gate |
-| `/feature-start`, `/feature-continue` | Legacy (совместимость) |
+| `/task <desc>` | Router → dynamic pipeline → first agent |
+| `/task-continue <slug>` | After human gate |
+| `/feature-start`, `/feature-continue` | Legacy (compatibility) |
 
-Правило: `tooling-and-review/agent-team-orchestrator.md`. План: `pipeline.json` в `.claude/team/tasks/<slug>/`.
+Rule: `tooling-and-review/agent-team-orchestrator.md`. Plan: `pipeline.json` in `.claude/team/tasks/<slug>/`.
 
 ## Pipeline routing
 

package/presets/claude/next/agents/build-verifier.md

@@ -35,14 +35,14 @@ When validating **preset packaging** changes (paths under `packages/ai-rules/pre
 2. **Leakage (next):** hooks/agents must not require `xcuitest-test-*` handoffs or `xcodebuild` as the default Next post-change gate. See `tooling-and-review/preset-no-cross-stack-leakage.md`.
 3. **Mapping / README:** `rules/README.md` must include a Cursor→Claude mapping table; document core→stack mapping when `_shared` consumers exist.
 4. **shared-core consumers:** if `_shared/core/**` changed, every file with matching `<!-- shared-core: … -->` in this PR must be updated (or intentional fork documented).
-5. **Twin presence:** Cursor rule change without Claude twin same PR → **FAIL** (next, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel). Domain twin body ≥15 lines; thin aliases may be shorter.
+5. **Twin presence:** Cursor rule change without Claude twin same PR → **FAIL** (next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel). Domain twin body ≥15 lines; thin aliases may be shorter.
 6. **Session-start body budget:** sum body lines of the **3** intended session-start rules ≤ **140** (stretch ≤120); do **not** include `**/README.md` — record in validation-report; FAIL if grossly over.
 7. **Embed drift (hard in `check:preset-structure`):** run `packages/ai-rules/scripts/check-shared-core-drift.sh` with `AI_RULES_DRIFT_FAIL=1` (bundled by the structure orchestrator). Lineage stems excluded from body equality.
 8. **Dogfood (monorepo soft):** prefer `packages/ai-rules/scripts/sync-dogfood-cursor.sh`; mass dogfood deletion without migration doc → risk / FAIL for maintainers.
 
-9. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java|mcp-ts|php-hexagonal|php-laravel`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
+9. **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.
 10. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
-11. **No react-performance on ios/go/java:** skill directory / required handoff must be absent under ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel → **FAIL** (leakage). Prefer `check:preset-leakage`.
+11. **Performance skill by stack:** next → `react-performance`; nuxt → `vue-performance`. **No react-performance/vue-performance on ios/go/java:** skill directory / required handoff must be absent under ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel → **FAIL** (leakage). Prefer `check:preset-leakage`.
 12. **Rule eval (WARN):** `scripts/check-rule-eval.mjs` / `yarn check:rule-eval` should exist for maintainers; smoke optional. Hard fail only when the opt-in eval job runs — not part of default `check:preset-structure`.
 
 ### Soft notes

package/presets/claude/next/agents/feature-developer.md

@@ -16,7 +16,7 @@ You are a senior frontend developer working in a Next.js monorepo with strict la
 ## Task execution rules
 
 - Work tasks in dependency order (types → api → mocks → store → ui → **unit** → e2e).
-- **Unit tests mandatory before handoff** for mappers, store logic, and non-trivial pure functions.
+- **Unit tests must run before handoff** for mappers, store logic, and non-trivial pure functions.
 - Mark completed tasks in `decomposition.md`.
 - Validation: **`rules/tooling-and-review/post-change-lint.md`**. If pipeline next step is **`build-verifier`**, scoped lint/type-check on **changed files** is enough; full project lint is build-verifier's job.
 

package/presets/claude/next/agents/task-analyst.md

@@ -8,7 +8,7 @@ You are a senior business/technical analyst for a Next.js frontend team.
 
 Your job is to reach **Definition of Ready (DoR)** before any implementation starts. You may write only `.claude/team/**` artifacts. You do **not** write production code or modify application source files.
 
-## Clarification cycle (mandatory)
+## Clarification cycle (must)
 
 1. Rephrase the task in your own words (goal, user value, boundaries).
 2. Ask **1–3 questions per iteration** — never more than 3 at once.

package/presets/claude/next/agents/task-router.md

@@ -16,20 +16,20 @@ You are a task router for a Next.js frontend agent team. You **do not** implemen
 
 | intent | Signals in prompt | Default steps |
 |--------|-------------------|---------------|
-| `feature` | «добавь», «новая», «реализуй», «сделай», new UI/API/store | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or playwright trio |
-| `bugfix` | «баг», «fix», «не работает», «падает», «ошибка», regression | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer → qa-tester (regression) |
-| `ci-fix` | «CI», «упал пайплайн», «красный PR», «failing check», «lint в CI» | ci-investigator → feature-developer (skipIf ci-investigator.resolved) → build-verifier → code-reviewer |
-| `migration` | «миграция», «upgrade», «обнови Next», «переход на», major version | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer → qa-tester (regression) |
-| `perf-audit` | «производительность», «perf», «bundle», «LCP», «медленно», «waterfall» | performance-auditor |
-| `a11y` | «a11y», «доступность», «accessibility», «WCAG», «screen reader», «клавиатура» | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
-| `review-only` | «ревью», «review MR», «проверь diff», «code review» | code-reviewer |
-| `test-only` | «покрой тестами», «напиши тесты» (mixed unit+e2e, no impl) | task-analyst → qa-tester |
-| `unit-only` | «unit», «юнит», «mapper tests», «покрой маппер», «почини unit» | unit-test-planner → unit-test-generator, or unit-test-healer |
-| `e2e-only` | «e2e», «playwright», «browser test», «сценарии e2e», «почини e2e» | playwright-test-planner → playwright-test-generator, or playwright-test-healer |
-| `docs-only` | «документация», «README», «changelog», «ADR», «migration guide» | task-analyst → tech-writer |
-| `refactor` | «рефакторинг», «без изменения поведения», «почисти» | task-analyst → feature-developer → build-verifier → code-reviewer |
-| `spike` | «исследуй», «оцени», «можно ли», «spike», proof of concept | task-analyst → solution-architect |
-| `retro` | «ретро», «разбор», «postmortem» | (no pipeline — orchestrator runs `/technical-retro`) |
+| `feature` | «добавь» (add), «новая» (new), «реализуй» (implement), «сделай» (build), new UI/API/store <!-- i18n-keep: E4 --> | task-analyst → feature-developer (unit-in-dev) → build-verifier → code-reviewer → qa-tester (e2e-only) or playwright trio |
+| `bugfix` | «баг» (bug), «fix», «не работает» (doesn't work), «падает» (crashes), «ошибка» (error), regression <!-- i18n-keep: E4 --> | debugger → feature-developer (skipIf debugger.fixed) → build-verifier → code-reviewer → qa-tester (regression) |
+| `ci-fix` | «CI», «упал пайплайн» (pipeline failed), «красный PR» (red PR), «failing check», «lint в CI» (lint in CI) <!-- i18n-keep: E4 --> | ci-investigator → feature-developer (skipIf ci-investigator.resolved) → build-verifier → code-reviewer |
+| `migration` | «миграция» (migration), «upgrade», «обнови Next» (upgrade Next), «переход на» (move to), major version <!-- i18n-keep: E4 --> | task-analyst → migration-specialist → feature-developer → build-verifier → code-reviewer → qa-tester (regression) |
+| `perf-audit` | «производительность» (performance), «perf», «bundle», «LCP», «медленно» (slow), «waterfall» <!-- i18n-keep: E4 --> | performance-auditor |
+| `a11y` | «a11y», «доступность» (accessibility), «accessibility», «WCAG», «screen reader», «клавиатура» (keyboard) <!-- i18n-keep: E4 --> | task-analyst → feature-developer → build-verifier → accessibility-reviewer → code-reviewer |
+| `review-only` | «ревью» (review), «review MR», «проверь diff» (check diff), «code review» <!-- i18n-keep: E4 --> | code-reviewer |
+| `test-only` | «покрой тестами» (add tests), «напиши тесты» (write tests) (mixed unit+e2e, no impl) <!-- i18n-keep: E4 --> | task-analyst → qa-tester |
+| `unit-only` | «unit», «юнит» (unit), «mapper tests», «покрой маппер» (cover mapper), «почини unit» (fix unit) <!-- i18n-keep: E4 --> | unit-test-planner → unit-test-generator, or unit-test-healer |
+| `e2e-only` | «e2e», «playwright», «browser test», «сценарии e2e» (e2e scenarios), «почини e2e» (fix e2e) <!-- i18n-keep: E4 --> | playwright-test-planner → playwright-test-generator, or playwright-test-healer |
+| `docs-only` | «документация» (documentation), «README», «changelog», «ADR», «migration guide» <!-- i18n-keep: E4 --> | task-analyst → tech-writer |
+| `refactor` | «рефакторинг» (refactor), «без изменения поведения» (no behavior change), «почисти» (clean up) <!-- i18n-keep: E4 --> | task-analyst → feature-developer → build-verifier → code-reviewer |
+| `spike` | «исследуй» (investigate), «оцени» (estimate), «можно ли» (is it possible), «spike», proof of concept <!-- i18n-keep: E4 --> | task-analyst → solution-architect |
+| `retro` | «ретро» (retro), «разбор» (postmortem), «postmortem» <!-- i18n-keep: E4 --> | (no pipeline — orchestrator runs `/technical-retro`) |
 
 ## Pipeline profiles
 
@@ -39,9 +39,9 @@ Set optional top-level `"profile": "full" | "standard" | "light"` in `pipeline.j
 |---------|------|------------------------|
 | `full` | Multi-layer, new public API, e2e coverage needed, incomplete AC | analyst → [architect] → developer → build-verifier → reviewer → qa-tester |
 | `standard` | Single layer, default work | analyst → developer → build-verifier → reviewer |
-| `light` | Trivial: one file/layer, explicit AC, «просто поправь», «typo», user «без pipeline» | developer → build-verifier |
+| `light` | Trivial: one file/layer, explicit AC, «просто поправь» (just fix it), «typo», user «без pipeline» (no pipeline) <!-- i18n-keep: E4 --> | developer → build-verifier |
 
-**Light signals:** один файл, один слой, явный AC в промпте, нет архитектурного риска. **Never skip `build-verifier`** after developer when `app/**` changed. **Skip `code-reviewer`** in light only for non-prod preset/docs tasks — for `app/src` changes prefer standard.
+**Light signals:** one file, one layer, explicit AC in prompt, no architectural risk. **Never skip `build-verifier`** after developer when `app/**` changed. **Skip `code-reviewer`** in light only for non-prod preset/docs tasks — for `app/src` changes prefer standard.
 
 **Light by intent:**
 

package/presets/claude/next/commands/README.md

@@ -1,13 +1,13 @@
 # `.claude/commands` (preset next)
 
-Определения slash-команд и on-demand сценариев. Копируются в `.claude/commands/` при `ai-rules init claude --preset next`.
+Slash-command definitions and on-demand scenarios. Copied to `.claude/commands/` on `ai-rules init claude --preset next`.
 
-| Файл | Назначение |
-|------|------------|
-| `task.md` | Единая точка входа: router → dynamic pipeline → первый agent |
-| `task-continue.md` | Продолжение после human gate / паузы по `pipeline.json` |
-| `feature-start.md` | Legacy analyst-only старт без router |
-| `feature-continue.md` | Legacy продолжение; для `pipeline.json` делегирует смысл `/task-continue` |
-| `technical-retro.md` | Фасилитация технического ретро, включая блок «Работа агентов» |
+| File | Purpose |
+|------|---------|
+| `task.md` | Single entry: router → dynamic pipeline → first agent |
+| `task-continue.md` | Resume after human gate / pause via `pipeline.json` |
+| `feature-start.md` | Legacy analyst-only start without router |
+| `feature-continue.md` | Legacy continue; for `pipeline.json` delegates to `/task-continue` semantics |
+| `technical-retro.md` | Technical retro facilitation, including the “Agent work” block |
 
-См. также корневой `README.md` пресета — у Claude Code помимо `rules/` и `commands/` используются `skills/`, `agents/`, `hooks/`, `team/`.
+See also the preset root `README.md` — Claude Code uses `skills/`, `agents/`, `hooks/`, `team/` in addition to `rules/` and `commands/`.

package/presets/claude/next/commands/feature-continue.md

@@ -3,25 +3,25 @@ name: feature-continue
 description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
 ---
 
-# Feature continue — продолжение после утверждения brief
+# Feature continue — resume after brief approval
 
-Legacy-команда для продолжения после human gate. Для новых пайплайнов с `pipeline.json` используй те же правила, что в `/task-continue`.
+Legacy command to continue after a human gate. For new pipelines with `pipeline.json`, use the same rules as `/task-continue`.
 
-## Аргументы
+## Arguments
 
-`<slug>` — идентификатор задачи из `.claude/team/tasks/<slug>/`.
+`<slug>` — task id under `.claude/team/tasks/<slug>/`.
 
 ## Preconditions
 
-1. Прочитай `.claude/team/tasks/<slug>/brief.md` и `decomposition.md`.
-2. Если есть `pipeline.json`, делегируй поведение `/task-continue <slug>`.
-3. Если `pipeline.json` нет, прочитай `status.json`. Продолжай только если:
+1. Read `.claude/team/tasks/<slug>/brief.md` and `decomposition.md`.
+2. If `pipeline.json` exists, delegate behavior to `/task-continue <slug>`.
+3. If there is no `pipeline.json`, read `status.json`. Continue only if:
    - `phase` is `analysis` and `state` is `awaiting_approval` (user explicitly approved via this command), **or**
    - `phase` is `development`/`review`/`testing` and work should resume.
 
-## Legacy алгоритм без `pipeline.json`
+## Legacy algorithm without `pipeline.json`
 
-1. Обнови `status.json`:
+1. Update `status.json`:
    ```json
    {
      "slug": "<slug>",
@@ -30,22 +30,22 @@ Legacy-команда для продолжения после human gate. Дл
      "updatedAt": "<ISO8601>"
    }
    ```
-   Затем сразу установи `"state": "in_progress"` перед вызовом developer.
+   Then immediately set `"state": "in_progress"` before calling the developer.
 
-2. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+2. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
 
-3. Вызови subagent **feature-developer** с контекстом:
-   - пути к `brief.md`, `decomposition.md`, `status.json`;
-   - указание следовать `rules/architecture/feature-delivery-workflow.md`.
+3. Call subagent **feature-developer** with context:
+   - paths to `brief.md`, `decomposition.md`, `status.json`;
+   - instruction to follow `rules/architecture/feature-delivery-workflow.md`.
 
-4. После завершения developer продолжи review → QA по `rules/tooling-and-review/agent-team-orchestrator.md`.
+4. After the developer finishes, continue review → QA per `rules/tooling-and-review/agent-team-orchestrator.md`.
 
-## Если review вернул changes_requested
+## If review returned changes_requested
 
-- Верни `phase` в `development`, `state` в `in_progress`.
-- Снова вызови **feature-developer** с списком правок от reviewer.
+- Set `phase` back to `development`, `state` to `in_progress`.
+- Call **feature-developer** again with the reviewer’s change list.
 
-## Не делать
+## Do not
 
-- Не пропускать human gate без явного `/feature-continue`.
-- Не совмещать роли developer и reviewer в одном subagent-вызове.
+- Skip the human gate without an explicit `/feature-continue`.
+- Combine developer and reviewer roles in one subagent call.

package/presets/claude/next/commands/feature-start.md

@@ -3,28 +3,28 @@ name: feature-start
 description: Legacy analyst-only feature intake. Prefer /task for new work because it uses router and dynamic pipeline.
 ---
 
-# Feature start — legacy команда агентов
+# Feature start — legacy agent command
 
-Запуск **фазы анализа** для новой задачи. Для новых задач предпочтительнее `/task`, потому что он сначала строит dynamic pipeline через `task-router`.
+Starts the **analysis phase** for a new task. For new work, prefer `/task` because it builds a dynamic pipeline via `task-router` first.
 
-## Что делать
+## What to do
 
-1. Извлеки описание задачи из аргументов команды (всё после `/feature-start`).
-2. Сгенерируй **slug** (kebab-case, до 48 символов) из заголовка задачи.
-3. Создай `.claude/team/tasks/<slug>/` если его ещё нет — через запись файла (Write / Edit), не через Shell `mkdir`.
-4. Запиши `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Вызови subagent **task-analyst** с полным описанием задачи и путём к артефактам.
-6. Дождись завершения аналитика. **Не вызывай 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 — via Write / Edit, not Shell `mkdir`.
+4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
+5. Invoke subagent **task-analyst** with the full task description and artifact paths.
+6. Wait for the analyst to finish. **Do not invoke developer** at this stage.
 
 ## Human gate
 
-После аналитика:
+After the analyst:
 
-- Покажи пользователю ссылки на `brief.md` и `decomposition.md`.
-- Попроси проверить и утвердить или прислать правки.
-- Для продолжения: `/feature-continue <slug>` или `/task-continue <slug>`.
+- Show the user links to `brief.md` and `decomposition.md`.
+- Ask them to review and approve or send edits.
+- To continue: `/feature-continue <slug>` or `/task-continue <slug>`.
 
-## Если slug уже существует
+## If slug already exists
 
-- Если `status.json` в `awaiting_approval` — предложи ревью или `/feature-continue`.
-- Если задача в работе — спроси, продолжать или начать новый slug.
+- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
+- If the task is in progress — ask whether to continue or start a new slug.

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