@bonesofspring/ai-rules 0.2.6 → 0.2.8

package/presets/claude/go/hooks/examples/test-on-save.example.sh

@@ -0,0 +1,11 @@
+#!/usr/bin/env bash
+# Optional: package-scoped go test for changed packages.
+# NOT in default hooks.json.
+set -euo pipefail
+pkgs=$(git diff --name-only --diff-filter=ACMR HEAD 2>/dev/null | grep '\.go$' | xargs -n1 dirname 2>/dev/null | sort -u | sed 's|^|./|' || true)
+if [[ -n "${pkgs:-}" ]]; then
+  go test $pkgs 2>/dev/null || true
+else
+  go test ./... 2>/dev/null || true
+fi
+exit 0

package/presets/claude/go/rules/api-and-data/api-http.md

@@ -6,15 +6,21 @@ paths:
   - **/*router*.go
 ---
 
-
 # HTTP API adapters
 
-- Handlers call inbound ports / use cases; return mapped status + body.
-- Use consistent error envelope; map domain errors centrally.
+- Handlers are **thin**: parse input, call one inbound port / use case, map status + body.
+- Use consistent error envelope; map **domain exceptions** centrally — do not leak transport types into use cases.
 - Version routes if the repo already versions (`/v1/...`).
 - Prefer `net/http` interfaces so tests can use `httptest` without a full framework.
 - Timeouts: set server read/write timeouts; propagate request context.
 
+## Resilience
+
+- Side-effect endpoints (charge, create, enqueue): accept/propagate an **idempotency key** when the domain already uses one; document if intentionally omitted.
+- Outbound HTTP to third parties: prefer **per-provider clients** (separate timeouts/pools) — bulkhead isolation, not one shared client for everything.
+- Provider/ACL adapters return typed results or errors — never raw `map[string]any` / untyped JSON blobs into the domain.
+- Soft file-size hint: plan a split when a handler/router file grows past ~400 LOC; prefer package + re-export over god-files.
+
 ## Testing
 
 - Prefer `httptest` against handler/router with mocked use cases (unit of adapter).
@@ -24,3 +30,4 @@ paths:
 
 - Business rules or SQL in handlers.
 - Ignoring `ctx` cancelation from `r.Context()`.
+- Raising transport-only errors from use cases (keep HTTP mapping at the adapter edge).

package/presets/claude/go/rules/architecture/reference-features.md

@@ -21,6 +21,10 @@ Fill TBD paths after adopting this preset in a real service repo.
 | Unit tests | `*_test.go` beside packages | `**/*_test.go` |
 | Integration | `**/integration/` | `**/*_integration_test.go` |
 
+## Living conventions
+
+Post-init gotchas / patterns / decisions: **`.claude/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.
+
 ## Dogfood scenarios
 
 1. `/task` new use case — domain → ports → adapters → wire → `post-change-test`.

package/presets/claude/go/rules/stack/go-conventions.md

@@ -4,21 +4,48 @@ paths:
   - **/*.go
 ---
 
-
 # Go conventions
 
 - Follow [Effective Go](https://go.dev/doc/effective_go) and repo `golangci-lint` / `staticcheck` when present.
 - Accept `context.Context` as first param on I/O and use-case methods.
-- Wrap errors: `fmt.Errorf("…: %w", err)`; avoid panics in library/service code.
 - Prefer `camelCase` unexported, `PascalCase` exported; package names short and lowercase.
 - Do not expose `internal/` outside the module.
 - Prefer table-driven tests; use `t.Parallel` only when safe.
 
+## Errors
+
+- Always handle errors — never `_ = err`.
+- Wrap with `fmt.Errorf("…: %w", err)`; check with `errors.Is` / `errors.As`.
+- Prefer domain/custom error types for structured cases; avoid panics in library/service code.
+
+## Interfaces
+
+- Accept interfaces, return concrete types.
+- Define interfaces at the **call site** (ports / consumers), not on every implementation.
+- Prefer small, single-method interfaces when they match the use.
+
 ## Packages
 
 - Avoid `util`/`common` dumping grounds — name by domain capability.
 - Keep `main` packages thin (see composition-root).
+- No `init()` for business logic; no package-level mutable state for request data.
 
 ## Concurrency
 
-- Document cancelation; do not start unbounded goroutines from handlers without supervision.
+- Document cancelation; `defer cancel()` after creating a derived context.
+- Do not start unbounded goroutines from handlers without a termination condition / supervision (`WaitGroup`, errgroup, or context cancel).
+- Channels for communication, mutexes for shared state — match existing package patterns.
+
+## Anti-hallucination
+
+| ❌ Avoid | ✅ Prefer |
+|---------|----------|
+| `_ = err` / ignored errors | Handle or wrap with `%w` |
+| Interfaces on every struct «just in case» | Ports at consumer / call site |
+| Invented modules not in `go.mod` | Add dependency explicitly or copy existing import |
+| `interface{}` where generics or a concrete type fit | Generics / concrete types used by the repo |
+| Business logic in `init()` | Wire in composition root / `main` |
+
+## Agent requirement
+
+New Go code must stay idiomatic and verifiable against `go.mod` and neighboring packages. Less guessed code is better than more.

package/presets/claude/go/rules/tooling-and-review/agent-team-intake.md

@@ -16,7 +16,7 @@ When the user message looks like a **work request** (implement, add, fix, refact
 
 1. Prefer **`/task <their request>`** or invoke **task-router** first.
 2. Do not jump straight to coding without router + pipeline when scope is non-trivial.
-3. Pure questions («как работает X», «объясни») — answer normally, no `/task`.
+3. Pure questions («как работает X», «объясни») — prefer agent **`codebase-analyzer`** (explain-as-is); trivial one-liners may be answered inline. Do not open `/task`.
 
 Exceptions: user explicitly says «без pipeline», «просто сделай», or continues an active slug.
 

package/presets/claude/go/rules/tooling-and-review/agent-team-orchestrator.md

@@ -138,7 +138,7 @@ If `pipeline.json` is missing (old `/feature-start` tasks), fall back to fixed p
 
 Do **not** run `/task` + router for:
 
-- Pure questions («как работает X», «объясни»).
+- Pure questions («как работает X», «объясни») — prefer agent **`codebase-analyzer`** for deep traces; inline OK for trivial one-liners.
 - 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.

package/presets/claude/go/rules/tooling-and-review/code-quality.md

@@ -61,8 +61,18 @@ description: Code quality and light refactoring for Go hexagonal services
 - **Boy scout rule:** оставлять модуль немного лучше, чем до изменения (простые, безопасные улучшения).
 - Не жертвовать архитектурой и слоями ради краткости реализации.
 
-> Stack-specific lint gates, примеры и toolchain — в секции **Stack notes** адаптера пресета.
+## 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.
 
+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.
+
+> Stack-specific lint gates, примеры и toolchain — в секции **Stack notes** адаптера пресета.
 ## Stack notes
 
 - **No UI layer in this preset** — ignore shared-core bullets about дизайн‑система / UI‑пакеты / CSS‑токены; apply public-API and boy-scout rules to Go packages/ports instead.
@@ -70,3 +80,4 @@ description: Code quality and light refactoring for Go hexagonal services
 - Prefer wrapping errors with `%w`; check with `errors.Is` / `errors.As`.
 - Interfaces belong at **ports** (consumer side), not on every struct.
 - Post-change gate: **`post-change-test.md`** + **`go-tooling.md`** (not yarn lint / xcodebuild).
+- Style: **gofmt** / **goimports** + **golangci-lint** when configured — authoritative style gate; do not duplicate linter rules in prose.

package/presets/claude/go/rules/tooling-and-review/code-review.md

@@ -40,6 +40,15 @@ Concrete rule stems — in **Stack notes**.
 - Boy scout rule: suggest fixes feasible within the MR scope.
 - No «большие рефакторинги» without an explicit request (`code-quality-and-refactoring`).
 
+## Output contract
+
+Procedure details live in skill `code-review`. Required shape:
+
+- Each finding cites **`path:line`**, the problem, impact, and a concrete fix direction.
+- Rank by severity: **`blocker` | `important` | `nit`** (list blocker → nit).
+- Vague («looks risky») is not a finding — cite evidence or ask for surrounding file context.
+- End with a verdict on its own line: **`Safe to merge | needs changes | reject`**.
+
 ## Stack notes
 
 - Hexagonal boundaries: `architecture-boundaries`, `domain-layer`, ports vs adapters.

package/presets/claude/go/rules/tooling-and-review/preset-layering.md

@@ -24,7 +24,7 @@ paths:
 ## Куда класть новое правило
 
 1. Общие принципы для всех стеков → **core** + адаптеры с `<!-- shared-core: … -->`.
-2. Только один из installable стеков (`next` / `ios-swift` / `go`) → **stack-specific** (не в `_shared`).
+2. Только один из installable стеков (`next` / `ios-swift` / `go` / `java`) → **stack-specific** (не в `_shared`).
 3. Только Cursor или только Claude packaging → platform artifact / frontmatter, не дублировать семантику.
 
 ## SoT

package/presets/claude/go/rules/tooling-and-review/preset-no-cross-stack-leakage.md

@@ -17,7 +17,7 @@ paths:
 
 - `next` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
 - `ios-swift` must not ship Playwright handoffs or Next lint recipes as required commands.
-- `go` must not ship Playwright, XCUITest, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
+- `go` / `java` must not ship Playwright, XCUITest, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
 - Shared core must not embed stack paths (`app/src/**`, `Features/**`, `playwright`, `xcodebuild`).
 
 ## Forbidden in ios-swift hooks/agents (FAIL)
@@ -35,14 +35,16 @@ Required instead: `xcuitest-test-*` stems; build-verifier mentions `xcodebuild`
 - `xcuitest-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Next app work
 
-## Forbidden in go hooks/agents (FAIL)
+## Forbidden in go / java hooks/agents (FAIL)
+
+Shared backend-stack bans (both `go` and `java`):
 
 - `playwright-test-`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`
 - Positive yarn recipes `lint:js` / `lint:css`
 - `xcuitest-test-`, `xcodebuild`, `SwiftLint` as required handoffs
 - Agent file `accessibility-reviewer` (no UI surface)
 
-Required instead: `integration-test-*`; build-verifier / `post-change-test` / `go-tooling` (`go test`, `go vet`).
+Required instead: `integration-test-*`; build-verifier / `post-change-test` plus stack tooling — `go-tooling` (`go test`, `go vet`) or `java-tooling` (`mvn test` / `./gradlew test`).
 
 ## Soft / document
 
@@ -51,8 +53,4 @@ Required instead: `integration-test-*`; build-verifier / `post-change-test` / `g
 
 ## Chain fork
 
-`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `ios-swift`, and `go` (per platform).
-
-## Stack notes
-
-Forbidden positive handoffs on this stack are listed in core § go. Prefer `integration-test-*` and `post-change-test`.
+`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `ios-swift`, `go`, and `java` (per platform).

package/presets/claude/go/rules/tooling-and-review/preset-pr-checklist.md

@@ -17,7 +17,7 @@ paths:
 
 - [ ] **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/claude/go/rules/tooling-and-review/preset-twin-sync.md

@@ -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/claude/go/skills/README.md

@@ -1,5 +1,5 @@
 # Skills (preset go)
 
-7 skills: `feature-delivery`, `unit-testing`, `integration-testing`, `ci-investigation`, `debug-investigation`, `code-review`, `technical-retro`.
+8 skills: `feature-delivery`, `unit-testing`, `integration-testing`, `ci-investigation`, `debug-investigation`, `code-review`, `technical-retro`, `write-adr`.
 
-No `playwright-e2e` / `xcuitest-e2e`.
+No `playwright-e2e` / `xcuitest-e2e` / `react-performance`.

package/presets/claude/go/skills/code-review/SKILL.md

@@ -5,9 +5,18 @@ description: Reviews pull requests and branch diffs for Go hexagonal services us
 
 # Code review (Go)
 
-1. Diff-first; load `code-review-mr.mdc` + hexagonal rules.
+1. Diff-first; load `tooling-and-review/code-review.md` + hexagonal rules.
 2. Check layer leaks, port ownership, composition root purity, tests, security-sensitive bits.
-3. Write `review.md` with APPROVE or REQUEST_CHANGES.
+3. **Reuse lens:** flag new helpers that duplicate existing packages/utilities; prefer shared adapters over copy-paste.
+4. **Efficiency lens:** unnecessary allocations, N+1 I/O, sequential work that should be concurrent, hot-path bloat, missing context cancellation.
+5. Write `review.md` using the output contract below.
+
+## Output
+
+- Each finding: **`path:line`** — problem — impact — concrete fix direction.
+- Severity: **`blocker` | `important` | `nit`** (list blocker → nit).
+- End with a verdict line: **`Safe to merge | needs changes | reject`**.
+- Map agent status: Safe to merge → `completed`; needs changes / reject → `changes_requested`.
 
 Never require iOS/Next-only gates (XCUITest, Playwright, `lint:js`).
 

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

@@ -17,6 +17,10 @@ description: Delivers Go hexagonal backend features end-to-end across domain, ap
 - **Don't** put SQL/business rules in HTTP handlers or frameworks in domain.
 - **Don't** use Playwright, XCUITest, or yarn lint as this stack's gate.
 
+## Scope discipline
+
+Implement only the current AC / decomposition task. Clarify ambiguity before coding; do not add unrelated hardening or drive-by refactors. See `feature-developer` → **Zero improvisation**.
+
 ## Handoff
 
 Summarize by layer + validation. Update `.claude/team/tasks/<slug>/status.json`.

package/presets/claude/go/skills/technical-retro/SKILL.md

@@ -5,6 +5,50 @@ description: Facilitates technical retrospectives for tasks, sprints, incidents,
 
 # Technical Retro
 
-Same structure as next technical-retro skill. For `/task` pipelines include router, analyst, developer, **build-verifier** (go test), reviewer, QA/integration tests, hooks, rules.
+## Inputs
 
-Preset feedback: propose updates to `.claude/rules|agents|skills` — do not apply without approval.
+Ask for missing period, focus, task slug, participants, or format constraints. If a slug is provided, read `.claude/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** (go test), reviewer, QA/integration tests, 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 (or **3+** for packaging a new rule/skill — Rule of Three), add section **Preset updates**:
+
+- Proposed change to `.claude/rules/`, `.claude/agents/`, `.claude/skills/`, or **`.claude/team/conventions.md`** (prefer conventions for project gotchas)
+- One concrete snippet or file path
+- Whether it belongs in session-start vs `paths:` vs skill vs conventions (see `PRESET-CONTRIBUTION` → Building blocks)
+
+Do not apply preset or conventions changes without user approval.

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

package/presets/claude/go/team/fixtures/feature-full.json

@@ -10,34 +10,16 @@
     { "agent": "build-verifier", "label": "go test / go vet / golangci-lint", "model": "cheap" },
     { "agent": "security-reviewer", "label": "Security review", "model": "strong" },
     { "agent": "code-reviewer", "label": "Code review", "model": "cheap" },
-    { "agent": "qa-tester", "label": "Integration tests", "scope": "e2e-only" }
+    { "agent": "qa-tester", "label": "Integration tests", "scope": "e2e-only" },
+    { "agent": "integration-test-planner", "label": "Plan integration coverage" },
+    { "agent": "integration-test-generator", "label": "Generate integration tests" }
   ],
   "humanGates": ["after:task-analyst"],
   "autoChain": true,
   "skipped": [
     {
-      "agent": "playwright-test-planner",
-      "reason": "Go backend uses integration-test-* — not Playwright"
-    },
-    {
-      "agent": "playwright-test-generator",
-      "reason": "Go backend uses integration-test-*"
-    },
-    {
-      "agent": "playwright-test-healer",
-      "reason": "Go backend uses integration-test-*"
-    },
-    {
-      "agent": "xcuitest-test-planner",
-      "reason": "Go backend uses integration-test-* — not XCUITest"
-    },
-    {
-      "agent": "xcuitest-test-generator",
-      "reason": "Go backend uses integration-test-*"
-    },
-    {
-      "agent": "xcuitest-test-healer",
-      "reason": "Go backend uses integration-test-*"
+      "agent": "accessibility-reviewer",
+      "reason": "Go backend has no UI surface"
     }
   ]
 }

package/presets/claude/ios-swift/CLAUDE.md

@@ -2,6 +2,8 @@
 
 Краткая точка входа для Claude Code. Подробные правила — модульные topic `.md` под `rules/` (derived из Cursor SoT).
 
+**Repo-root agents:** see [`AGENTS.md`](../../AGENTS.md) at the project root (cross-tool setup, commands, security, living conventions pointers).
+
 See @rules/README.md for mapping and loading strategy.
 
 ## Conventions
@@ -24,6 +26,7 @@ See @rules/README.md for mapping and loading strategy.
 | UI-тесты | skill `xcuitest-e2e` |
 | Security | `tooling-and-review/security-ios.md` |
 | Валидация | agent `build-verifier` |
+| Как работает X | agent `codebase-analyzer` (explain-as-is) |
 | Ретро | `commands/technical-retro.md` |
 
 ## Install
@@ -32,4 +35,4 @@ See @rules/README.md for mapping and loading strategy.
 npx @bonesofspring/ai-rules init claude --preset ios-swift
 ```
 
-Копирует `CLAUDE.md`, `rules/**`, `commands/**`, `agents/**`, `skills/**`, `hooks/**`, `team/**`, `MCP.md` в `.claude/`, плюс `mcp.json` → **`.mcp.json`** в корне.
+Копирует `CLAUDE.md`, `rules/**`, `commands/**`, `agents/**`, `skills/**`, `hooks/**`, `team/**`, `MCP.md` в `.claude/`, плюс `mcp.json` → **`.mcp.json`** и `REPO_AGENTS.md` → корневой **`AGENTS.md`**. Skill: `write-adr` (on-demand).

package/presets/claude/ios-swift/README.md

@@ -10,7 +10,7 @@
 | `rules/**` | `.claude/rules/**` |
 | `commands/**` | `.claude/commands/**` |
 | `skills/**` | `.claude/skills/**` (**7**, в т.ч. `xcuitest-e2e`) |
-| `agents/**` | `.claude/agents/**` (**21**, XCUITest trio) |
+| `agents/**` | `.claude/agents/**` (**22**, XCUITest trio + `codebase-analyzer`) |
 | `hooks/**` | `.claude/hooks/**` (scripts + README; **нет** `hooks.json`) |
 | `team/**` | `.claude/team/**` |
 | `mcp.json` | **`.mcp.json`** в корне (Context7 + Figma) |
@@ -37,3 +37,7 @@ npx @bonesofspring/ai-rules init claude --preset ios-swift
 - Change Cursor → update Claude twin **same PR**
 - Mapping: [`rules/README.md`](./rules/README.md)
 - **`BUGBOT.md`:** Cursor-only (нет twin); review в Claude — skill `code-review` + `tooling-and-review/code-review.md`
+
+## Cross-tool root AGENTS
+
+`REPO_AGENTS.md` → project-root `AGENTS.md` on init. Living conventions: `team/conventions.md`. Skill `write-adr` on-demand.

package/presets/claude/ios-swift/REPO_AGENTS.md

@@ -0,0 +1,46 @@
+# iOS Swift — agent instructions
+
+Cross-tool repo-root guide. Tool-specific maps stay under `.cursor/AGENTS.md` and `.claude/CLAUDE.md`.
+
+## Cross-tool setup
+
+- Treat this file as the **shared** entry for any agent (Cursor, Claude Code, or other).
+- Tool maps live in `.cursor/AGENTS.md` / `.claude/CLAUDE.md` when that tool is installed.
+- Install:
+
+```bash
+npx @bonesofspring/ai-rules init cursor --preset ios-swift
+npx @bonesofspring/ai-rules init claude --preset ios-swift
+```
+
+`init` overwrites this file from the preset (`REPO_AGENTS.md` → `AGENTS.md`). Living gotchas belong in `team/conventions.md`, not here.
+
+## Commands (test / lint / build)
+
+| Gate | Typical command |
+|------|-----------------|
+| Build | `xcodebuild` (scheme/workspace as in project docs) |
+| Lint | **SwiftLint** (config in repo; see `xcode-tooling` / conventions) |
+| Format | SwiftFormat when configured |
+| Tests | `xcodebuild test` slice for the changed target |
+
+After code edits: invoke **`post-change-build`** (requestable). Full gate: agent `build-verifier`.
+
+## Security basics
+
+- Do not commit secrets (API keys, Keychain dumps, `.env`).
+- Review destructive git before running; respect shell hooks.
+- Do not skip signing / CI gates unless the user explicitly asks.
+
+## Tool entry points
+
+| Tool | Map |
+|------|-----|
+| Cursor | `.cursor/AGENTS.md` (optional if Cursor not installed) |
+| Claude Code | `.claude/CLAUDE.md` (optional if Claude not installed) |
+
+Rules: `.cursor/rules/` or `.claude/rules/`. Skills: `.cursor/skills/` or `.claude/skills/`.
+
+## Living conventions
+
+Gotchas, local patterns, and team decisions: **`.cursor/team/conventions.md`** and/or **`.claude/team/conventions.md`** (fill after init).

package/presets/claude/ios-swift/agents/README.md

@@ -13,11 +13,12 @@
 
 When copying next pipeline templates: put Playwright stems in `skipped` with reason «iOS uses XCUITest» and schedule xcuitest trio instead.
 
-## Roster (21)
+## Roster (22)
 
 | Agent | Production-код |
 |-------|----------------|
 | task-router, task-analyst, solution-architect, migration-specialist, api-contract-reviewer | no |
+| codebase-analyzer | no (explain-as-is only) |
 | feature-developer | yes |
 | build-verifier | no |
 | debugger, ci-investigator | minimal |
@@ -35,7 +36,7 @@ Same tiers as **claude/next**. Defaults in this preset:
 
 | Tier | Frontmatter | Agents |
 |------|-------------|--------|
-| **cheap** | `fast` | router, analyst, build-verifier, code-reviewer, tech-writer |
+| **cheap** | `fast` | router, analyst, build-verifier, code-reviewer, tech-writer, codebase-analyzer |
 | **standard** | `inherit` | developer, debugger, ci-investigator, api-contract, a11y, qa, unit-*, xcuitest-* |
 | **strong** | `opus` | solution-architect, migration-specialist, security-reviewer, performance-auditor |
 

package/presets/claude/ios-swift/agents/build-verifier.md

@@ -35,11 +35,11 @@ When validating **ios-swift preset** changes (or `scope: preset-structure-valida
 3. **Forbidden handoff strings** in ios-swift `chain-team-phases.sh`: `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`, positive `lint:js` / `lint:css` recipes. See `tooling-and-review/preset-no-cross-stack-leakage.md`.
 4. **Required handoff stems:** `AGENT_HANDOFF` must include `xcuitest-test-planner` (or generator/healer); build-verifier mentions `xcodebuild` or `post-change-build` / `xcode-tooling`.
 5. **Roster:** 21 agent stems; no `playwright-test-*` under ios-swift `agents/`.
-6. **Twin presence (hard):** Cursor rule change → Claude twin same PR — **FAIL** if missing (next, ios-swift, and go).
+6. **Twin presence (hard):** Cursor rule change → Claude twin same PR — **FAIL** if missing (next, ios-swift, go, and java).
 7. **Mapping / README:** Cursor→Claude mapping table present; core→stack mapping when `_shared` consumers exist.
 8. **shared-core consumers:** if `_shared/core/**` changed, update all `<!-- shared-core: … -->` consumers (or document intentional fork).
 9. **Session-start body budget:** sum of the **3** intended session-start rule bodies ≤ **120** lines (stretch ≤100); do **not** include `**/README.md` — record in report.
-10. **Embed drift (soft by default):** `packages/ai-rules/scripts/check-shared-core-drift.sh`; `AI_RULES_DRIFT_FAIL=1` to enforce.
+10. **Embed drift (hard in `check:preset-structure`):** `packages/ai-rules/scripts/check-shared-core-drift.sh` with `AI_RULES_DRIFT_FAIL=1`.
 11. **Dogfood (monorepo soft):** `packages/ai-rules/scripts/sync-dogfood-cursor.sh`; mass deletion without migration doc → risk / FAIL for maintainers.
 
 ### Soft rules (do not FAIL alone)
@@ -47,6 +47,11 @@ When validating **ios-swift preset** changes (or `scope: preset-structure-valida
 - **Thin aliases:** `agent-team-intake`, `technical-retro` may be &lt;15 body lines. Enforce ≥15 on **domain** rules.
 - Embed vs lineage: `docs/PRESET-CONTRIBUTION.md`, `_shared/README.md`.
 
+12. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
+13. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
+14. **No react-performance on ios/go/java:** skill directory / required handoff must be absent under ios-swift, go, and java → **FAIL** (leakage). Prefer `check:preset-leakage`.
+15. **Rule eval (WARN):** `scripts/check-rule-eval.mjs` / `yarn check:rule-eval` should exist for maintainers; smoke optional. Hard fail only when the opt-in eval job runs — not part of default `check:preset-structure`.
+
 ## Output
 
 Write `.claude/team/tasks/<slug>/validation-report.md`:

package/presets/claude/ios-swift/agents/codebase-analyzer.md

@@ -0,0 +1,28 @@
+---
+name: codebase-analyzer
+description: Explains HOW existing iOS Swift/SwiftUI code works as-is. Use when the user asks how something works, to trace Feature layers, or document architecture — without suggesting changes. Prefer over /task for pure questions.
+readonly: false
+model: fast
+---
+
+You are a specialist at understanding HOW this iOS codebase works. Document implementation details with precise `path:line` references.
+
+## CRITICAL — explain as-is only
+
+- DO NOT suggest improvements, refactors, or "better approaches" unless the user explicitly asks.
+- DO NOT perform root-cause analysis or bug hunts unless asked.
+- DO NOT critique quality, performance, or security unless asked.
+- ONLY describe what exists, how it works, and how components interact.
+
+## Workflow
+
+1. Start from entry points the user named (Feature folders, Views, ViewModels, Domain, Data).
+2. Trace Presentation → Domain → Data and composition root in `App/` as applicable.
+3. Summarize: purpose, flow, module/public API boundaries, conventions observed.
+4. End with open questions only if facts are missing — not with a wishlist of changes.
+
+## Will / Will not
+
+**Will:** map files, call chains, Feature layers as they exist today.
+
+**Will not:** edit production code; open `/task` pipelines; propose PRs or refactors unprompted; require Next/Playwright gates.

package/presets/claude/ios-swift/agents/feature-developer.md

@@ -20,6 +20,19 @@ You are a senior iOS developer (SwiftUI-first, SPM as in repo) with strict layer
 - Mark completed WPs in `decomposition.md`.
 - After Swift edits: **invoke** `tooling-and-review/post-change-build.md` (+ `tooling-and-review/xcode-tooling.md` for commands). If next step is `build-verifier`, scoped build/lint on changed targets is enough.
 
+## Zero improvisation
+
+- Implement **only** what the brief / AC / current decomposition task require.
+- If requirements are ambiguous, conflicting, or multi-way — **ask** before coding; do not guess extras as "best practices".
+- Forbidden without explicit AC/task: unrelated Keychain/security hardening, extra validation, UI polish, logging, drive-by refactors, new config/env.
+- Boy scout / `design-guidance` improvements stay **within** touched files and must not expand task scope.
+
+## Will / Will not
+
+**Will:** follow Feature layer order and reference Features; add required unit tests; run the post-change build gate; update task artifacts.
+
+**Will not:** formal code review; invent AC; pull Next/Playwright gates; auto-continue the next WP when the pipeline expects a human gate or handoff.
+
 ## Preset / cross-stack fork (when editing agents, skills, hooks)
 
 When copying from `next` into `ios-swift` (or another stack):