@bonesofspring/ai-rules 0.2.6 → 0.2.8

package/presets/cursor/next/rules/preset-pr-checklist.mdc

@@ -17,7 +17,7 @@ alwaysApply: false
 
 - [ ] **SoT:** правки в `packages/…` (не только root `.cursor/`)
 - [ ] **Core:** если менялся `_shared/core/**` — обновлены все `<!-- shared-core: … -->` consumers (или documented intentional fork)
-- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, ios-swift, and go — см. `preset-twin-sync`)
+- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, ios-swift, go, and java — см. `preset-twin-sync`)
 - [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table актуален
 - [ ] **Token budget:** alwaysApply / session-start ≤ 3; meta rules not always-on
 - [ ] **Leakage:** нет чужих stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)

package/presets/cursor/next/rules/preset-twin-sync.mdc

@@ -20,6 +20,7 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 | `next` | `presets/cursor/next/rules/*.mdc` | `presets/claude/next/rules/<topic>/` | **Required** in `claude/next/rules/README.md` |
 | `ios-swift` | `presets/cursor/ios-swift/rules/*.mdc` | `presets/claude/ios-swift/rules/<topic>/` | Keep in `claude/ios-swift/rules/README.md` |
 | `go` | `presets/cursor/go/rules/*.mdc` | `presets/claude/go/rules/<topic>/` | Keep in `claude/go/rules/README.md` |
+| `java` | `presets/cursor/java/rules/*.mdc` | `presets/claude/java/rules/<topic>/` | Keep in `claude/java/rules/README.md` |
 
 ## Same-PR checklist
 
@@ -38,5 +39,6 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 - **next:** missing Claude twin for a changed Cursor rule → **FAIL** (mapping table required).
 - **ios-swift:** missing Claude twin for a changed Cursor rule → **FAIL**.
 - **go:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift; mapping table required).
+- **java:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go; mapping table required).
 
 Dogfood: sync packages → root `.cursor/` after Cursor SoT changes (not the reverse). Use `packages/ai-rules/scripts/sync-dogfood-cursor.sh`.

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

@@ -7,6 +7,7 @@ globs:
   - app/src/types/**/*
   - app/src/api/**/*
 alwaysApply: false
+impact: HIGH
 ---
 
 # Публичные импорты (`@/types`, `@/api`)
@@ -46,3 +47,16 @@ import { MedcardApiService } from '@/api/services/MedcardApiService/MedcardApiSe
 ```
 
 Новые публичные символы API — реэкспорт в `app/src/api/index.ts` по **`layer-barrel-exports.mdc`**.
+## Incorrect
+
+```ts
+import type { TUserProfile } from '@/types/User.types'
+import { OrdersApi } from '@/api/services/OrdersApi'
+```
+
+## Correct
+
+```ts
+import type { TUserProfile } from '@/types'
+import { ordersApi } from '@/api'
+```

package/presets/cursor/next/rules/react-ui.mdc

@@ -2,6 +2,7 @@
 description: Паттерны React/Next UI и стилей (preset)
 globs: app/src/ui/**/*.tsx,app/src/ui/**/*.ts
 alwaysApply: false
+impact: HIGH
 ---
 
 # Общие правила компонентов
@@ -89,4 +90,23 @@ alwaysApply: false
   - **Testing Library** для React, как принято в проекте;
   - проверять поведение и бизнес‑правила, а не конкретные CSS‑классы.
 - В тестах ориентироваться на текст, роли и aria‑атрибуты.
+## Incorrect
 
+```tsx
+import { mapUserDto } from '@/api/services/UsersApi/userResponseMappers'
+
+export const UserBadge = ({ dto }: { dto: unknown }) => {
+  const user = mapUserDto(dto as any) // mapping + deep import in UI
+  return <span>{user.name}</span>
+}
+```
+
+## Correct
+
+```tsx
+import type { TUserProfile } from '@/types'
+
+export const UserBadge = ({ user }: { user: TUserProfile }) => {
+  return <span>{user.name}</span>
+}
+```

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

@@ -38,6 +38,10 @@ Taxonomy / shared core: [`presets/_shared/README.md`](../../../../_shared/README
 3. Зеркаль именование, порядок файлов, паттерны импортов и тестов.
 4. Если эталона нет — выбери **самую близкую** существующую фичу того же слоя и зафиксируй выбор в handoff.
 
+## Living conventions
+
+Post-init gotchas / patterns / decisions: **`.cursor/team/conventions.md`** (and the twin tool path if both Cursor and Claude are installed). Consumer-owned; not always-on. See root `AGENTS.md` § Living conventions.
+
 ## Связанные правила
 
 - `code-quality-and-refactoring.mdc` — повторять паттерны, не deep-import.

package/presets/cursor/next/rules/security-next.mdc

@@ -0,0 +1,57 @@
+---
+description: Next.js frontend security — secrets, auth, XSS, Server Actions, env
+globs:
+  - "app/src/**/*.{ts,tsx}"
+  - "app/**/app/**/*.{ts,tsx}"
+  - "**/*Auth*.{ts,tsx}"
+  - "**/*Session*.{ts,tsx}"
+  - "**/.env*"
+alwaysApply: false
+impact: CRITICAL
+---
+
+# Security (Next.js)
+
+Coding-time checklist. Full audit → agent `security-reviewer` + skill `code-review`.
+
+## Secrets and env
+
+- Never put service / secret keys in `NEXT_PUBLIC_*` or client bundles (`sk_`, private API keys, DB URLs).
+- Do not commit `.env*` with real secrets; use CI / secret manager patterns already in the repo.
+- Prefer server-only modules for privileged clients; do not import them into Client Components.
+
+## Auth and session
+
+- Enforce auth on the **server** (layouts, pages, Server Actions, route handlers) — not only Edge middleware.
+- Middleware may refresh sessions; do not treat middleware alone as authorization.
+- Prefer httpOnly secure cookies over `localStorage` for tokens when the repo pattern allows.
+- Never trust client-only session claims without a server verify step used by the project.
+
+## Mutations and input
+
+- Server Actions / route handlers: validate untrusted input at the edge (Zod or the repo’s schema pattern).
+- Prefer an explicit success/error response shape over throwing opaque errors to the client.
+- CSRF / origin checks — follow existing repo middleware and form patterns for state-changing requests.
+
+## XSS and output
+
+- Avoid `dangerouslySetInnerHTML` unless sanitized and unavoidable; prefer text nodes / safe components.
+- Sanitize or encode user-generated HTML/markdown before render.
+- Open redirects: validate redirect targets against an allowlist or same-origin paths.
+
+## Data exposure
+
+- Do not log tokens, passwords, or full PII in client or server logs.
+- Do not return full privileged records to the client — map to the minimum domain fields the UI needs.
+
+## Anti-hallucination
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| Invented auth helpers not in `package.json` / codebase | Copy patterns from existing auth routes |
+| Putting secrets in `NEXT_PUBLIC_*` | Server-only env + server modules |
+| Auth only in middleware | Server `getUser` / session verify in layout/page/action |
+
+## Agent requirement
+
+On auth, forms, payments, or env changes — load this rule and `code-review-mr.mdc`. Route sensitive features through `security-reviewer`.

package/presets/cursor/next/rules/store-rtk.mdc

@@ -2,6 +2,7 @@
 description: Redux Toolkit и состояние приложения
 globs: app/src/store/**/*.ts
 alwaysApply: false
+impact: HIGH
 ---
 
 # Общие принципы
@@ -63,4 +64,22 @@ alwaysApply: false
 - Строго типизировать state и actions.
 - Использовать единый стиль именования actions и селекторов, как в существующих слайсах.
 - При работе с ошибками и ответами HTTP опираться на **`http-client.mdc`** и контракты из `@/types`, а не на типы внешних HTTP‑библиотек вне зависимостей проекта.
+## Incorrect
 
+```ts
+export const loadProfile = createAsyncThunk('profile/load', async () => {
+  const res = await fetch('/api/profile')
+  return res.json() // raw DTO into slice
+})
+```
+
+## Correct
+
+```ts
+import { profileApi } from '@/api'
+
+export const loadProfile = createAsyncThunk('profile/load', async () => {
+  // service returns domain model already mapped
+  return profileApi.getProfile()
+})
+```

package/presets/cursor/next/rules/tests-unit.mdc

@@ -4,6 +4,7 @@ globs:
   - app/src/**/*.spec.{ts,tsx}
   - app/src/**/*.test.{ts,tsx}
 alwaysApply: false
+impact: MEDIUM
 ---
 
 # Общие правила тестирования
@@ -63,4 +64,15 @@ it('Returns empty list when user is guest', () => {})
    - для **компонентов UI** — **не создавать** поддиректорию `__tests__` внутри папки компонента; тест — соседний `*.spec.tsx`.
    - в **других модулях** (например `api/services`) допустима уже существующая схема с `__tests__` — не ломать ради единообразия с UI.
    - **новые** файлы — `*.spec.ts` / `*.spec.tsx` (см. блок «Имена файлов» выше).
+## Incorrect
 
+```ts
+it('returns empty list when guest', () => {})
+it('Возвращает пустой список. пользователь не авторизован', () => {})
+```
+
+## Correct
+
+```ts
+it('Возвращает пустой список. Пользователь не авторизован', () => {})
+```

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

@@ -11,5 +11,7 @@ Project skills for Cursor. They keep long workflows out of always-on rules while
 | `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 |
+| `write-adr` | Author an Architecture Decision Record (context / decision / consequences) |
+| `react-performance` | Implementer checklist: bundle, RSC/client, memo, waterfalls, CWV (not a perf audit agent) |
 
 Skills are copied to `.cursor/skills/` by `ai-rules init cursor --preset next`.

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

@@ -17,11 +17,19 @@ Use the local repository as the source of truth: `git status`, `git diff`, task
 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.
+7. **Reuse lens:** flag new helpers that duplicate existing utilities; prefer adjacent shared modules over copy-paste.
+8. **Efficiency lens:** unnecessary work, sequential ops that should be parallel, hot-path bloat, no-op store updates, overly broad reads.
+9. 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.
+Lead with findings ordered by severity. Required shape (also in `code-review-mr`):
+
+- Each finding: **`path:line`** — problem — impact — concrete fix direction.
+- Severity: **`blocker` | `important` | `nit`** (list blocker → nit).
+- Vague («looks risky») is not a finding — cite evidence or ask for surrounding context.
+- End with a verdict line: **`Safe to merge | needs changes | reject`**.
+- 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/feature-delivery/SKILL.md

@@ -10,6 +10,10 @@ description: Delivers Next.js frontend features end-to-end across domain types,
 3. Add or update focused tests for changed behavior.
 4. Validation from `app/`: **invoke** **`post-change-lint.mdc`** after code edits (requestable, not always-on — but mandatory when code changed). Pipeline: scoped lint OK if next step is `build-verifier`.
 
+## Scope discipline
+
+Implement only the current AC / decomposition task. Clarify ambiguity before coding; do not add unrelated hardening, polish, or refactors. See `feature-developer` → **Zero improvisation**.
+
 ## Handoff
 
 Summarize by layer, validation results, and known gaps. Agent team: update `.cursor/team/tasks/<slug>/status.json`.

package/presets/cursor/next/skills/react-performance/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: react-performance
+description: Next.js React performance checklist for implementers — bundle, RSC/client boundaries, memoization discipline, data-fetch waterfalls, Core Web Vitals. Use while coding a next feature; not a substitute for the performance-auditor agent when the user asks for an audit report.
+---
+
+# React performance (next)
+
+On-demand checklist for **implementers** shipping Next.js UI. For a formal diff audit report, use the **`performance-auditor`** agent instead — this skill does not replace it.
+
+## Bundle
+
+- Prefer route-level and component-level code splitting for heavy UI (charts, editors).
+- Avoid importing large libraries into shared layouts; keep client entry points small.
+- Check that barrel files do not re-export heavy modules into every consumer.
+
+## RSC / client boundaries
+
+- Default to Server Components; add `"use client"` only when hooks, browser APIs, or interactivity require it.
+- Keep client leaves small; pass serializable props from server parents.
+- Do not pull server-only modules (secrets, Node APIs) into client components.
+
+## Memoization discipline
+
+- Do **not** add `useMemo` / `useCallback` by default — follow the repo’s React Compiler / team guidance.
+- Memoize when profiling shows unstable props causing expensive subtree re-renders, or when an existing pattern already does.
+- Prefer fixing state placement and list keys over blanket memo wrappers.
+
+## Data-fetch waterfalls
+
+- Avoid sequential awaits that could be parallel (`Promise.all`) when independent.
+- Lift shared fetches to a layout/parent when multiple children need the same data.
+- Prefer store/thunk or server fetch patterns already used in the feature’s reference slice — do not invent a second data layer.
+
+## Core Web Vitals (quick)
+
+| Metric | Implementer checks |
+|--------|--------------------|
+| LCP | Hero/media not blocked by unnecessary client JS; sensible image sizing |
+| INP | Click handlers lean; avoid long sync work on the main thread |
+| CLS | Reserve space for images/skeleton; stable fonts |
+
+## Handoff
+
+If the user asks for a **performance audit report** of a diff/deliverable, route to **`performance-auditor`** (readonly `perf-report.md`), not this skill alone.

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

@@ -29,12 +29,26 @@ Ask for missing period, focus, task slug, participants, or format constraints. I
 
 For `/task` pipelines, include router, analyst, developer, **build-verifier**, reviewer, QA/e2e, hooks, and rules.
 
+## Wrong-turn taxonomy (optional)
+
+When artifacts or the user mention agent mistakes, tag incidents:
+
+| Kind | Signal |
+|------|--------|
+| `correction` | User pushback («no», «don't», «actually») |
+| `retry` | Same tool/approach 2+ times before success |
+| `waste` | Many searches before the right file |
+| `reversal` | Edit then revert / delete |
+| `dead-end` | Env/tool failure (missing binary, wrong path) |
+
+Severity: **high** (explicit correction / large waste) · **med** · **low**. Confidence 0–100 — be honest; low-confidence items are optional.
+
 ## Preset feedback loop
 
-If the same issue appeared in 2+ tasks, add section **Preset updates**:
+If the same issue appeared in **2+** tasks (or **3+** for packaging a new rule/skill — Rule of Three), 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
+- Proposed change to `.cursor/rules/`, `.cursor/agents/`, `.cursor/skills/`, or **`.cursor/team/conventions.md`** (prefer conventions for project gotchas)
+- One concrete snippet or file path
+- Whether it belongs in always-on vs globs vs skill vs conventions (see `PRESET-CONTRIBUTION` → Building blocks)
 
-Do not apply preset changes without user approval.
+Do not apply preset or conventions changes without user approval.

package/presets/cursor/next/skills/write-adr/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: write-adr
+description: Author an Architecture Decision Record (ADR) with Context, Decision, Consequences, and Links. Use when capturing a durable technical choice for the team.
+---
+
+# Write ADR
+
+On-demand skill for durable architecture decisions. Stack-agnostic sections — fill with project-specific paths and links.
+
+## When to use
+
+- Choosing between non-trivial alternatives (storage, layering, library, API shape).
+- Recording a decision that future agents/humans should not silently reverse.
+- User asks for an ADR, decision log, or “why did we pick X”.
+
+## Template
+
+Create (or append) a short markdown ADR in the repo’s agreed location (e.g. `docs/adr/`, `.cursor/team/`, wiki). Suggested filename: `NNNN-short-title.md`.
+
+```markdown
+# ADR NNNN: <Title>
+
+## Context
+What problem / constraint / force requires a decision?
+
+## Decision
+What we chose (one clear option). Include rejected alternatives briefly if useful.
+
+## Consequences
+Positive and negative outcomes; follow-up work; what becomes harder.
+
+## Links
+Related PRs, issues, rules, prior ADRs, diagrams.
+```
+
+## Guidelines
+
+- Prefer one decision per ADR.
+- Keep Context factual; Decision imperative and short.
+- Link living gotchas to `team/conventions.md` when the decision becomes a recurring local pattern.
+- Do not put ADR bodies only in root `AGENTS.md` (overwrite on init).

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

@@ -0,0 +1,21 @@
+# Living conventions (team)
+
+Consumer-owned store for post-init gotchas, patterns, and decisions. **Not** always-on. Fill after `ai-rules init`. Root `AGENTS.md` only points here.
+
+## Gotchas
+
+<!-- e.g. fragile flows, “never do X in this repo” -->
+
+-
+
+## Patterns
+
+<!-- local patterns beyond reference-features table -->
+
+-
+
+## Decisions
+
+<!-- short pointers to ADRs / product choices that affect code -->
+
+-