@bonesofspring/ai-rules 0.2.8 → 0.2.10

package/presets/cursor/java/rules/messaging-adapters.mdc

@@ -1,5 +1,5 @@
 ---
-description: Messaging driven/driving adapters for Java hexagonal services (stub)
+description: Messaging driven/driving adapters for Java hexagonal services
 globs:
   - "**/adapters/outbound/messaging/**/*"
   - "**/adapters/inbound/messaging/**/*"
@@ -7,20 +7,26 @@ globs:
 alwaysApply: false
 ---
 
+# Messaging adapters
 
-# Messaging adapters (documented stub)
+- **Publisher** (driven): implements an outbound port; serializes application/domain events to wire format inside the adapter.
+- **Consumer** (driving): deserializes → maps to application/domain types → calls inbound port / use case; **ack/nack** (and commit) stays in the adapter.
+- Idempotency keys, retry, and DLQ/parking-lot policy are adapter (or infra) concerns — document at-least-once vs exactly-once assumptions at the port.
+- Use the broker client already present in the repo (`KafkaTemplate`, JMS, Spring Cloud Stream, etc.) — do not invent a second stack.
 
-> **Stub (v1):** Light guidance only — not a full Kafka/Rabbit/JMS cookbook. **When to use:** editing `adapters/**/messaging/**` or adding broker publishers/consumers. Prefer expanding this rule when the consumer repo standardizes on a broker.
+## Event shapes
 
-- **Publisher** (driven): implements outbound port; serializes domain events / integration events.
-- **Consumer** (driving): deserializes → calls use case / inbound port; ack/nack policy here.
-- Idempotency keys and retry/DLQ are adapter concerns; document at-least-once assumptions.
-- Do not put broker client types (`KafkaTemplate`, JMS sessions, etc.) in domain or application signatures.
+- Prefer explicit event types in application or a small `events` package used by ports.
+- Map wire DTOs ↔ application events **only** in the adapter; never pass `ConsumerRecord` / broker payloads into domain.
 
-## Event shapes
+## Forbidden
 
-- Prefer explicit event types in application or a small `events` package used by ports — map to wire format in the adapter.
+- Broker client types (`KafkaTemplate`, JMS sessions, `MessageListener`) in domain or application signatures.
+- Business rules inside listeners beyond mapping + calling one use case.
+- Silent catch-and-ack that drops poison messages without DLQ/metrics policy.
 
 ## Tests
 
-- Unit-test mapping with fakes; integration against embedded/broker Testcontainers when the repo has them.
+- Unit-test mapping and idempotency branches with fakes.
+- Integration against embedded broker / Testcontainers **when the repo already has that setup**.
+- After edits: `post-change-test` (+ `java-tooling`); agents `integration-test-*` when adding consumer contracts.

package/presets/cursor/java/rules/preset-token-budget.mdc

@@ -22,7 +22,7 @@ alwaysApply: false
 
 **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 (где задокументировано): ≤120 строк суммарно (stretch ≤100).
+Session-start body budget (где задокументировано): ≤140 строк суммарно (stretch ≤120).
 
 ## Meta / author rules
 

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

@@ -37,7 +37,7 @@ When validating **preset packaging** changes (paths under `packages/ai-rules/pre
 3. **Mapping / README:** `claude/next/rules/README.md` must include a Cursor→Claude mapping table; stack `rules/README.md` should 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 in validation-report).
 5. **Twin presence:** Cursor rule change without Claude twin same PR → **FAIL** (next, ios-swift, go, and java). Domain twin body ≥15 lines; thin aliases (`agent-team-intake`, `technical-retro`) may be shorter.
-6. **Session-start body budget (soft→document, FAIL if grossly over):** sum body lines of the **3** intended always-on / session-start rules ≤ **120** (stretch ≤100); do **not** include `**/README.md`. Record the sum in validation-report.
+6. **Session-start body budget (soft→document, FAIL if grossly over):** sum body lines of the **3** intended always-on / session-start rules ≤ **140** (stretch ≤120); do **not** include `**/README.md`. Record the sum in validation-report.
 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 are excluded from body equality.
 8. **Dogfood (monorepo soft):** if root `.cursor/` is in the PR, prefer sync via `packages/ai-rules/scripts/sync-dogfood-cursor.sh`; mass deletion of tracked dogfood without migration doc → note as risk / FAIL for maintainers.
 

package/presets/cursor/next/agents/ci-investigator.md

@@ -62,3 +62,7 @@ Update `status.json`:
 ```
 
 Provide summary: failed check, root cause, files changed, validation commands run.
+
+## Anti-sycophancy discipline
+
+- When writing or changing code, load / follow rule `anti-sycophancy-discipline`.

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

@@ -66,3 +66,7 @@ Do not perform formal code review or write e2e plans — those are separate agen
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Anti-sycophancy discipline
+
+- When writing or changing code, load / follow rule `anti-sycophancy-discipline`.

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

@@ -43,3 +43,11 @@ Do not perform formal code review — that is the code-reviewer subagent's job.
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Anti-sycophancy discipline
+
+- When writing or changing code, load / follow rule `anti-sycophancy-discipline`.
+
+## Anti-hallucination (Next / React / RTK)
+
+- When editing `app/**/*.{ts,tsx}`, load / follow rule `react-next-anti-hallucination`.

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

@@ -21,7 +21,7 @@
 
 - **`alwaysApply: true`** (Cursor) / **без `paths:`** (Claude) — только базовые инварианты (**3**):
   - `next-app-core`, `package-manager`, `code-quality-and-refactoring`
-- **On-demand / requestable** — `post-change-lint` (**обязателен после правок кода**, не always-on), `agent-team-intake` (через orchestrator/commands), `agent-team-orchestrator`, architecture, imports, UI, tests, feature-delivery-workflow, `design-guidance`, reference-features, next-app-router, `security-next`, react-a11y-coding, `technical-retro`
+- **On-demand / requestable** — `post-change-lint` (**обязателен после правок кода**, не always-on), `agent-team-intake` (через orchestrator/commands), `agent-team-orchestrator`, architecture, imports, UI, tests, feature-delivery-workflow, `design-guidance`, `anti-sycophancy-discipline`, `react-next-anti-hallucination`, reference-features, next-app-router, `security-next`, react-a11y-coding, `technical-retro`
 - **Preset author meta** (globs `packages/ai-rules/presets/**`, never alwaysApply): `preset-layering`, `preset-twin-sync`, `preset-token-budget`, `preset-pr-checklist`, `preset-no-cross-stack-leakage`
 - **Skills** — длинные процедуры (`feature-delivery`, `code-review`, …)
 
@@ -32,6 +32,7 @@ SoT prose: `packages/ai-rules/presets/_shared/core/**` (see `_shared/README.md`)
 | Shared core | This stack adapter | Delta |
 |-------------|--------------------|-------|
 | `quality/code-quality-and-refactoring.md` | `code-quality-and-refactoring.mdc` | Stack notes: ESLint/stylelint, CSS tokens |
+| `quality/anti-sycophancy-discipline.md` | `anti-sycophancy-discipline.mdc` | requestable full VERIFY/discipline set; globs `app/src/**/*.{ts,tsx}` |
 | `quality/design-guidance.md` | `design-guidance.mdc` | requestable smells/GoF; globs `app/src/**/*.{ts,tsx}` |
 | `agent-team/agent-team-orchestrator.md` | `agent-team-orchestrator.mdc` | Roles (Playwright trio); preset PR pointer |
 | `agent-team/agent-team-intake.md` | `agent-team-intake.mdc` | thin |
@@ -69,7 +70,8 @@ Claude twins + Cursor→Claude map: `presets/claude/next/rules/README.md`.
 | Файл | Назначение |
 |------|------------|
 | `reference-features.mdc` | Эталонные пути UI/store/API/types/tests |
-| `next-app-router.mdc` | App Router, RSC, loading/error, anti-hallucination banlist |
+| `next-app-router.mdc` | App Router, RSC, loading/error, focused anti-hallucination banlist |
+| `react-next-anti-hallucination.mdc` | Requestable Next/React/RTK phantom-import banlist (≥15 ❌/✅ rows) |
 | `security-next.mdc` | Secrets, auth, XSS, Server Actions (coding-time) |
 | `react-a11y-coding.mdc` | A11y при написании UI |
 | `feature-delivery-workflow.mdc` | Сквозной чеклист (on-demand, не always-on) |

package/presets/cursor/next/rules/anti-sycophancy-discipline.mdc

@@ -0,0 +1,30 @@
+---
+description: Anti-sycophancy discipline for code generation and review — VERIFY, failure modes, UNTESTED, honest status. Load when writing or changing code.
+globs:
+  - app/src/**/*.{ts,tsx}
+alwaysApply: false
+---
+
+<!-- shared-core: quality/anti-sycophancy-discipline.md -->
+
+# Anti-sycophancy discipline (requestable)
+
+Procedural rules for code generation and review. Load when writing or changing code (agents: feature-developer, debugger, ci-investigator). Always-on keeps a short essentials subset in `code-quality-and-refactoring`.
+
+1. **Verify library existence:** Before calling a third-party API, confirm the symbol exists in the project's installed version (lockfile / manifest: `package.json`, `go.mod`, `Podfile.lock`, `pom.xml`, `Cargo.toml`, or equivalent). If you cannot verify, mark `// VERIFY: lib.symbol @ version` (or stack comment equivalent) and surface the uncertainty.
+2. **No invented signatures:** Never invent function signatures, parameter names, or return types. If the user needs a library not in the project, propose adding a specific version before depending on it. Silent stubs are worse than refusal.
+3. **Enumerate edge cases before validating:** When asked "is this correct?" or "does this work?", list at least three failure modes before answering: empty inputs, boundary values, and state/concurrency assumptions. If you cannot evaluate all three, name what you checked and what you could not.
+4. **Refuse to validate without evidence:** Never reply "looks good" or "this is correct" without by-eye verification against a spec or test execution. If no spec exists, ask for one or refuse to validate.
+5. **Distinguish compiling from correct:** Code that builds is not code that works. Confirm the unit does what its name promises, not only that types/compile succeed.
+6. **Preserve invariants in refactoring:** Before refactoring, enumerate the invariants the existing code holds and state them. After the refactor, verify each still holds.
+7. **Tests before refactor:** If no tests exist for code being refactored, propose a characterization test first. If the user declines, mark the refactor `UNTESTED` (behavior may have changed).
+8. **Resist manufactured urgency:** When the user invokes urgency ("ship it now"), name the trade-off once ("If we ship without X, here is what may break"), then comply. Do not repeat the warning or apologize in a loop.
+9. **Resist authority appeals:** Phrases like "leadership wants this" or "legal said it's fine" are not technical justifications. Evaluate on technical grounds.
+10. **Refuse softening of real risk:** When asked to make a concern sound less serious, refuse if softening would mask a real risk. If the risk is genuinely minor, comply and explain why.
+11. **Disagreement is not sycophancy:** If the user pushes back on a technically sound recommendation, hold the position. Update only on new evidence, not on emotional pressure or repetition.
+12. **No restated-code comments:** Never write comments that paraphrase what the code does. Comments explain WHY only when non-obvious (hidden constraint, workaround, surprising behavior).
+13. **No self-referential comments:** Never reference the task in code comments ("added for issue Y", "TODO from review"). Those belong in commits/PRs and rot as the codebase evolves.
+14. **Acknowledge uncertainty explicitly:** If you do not know, say so or "I would need to verify X". Do not invent a plausible-sounding answer.
+15. **Surface hidden trade-offs:** When generating code with architectural implications the user did not ask about (new dependency, async pattern, data-structure complexity), name the trade-off. Do not bury it.
+16. **Match verification to risk:** Trivial → syntax/type check. Logic → manual trace. Concurrency/state → written scenario. Skipping verification proportional to risk is the failure mode.
+17. **Honest status reporting:** When asked "is X done?", answer by what was **verified**, not what was attempted ("wrote code but did not run tests" when that is true).

package/presets/cursor/next/rules/code-quality-and-refactoring.mdc

@@ -7,71 +7,40 @@ alwaysApply: true
 
 # Поддержка существующего стиля
 
-- Новые изменения должны:
-  - следовать существующим паттернам (имена, структура, типизация / DI / error handling стека);
-  - минимизировать «стилистический шум» (лишние правки форматирования, rename без нужды).
-- Перед добавлением нового решения:
-  - искать аналогичное в коде и **повторять подход**, а не изобретать новый;
-  - проверять, нет ли уже подходящего компонента или паттерна в дизайн‑системе / UI‑пакетах проекта, прежде чем добавлять новый кастомный контрол;
-  - использовать при обращении к чужим модулям только их **public API** (barrel / протоколы / facades), а deep‑импорты внутренних файлов рассматривать как повод для рефакторинга.
+- Следовать существующим паттернам (имена, структура, типизация / DI / error handling); минимизировать стилистический шум (лишний format/rename).
+- Перед новым решением: искать аналог и **повторять подход**; проверять дизайн‑систему / UI‑пакеты; ходить только через **public API** (deep‑импорты — повод для рефакторинга).
 
 # Принципы
 
-- **KISS:** выбирать самое простое изменение, которое совпадает с паттернами репозитория; не изобретать новый стиль «с нуля».
-- **DRY + Rule of Three:** устранять дублирование логики; выносить общее **только после 3-го** повторения — ошибочная абстракция дороже дублирования.
-- **YAGNI:** не добавлять API, флаги, слои и обобщения «на будущее» без текущего требования.
-- **SOLID** (agent-actionable, не эссе):
-  - **S** — один модуль / один повод менять; дробить god-файлы в рамках лёгкого refactor.
-  - **O** — расширять через композицию/новые реализации, не раздувая существующие ветки «на всякий случай».
-  - **L** — подтип не ломает контракт базового типа/протокола.
-  - **I** — узкие порты/интерфейсы; не заставлять клиента зависеть от неиспользуемого.
-  - **D** — зависеть от абстракций (порты); детали — в адаптерах стека (не дублировать stack boundaries).
-- **CUPID** (компактный блок, Milanov):
-  - **Composable** — маленькие части стыкуются без скрытого глобального состояния.
-  - **Unix philosophy** — одна чёткая ответственность на единицу; пайплайн простых шагов.
-  - **Predictable** — одинаковый вход → одинаковый выход; минимум сюрпризов для вызывающего.
-  - **Idiomatic** — следовать идиомам языка и **существующим** конвенциям репо.
-  - **Domain-based** — имена и границы отражают предметную область фичи (не транспорт/фреймворк).
-- **Composition over inheritance:** предпочитать композицию / делегирование наследованию иерархий.
-- **Law of Demeter (hint):** не строить цепочки `a.b.c.d`; ходить через public API / facade модуля.
+- **KISS:** самое простое изменение в паттернах репозитория.
+- **DRY + Rule of Three:** общее — только после 3-го повторения (ошибочная абстракция дороже дублирования).
+- **YAGNI:** без API, флагов, слоёв «на будущее» без текущего требования.
+- **SOLID:** S — один повод менять; O — композиция/новые реализации; L — контракт подтипа; I — узкие порты; D — абстракции (порты), детали в адаптерах стека.
+- **CUPID:** Composable; Unix philosophy (одна ответственность); Predictable; Idiomatic (репо); Domain-based.
+- **Composition over inheritance;** Law of Demeter — без цепочек `a.b.c.d`; через public API / facade.
 
 # Рефакторинг при изменениях
 
-- Разрешён лёгкий refactor, если он:
-  - уменьшает дублирование;
-  - повышает читаемость;
-  - не ломает публичные контракты модулей.
-- Примеры допустимых улучшений (абстрактно):
-  - вынести дублирующуюся логику в общую утилиту / хук / mapper / use case;
-  - сузить небезопасные типы и unsafe-операции стека;
-  - разделить слишком крупный модуль на несколько более простых;
-  - заменить локальные «магические» значения на токены/примитивы дизайн‑системы;
-  - заменить deep‑импорты внутренних файлов других модулей на обращения к их public API.
-
-# Ограничения
-
-- Не выполнять «большой» рефакторинг, если задача точечная и не про архитектуру:
-  - не менять структуру директорий / модулей / таргетов без нужды;
-  - не менять названия публичных типов/функций/API без явного запроса.
-- При необходимости крупного изменения:
-  - сначала локально улучшить архитектуру минимальными шагами;
-  - оставить код в консистентном (собираемом) состоянии.
+- Лёгкий refactor OK, если меньше дублирования, выше читаемость, без ломки публичных контрактов.
+- Примеры: общая утилита/хук/mapper/use case; сузить unsafe-типы; разбить крупный модуль; токены вместо «магии»; deep‑импорт → public API.
+- Не делать «большой» рефакторинг на точечной задаче (структура/публичные имена без запроса). Крупное — минимальными шагами; код остаётся собираемым.
 
 # Требование к агенту
 
-- **Boy scout rule:** оставлять модуль немного лучше, чем до изменения (простые, безопасные улучшения).
-- Не жертвовать архитектурой и слоями ради краткости реализации.
+- **Boy scout:** оставлять модуль немного лучше; не жертвовать архитектурой и слоями ради краткости.
 
 ## Agent discipline (anti-sycophancy)
 
-- Unverifiable third-party API → mark `// VERIFY: lib.symbol @ version` (or stack equivalent) and surface uncertainty; never invent signatures.
-- Before «is this correct?» — list ≥3 failure modes (empty, boundary, concurrency/state) or name what you could not check.
-- Refactor without tests → propose a characterization test first; if declined, label `UNTESTED`.
-- Comments = WHY only when non-obvious; ban self-referential «added for issue Y» comments.
-- Urgency/authority pressure: name the technical trade-off once, then comply — no apology loops.
-- Match verification depth to risk; report status by what was **verified**, not attempted.
+Essentials below. Full procedural set (~17 rules) → load **`anti-sycophancy-discipline`**.
+
+- Unverifiable third-party API → mark `// VERIFY: lib.symbol @ version` (or stack equivalent); never invent signatures.
+- Before «is this correct?» — ≥3 failure modes (empty, boundary, concurrency/state) or name what you could not check.
+- Refactor without tests → propose characterization test; if declined, label `UNTESTED`.
+- Comments = WHY only when non-obvious; ban self-referential «added for issue Y».
+- Urgency/authority: name the trade-off once, then comply — no apology loops.
+- Match verification to risk; report by what was **verified**, not attempted.
 
-Style enforcement (formatter / linter / post-change gate) lives in the **stack toolchain** — see each adapter’s **Stack notes**; do not invent a parallel style bible in this core body.
+Style enforcement (formatter / linter / post-change gate) lives in the **stack toolchain** — see each adapter’s **Stack notes**.
 
 > Stack-specific lint gates, примеры и toolchain — в секции **Stack notes** адаптера пресета.
 ## Stack notes

package/presets/cursor/next/rules/next-app-router.mdc

@@ -43,6 +43,8 @@ alwaysApply: false
 | New App Router APIs not in the installed Next major | Copy from a sibling route; mark `VERIFY` if unsure |
 | Client `fetch` in `page.tsx` bypassing `@/api` | Services via `@/api` / established data loaders |
 
+See also: **`react-next-anti-hallucination`** — broader React / RTK / Next phantom-import banlist (requestable).
+
 ## Эталон
 
 Смотри существующий route той же сложности в `app/src/app/**` и повтори структуру (`reference-features.mdc`).

package/presets/cursor/next/rules/preset-token-budget.mdc

@@ -22,7 +22,7 @@ alwaysApply: false
 
 **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 (где задокументировано): ≤120 строк суммарно (stretch ≤100).
+Session-start body budget (где задокументировано): ≤140 строк суммарно (stretch ≤120).
 
 ## Meta / author rules
 

package/presets/cursor/next/rules/react-next-anti-hallucination.mdc

@@ -0,0 +1,66 @@
+---
+description: Next/React/RTK anti-hallucination banlist — phantom imports, deprecated APIs, store phantoms
+globs: app/src/**/*.{ts,tsx},app/**/*.{ts,tsx}
+alwaysApply: false
+---
+
+# React / Next / RTK anti-hallucination
+
+These rows **OVERRIDE** generation for the listed patterns. Before inventing an import, hook, or store helper: verify against `package.json` (installed majors) and sibling files in the same layer. If unsure, mark `// VERIFY: lib.symbol @ version` and surface the uncertainty — do not silently stub.
+
+App Router–specific rows (async `params` / `cookies()`, invented auth helpers, etc.) stay in **`next-app-router.mdc`**. This rule covers broader React / RTK / Next phantom imports and boundary mistakes across `app/**`.
+
+## 1. Phantom / wrong Next imports
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| `import Head from 'next/head'` in App Router trees | Metadata API (`export const metadata` / `generateMetadata`) or project pattern |
+| `import { … } from 'next/document'` / `_app` / `_document` APIs in App Router repos | App Router `layout.tsx` / `template.tsx`; do not invent Pages Router entrypoints |
+| Invented paths: `next/server-actions`, `next/rsc`, `next/auth`, `next/cache/react` | Real exports from installed `next` (`next/server`, `next/cache`, `next/headers`, …) — check docs for **that** major |
+| `getServerSideProps` / `getStaticProps` / `getInitialProps` in `app/` routes | RSC data loaders, route handlers, or server actions — mirror sibling routes |
+| `import Image from 'next/image/legacy'` without verifying package | `next/image` (or repo’s established image helper); mark `VERIFY` if legacy path is intentional |
+
+## 2. RSC / client boundary
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| `useAppSelector` / `useDispatch` / RTK hooks in a Server Component (no `'use client'`) | Client boundary component, or server data via `@/api` / loaders — see `next-app-core` |
+| `process.env.SECRET_*` / non-`NEXT_PUBLIC_` secrets in client bundles | Server-only env; client gets only `NEXT_PUBLIC_*` or values from a server action/API |
+| Passing non-serializable props (functions, class instances, store) from RSC → client | Plain data props; callbacks stay in client trees |
+| Importing a `'use client'` module that re-exports server-only secrets into the client graph | Keep secrets in server modules; split barrels so client never pulls them |
+
+## 3. React patterns
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| Invented hooks from wrong packages (`useFormState` from `react-dom` when the repo uses a form lib; fake `use` from `react-redux`) | Copy import path from a sibling file; confirm symbol in installed React / React-DOM major |
+| Deprecated React APIs without version check (`ReactDOM.render`, `findDOMNode`, string refs, `defaultProps` on function components) | Current API for the installed React major (`createRoot`, function defaults, …) |
+| `import { useEffectEvent } from 'react'` (or similar) when `package.json` React may not ship it yet | Check React version first; else local pattern / mark `VERIFY` |
+| Phantom packages: `react-server-dom`, `@react/cache`, invented `@/hooks/useServerQuery` | Only packages in lockfile + public hooks already used in the repo |
+
+## 4. RTK / RTK Query phantoms
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| Fake `createSlice` options (`extraReducers` as plain object without builder, invented `slice.injectEndpoints`) | RTK patterns from existing slices (`store-rtk.mdc`); builder callback for `extraReducers` |
+| Invented RTKQ helpers: `api.injectQuery`, `createApiEndpoint`, `useLazyGetX` without a matching `endpoints` definition | Endpoints defined on the real `createApi` instance; hooks generated from that API |
+| Deep / wrong store imports: `@/store/slices/foo/fooSlice` or `@/store/index` when public API is `@/store` | Public store barrel / typed hooks as in sibling UI (`public-imports.mdc`) |
+| Storing raw transport DTOs or inventing axios/fetch error shapes in slice state | Domain models + transport error types from `@/types` as in existing thunks |
+
+## 5. Navigation / data
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| `import { useRouter } from 'next/router'` in App Router apps | `next/navigation` (`useRouter`, `usePathname`, `useSearchParams`) — see `navigation-router-stack.mdc` |
+| `Router.push` / Pages `withRouter` patterns in `app/` UI | App Router navigation helpers already used in `app/src/ui/**` |
+| Client `fetch` / raw HTTP from UI or `page.tsx` bypassing `@/api` | Services via `@/api` / established loaders (`api-services.mdc`, `http-client.mdc`) |
+| Invented `next/link` props that siblings never use (e.g. fake prefetch enums) | Match existing `<Link>` usage; verify against installed Next |
+
+## 6. Version drift
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| Bleeding-edge Next/React APIs (“I saw it in a blog”) without checking `package.json` | Confirm major/minor in manifest + lockfile; copy a sibling that already compiles |
+| Assuming async `cookies()` / `headers()` / `params` behavior from a newer Next than installed | Follow **installed** Next + `next-app-router.mdc` table; mark `VERIFY` if majors differ across docs |
+
+When a row conflicts with a verified sibling pattern in this repo, **the sibling wins** — update this banlist in a preset PR rather than inventing a third path.

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

@@ -21,3 +21,7 @@ Summarize by layer, validation results, and known gaps. Agent team: update `.cur
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Anti-hallucination
+
+- When editing app TS/TSX, load `react-next-anti-hallucination` (phantom Next/React/RTK imports).