@bonesofspring/ai-rules 0.1.42 → 0.2.0

package/presets/claude/next/rules/ui-and-accessibility/css-property-order.md

@@ -1,26 +1,14 @@
 ---
 paths:
-  - app/src/**/*.{css,ts,tsx}
+  - app/src/ui/**/*.styles.ts
+  - app/src/ui/**/*.styles.tsx
+  - app/src/ui/**/styles.ts
+  - app/src/ui/**/styles.tsx
   - app/**/*.css
 ---
 
 # Порядок CSS-свойств (как в Stylelint)
 
-Действует для **любого** CSS в репозитории: `.css`, стилевые блоки в `styles.ts` / `styles.tsx`, `styled` / Linaria и другой CSS-in-JS в `.ts` / `.tsx`, если этот код попадает под `lint:css`.
+Порядок свойств — как в **`app/.stylelintrc`** (`stylelint-config-idiomatic-order`). Не дублировать список вручную.
 
-Источник: `app/.stylelintrc` → `@sh/stylelint-config-react` → пакет **`stylelint-config-idiomatic-order`** (правило `order/properties-order`). Свойства, не попавшие в список, идут **в конце блока в алфавитном порядке** (`unspecified: bottomAlphabetical`).
-
-Пиши объявления в **одном** блоке в такой последовательности групп:
-
-1. **`composes`** — только для CSS Modules (если есть).
-2. **`all`**
-3. **Позиционирование:** `position`, `z-index`, затем `top`, `right`, `bottom`, `left`.
-4. **Отображение и раскладка:** `display`, `overflow`.
-5. **Размеры:** `width`, `min-width`, `max-width`, `height`, `min-height`, `max-height`, `box-sizing`.
-6. **Flex:** `flex`, `flex-basis`, `flex-direction`, `flex-flow`, `flex-grow`, `flex-shrink`, `flex-wrap`, `align-content`, `align-items`, `align-self`, `justify-content`, `order`.
-7. **Внутренние отступы:** `padding-top`, `padding-right`, `padding-bottom`, `padding-left`.
-8. **Рамка:** общие `border`, `border-width`, `border-style`, `border-color`, `border-radius`; затем для сторон **сверху по часовой** — `border-top` и его `-width`, `-style`, `-color`, `-radius`, то же для `right`, `bottom`, `left`.
-9. **Внешние отступы:** `margin-top`, `margin-right`, `margin-bottom`, `margin-left`.
-10. **Остальные свойства** — после перечисленных, **по алфавиту** (типографика, фон, анимации, `cursor`, и т.д.).
-
-Автоисправление из каталога `app`: `lint:css --fix` (проверяет `**/*.{css,ts}`; менеджер пакетов — `tooling-and-review/package-manager.md`).
+Автоисправление из `app/`: **`lint:css --fix`**. Полный прогон — **`tooling-and-review/post-change-lint.md`**.

package/presets/claude/next/rules/ui-and-accessibility/react-ui.md

@@ -72,7 +72,7 @@ paths:
 - **Не передавать пропы в компоненты через spread** (`<Foo {...x} />`). Только явные атрибуты; подробности — `ui-and-accessibility/no-props-spread.md` (в `app/src/ui` это дополнительно ловит ESLint).
 - Описывать пропсы через `type Props = { ... }` или `interface Props { ... }`.
 - Не использовать `any`; при необходимости — обобщения (`<T>`), `unknown`, type guards.
-- Для доменных сущностей использовать типы из `@/types` (и enum из `@/types/enums`), а не описывать их заново (`architecture/types-public-imports.md`).
+- Для доменных сущностей использовать типы из `@/types` (и enum из `@/types/enums`), а не описывать их заново (`architecture/public-imports.md`).
 
 # Логика и side effects
 

package/presets/claude/next/skills/feature-delivery/SKILL.md

@@ -5,26 +5,11 @@ description: Delivers Next.js frontend features end-to-end across domain types,
 
 # Feature Delivery
 
-## Workflow
-
-1. Read the task brief, acceptance criteria, and decomposition if present.
-2. Read **`architecture/reference-features.md`** and mirror the closest reference feature.
-3. Work in layer order: types -> API -> store -> UI -> **unit tests** -> e2e (if in scope).
-4. Keep DTOs out of UI/store; expose domain types through `@/types` and API calls through `@/api`.
-5. Prefer small, reviewable edits; update barrels when adding public symbols.
-6. Add or update focused tests for changed behavior.
-7. Run project validation from `app/`: `lint:js`, `lint:css`, and `type-check` when TypeScript changed.
-
-## Rule Map
-
-- Core stack and layers: `rules/stack/next-app-core.md`, `rules/architecture/architecture-boundaries.md`.
-- Data/API: `rules/api-and-data/http-client.md`, `rules/api-and-data/api-services.md`, `rules/api-and-data/store-rtk.md`.
-- Public imports: `rules/architecture/types-public-imports.md`, `rules/architecture/api-public-imports.md`, `rules/architecture/layer-barrel-exports.md`.
-- UI: `rules/ui-and-accessibility/react-ui.md`, `react-a11y-coding.md`, `no-props-spread.md`, `component-styles.md`.
-- App Router: `rules/stack/next-app-router.md`.
-- Tests: `rules/testing/tests-unit.md`, `rules/testing/tests-e2e-structure.md`, `rules/testing/playwright-agents.md`.
-- Finish: `rules/tooling-and-review/post-change-lint.md`, `rules/tooling-and-review/package-manager.md`.
+1. Read task brief, acceptance criteria, and decomposition if present.
+2. Read **`rules/architecture/feature-delivery-workflow.md`** and **`rules/architecture/reference-features.md`** — follow layer order and mirror closest reference feature.
+3. Add or update focused tests for changed behavior.
+4. Validation from `app/`: see **`rules/tooling-and-review/post-change-lint.md`** (pipeline: scoped lint OK if next step is `build-verifier`).
 
 ## Handoff
 
-Summarize completed work by layer, validation results, and known gaps. If this is part of an agent team task, update `.claude/team/tasks/<slug>/status.json`.
+Summarize by layer, validation results, and known gaps. Agent team: update `.claude/team/tasks/<slug>/status.json`.

package/presets/cursor/next/AGENTS.md

@@ -8,7 +8,7 @@ See `.cursor/rules/README.md` for the full catalog and loading strategy.
 
 | Задача | Куда смотреть |
 |--------|----------------|
-| Любая новая work-задача | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` |
+| Любая новая work-задача | `/task` → `commands/task.md` + `agent-team-orchestrator.mdc` (+ `agent-team-intake.mdc` on-demand) |
 | Новая фича end-to-end | skill `feature-delivery` + `feature-delivery-workflow.mdc` |
 | Стек и слои | `next-app-core.mdc` |
 | Эталонные фичи | `reference-features.mdc` (заполнить пути в репо) |

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

@@ -75,3 +75,84 @@
 | `docs-only` | analyst → tech-writer |
 
 Опциональные шаги (router добавляет по контексту): `api-contract-reviewer`, `accessibility-reviewer`, `security-reviewer`, `performance-auditor`, `tech-writer`.
+
+## pipeline.json reference
+
+### Step fields
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `agent` | yes | Subagent name (kebab-case) or array for `parallel: true` |
+| `label` | yes | Short human-readable step name |
+| `scope` | no | e.g. `unit-in-dev`, `e2e-only`, `regression`, `full` |
+| `skipIf` | no | `debugger.fixed` \| `ci-investigator.resolved` |
+| `parallel` | no | When `true` and `agent` is array — invoke all in one turn |
+
+### Minimal template
+
+```json
+{
+  "slug": "<slug>",
+  "intent": "feature",
+  "summary": "One-line task summary",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify and decompose" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Lint, type-check, unit smoke" },
+    { "agent": "code-reviewer", "label": "Code review" }
+  ],
+  "humanGates": ["after:task-analyst"],
+  "autoChain": true,
+  "skipped": []
+}
+```
+
+### Example: parallel reviewers
+
+```json
+{
+  "intent": "feature",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify" },
+    { "agent": "feature-developer", "label": "Implement", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate" },
+    {
+      "agent": ["accessibility-reviewer", "security-reviewer"],
+      "parallel": true,
+      "label": "A11y and security"
+    },
+    { "agent": "code-reviewer", "label": "Review" }
+  ],
+  "humanGates": ["after:task-analyst"]
+}
+```
+
+### Example: bugfix skipIf
+
+```json
+{
+  "intent": "bugfix",
+  "steps": [
+    { "agent": "debugger", "label": "Root cause" },
+    { "agent": "feature-developer", "label": "Fix if needed", "skipIf": "debugger.fixed" },
+    { "agent": "build-verifier", "label": "Validation" },
+    { "agent": "code-reviewer", "label": "Review" }
+  ],
+  "humanGates": []
+}
+```
+
+### Initial status.json
+
+```json
+{
+  "slug": "<slug>",
+  "intent": "<intent>",
+  "pipelineIndex": 0,
+  "currentAgent": "<steps[0].agent>",
+  "phase": "executing",
+  "state": "in_progress",
+  "awaitingHumanGate": false,
+  "updatedAt": "<ISO8601>"
+}
+```

package/presets/cursor/next/agents/api-contract-reviewer.md

@@ -13,7 +13,7 @@ You are an API contract reviewer for a layered Next.js frontend (`@/types`, `@/a
 2. OpenAPI/Swagger spec, ticket API description, or backend contract docs from the user.
 3. Changed files in `app/src/types/**`, `app/src/api/**`, mocks, store thunks.
 
-Apply **`types-public-imports.mdc`**, **`api-public-imports.mdc`**, **`api-services.mdc`**, **`http-client.mdc`**.
+Apply **`public-imports.mdc`**, **`api-services.mdc`**, **`http-client.mdc`**.
 
 ## Review scope
 

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

@@ -7,6 +7,8 @@ model: fast
 
 You are a build verification specialist. You **validate** implementation quality before code review — you do not edit production code or tests.
 
+**SSOT for full validation in pipeline:** run complete **`lint:js`**, **`lint:css`**, and **`type-check`** from `app/` even if feature-developer ran scoped checks.
+
 ## Inputs
 
 1. `.cursor/team/tasks/<slug>/brief.md` and `decomposition.md`.

package/presets/cursor/next/agents/code-reviewer.md

@@ -13,7 +13,7 @@ You are a senior code reviewer. You may write only review artifacts under `.curs
 2. `.cursor/team/tasks/<slug>/decomposition.md` — check coverage of planned tasks.
 3. Git diff for changed files (`git diff`, `git status`).
 
-Apply the **`code-review` skill** and checklist from **`code-review-mr.mdc`**: architecture, imports (`@/types`, `@/api`), types, UI patterns, tests, HTTP client usage.
+Apply the **`code-review` skill** and **`code-review-mr.mdc`** checklist.
 
 ## Tests gate
 

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

@@ -8,41 +8,20 @@ You are a senior frontend developer working in a Next.js monorepo with strict la
 
 ## Before coding
 
-1. Read `.cursor/team/tasks/<slug>/brief.md` and `decomposition.md`.
-2. Read `architecture.md`, `migration-plan.md`, `api-contract-review.md`, `debug-report.md`, `validation-report.md`, and `review.md` if present.
-3. Read `status.json` — proceed if `state` is `in_progress`, `approved`, or continuing after `/task-continue` / fix loop (`retryAfterFix`).
-4. Read `pipeline.json` if present for step context and scope.
-5. Read **`reference-features.mdc`** and mirror the closest reference feature structure.
-6. Use the **`feature-delivery` skill** and **`feature-delivery-workflow.mdc`** for layer order.
+1. Read `.cursor/team/tasks/<slug>/brief.md`, `decomposition.md`, and prior artifacts if present (`architecture.md`, `debug-report.md`, `validation-report.md`, `review.md`, …).
+2. Read `status.json` — proceed if `in_progress`, `approved`, or `retryAfterFix`.
+3. Read `pipeline.json` for step context and scope.
+4. Follow the **`feature-delivery` skill** (layer order, reference features, validation handoff).
 
 ## Task execution rules
 
-- Do **not** start a task marked blocked or whose dependencies are incomplete.
-- Work tasks in dependency order (types → api → mocks → store → ui → **unit** → e2e).
-- **Unit tests are mandatory before handoff** for mappers, store logic, and non-trivial pure functions (`tests-unit.mdc`). E2E is usually a later pipeline step.
-- Mark completed tasks in `decomposition.md` with `[x]` or a **Done** column update.
-- After all code changes run **`post-change-lint.mdc`**: `lint:js`, `lint:css`, `type-check` from `app/`.
+- Do **not** start blocked tasks or tasks with incomplete dependencies.
+- **Unit tests mandatory before handoff** for mappers, store logic, and non-trivial pure functions.
+- Mark completed tasks in `decomposition.md`.
+- Validation: **`post-change-lint.mdc`**. If pipeline next step is **`build-verifier`**, scoped lint/type-check on **changed files** is enough; full project lint is build-verifier's job.
 
 ## On completion
 
-Update `status.json`:
-
-```json
-{
-  "slug": "<slug>",
-  "currentAgent": "feature-developer",
-  "phase": "executing",
-  "state": "completed",
-  "updatedAt": "<ISO8601>"
-}
-```
-
-Provide a short handoff summary:
-
-- Tasks completed vs remaining
-- Files changed (by layer)
-- Unit specs added/updated
-- Lint/type-check result
-- Known gaps for build-verifier or reviewer
+Update `status.json` (`currentAgent`: `feature-developer`, `state`: `completed`). Handoff: tasks done, files by layer, unit specs, validation result, gaps for build-verifier/reviewer.
 
 Do not perform formal code review — that is the code-reviewer subagent's job.

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

@@ -11,6 +11,7 @@ You are a task router for a Next.js frontend agent team. You **do not** implemen
 
 - User task description (from `/task` or orchestrator).
 - Optional: existing files under `.cursor/team/tasks/<slug>/`.
+- Pipeline JSON schema, examples, step fields — **`agents/README.md`**.
 
 ## Intent detection
 
@@ -24,150 +25,47 @@ You are a task router for a Next.js frontend agent team. You **do not** implemen
 | `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 for failing unit tests |
-| `e2e-only` | «e2e», «playwright», «browser test», «сценарии e2e», «почини e2e» | playwright-test-planner → playwright-test-generator, or playwright-test-healer for failing tests |
+| `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`) |
 
-Adjust steps when context is clear:
+## Adjust steps (when context is clear)
 
-- **Skip task-analyst** if AC and scope are fully specified (document in `skipped`).
-- **Add solution-architect** for cross-layer features (API + store + UI), new public APIs, or architecture uncertainty — insert after analyst, before developer.
-- **Add api-contract-reviewer** when new/changed backend endpoints, OpenAPI/Swagger, or DTO contract sync — insert after architect (or after analyst if no architect), before developer.
-- **Add accessibility-reviewer** for UI-heavy `feature` tasks — after build-verifier, **parallel with security-reviewer** when both apply (see parallel step example).
-- **Add security-reviewer** for auth, tokens, forms, sensitive data — after build-verifier, parallel with accessibility-reviewer when both apply; before code-reviewer.
-- **Add performance-auditor** for perf-sensitive features — insert after developer or as optional post-review audit step.
-- **Add tech-writer** when docs/changelog/README explicitly requested — append as final step for `feature`, `migration`, `docs-only`.
-- **Use unit-test trio** instead of `qa-tester` when request is explicitly unit-only.
-- **Use Playwright specialists** for e2e-heavy features instead of `qa-tester` (scope e2e-only on qa when both unit and e2e needed).
-- **Always insert build-verifier** after feature-developer (or ci-investigator/debugger when they changed code) for `feature`, `bugfix`, `refactor`, `migration`, `a11y`.
-- **Skip qa-tester** for review-only, spike (no code), ci-fix (unless regression scope needed), perf-audit, docs-only, unit-only/e2e-only handled by specialists, or trivial one-line fixes (document risk).
-- **Skip feature-developer** for review-only, test-only (tests only), retro, perf-audit, docs-only (after analyst), ci-fix when investigator fixes in place.
-- **ci-fix:** skip feature-developer with `skipIf: ci-investigator.resolved` when investigator fixes in place.
-- **bugfix:** use `skipIf: debugger.fixed` on feature-developer when debugger applied the fix.
-- **Model:** use `model: inherit` (not fast) when pipeline has 4+ steps or cross-layer uncertainty (API + store + UI).
+- Skip **task-analyst** if AC/scope fully specified → document in `skipped`.
+- Add **solution-architect** for cross-layer / new public APIs — after analyst, before developer.
+- Add **api-contract-reviewer** for new/changed backend contracts — before developer.
+- Add **accessibility-reviewer** / **security-reviewer** after build-verifier (parallel when both apply).
+- Add **tech-writer** when docs/changelog requested.
+- **Always build-verifier** after developer (or after ci-investigator/debugger if they changed code) for `feature`, `bugfix`, `refactor`, `migration`, `a11y`.
+- **skipIf:** `debugger.fixed` on developer (bugfix); `ci-investigator.resolved` (ci-fix).
+- **Model:** `inherit` when 4+ steps or cross-layer uncertainty.
 
-## Output: pipeline.json
-
-Write to `.cursor/team/tasks/<slug>/pipeline.json`:
-
-```json
-{
-  "slug": "<slug>",
-  "intent": "feature",
-  "summary": "One-line task summary",
-  "steps": [
-    { "agent": "task-analyst", "label": "Clarify and decompose" },
-    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
-    { "agent": "build-verifier", "label": "Lint, type-check, unit smoke" },
-    { "agent": "code-reviewer", "label": "Code review" },
-    { "agent": "qa-tester", "label": "E2E tests", "scope": "e2e-only" }
-  ],
-  "humanGates": ["after:task-analyst"],
-  "autoChain": true,
-  "skipped": []
-}
-```
-
-### Example: feature with optional reviewers
-
-```json
-{
-  "intent": "feature",
-  "steps": [
-    { "agent": "task-analyst", "label": "Clarify and decompose" },
-    { "agent": "api-contract-reviewer", "label": "Validate API contract" },
-    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
-    { "agent": "build-verifier", "label": "Validation gate" },
-    {
-      "agent": ["accessibility-reviewer", "security-reviewer"],
-      "parallel": true,
-      "label": "A11y and security review"
-    },
-    { "agent": "code-reviewer", "label": "Code review" },
-    { "agent": "playwright-test-planner", "label": "E2E plan", "scope": "changed-flows-only" },
-    { "agent": "playwright-test-generator", "label": "E2E specs" },
-    { "agent": "tech-writer", "label": "Documentation" }
-  ],
-  "humanGates": ["after:task-analyst"]
-}
-```
-
-### Example: bugfix with skip
-
-```json
-{
-  "intent": "bugfix",
-  "steps": [
-    { "agent": "debugger", "label": "Root cause" },
-    { "agent": "feature-developer", "label": "Fix if needed", "skipIf": "debugger.fixed" },
-    { "agent": "build-verifier", "label": "Validation" },
-    { "agent": "code-reviewer", "label": "Review" }
-  ],
-  "humanGates": []
-}
-```
-
-### Step fields
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| `agent` | yes | Subagent name (kebab-case) or array for `parallel: true` |
-| `label` | yes | Short human-readable step name |
-| `scope` | no | e.g. `unit-in-dev`, `e2e-only`, `regression`, `full` — passed to agents |
-| `skipIf` | no | `debugger.fixed` \| `ci-investigator.resolved` — skip step when artifact says fix already applied |
-| `parallel` | no | When `true` and `agent` is array — orchestrator invokes all agents in one turn |
-
-### humanGates
-
-Values: `after:<agent-name>` — orchestrator stops after that agent; user runs `/task-continue <slug>` or `/feature-continue <slug>`.
+## humanGates (defaults)
 
 | Intent | Default humanGates |
 |--------|-------------------|
 | `feature`, `refactor`, `test-only`, `a11y` | `["after:task-analyst"]` |
 | `migration` | `["after:migration-specialist"]` |
 | `docs-only` | `["after:task-analyst"]` |
-| `unit-only` | `["after:unit-test-planner"]` when new plan before generation; `[]` for pure healer |
-| `e2e-only` | `["after:playwright-test-planner"]` when new plan; `[]` for pure healer |
-| `bugfix`, `review-only`, `ci-fix` | `[]` (unless analyst added) |
+| `unit-only` | `["after:unit-test-planner"]` when new plan; `[]` for healer |
+| `e2e-only` | `["after:playwright-test-planner"]` when new plan; `[]` for healer |
+| `bugfix`, `review-only`, `ci-fix` | `[]` |
 | `spike` | `["after:solution-architect"]` |
 | `perf-audit` | `[]` |
 
-### skipped (optional)
-
-```json
-"skipped": [{ "agent": "task-analyst", "reason": "AC provided in ticket" }]
-```
-
-## Initial status.json
+## Output
 
-After writing pipeline.json, write:
-
-```json
-{
-  "slug": "<slug>",
-  "intent": "<intent>",
-  "pipelineIndex": 0,
-  "currentAgent": "<steps[0].agent>",
-  "phase": "executing",
-  "state": "in_progress",
-  "awaitingHumanGate": false,
-  "updatedAt": "<ISO8601>"
-}
-```
-
-Also write `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
+Write `.cursor/team/tasks/<slug>/pipeline.json` and initial `status.json`; set `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`. Minimal template — см. **`agents/README.md`**.
 
 ## Handoff to orchestrator
 
-Respond with:
-
-1. **Intent** and one-line summary.
-2. **Planned steps** (table: #, agent, label).
-3. **Skipped roles** and why.
-4. **Human gates** (if any).
-5. Tell orchestrator to invoke `steps[0].agent` now (unless intent is `retro` — then run `/technical-retro`).
+1. Intent + one-line summary.
+2. Planned steps (table: #, agent, label).
+3. Skipped roles and why.
+4. Human gates (if any).
+5. Invoke `steps[0].agent` now (unless `retro` → `/technical-retro`).
 
 Do not invoke implementation agents yourself.

package/presets/cursor/next/commands/task.md

@@ -5,7 +5,7 @@ description: Route a natural-language task through the agent-team pipeline: task
 
 # Task — единая точка входа (router + pipeline)
 
-Главная команда для постановки задачи. Родительский агент = оркестратор (`agent-team-orchestrator.mdc`).
+Главная команда для постановки задачи. Родительский агент = оркестратор (`agent-team-orchestrator.mdc`). Intake для work-запросов без `/task` — `agent-team-intake.mdc`.
 
 ## Аргументы
 

package/presets/cursor/next/rules/README.md

@@ -20,8 +20,8 @@
 ### Loading strategy
 
 - **`alwaysApply: true`** (Cursor) / **без `paths:`** (Claude) — только базовые инварианты:
-  - `next-app-core`, `post-change-lint`, `package-manager`, `agent-team-intake`, `code-quality-and-refactoring`
-- **Globs / `paths:`** — architecture, imports, UI, tests, feature-delivery-workflow, reference-features, next-app-router, react-a11y-coding
+  - `next-app-core`, `post-change-lint`, `package-manager`, `code-quality-and-refactoring`
+- **On-demand** — `agent-team-intake` (через orchestrator/commands), `agent-team-orchestrator`, architecture, imports, UI, tests, feature-delivery-workflow, reference-features, next-app-router, react-a11y-coding
 - **Skills** — длинные процедуры (`feature-delivery`, `code-review`, …)
 
 ### Эталонные фичи
@@ -36,17 +36,16 @@
 | `next-app-router.mdc` | App Router, RSC, loading/error |
 | `react-a11y-coding.mdc` | A11y при написании UI |
 | `feature-delivery-workflow.mdc` | Сквозной чеклист (on-demand, не always-on) |
-| `agent-team-intake.mdc` | Автоподсказка `/task` при постановке задачи (alwaysApply) |
+| `agent-team-intake.mdc` | Подсказка `/task` при work-запросе (on-demand, через orchestrator) |
 | `package-manager.mdc` | Перед `install` / `run` в терминале определить менеджер пакетов репо (lockfile, `packageManager`) и использовать только его |
 | `agent-team-orchestrator.mdc` | `/task`, router, `pipeline.json`, build-verifier, parallel steps |
-| `next-app-core.mdc` | Стек, слои, порты‑адаптеры (alwaysApply) |
+| `next-app-core.mdc` | Стек, слои, карта каталогов (alwaysApply) |
 | `post-change-lint.mdc` | **Обязательный** прогон ESLint + Stylelint после любых изменений кода |
 | `architecture-boundaries.mdc` | Границы UI / store / API, импорты (`@/types`, `@/api`), порты‑адаптеры, фича как срез |
 | `http-client.mdc` | Один HTTP‑стек, контракты из `@/types`, без разбросанного низкоуровневого API |
 | `api-services.mdc` | Сервисы, мапперы, вызовы через прикладные API‑клиенты |
 | `store-rtk.mdc` | Redux Toolkit, thunk’и, типизация ошибок/ответов как в коде репо |
-| `types-public-imports.mdc` | Импорты только через barrel `@/types` |
-| `api-public-imports.mdc` | Импорты только через barrel `@/api` (вне `app/src/api/**`) |
+| `public-imports.mdc` | Импорты `@/types`, `@/types/enums`, `@/api` (вне `app/src/api/**`); stubs: `types-public-imports.mdc`, `api-public-imports.mdc` |
 | `layer-barrel-exports.mdc` | Двухуровневые barrel для слоёв с public API (`@/api`, `@/types`, `@/core`, …) |
 | `types-jsdoc.mdc` | JSDoc для типов в `app/src/types` (русский текст, `[computed]`, без `@param`/`@returns`) |
 | `no-type-assertion-as-import-export.mdc` | Ограничение `as`, в т.ч. `instanceof` для ошибок транспорта в `catch` |
@@ -55,6 +54,6 @@
 | `playwright-agents.mdc`, `tests-e2e-structure.mdc` | E2E |
 | `react-ui.mdc` | React/Next UI: структура компонентов, соседние `ComponentName.data.ts` / `.utils.ts`, стили, пропсы |
 
-**Коллизии формулировок:** если в разных `.mdc` расходятся детали **импорта типов**, источник правды — **`types-public-imports.mdc`** (`@/types`, `@/types/enums`); по **импорту из API‑слоя** (store, UI, прочий код вне `app/src/api/**`) — **`api-public-imports.mdc`** (`@/api`), в том же смысле что правило ESLint `no-restricted-imports` в `app/eslint.config.mjs`.
+**Коллизии формулировок:** импорт типов и API — источник правды **`public-imports.mdc`**; дублирует ESLint `no-restricted-imports` в `app/eslint.config.mjs`.
 
 Задачи на **сеть, замену HTTP‑библиотеки, новые эндпоинты**: опираться на **`http-client.mdc`** + **`api-services.mdc`** + **`store-rtk.mdc`**.

package/presets/cursor/next/rules/agent-team-intake.mdc

@@ -1,6 +1,6 @@
 ---
-description: When the user describes a new task, feature, bug, or implementation request (not a pure question), suggest or use /task to run the agent team router. Lightweight intake hint only.
-alwaysApply: true
+description: Use when user posts a work request without /task — suggest or use /task to run the agent team router. Lightweight intake hint only.
+alwaysApply: false
 ---
 
 # Agent team intake

package/presets/cursor/next/rules/agent-team-orchestrator.mdc

@@ -7,6 +7,8 @@ alwaysApply: false
 
 Parent agent = **manager**. Router plans; specialists execute. Artifacts: `.cursor/team/tasks/<slug>/`.
 
+Work request без `/task` — см. **`agent-team-intake.mdc`** (когда предлагать router вместо прямого кодинга).
+
 ## Entry points
 
 | Command | When |
@@ -121,6 +123,17 @@ After each agent completes, ensure `status.json` has `state: completed` (or `awa
 
 If `pipeline.json` is missing (old `/feature-start` tasks), fall back to fixed phases: analysis → development → review → testing. Hook supports both.
 
+## Skip pipeline when
+
+Do **not** run `/task` + router for:
+
+- Pure questions («как работает X», «объясни»).
+- Typo / one-file fix / trivial config with no architecture risk.
+- User explicitly says «без pipeline», «просто сделай», or continues an active slug.
+- Single-line `docs-only` with no code impact.
+
+Borderline work requests — см. **`agent-team-intake.mdc`**.
+
 ## Auto-detection (optional)
 
-When user describes a **task** (not a question "how does X work"), suggest `/task <their message>` or run router proactively if they agree.
+When user describes a **non-trivial task** (not a question), suggest `/task <message>` or run router if they agree.

package/presets/cursor/next/rules/api-public-imports.mdc

@@ -1,29 +1,8 @@
 ---
-description: Импорт из API-слоя только через публичный barrel @/api
-globs: app/src/**/*.ts,app/src/**/*.tsx
+description: Moved to public-imports.mdc — read that file instead
 alwaysApply: false
 ---
 
-# Импорты из `@/api`
+# Deprecated
 
-- **Публичный API слоя API** — barrel `app/src/api/index.ts`. Для файлов **вне** `app/src/api/**` импортировать сервисы, клиенты, эндпоинты и публичные типы API **только** как `import … from '@/api'` (или `from '@/api/index'` при необходимости явного пути).
-- **Запрещено** для таких потребителей обходить barrel: любой импорт вида `@/api/<что‑угодно>`, кроме `@/api/index`. Это дублирует правило ESLint `no-restricted-imports` в `app/eslint.config.mjs` (паттерн `@/api/*` с исключением `@/api/index`).
-- При **добавлении** публичного символа в регламентированный слой — реэкспорт в корневой barrel по **`layer-barrel-exports.mdc`**.
-
-## Внутри слоя `app/src/api/**`
-
-- При реализации сервисов, клиентов и barrel допустимы **относительные** импорты и пути вида `@/api/services/**`, `@/api/clients/**` между файлами этого слоя. Это не относится к потребителям снаружи `app/src/api/**`.
-
-## Примеры
-
-```typescript
-// ✅ Допустимо в store, UI, lib вне app/src/api — только barrel
-import { MedcardApiService, MarketplaceApiService } from '@/api'
-import type { TReferenceRequest } from '@/api'
-
-// ❌ Запрещено снаружи app/src/api (сработает ESLint)
-import { MedcardApiService } from '@/api/services/MedcardApiService/MedcardApiService'
-import { MedcardApiClient } from '@/api/clients/MedcardApiClient'
-```
-
-При ревью и правках кода **не добавлять** новые импорты из `@/api/...` кроме `@/api` / `@/api/index` в файлах вне `app/src/api/**`.
+Содержимое перенесено в **`public-imports.mdc`** (раздел `@/api`).

package/presets/cursor/next/rules/api-services.mdc

@@ -12,7 +12,7 @@ alwaysApply: false
   - заголовками и кодами ответов,
   - DTO backend.
 - Предоставлять UI и store **стабильный доменный интерфейс**:
-  - функции, работающие с доменными типами из `@/types` (`types-public-imports.mdc`).
+  - функции, работающие с доменными типами из `@/types` (`public-imports.mdc`).
   - мапперы между DTO и доменными типами.
 
 # Структура модулей
@@ -23,7 +23,7 @@ alwaysApply: false
   - файлы с вызовами API (`index.ts` или `*.service.ts`);
   - файлы мапперов (`*responseMappers.ts`);
   - специфичные типы запросов/ответов (если не вынесены в `app/src/types/**` с экспортом через barrel `@/types`).
-  - при необходимости — локальные `index.ts` / barrel внутри модуля для структуры **внутри** `app/src/api/**`; **снаружи** этого слоя UI, store и остальной код импортируют только из корневого barrel `app/src/api/index.ts` (`import … from '@/api'`, **`api-public-imports.mdc`**).
+  - при необходимости — локальные `index.ts` / barrel внутри модуля для структуры **внутри** `app/src/api/**`; **снаружи** этого слоя UI, store и остальной код импортируют только из корневого barrel `app/src/api/index.ts` (`import … from '@/api'`, **`public-imports.mdc`**).
 
 # Мапперы и типы
 
@@ -54,5 +54,5 @@ alwaysApply: false
 - Не смешивать слой API и UI/store:
   - компоненты не должны зависеть от DTO;
   - store не должен сам собирать URL/коды эндпоинтов и не обходить сервисы; **транспортный тип ответа** и **контракт ошибки** из `@/types` (как у прикладного клиента) допустимы во thunk при разборе `catch`/payload, если так выстроен сервис (см. `store-rtk.mdc`, `http-client.mdc`).
-- При использовании API‑сервисов в UI, store и утилитах **вне** `app/src/api/**` импортировать **только** из `@/api` (корневой barrel), см. **`api-public-imports.mdc`**; внутри слоя API — по относительным путям или `@/api/services/**` / `@/api/clients/**`, не дублируя публичный контракт мимо корневого barrel для внешних потребителей.
+- При использовании API‑сервисов в UI, store и утилитах **вне** `app/src/api/**` импортировать **только** из `@/api` (корневой barrel), см. **`public-imports.mdc`**; внутри слоя API — по относительным путям или `@/api/services/**` / `@/api/clients/**`, не дублируя публичный контракт мимо корневого barrel для внешних потребителей.