@bonesofspring/ai-rules 0.2.26 → 0.2.28

package/presets/mavis/ios-swift/agents/unit-test-healer.md

@@ -1,3 +1,19 @@
+## Rules to load (subagent context)
+
+This subagent runs standalone (`mcode exec --file`) and inherits no global context. Read these rules explicitly before acting:
+
+- `.mavis/rules/ios-app-core.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/feature-delivery-workflow.md` — layer order, mockup gate, ux-design gate
+- `.mavis/rules/reference-features.md` — analog files first
+- `.mavis/rules/anti-sycophancy-discipline.md` — procedural anti-sycophancy rules
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-unit.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You debug and fix failing **iOS unit tests**.
 
 ## Inputs

package/presets/mavis/ios-swift/agents/unit-test-planner.md

@@ -1,3 +1,19 @@
+## Rules to load (subagent context)
+
+This subagent runs standalone (`mcode exec --file`) and inherits no global context. Read these rules explicitly before acting:
+
+- `.mavis/rules/ios-app-core.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/feature-delivery-workflow.md` — layer order, mockup gate, ux-design gate
+- `.mavis/rules/reference-features.md` — analog files first
+- `.mavis/rules/anti-sycophancy-discipline.md` — procedural anti-sycophancy rules
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-unit.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a unit test planner for an **iOS** codebase using XCTest or Swift Testing.
 
 Use the **`unit-testing` skill** and `tests-unit.md`.

package/presets/mavis/ios-swift/agents/xcuitest-test-generator.md

@@ -1,3 +1,19 @@
+## Rules to load (subagent context)
+
+This subagent runs standalone (`mcode exec --file`) and inherits no global context. Read these rules explicitly before acting:
+
+- `.mavis/rules/ios-app-core.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/feature-delivery-workflow.md` — layer order, mockup gate, ux-design gate
+- `.mavis/rules/reference-features.md` — analog files first
+- `.mavis/rules/anti-sycophancy-discipline.md` — procedural anti-sycophancy rules
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-ui.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You generate XCUITest cases from project UI test plans.
 
 ## Inputs

package/presets/mavis/ios-swift/agents/xcuitest-test-healer.md

@@ -1,3 +1,19 @@
+## Rules to load (subagent context)
+
+This subagent runs standalone (`mcode exec --file`) and inherits no global context. Read these rules explicitly before acting:
+
+- `.mavis/rules/ios-app-core.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/feature-delivery-workflow.md` — layer order, mockup gate, ux-design gate
+- `.mavis/rules/reference-features.md` — analog files first
+- `.mavis/rules/anti-sycophancy-discipline.md` — procedural anti-sycophancy rules
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-ui.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You debug and fix failing **XCUITest** UI tests.
 
 ## Inputs

package/presets/mavis/ios-swift/agents/xcuitest-test-planner.md

@@ -1,3 +1,19 @@
+## Rules to load (subagent context)
+
+This subagent runs standalone (`mcode exec --file`) and inherits no global context. Read these rules explicitly before acting:
+
+- `.mavis/rules/ios-app-core.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/feature-delivery-workflow.md` — layer order, mockup gate, ux-design gate
+- `.mavis/rules/reference-features.md` — analog files first
+- `.mavis/rules/anti-sycophancy-discipline.md` — procedural anti-sycophancy rules
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-ui.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are an expert UI test planner for an **iOS** app using XCUITest.
 
 ## Project structure

package/presets/mavis/ios-swift/commands/spec-start.md

@@ -4,7 +4,7 @@ Routes intent **`spec-gen`** (or bootstrap) → **task-analyst** in **author mod
 
 ## What to do
 
-1. Extract description from arguments after the spec-start procedure in `.mavis/commands/spec-start.md` (domain, page/feature ids, sources).
+1. Extract description from arguments after `/spec-start` (domain, page/feature ids, sources).
 2. Generate a **slug** (kebab-case, ≤48 chars), e.g. `spec-<domain>-<id>`.
 3. Ensure `.ai.local/team/tasks/<slug>/` exists (Write artifacts; not Shell mkdir).
 4. Write `.ai.local/team/active-task.json` → `{ "slug": "<slug>" }`.
@@ -16,7 +16,7 @@ Routes intent **`spec-gen`** (or bootstrap) → **task-analyst** in **author mod
 
 - Show created/updated spec paths and INDEX diff.
 - Ask user to approve drafts (`status: draft` → promote) or send edits.
-- Continue: continue `<slug>` using `.mavis/commands/task-continue.md` only after approval when implementation follows; otherwise stop after docs.
+- Continue: `/task-continue <slug>` only after approval when implementation follows; otherwise stop after docs.
 
 ## Notes
 

package/presets/mavis/ios-swift/commands/task.md

@@ -1,10 +1,10 @@
 # Task — single entry point (router + pipeline)
 
-Main command for filing work. Parent agent = orchestrator (`agent-team-orchestrator.md`). Intake for work requests without the task procedure in `.mavis/commands/task.md` — `agent-team-intake.md`.
+Main command for filing work. Parent agent = orchestrator (`agent-team-orchestrator.md`). Intake for work requests without `/task` — `agent-team-intake.md`.
 
 ## Arguments
 
-Everything after the task procedure in `.mavis/commands/task.md` is a natural-language task description.
+Everything after `/task` is a natural-language task description.
 
 Examples:
 
@@ -25,13 +25,13 @@ Examples:
 1. **Slug** — kebab-case from the description (≤48 characters). Create `.ai.local/team/tasks/<slug>/` via **Write** (e.g. placeholder `pipeline.json` or empty marker) — the runtime/hook owns `status.json` — **not** via Shell `mkdir` (sandbox → `Operation not permitted`).
 2. **Router** — invoke subagent **task-router** with the task description and slug path.
 3. **Plan** — show the user the table from `pipeline.json`: intent, steps, skipped, humanGates.
-4. **Intent retro** — if `intent === "retro"`, run the technical-retro procedure in `.mavis/commands/technical-retro.md` and **stop**.
+4. **Intent retro** — if `intent === "retro"`, run `/technical-retro` and **stop**.
 5. **Start** — after the router:
    - confirm `pipeline.json` and `active-task.json`;
    - do **not** write `status.json` / `metrics.json` lifecycle fields yourself — the orchestration runtime/hook owns them (see **agent-artifact-contracts**). If `status.json` is missing, only a minimal bootstrap is allowed (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — do **not** increment `pipelineIndex` manually;
    - invoke the subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
 6. **After each agent** — wait for hook handoff / reconciliation of the terminal receipt → `status.state`; do not start the next step until `status.json` reflects the handoff (or until there is a hook `followup_message`).
-7. **Human gate** — if after the current step there is a gate in `humanGates` (`after:<agent>`), after the agent finishes **stop** and ask for continue `<slug>` using `.mavis/commands/task-continue.md`.
+7. **Human gate** — if after the current step there is a gate in `humanGates` (`after:<agent>`), after the agent finishes **stop** and ask for `/task-continue <slug>`.
 
 ## Do not
 
@@ -41,9 +41,9 @@ Examples:
 
 ## If the slug is taken
 
-- `awaitingHumanGate` / `state: awaiting_approval` → offer artifact review or continue `<slug>` using `.mavis/commands/task-continue.md`.
+- `awaitingHumanGate` / `state: awaiting_approval` → offer artifact review or `/task-continue <slug>`.
 - `in_progress` → ask: continue or new slug.
 
 ## Metrics
 
-Runtime/hook owns `metrics.json` and `status.json` attempt ledgers. Before the first invocation ensure `task_started` and one `activeAttempts[attemptId]` + `attempt_started` exist (router/runtime bootstrap — parent must not invent parallel indices). On the task-continue procedure in `.mavis/commands/task-continue.md`, run the installed chain hook `end_human_gate` action (or wrapper) so `human_gate_ended` lands before the next attempt. Do not calculate durations in agents.
+Runtime/hook owns `metrics.json` and `status.json` attempt ledgers. Before the first invocation ensure `task_started` and one `activeAttempts[attemptId]` + `attempt_started` exist (router/runtime bootstrap — parent must not invent parallel indices). On `/task-continue`, run the installed chain hook `end_human_gate` action (or wrapper) so `human_gate_ended` lands before the next attempt. Do not calculate durations in agents.

package/presets/mavis/ios-swift/hooks/chain-team-phases.sh

@@ -42,7 +42,10 @@ try {
 }
 
 const slug = active.slug;
-if (!slug) {
+// Reject non-kebab / traversal slugs: the runtime writes status.json and
+// metrics.json under tasks/<slug>, so an unchecked slug could escape the tree.
+const SLUG_RE = /^[a-z0-9]+(?:-[a-z0-9]+)*$/;
+if (typeof slug !== 'string' || slug.length > 48 || !SLUG_RE.test(slug)) {
   process.stdout.write('{}');
   process.exit(0);
 }
@@ -69,6 +72,9 @@ function waitForMetricsLock() {
   // and never blocked on the lock file, so two concurrent subagentStop events
   // could both acquire the lock and corrupt metrics.json. Retry EEXIST with a
   // 10 ms sleep up to 200 attempts (2 s ceiling). On any other error, throw.
+  // A lock left behind by a killed process is reclaimed once its mtime is older
+  // than STALE_LOCK_MS, so one crash cannot brick the task forever.
+  const STALE_LOCK_MS = 30000;
   for (let attempt = 0; attempt < 200; attempt += 1) {
     try {
       const fd = fs.openSync(METRICS_LOCK, 'wx');
@@ -76,6 +82,13 @@ function waitForMetricsLock() {
       return;
     } catch (error) {
       if (!error || error.code !== 'EEXIST') throw error;
+      try {
+        const lockStat = fs.statSync(METRICS_LOCK);
+        if (Date.now() - lockStat.mtimeMs > STALE_LOCK_MS) {
+          fs.unlinkSync(METRICS_LOCK);
+          continue;
+        }
+      } catch {}
       const until = Date.now() + 10;
       while (Date.now() < until) { /* 10 ms busy-wait */ }
     }
@@ -495,7 +508,10 @@ function legacyFlow() {
 
 
 if (hookInput.action === 'end_human_gate') {
-    status.awaitingHumanGate = false;
+  // Only advance when a gate was actually open. A duplicate or retried
+  // end_human_gate must be a no-op, not a silent pipeline skip.
+  const gateWasOpen = Boolean(status.activeHumanGateEventId) || status.awaitingHumanGate === true;
+  status.awaitingHumanGate = false;
   // A2 (retro §8): pin a single runId per pipeline so subsequent events don't
   // fragment the metrics ledger across multiple runId sequences. Prefer
   // metrics.json.task.runId when metrics already exist, then status.metricsRunId,
@@ -522,7 +538,7 @@ if (hookInput.action === 'end_human_gate') {
     });
     delete status.activeHumanGateEventId;
   }
-  if (hookInput.activateNext && fs.existsSync(pipelinePath)) {
+  if (gateWasOpen && hookInput.activateNext && fs.existsSync(pipelinePath)) {
     let resumePipeline = null;
     try { resumePipeline = JSON.parse(fs.readFileSync(pipelinePath, 'utf8')); } catch {}
     if (resumePipeline) {
@@ -544,6 +560,19 @@ if (hookInput.action === 'end_human_gate') {
         else out(handoffForAgent(resumeAgents[0], resumeNext.step.scope, resumeNext.step));
         process.exit(0);
       }
+      // Gate on the final step: no executable step remains. Complete the
+      // pipeline instead of leaving it in_progress forever.
+      status.state = 'completed';
+      completeTaskMetrics();
+      writeStatus({
+        pipelineIndex: resumeSteps.length,
+        phase: 'done',
+        state: 'completed',
+        currentAgent: null,
+        awaitingHumanGate: false,
+      });
+      out(`Pipeline complete for "${slug}". Run /technical-retro ${slug}.`);
+      process.exit(0);
     }
   }
   // A2 (retro §8): if gate closes the final human gate of the pipeline

package/presets/mavis/ios-swift/rules/code-quality-and-refactoring.md

@@ -14,6 +14,12 @@
 - **CUPID:** Composable; Unix philosophy (one responsibility); Predictable; Idiomatic (repo); Domain-based.
 - **Composition over inheritance;** Law of Demeter — no `a.b.c.d` chains; via public API / facade.
 
+# Over-abstraction guardrails
+
+- **No unnecessary constants:** do not hoist a one-off literal, string, or boolean into a named constant. Inline it, or use an existing token/enum when the value is meaningful and reused. Named constants are for shared, semantic, or repeated values.
+- **No invented utilities:** do not add a `utils`/helper for a single call site or a thin pass-through wrapper. Inline it or extend the existing helper; a new shared utility is justified only after the Rule of Three.
+- **Decompose over conditionals:** a unit (function, component, hook) that accumulates several branches (`if` / ternary / `switch`) should be split into smaller units with one reason to change instead of piling up conditions.
+
 # Refactoring during changes
 
 - Light refactor is OK if it reduces duplication, improves readability, and does not break public contracts.
@@ -38,3 +44,11 @@ Essentials below. Full procedural set (~17 rules) → load **`anti-sycophancy-di
 Style enforcement (formatter / linter / post-change gate) lives in the **stack toolchain** — see each adapter’s **Stack notes**.
 
 > Stack-specific lint gates, examples, and toolchain — in the preset adapter **Stack notes** section.
+
+## Stack notes
+
+- Before adding a new UI control, check DesignSystem and existing components.
+- Public API: protocols and facades between features.
+- Acceptable examples: shared mapper/validation; replace force unwrap; split an overloaded ViewModel into use cases; design tokens instead of magic numbers/colors; remove a direct View→Data dependency in favor of a protocol.
+- Post-change gate: **`post-change-build.mdc`** + `xcode-tooling.mdc` (not yarn lint).
+- Style: **SwiftLint** (+ SwiftFormat when configured) — authoritative style gate; do not duplicate linter rules in prose.

package/presets/mavis/ios-swift/rules/code-review-mr.md

@@ -38,3 +38,42 @@ Procedure details live in skill `code-review`. Required shape:
 - 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
+
+On-demand rule for review flows (not always-on).
+
+- **When to apply**
+  - Requests: “review this”, “evaluate the MR/branch/diff”, “look at the changes”.
+  - Rely on the local repository: branch, `git diff`, open files.
+
+- **What the agent must check**
+  - **Architecture and layers** (`architecture-boundaries.mdc`, `ios-app-core.mdc`):
+    - View does not call APIs and does not know DTOs.
+    - ViewModel does not depend on Data implementations directly.
+    - Domain does not import SwiftUI/UIKit.
+    - Data does not pull Presentation.
+  - **Dependencies and modules**:
+    - DI via protocols; composition root in App.
+    - No deep-import between features.
+    - Files in the correct layers (`Presentation`, `Domain`, `Data`, `DesignSystem`).
+  - **Swift and concurrency** (`swift-conventions.mdc`):
+    - `@MainActor` on UI; no unjustified force unwraps.
+    - Typed errors; correct Task cancellation where needed.
+  - **UI** (`swiftui-ui.mdc`):
+    - Thin Views; Design System tokens; accessibility identifiers for testable elements.
+  - **Networking and data** (`networking-services.mdc`):
+    - DTOs separated from domain; mappers cover edge cases.
+  - **Tests**:
+    - Non-trivial logic — unit (`tests-unit.mdc`); user flows — UI (`tests-ui.mdc`).
+    - State which tests to add or update.
+
+- **Depth and format**
+  - Focus on the **MR diff**, not the whole project.
+  - Overview first (MR goal, risks), then concrete comments with file and a fix suggestion matching repo patterns.
+  - No “big refactors” without a request (`code-quality-and-refactoring.mdc`).
+
+- **Constraints**
+  - Do not invent CI/MR hosting metadata without local data.
+  - Boy scout rule within the MR.
+  - BUGBOT automated review — see root `BUGBOT.md` (Cursor).

package/presets/mavis/ios-swift/rules/design-guidance.md

@@ -97,3 +97,8 @@ Do not introduce a second stem (`refactoring-smells` / `design-patterns-for-agen
 - Ubiquitous language: `feature-delivery-workflow` (lineage).
 - MR checklist (smells in scope; pattern name only if repo uses it): `code-review-mr`.
 - Token / twin policy for authors: `preset-token-budget`, `preset-twin-sync` (meta, not consumer always-on).
+
+## Stack notes
+
+- Prefer protocol + composition over class inheritance hierarchies.
+- Suggest Adapter/Facade at Feature public API / DI boundaries — not inside Views.

package/presets/mavis/ios-swift/rules/feature-delivery-workflow.md

@@ -47,3 +47,69 @@ flowchart LR
 ## Zone → rules matrix
 
 Filled in the stack adapter: concrete globs/paths and `.mdc` / topic `.md` names.
+
+## Stack notes
+
+When the prompt or `brief.md` contains a `figma.com` URL, **mockup review** (`mockup-reviewer` / skill `mockup-review`) must complete — or the user must continue past FAIL/`BLOCKED_MCP` via `/task-continue` — **before UI implementation**. Non-UI tasks no-op this gate. When required-signal and **no** `figma.com`, **`ux-design.md`** (on the analysis manifest entry) must exist and not be `INCOMPLETE` before UI work — else **blocked**, hand back to `task-analyst`. Parallel to the mockup gate.
+
+Typical feature with data and UI. Layer details — `architecture-boundaries.mdc`, `ios-app-core.mdc`.
+
+## Checklist (work order)
+
+1. **Domain** — entities, value types, repository / use case protocols (`Features/**/Domain/**`).
+2. **Data** — DTOs (`Codable`), Domain ↔ DTO mappers, repository implementations, API client (`networking-services.mdc`).
+3. **ViewModel** — state, use case / protocol calls; DI from App; no DTOs or URLs (`state-and-viewmodels.mdc`).
+4. **View / navigation** — thin SwiftUI Views, Design System; navigation as in the repo (`swiftui-ui.mdc`).
+5. **Tests** — unit for mappers / use cases / VM (`tests-unit.mdc`); UI flows — XCUITest (`tests-ui.mdc`).
+6. **Completion** — **invoke** `post-change-build.mdc` (+ `xcode-tooling.mdc` for schemes/commands): build touched targets + lint/format per repo config. When the current WP spans **more than one** layer or module, `implementation.md` includes a **Code Map** (3–8 annotated paths) and **Suggested Review Order** (`concern | path:line | ≤15 word note`). Omit both for a single-file or single-layer WP.
+
+## Data flow (orientation)
+
+```mermaid
+flowchart LR
+  DTO[DTO] --> Mappers[Mappers]
+  Mappers --> Domain[Domain]
+  Domain --> Repo[Repository protocol]
+  Repo --> VM[ViewModel]
+  VM --> View[SwiftUI View]
+  DataImpl[Data impl] -.-> Repo
+```
+
+## Partial scenarios
+
+| Task | Minimum |
+|------|---------|
+| API / model only | Domain + DTO + mapper + repo impl; unit for mapper. |
+| VM / logic only | Domain protocols; mocks in tests; no HTTP in View. |
+| UI only | View + existing VM/state; no DTOs. |
+| Tests only | Specs per repo convention; do not change production without need. |
+
+## Anti-patterns
+
+- DTO / `Codable` transport types in View or ViewModel.
+- `URLSession` / concrete API client in ViewModel or View.
+- Domain imports SwiftUI / UIKit.
+- Deep-import of another feature’s internal files.
+- Assembling DI inside a View.
+- **Ubiquitous language:** Domain/type names reflect the feature domain — do not mix transport/framework terms into domain without need.
+- Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+- Do not mutate pipeline `status.json` / `metrics.json`; the orchestration hook is the single writer. Skills upsert the owned terminal receipt in `artifact-manifest.json`.
+
+## Matrix: zone → rules
+
+| Zone | Rules |
+|------|---------|
+| `Features/**/Domain/**`, `Core/Domain/**` | `architecture-boundaries.mdc`, `ios-app-core.mdc` |
+| `Features/**/Data/**`, `**/Network*/**` | `networking-services.mdc`, `architecture-boundaries.mdc` |
+| `*ViewModel*.swift`, Presentation state | `state-and-viewmodels.mdc` |
+| `Presentation/**`, `DesignSystem/**` | `swiftui-ui.mdc`, `architecture-boundaries.mdc` |
+| `**/*.swift` (style) | `swift-conventions.mdc` |
+| `*Tests/**` | `tests-unit.mdc` |
+| `*UITests/**` | `tests-ui.mdc` |
+| After Swift edits | `post-change-build.mdc` |
+
+When adding or extending a feature, **walk the checklist** and the table rules for touched zones.
+
+## Related
+
+- Product behavior discovery: requestable **`product-specs`** (`docs/specs/INDEX.md`) — do not paste the discovery algorithm here.

package/presets/mavis/ios-swift/rules/mcp-usage.md

@@ -84,3 +84,11 @@ Policy is stack-class-specific — see adapter **Stack notes**. If a Figma **plu
 - Treating overlay absence as blocked (except user-required SoT)
 - Tracker/admin write tools without an explicit ask
 - Calling overlay MCP “just in case” on unrelated tasks
+
+## Stack notes
+
+- Pipeline **`mockup-reviewer`** is the only agent that reads Figma for mockup review. See `mockup-review`.
+- Shipped besides Context7: Figma (mockup-review pipeline). See `mockup-review`.
+- Do **not** require Storybook, Playwright, or Chrome DevTools MCP as handoffs or delivery gates.
+- Observability and ticket overlays still apply when present.
+- `init` **merges** `mcpServers`: preset keys update; extra local servers are kept.

package/presets/mavis/ios-swift/rules/mockup-review.md

@@ -105,3 +105,7 @@ PASS | PASS_WITH_NOTES | FAIL | BLOCKED_MCP
 ## AC coverage
 | Criterion | Status | Notes |
 ```
+
+## Stack notes
+
+Illustrative iOS size classes (not enforced pixels): compact / regular (e.g. small iPhone, large iPhone, iPad) mapped to small / medium / large.

package/presets/mavis/ios-swift/rules/preset-layering.md

@@ -9,7 +9,7 @@ Rules for **preset authors** (`packages/ai-rules/presets/**`). Not always-on in
 | Layer | Where | What to put |
 |-------|-------|-------------|
 | **Core** | `presets/_shared/core/**` | Stack-agnostic prose + checklists; no frontmatter; no paths `app/**`, `Features/**`, Playwright, xcodebuild |
-| **Stack** | `presets/{cursor\|claude\|mavis\|opencode}/<stack>/` | Domain/tooling, stack always-on trio, stack examples in **Stack notes** |
+| **Stack** | `presets/{cursor\|claude\|mavis\|opencode}/<stack>/` | Domain/tooling, stack always-on set (3–5), stack examples in **Stack notes** |
 | **Platform** | Cursor `.mdc` / Claude `.md` / Mavis `.md` / OpenCode `.md` | Frontmatter (`alwaysApply`/`globs` vs `paths:` vs OpenCode `mode`/`permission`), platform-only (`BUGBOT.md`, `CLAUDE.md`) |
 
 ## Where to put a new rule

package/presets/mavis/ios-swift/rules/preset-pr-checklist.md

@@ -12,7 +12,7 @@ Checklist for PRs that touch `packages/ai-rules/presets/**` (and dogfood `.curso
 - [ ] **Mavis derive:** mapped `cursor/<stack>/` change → `mavis/<stack>/` + `adapter-map.json` **same PR** when the stack is in `releasedStacks` (run `generate-mavis.mjs --stack <stack>` + `check-mavis-adapter-map.mjs`; see `preset-twin-sync` § Mavis derivation)
 - [ ] **OpenCode derive:** mapped `cursor/<stack>/` change → `opencode/<stack>/` + `adapter-map.json` **same PR** when the stack is in `releasedStacks` (run `generate-opencode.mjs --stack <stack>` + `check-opencode-adapter-map.mjs`; see `preset-twin-sync` § OpenCode derivation)
 - [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table is current
-- [ ] **Token budget:** Cursor `alwaysApply` ≤ 4 (4th slot reserved for `ai-local-overlay`); Claude session-start exactly 3; meta rules not always-on
+- [ ] **Token budget:** Cursor `alwaysApply` and Claude session-start both **3–5** (extra slots reserved for `ai-local-overlay`); body sum ≤200 (stretch ≤170); meta rules not always-on
 - [ ] **Local overlay coverage:** every installable stack ships `ai-local-overlay.mdc` (Cursor) and `ai-local-overlay.md` (Claude) with `MANDATORY` + acknowledgement format + `docs/LOCAL-OVERLAY.md` pointer; Claude twin listed in `claude/<stack>/rules/README.md` mapping table. Run `packages/ai-rules/scripts/check-local-overlay.sh`.
 - [ ] **Leakage:** no foreign stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
 - [ ] **Hook-only lifecycle:** `status.json` / `metrics.json` writes happen only inside `hooks/`; agents read but never rewrite lifecycle fields. Run `packages/ai-rules/scripts/check-hook-only-lifecycle.sh`.

package/presets/mavis/ios-swift/rules/preset-token-budget.md

@@ -8,19 +8,19 @@ Invariants for rule loading in an **installed** preset (consumer app).
 
 | Platform | Always-on | Cap |
 |----------|-----------|-----|
-| Cursor | `alwaysApply: true` | **≤ 4** |
-| Claude | rules **without** `paths:` | **exactly 3** |
-| Mavis | `adapter-map` rules with `loadMode: root-entry` | **≤ 4** |
-| OpenCode | `adapter-map` rules with `loadMode: root-entry` | **≤ 4** |
+| Cursor | `alwaysApply: true` | **3–5** |
+| Claude | rules **without** `paths:` | **3–5** |
+| Mavis | `adapter-map` rules with `loadMode: root-entry` | **3–5** |
+| OpenCode | `adapter-map` rules with `loadMode: root-entry` | **3–5** |
 
-**Cursor 4th slot is reserved for `ai-local-overlay`** (consumer-owned `.ai.local/` rules). If you do not need local overlay, demote that rule to `globs: ["**/.ai.local/**"]` and revert to ≤3.
+Caps are **aligned** across platforms: minimum **3** (base invariants), maximum **5**. Slots beyond the base invariants are reserved for `ai-local-overlay` (consumer-owned `.ai.local/` rules). If you do not need local overlay, demote that rule to `globs: ["**/.ai.local/**"]` / Claude `paths:`, or a non-root load mode on Mavis / OpenCode.
 
-**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.
+**Claude Option A (README exclusion):** when counting Claude rules without `paths:` / session-start, **exclude `**/README.md`** (topic indexes are not session-start rules). Body budget sums only the intended session-start rules (≤5).
 
 Session-start body budget:
-- Claude trio: ≤140 lines total (stretch ≤120).
-- Cursor 4-set: ≤170 lines total (4 rules including `ai-local-overlay`).
-- Mavis / OpenCode: ≤4 root-entry rule files; combined root `AGENTS.md` + platform entry ≤170 nonempty lines. Do not dump the full rule catalog into `AGENTS.md`.
+- Claude session-start: ≤200 lines total (stretch ≤170).
+- Cursor always-on: ≤200 lines total (stretch ≤170).
+- Mavis / OpenCode: ≤5 root-entry rule files; combined root `AGENTS.md` + platform entry ≤200 nonempty lines. Do not dump the full rule catalog into `AGENTS.md`.
 
 ## Meta / author rules
 
@@ -36,4 +36,4 @@ Orchestrator, feature-delivery, code-review, post-change gates, domain globs —
 
 ## Verifier
 
-build-verifier **FAIL** if Cursor `alwaysApply` count exceeds 4, Claude session-start count exceeds 3 (Claude count **excludes `**/README.md`**), or if a `preset-*` meta rule is marked always-on.
+build-verifier **FAIL** if Cursor `alwaysApply` count or Claude session-start count is outside **3–5** (Claude count **excludes `**/README.md`**), or if a `preset-*` meta rule is marked always-on.

package/presets/mavis/ios-swift/rules/product-specs-authoring.md

@@ -110,3 +110,9 @@ Block handoff via `open_questions` until fixed:
 - Skill `spec-authoring` — procedural checklist
 - Skill `spec-discovery` — opt-in research-before-spec (not default)
 - Optional consumer script `scripts/check-product-specs.sh` (ships in the npm package; WARN default; `--strict` FAIL). Bash checks INDEX links, required frontmatter keys, and body headings — it does **not** evaluate `frontmatter-v1.schema.json`
+
+## Stack notes
+
+- Author via skill `spec-authoring`; templates from package assets / consumer `docs/specs/_templates/`.
+- Field semantics match discovery stem (`routes` = deep links; `e2e` = XCUITest). **No** web Playwright recipes.
+- Requestable — not always-on / session-start.

package/presets/mavis/ios-swift/rules/product-specs.md

@@ -54,3 +54,8 @@ Same-changeset INDEX updates, frontmatter v1, required body headings, templates,
 - Skill `spec-discovery` — opt-in research-before-spec (author mode only; not default consume).
 - `reference-features` — code structure mirror (how to layout files), not product behavior.
 - Consumer `.ai/context/**` when present — review/domain glossary; cross-link, do not replace.
+
+## Stack notes
+
+- `routes`: deep links / screen ids. `ui` / `store`: Feature / View / ViewModel modules (`Features/**` or equivalent) — **not** web `app/src/ui`. `e2e`: XCUITest paths.
+- Requestable / `docs/specs/**` globs — not always-on / session-start.

package/presets/mavis/ios-swift/rules/reference-features.md

@@ -43,3 +43,52 @@ Path pointer and stack tables — in the preset adapter (`.ai.local/conventions.
 - skill `feature-delivery` — end-to-end scenario.
 
 > Concrete path tables, globs, and dogfood checklists live in the stack adapter **Stack notes**.
+
+## Stack notes
+
+Before implementing, find a Feature of the same type and **mirror its structure**; do not invent a new file organization.
+
+Taxonomy / shared core: [`presets/_shared/README.md`](../../../_shared/README.md) · [Preset contribution guide](../../../../docs/PRESET-CONTRIBUTION.md).
+
+## Reference table
+
+After `ai-rules init`, replace examples with **real** consumer-repo paths. Below — conventional placeholders for greenfield / dogfood.
+
+| Layer | Reference (example → replace) | Conventional glob / path |
+|------|----------------------------|--------------------------|
+| Feature module | `Features/Orders/` | `Features/**` |
+| Presentation / UI | `Features/Orders/Presentation/` | `**/Presentation/**`, `**/DesignSystem/**` |
+| Domain | `Features/Orders/Domain/` | `**/Domain/**` |
+| Data / Network | `Features/Orders/Data/` | `**/Data/**`, `**/Network*/**` |
+| Persistence | `Features/Orders/Data/Persistence/` | `**/Persistence/**`, `**/Keychain/**` |
+| Unit tests | `Features/OrdersTests/` or colocated `*Tests` | `**/*Tests/**/*.swift` |
+| UI tests | `OrdersUITests/` | `**/*UITests/**/*.swift` |
+
+If the repo uses another layout (`Modules/`, `Sources/`) — rewrite the table once and keep it as SoT for agents.
+
+## How to use
+
+1. Identify affected layers from `decomposition.md` or the task.
+2. Open the reference from the table (after paths are filled).
+3. Mirror naming, file order, DI, and test patterns.
+4. If there is no reference — pick the **closest** existing feature of the same layer and record the choice in the handoff.
+
+## Dogfood checklist (5 scenarios)
+
+Run after preset init (manual smoke for agents):
+
+1. `/task` new feature under `Features/<Name>` — analyst → developer → build-verifier (xcodebuild).
+2. ViewModel bug — debugger → fix → unit test.
+3. DTO↔domain mapper — unit-test-planner/generator.
+4. UI flow — `xcuitest-test-planner` → generator (accessibilityIdentifier).
+5. Auth/Keychain touch — security-reviewer + `security-ios.mdc`.
+
+## Living conventions
+
+Post-init gotchas / patterns / decisions: **`.ai.local/conventions.md`** (shared across tools; `.ai.local/team/**` is pipeline artifacts, not rules). Consumer-owned; not always-on. See root `AGENTS.md` § Living conventions.
+
+## Related rules
+
+- `code-quality-and-refactoring.mdc` — repeat patterns.
+- `feature-delivery-workflow.mdc` — layer order.
+- skill `feature-delivery` — end-to-end scenario.

package/presets/mavis/ios-swift/rules/swiftui-ui.md

@@ -8,6 +8,13 @@
 - Before a new custom control — look for a component in `DesignSystem/` or existing features.
 - Extract repeated UI logic into `ViewModifier`, `@ViewBuilder` helpers, or subviews.
 
+# Conditional rendering
+
+- Prefer **decomposition over conditionals**: a `body` with several `if` / `switch` branches should compose small subviews, not nest conditions inline.
+- Keep the condition in the parent; subviews receive resolved state.
+- For loading / empty / error, use dedicated subviews or a small `@ViewBuilder` helper.
+- A `mode` / `variant` flag that renders two unrelated layouts is **two** views, not one.
+
 # ViewModel and binding
 
 - ViewModel — `@MainActor`, `@Observable` (iOS 17+) or `ObservableObject` — as adopted in the project.

package/presets/mavis/ios-swift/rules/ux-design.md

@@ -97,3 +97,7 @@ PASS | PASS_WITH_NOTES | INCOMPLETE
 ## Spec feed
 ## Open probes
 ```
+
+## Stack notes
+
+Form-factor **ios**: navigation chrome, system gestures (swipe-back), Dynamic Type / VoiceOver intent. Same `ux-design.md` schema as web; put size-class examples here only — do not FAIL on exact points.

package/presets/mavis/ios-swift/skills/debug-investigation/SKILL.md

@@ -24,3 +24,42 @@ If **three** fix attempts fail, or the same symptom returns after two supposed f
 - Broad refactor during a bugfix.
 - Fix only where the error surfaces if invalid data originates elsewhere.
 - Claim `fixApplied: true` without re-running the failing check (see `quality/verification-before-completion.md`).
+
+## Stack notes
+
+### Stack process
+
+
+1. Reproduce the issue or collect the closest available evidence: Xcode console, lldb backtrace, crash log, failing XCTest/XCUITest output, Instruments note, or user steps.
+2. Define expected vs actual behavior in one sentence.
+3. Trace the failing path through the smallest relevant Feature slice (Presentation → Domain → Data).
+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 XCTest when the behavior is domain/VM logic or likely to recur.
+7. Run the narrow failing check first (`xcodebuild test` for the affected target), then broader build validation if needed (`xcode-tooling.mdc`).
+
+### Artifacts
+
+For agent team tasks, write `.ai.local/team/tasks/<slug>/debug-report.md` with:
+
+- Reproduction steps or evidence source.
+- Root cause.
+- Fix scope (`fixApplied`).
+- Regression coverage.
+- Remaining risk.
+
+Agent team: upsert the owned terminal receipt in `artifact-manifest.json`; do not mutate `status.json`.
+
+Do not use browser/Playwright tooling — this is an Xcode stack.
+
+
+### MCP usage
+
+Load requestable rule `mcp-usage` when verifying third-party library APIs (Context7) or when a local overlay MCP is present and the task fits. Discover tools at runtime; do not invent schemas. Overlay absence is not a blocker unless the user required that MCP as source of truth.
+
+If a Sentry/Datadog (or similar) MCP is ready and the task is a production error, event, or trace, use it. Do not invent telemetry.
+
+
+### Design guidance
+
+- Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.

package/presets/mavis/java/MAVIS.md

@@ -26,6 +26,19 @@ Do not write `~/.minimax/**`.
 
 See `.mavis/rules/README.md` for the full catalog and loading strategy.
 
+## Harness wiring
+
+- **Subagent rules** are re-declared inside every `.mavis/agents/*.md` via
+  the `## Rules to load (subagent context)` block (always-on + zone rules
+  filtered to stems that exist for this stack). Subagents run via
+  `mcode exec --file` and inherit no global context, so the block is the
+  authoritative mechanism.
+- **MiniMax Code has no permission/instructions config schema** (no analog
+  of OpenCode's `opencode.json` `permission.bash` or Claude Code's
+  `.claude/settings.json`). Universal `git commit/push deny` and
+  package-manager guards live in the agent prompt bodies; harness-level
+  enforcement is intentionally omitted.
+
 **Platform docs:** published with the `@bonesofspring/ai-rules` package
 (`docs/MAVIS.md`, `docs/MAVIS-COMPATIBILITY.md`) — **not** copied into
 the consumer repo. Source: https://github.com/bonesofspring/ai-rules