@bonesofspring/ai-rules 0.1.40 → 0.1.42

package/presets/cursor/next/rules/no-cross-component-styles-import.mdc

@@ -1,6 +1,9 @@
 ---
 description: Стили компонентов — колокация, импорты, корневой styled как Root
-alwaysApply: true
+globs:
+  - app/src/ui/**/*.ts
+  - app/src/ui/**/*.tsx
+alwaysApply: false
 ---
 
 # Стили только рядом с компонентом

package/presets/cursor/next/rules/no-props-spread.mdc

@@ -1,7 +1,7 @@
 ---
 description: Избегать спред-а пропов при передаче в компоненты
-alwaysApply: true
 globs: app/src/**/*.tsx
+alwaysApply: false
 ---
 
 # Не использовать спред пропов при передаче в компоненты

package/presets/cursor/next/rules/no-type-assertion-as-import-export.mdc

@@ -1,6 +1,7 @@
 ---
 description: Избегать приведения типов через as на границах модулей (импорт/экспорт)
-alwaysApply: true
+globs: app/src/**/*.ts,app/src/**/*.tsx
+alwaysApply: false
 ---
 
 # Не использовать `as` для приведения типов при экспорте и импорте (кроме необходимых случаев)

package/presets/cursor/next/rules/playwright-agents.mdc

@@ -1,6 +1,7 @@
 ---
 description: Playwright Agents (planner/generator/healer) configuration for e2e structure in app/__tests__/e2e
-alwaysApply: true
+globs: app/__tests__/e2e/**/*
+alwaysApply: false
 ---
 
 # Playwright Agents in this project

package/presets/cursor/next/rules/react-a11y-coding.mdc

@@ -0,0 +1,37 @@
+---
+description: Accessibility при написании React UI — семантика, формы, focus, keyboard
+globs: app/src/ui/**/*.tsx,app/src/ui/**/*.ts
+alwaysApply: false
+---
+
+# A11y при разработке UI
+
+Reviewer (`accessibility-reviewer`) проверяет diff; эти правила — **при написании** кода.
+
+## Семантика и ARIA
+
+- Предпочитать **нативные элементы** (`button`, `a`, `label`, `input`) вместо `div` с `onClick`.
+- **`role` / `aria-*`** — только когда нативного аналога нет; не дублировать то, что даёт семантика.
+- Заголовки — иераархия `h1`–`h6` без пропусков уровней ради стилей.
+
+## Формы
+
+- Каждый input связан с **`label`** (`htmlFor` / `id` или обёртка).
+- Сообщения об ошибках — **`aria-describedby`**, `aria-invalid` при validation errors.
+- Кнопки submit vs button — явный `type`.
+
+## Клавиатура и focus
+
+- Все интерактивные элементы **достижимы с Tab** и активируются Enter/Space где ожидается.
+- **Modals/drawers** — focus trap, возврат focus на trigger при закрытии, Esc закрывает (если по UX).
+- Не удалять видимый **focus outline** без замены на доступный custom focus style.
+
+## Контент
+
+- Изображения — **`alt`** (пустой `alt` только для декора).
+- Иконки-кнопки — **`aria-label`** или visually hidden text.
+- Динамические обновления — `aria-live` для критичных status/error (умеренно).
+
+## Проверка
+
+- При сомнении — devtools a11y tree или `accessibility-reviewer` в pipeline для UI-heavy фич.

package/presets/cursor/next/rules/reference-features.mdc

@@ -0,0 +1,35 @@
+---
+description: Эталонные фичи репозитория — копировать структуру при реализации новых задач. Заполните пути после init в целевом репо.
+globs: app/src/**/*
+alwaysApply: false
+---
+
+# Эталонные фичи (reference features)
+
+Перед реализацией найди фичу того же типа и **повтори её структуру**, не изобретая новую организацию файлов.
+
+## Таблица эталонов
+
+Замени **TBD** на реальные пути после договорённости в команде (или при `ai-rules init` в целевом репо):
+
+| Слой | Эталон | Что копировать |
+|------|--------|----------------|
+| UI page | **TBD** `app/src/ui/pages/<Example>/` | `components/`, `*.data.ts`, `styles.ts`, barrel |
+| Store slice | **TBD** `app/src/store/slices/<example>/` | slice, thunks, selectors, types |
+| API service | **TBD** `app/src/api/services/<example>/` | service, mappers, barrel |
+| Types module | **TBD** `app/src/types/<example>/` | domain types, JSDoc, barrel export |
+| Unit tests | **TBD** рядом с эталонным mapper/service | `*.spec.ts`, describe/it naming |
+| E2E area | **TBD** `app/__tests__/e2e/<Area>/` | `*.cases.md`, page objects, `_shared/` |
+
+## Как использовать
+
+1. Определи затронутые слои из `decomposition.md` или задачи.
+2. Открой эталон из таблицы (после заполнения путей).
+3. Зеркаль именование, порядок файлов, паттерны импортов и тестов.
+4. Если эталона нет — выбери **самую близкую** существующую фичу того же слоя и зафиксируй выбор в handoff.
+
+## Связанные правила
+
+- `code-quality-and-refactoring.mdc` — повторять паттерны, не deep-import.
+- `feature-delivery-workflow.mdc` — порядок слоёв.
+- skill `feature-delivery` — end-to-end сценарий.

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

@@ -1,6 +1,7 @@
 ---
 description: Импорт доменных типов только через публичный API @/types
-alwaysApply: true
+globs: app/src/**/*.ts,app/src/**/*.tsx
+alwaysApply: false
 ---
 
 # Импорты из `@/types`

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

@@ -0,0 +1,15 @@
+# `.cursor/skills` (preset next)
+
+Project skills for Cursor. They keep long workflows out of always-on rules while preserving the same team conventions as the Claude preset.
+
+| Skill | When to use |
+|-------|-------------|
+| `feature-delivery` | End-to-end feature work across types, API, store, UI, tests |
+| `code-review` | MR/diff review using project architecture and test standards |
+| `debug-investigation` | Reproducing and fixing bugs with root-cause evidence |
+| `ci-investigation` | Diagnosing and fixing failing CI checks on PRs/branches |
+| `unit-testing` | Planning, generating, or healing unit test coverage |
+| `playwright-e2e` | Planning, generating, or healing Playwright e2e coverage |
+| `technical-retro` | Technical retrospective for a task, sprint, incident, or agent pipeline |
+
+Skills are copied to `.cursor/skills/` by `ai-rules init cursor --preset next`.

package/presets/cursor/next/skills/ci-investigation/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: ci-investigation
+description: Investigates failing CI checks on PRs and branches — lint, type-check, unit, e2e — with local reproduction and minimal fixes. Use when CI is red or for ci-fix pipeline tasks.
+---
+
+# CI Investigation
+
+## Workflow
+
+1. Identify the **first failing check** (lint, type-check, unit, e2e, build).
+2. Capture error output — ignore cascading failures until root cause is found.
+3. Reproduce locally with the same commands CI uses from `app/`:
+   - `lint:js`, `lint:css`, `type-check`
+   - targeted unit test file or suite
+   - affected Playwright spec if e2e failed
+4. Inspect git diff for changed files related to the failure.
+5. Apply **minimal fix** — no unrelated refactors.
+
+## Artifact
+
+Write `ci-report.md` under the task slug folder:
+
+- Failed check name and link/log excerpt
+- Root cause classification
+- Fix applied (or handoff to feature-developer)
+- Validation commands and results
+
+## Handoff Rules
+
+- Config-only or one-line fixes → fix in place, re-run check.
+- Missing tests or architecture work → document and route to `feature-developer` or `qa-tester`.
+- Flaky e2e → prefer `playwright-test-healer` after ci-investigator identifies the spec.
+
+## Validation
+
+Always re-run the failing command locally before marking complete. If environment blocks execution, state the exact command and blocker.

package/presets/cursor/next/skills/code-review/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: code-review
+description: Reviews pull requests, merge requests, git diffs, and branch changes using the preset's architecture, import, UI, API, and testing standards. Use when the user asks for review or when code-reviewer runs in an agent pipeline.
+---
+
+# Code Review
+
+## Inputs
+
+Use the local repository as the source of truth: `git status`, `git diff`, task artifacts under `.cursor/team/tasks/<slug>/` when present, and opened files. Do not invent hosting metadata such as labels, CI status, or reviewers.
+
+## Review Order
+
+1. Understand the intent and affected layers.
+2. Check correctness and regressions first.
+3. Verify architecture boundaries: UI does not know DTO/transport, store does not depend on UI, API services do not pull UI/store.
+4. Check public imports through `@/types` and `@/api`, plus barrel updates for new public symbols.
+5. Review UI consistency, styling conventions, and prop shape.
+6. Check tests: unit for mapper/domain logic, behavior tests for HTTP client changes, e2e plan/spec updates for user flows.
+7. Report validation gaps: lint, stylelint, type-check, or relevant tests not run.
+
+## Output
+
+Lead with findings ordered by severity. Each finding should include the file, the problem, impact, and a concrete fix direction. If there are no findings, say so and call out remaining test or validation risk.
+
+For agent team tasks, write `.cursor/team/tasks/<slug>/review.md` and set `status.json` to `completed` or `changes_requested`.

package/presets/cursor/next/skills/debug-investigation/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: debug-investigation
+description: Investigates bugs, failing tests, crashes, and incorrect behavior with runtime evidence before applying minimal fixes. Use for bugfix tasks, debugger agent runs, regressions, and flaky test diagnosis.
+---
+
+# Debug Investigation
+
+## Process
+
+1. Reproduce the issue or collect the closest available evidence: error output, failing test, browser snapshot, logs, or user steps.
+2. Define expected vs actual behavior in one sentence.
+3. Trace the failing path through the smallest relevant slice of the codebase.
+4. Identify the root cause before editing. Avoid broad refactors during bugfixes.
+5. Apply the smallest fix that preserves existing architecture and public contracts.
+6. Add or update a regression test when the behavior is user-facing or likely to recur.
+7. Run the narrow failing check first, then relevant lint/type/test validation.
+
+## Artifacts
+
+For agent team tasks, write `.cursor/team/tasks/<slug>/debug-report.md` with:
+
+- Reproduction steps or evidence source.
+- Root cause.
+- Fix scope.
+- Regression coverage.
+- Remaining risk.
+
+Update `status.json` when complete.

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

@@ -0,0 +1,30 @@
+---
+name: feature-delivery
+description: Delivers Next.js frontend features end-to-end across domain types, API services, store, UI, mocks, tests, and validation. Use when implementing or extending a feature, especially through /task or feature-developer.
+---
+
+# Feature Delivery
+
+## Workflow
+
+1. Read the task brief, acceptance criteria, and decomposition if present.
+2. Read **`reference-features.mdc`** and mirror the closest reference feature.
+3. Work in layer order: types -> API contract/mappers -> services -> store -> UI -> mocks -> **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: `next-app-core.mdc`, `architecture-boundaries.mdc`.
+- Data/API: `http-client.mdc`, `api-services.mdc`, `store-rtk.mdc`.
+- Public imports: `types-public-imports.mdc`, `api-public-imports.mdc`, `layer-barrel-exports.mdc`.
+- UI: `react-ui.mdc`, `react-a11y-coding.mdc`, `no-props-spread.mdc`, `no-cross-component-styles-import.mdc`.
+- App Router: `next-app-router.mdc`.
+- Tests: `tests-unit.mdc`, `tests-e2e-structure.mdc`, `playwright-agents.mdc`.
+- Finish: `post-change-lint.mdc`, `package-manager.mdc`.
+
+## Handoff
+
+Summarize completed work by layer, validation results, and known gaps. If this is part of an agent team task, update `.cursor/team/tasks/<slug>/status.json`.

package/presets/cursor/next/skills/playwright-e2e/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: playwright-e2e
+description: Plans, generates, and heals Playwright e2e tests using this preset's app/__tests__/e2e layout, *.cases.md plans, page objects, and shared helpers. Use for e2e planning, test generation, or fixing failing browser tests.
+---
+
+# Playwright E2E
+
+## Project Layout
+
+- Test root: `app/__tests__/e2e`.
+- Test plans: `*.cases.md` files under the matching feature folder.
+- Executable specs: `*.spec.ts` files in the same folder.
+- Seed/setup reference: `app/__tests__/e2e/seed.spec.ts`.
+
+Do not introduce top-level `specs/` or `tests/` folders for real coverage unless the user explicitly asks for a sandbox.
+
+## Planner
+
+Create or update the relevant `*.cases.md` file. Each scenario should include title, preconditions, steps, and expected result. Cover happy path, important edge cases, validation, and error states.
+
+## Generator
+
+Generate specs from `*.cases.md` into the same folder. Reuse existing page objects and `_shared/` helpers. Keep test names aligned with scenario names.
+
+## Healer
+
+Fix selectors, waits, setup, or page-object details without weakening business assertions. Use the matching `*.cases.md` file as the behavior contract.
+
+## Validation
+
+Run the affected spec when feasible. If the environment blocks execution, report the command that should be run and the blocker.

package/presets/cursor/next/skills/technical-retro/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: technical-retro
+description: Facilitates technical retrospectives for tasks, sprints, incidents, releases, and agent-team pipelines. Use when the user asks for retro, postmortem, process review, or action items after delivery.
+---
+
+# Technical Retro
+
+## Inputs
+
+Ask for missing period, focus, task slug, participants, or format constraints. If a slug is provided, read `.cursor/team/tasks/<slug>/` artifacts and local git status/diff. Do not invent facts not present in artifacts or the user's message.
+
+## Facilitation Principles
+
+- Focus on process and system behavior, not blame.
+- Separate facts, interpretations, and proposed actions.
+- Balance what worked with what slowed delivery.
+- Keep action items concrete, owned, and measurable.
+
+## Default Structure
+
+1. Goal and scope.
+2. Timeline or factual observations.
+3. What worked.
+4. What hurt quality, speed, or confidence.
+5. Root causes for the top one or two issues.
+6. Experiments and action items.
+
+## Agent Team Block
+
+For `/task` pipelines, include router, analyst, developer, **build-verifier**, reviewer, QA/e2e, hooks, and rules.
+
+## Preset feedback loop
+
+If the same issue appeared in 2+ tasks, add section **Preset updates**:
+
+- Proposed change to `.cursor/rules/`, `.cursor/agents/`, or `.cursor/skills/`
+- One concrete diff or file path to update
+- Whether it belongs in always-on rules vs globs vs skill
+
+Do not apply preset changes without user approval.

package/presets/cursor/next/skills/unit-testing/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: unit-testing
+description: Plans, generates, and heals unit tests for mappers, thunks, HTTP client behavior, and React components using colocated *.spec.ts files and tests-unit rules. Use for unit test planning, generation, or fixing failing unit tests.
+---
+
+# Unit Testing
+
+## Project Layout
+
+- Specs colocated with source: `*.spec.ts` / `*.spec.tsx` next to the module under test.
+- Legacy `*.test.ts` / `*.test.tsx` — do not rename without a separate task.
+- Runner: Jest or Vitest as configured in the target repo; components use `@testing-library/react`.
+
+Follow **`tests-unit.mdc`** (Cursor) or **`rules/testing/tests-unit.md`** (Claude).
+
+## Planner
+
+Write or update `.cursor/team/tasks/<slug>/unit-test-plan.md` (or `.claude/team/...`).
+
+Each scenario needs a Russian `it()` title (capital letter after each sentence). Cover mappers, thunks, client behavior branches, and component interactions per AC.
+
+## Generator
+
+Implement specs from `unit-test-plan.md`. Reuse project test-store, HTTP mocks, and existing test utilities. Do not change production code.
+
+## Healer
+
+Fix mocks, async timing, selectors, and setup — preserve business assertions. Use `unit-test-plan.md` and `brief.md` as the behavior contract.
+
+## Validation
+
+Run affected unit tests from `app/` when feasible. Report command, pass/fail, and remaining gaps vs plan.

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

@@ -6,23 +6,27 @@
 
 ```
 .cursor/team/
-  active-task.json              # { "slug": "current-task-slug" }
+  active-task.json
   tasks/
     <slug>/
-      pipeline.json             # Router: intent, steps, humanGates
-      status.json               # Current step and state machine
-      brief.md                  # Analyst: Definition of Ready
-      decomposition.md          # Analyst: task breakdown
-      debug-report.md           # Debugger (bugfix)
-      architecture.md           # Solution architect (spike / complex)
+      pipeline.json
+      status.json
+      brief.md
+      decomposition.md
+      debug-report.md          # fixApplied: true/false
+      validation-report.md     # build-verifier: PASS | FAIL
+      architecture.md
+      migration-plan.md
+      ci-report.md
+      a11y-review.md
+      perf-report.md
+      security-review.md
+      api-contract-review.md
+      unit-test-plan.md
+      documentation.md
+      review.md
 ```
 
-## Slug
-
-- kebab-case, derived from task title
-- max 48 characters
-- example: `order-history-date-filter`
-
 ## pipeline.json schema
 
 ```json
@@ -32,9 +36,10 @@
   "summary": "Add date filter to Order History",
   "steps": [
     { "agent": "task-analyst", "label": "Clarify and decompose" },
-    { "agent": "feature-developer", "label": "Implement" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate" },
     { "agent": "code-reviewer", "label": "Code review" },
-    { "agent": "qa-tester", "label": "Tests", "scope": "full" }
+    { "agent": "qa-tester", "label": "E2E", "scope": "e2e-only" }
   ],
   "humanGates": ["after:task-analyst"],
   "autoChain": true,
@@ -42,11 +47,17 @@
 }
 ```
 
-### intent values
+### Step fields
 
-`feature` | `bugfix` | `review-only` | `test-only` | `refactor` | `spike` | `retro`
+| Field | Description |
+|-------|-------------|
+| `agent` | kebab-case name or array when `parallel: true` |
+| `label` | Human-readable step name |
+| `scope` | Passed to agents (e.g. `unit-in-dev`, `e2e-only`) |
+| `skipIf` | `debugger.fixed` \| `ci-investigator.resolved` |
+| `parallel` | Invoke all `agent` values in one parent turn |
 
-## status.json schema (pipeline mode)
+## status.json (pipeline mode)
 
 ```json
 {
@@ -57,20 +68,15 @@
   "phase": "executing",
   "state": "in_progress",
   "awaitingHumanGate": false,
+  "parallelCompleted": [],
+  "retryAfterFix": null,
   "updatedAt": "2026-05-29T12:00:00.000Z"
 }
 ```
 
 ### phase
 
-| Value | Description |
-|-------|-------------|
-| `executing` | Pipeline step in progress (preferred) |
-| `analysis` | Legacy: analyst phase |
-| `development` | Legacy: developer phase |
-| `review` | Legacy: review phase |
-| `testing` | Legacy: QA phase |
-| `done` | All steps complete |
+Prefer **`executing`** for pipeline mode. Legacy: `analysis`, `development`, `review`, `testing`, `done`.
 
 ### state
 
@@ -80,27 +86,19 @@
 | `completed` | Current step finished |
 | `awaiting_approval` | Human gate; use `/task-continue` |
 | `changes_requested` | Reviewer requires fixes |
-| `approved` | Legacy: approved via continue |
-
-## Git
-
-Commit task artifacts if you want them to survive `ai-rules clean cursor`. Alternatively copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.
+| `validation_failed` | build-verifier failed |
+| `approved` | Legacy continue |
 
 ## Workflow entry
 
 ```bash
 /task <описание задачи>
-# при human gate после analyst:
 /task-continue <slug>
-# или
-/feature-continue <slug>
-# после пайплайна:
 /technical-retro <slug>
 ```
 
-Legacy:
+Legacy: `/feature-start`, `/feature-continue`.
 
-```bash
-/feature-start <описание>
-/feature-continue <slug>
-```
+## Git
+
+Commit task artifacts if you want them to survive `ai-rules clean cursor`. Or copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.