@bonesofspring/ai-rules 0.2.27 → 0.2.28

package/presets/mavis/next/agents/codebase-analyzer.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a specialist at understanding HOW this Next.js codebase works. Document implementation details with precise `path:line` references.
 
 ## CRITICAL — explain as-is only

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

@@ -1,3 +1,37 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/public-imports.md` — @/types, @/api barrels
+- `.mavis/rules/react-ui.md` — UI component style (no FC, no spread, decomposition)
+- `.mavis/rules/store-rtk.md` — Redux Toolkit patterns
+- `.mavis/rules/react-next-anti-hallucination.md` — phantom import banlist
+- `.mavis/rules/no-props-spread.md`
+- `.mavis/rules/no-type-assertion-as-import-export.md`
+- `.mavis/rules/architecture-boundaries-ui.md`
+- `.mavis/rules/arrow-functions.md`
+- `.mavis/rules/css-property-order-stylelint.md`
+- `.mavis/rules/layer-barrel-exports.md`
+- `.mavis/rules/navigation-router-stack.md`
+- `.mavis/rules/navigation-router-ui.md`
+- `.mavis/rules/next-app-router.md`
+- `.mavis/rules/react-a11y-coding.md`
+- `.mavis/rules/types-jsdoc.md`
+- `.mavis/rules/api-services.md`
+- `.mavis/rules/http-client.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 debugger for a Next.js TypeScript frontend. Use the **`debug-investigation` skill** for the investigation loop.
 
 ## Inputs

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

@@ -1,3 +1,37 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/public-imports.md` — @/types, @/api barrels
+- `.mavis/rules/react-ui.md` — UI component style (no FC, no spread, decomposition)
+- `.mavis/rules/store-rtk.md` — Redux Toolkit patterns
+- `.mavis/rules/react-next-anti-hallucination.md` — phantom import banlist
+- `.mavis/rules/no-props-spread.md`
+- `.mavis/rules/no-type-assertion-as-import-export.md`
+- `.mavis/rules/architecture-boundaries-ui.md`
+- `.mavis/rules/arrow-functions.md`
+- `.mavis/rules/css-property-order-stylelint.md`
+- `.mavis/rules/layer-barrel-exports.md`
+- `.mavis/rules/navigation-router-stack.md`
+- `.mavis/rules/navigation-router-ui.md`
+- `.mavis/rules/next-app-router.md`
+- `.mavis/rules/react-a11y-coding.md`
+- `.mavis/rules/types-jsdoc.md`
+- `.mavis/rules/api-services.md`
+- `.mavis/rules/http-client.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a senior frontend developer working in a Next.js monorepo with strict layer boundaries.
 
 ## Before coding

package/presets/mavis/next/agents/migration-specialist.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a migration specialist for a Next.js frontend with strict layer boundaries.
 
 ## Inputs

package/presets/mavis/next/agents/mockup-reviewer.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a Figma mockup reviewer for a Next.js React frontend.
 
 You write **only** `.ai.local/team/tasks/<slug>/mockup-review.md` (and the owned manifest receipt). Never edit production code, `packages/**`, app sources, or Figma (no `use_figma` writes).

package/presets/mavis/next/agents/openspec-author.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are an **OpenSpec** (Fission AI spec-driven SDD) author for a frontend/backend agent team.
 
 Your only writes target `openspec/**` (and team artifact manifests). Production code lives behind `feature-developer`; you are **docs / spec only**.

package/presets/mavis/next/agents/performance-auditor.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a frontend performance auditor for a Next.js React application.
 
 ## Inputs

package/presets/mavis/next/agents/playwright-test-generator.md

@@ -1,3 +1,22 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/playwright-agents.md`
+- `.mavis/rules/tests-e2e-structure.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You generate Playwright tests from project test plans.
 
 ## Inputs

package/presets/mavis/next/agents/playwright-test-healer.md

@@ -1,3 +1,22 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/playwright-agents.md`
+- `.mavis/rules/tests-e2e-structure.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 Playwright e2e tests.
 
 ## Inputs

package/presets/mavis/next/agents/playwright-test-planner.md

@@ -1,3 +1,22 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/playwright-agents.md`
+- `.mavis/rules/tests-e2e-structure.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 web test planner for a Next.js frontend.
 
 ## Project structure

package/presets/mavis/next/agents/qa-tester.md

@@ -1,3 +1,23 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+- `.mavis/rules/tests-unit.md`
+- `.mavis/rules/playwright-agents.md`
+- `.mavis/rules/tests-e2e-structure.md`
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a QA engineer for a Next.js frontend with Jest unit tests and Playwright e2e.
 
 ## Inputs

package/presets/mavis/next/agents/security-reviewer.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a frontend security reviewer for a Next.js TypeScript application.
 
 ## Inputs

package/presets/mavis/next/agents/solution-architect.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a solution architect for a Next.js frontend with strict layer boundaries (types, api, store, ui).
 
 ## Inputs

package/presets/mavis/next/agents/task-analyst.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a senior business/technical analyst for a Next.js frontend team.
 
 Your job is to reach **Definition of Ready (DoR)** before any implementation starts. You may write only `.ai.local/team/**` artifacts. You do **not** write production code or modify application source files.

package/presets/mavis/next/agents/task-router.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a task router for a Next.js frontend agent team. You **do not** implement tasks — you classify intent and plan the agent pipeline.
 
 ## Inputs

package/presets/mavis/next/agents/tech-writer.md

@@ -1,3 +1,20 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.mavis/rules/mcp-usage.md` — when verifying third-party APIs (Context7)
+
+Also read matching `.ai.local/rules/*.md` (local overlay) for the active zone, and the project strict rules if present.
+
 You are a technical writer for a Next.js frontend team.
 
 ## Inputs

package/presets/mavis/next/agents/unit-test-generator.md

@@ -1,3 +1,21 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.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 generate unit tests from project test plans.
 
 ## Inputs

package/presets/mavis/next/agents/unit-test-healer.md

@@ -1,3 +1,21 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.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 unit tests.
 
 ## Inputs

package/presets/mavis/next/agents/unit-test-planner.md

@@ -1,3 +1,21 @@
+## 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/next-app-core.md`
+- `.mavis/rules/package-manager.md`
+- `.mavis/rules/code-quality-and-refactoring.md`
+- `.mavis/rules/ai-local-overlay.md`
+- `.mavis/rules/architecture-boundaries.md` — layer boundaries and allowed imports
+- `.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/post-change-lint.md` — lint/type-check after code edits
+- `.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 a Next.js frontend with Jest/Vitest and Testing Library.
 
 Use the **`unit-testing` skill** and **`tests-unit.md`**.

package/presets/mavis/next/ai-local/rules-library/agent-artifacts-no-local-paths.md

@@ -0,0 +1,38 @@
+glob: always
+
+## Body
+
+# Agent artifacts: no local machine paths
+
+When this rule applies, acknowledge: `Using .ai.local: agent-artifacts-no-local-paths(, …)*`.
+
+Committed agent artifacts leak into git history. Absolute host paths expose the developer machine layout even if the file is deleted in a later MR.
+
+## Forbidden
+
+Do **not** write host-absolute paths, including:
+
+- `/Users/<username>/…` (macOS)
+- `/home/<username>/…` (Linux)
+- `C:\Users\<username>\…` and `C:/Users/<username>/…` (Windows)
+- Any other absolute checkout root.
+
+Do **not** put those strings in `productionTarget.root`, `instructions[]`, summaries, or evidence lists.
+
+## Required instead
+
+- This repo: path from workspace root (`src/…`, `.ai.local/team/tasks/<slug>/pipeline.json`).
+- Task-local artifacts: basename is enough (`pipeline.json`, `brief.md`) when the file lives in the same task directory.
+- Sibling / other repo: **repo name** + repo-relative path. Never the filesystem location of that checkout.
+
+## Gate before finishing a write
+
+After writing or editing a team artifact, scan the file (and any JSON you are about to write) for `/Users/`, `/home/`, `C:\Users`, `C:/Users`. If any match, rewrite to repo-relative **before** considering the step done.
+
+Deleting a leaked file later does **not** remove it from git history — prevention is the only fix.
+
+## Allowed (not this ban)
+
+- Repo-relative paths, `@/` aliases, URL paths (`/api/…`).
+- Public URLs (`https://…`, `figma.com/…`).
+- Ephemeral local logs that are **not** committed.

package/presets/mavis/next/ai-local/rules-library/commit-hygiene.md

@@ -0,0 +1,17 @@
+glob: always
+
+## Body
+
+# Commit hygiene
+
+When committing or preparing a commit, acknowledge: `Using .ai.local: commit-hygiene(, …)*`.
+
+Agents do not run `git commit`/`git push`. This rule constrains the **human commit step** and the agent's end-of-turn commit guidance.
+
+## Rules
+
+- **One area per commit.** Do not mix unrelated feature areas or layers in one commit. A commit that spans more than one area tag (or >~40 files) must be split, or the split must be justified in the message.
+- **Never mix trees.** Do not put `src/**` (or any product path) in the same commit as `**/team/tasks/**`, `openspec/**`, `docs/**`, storybook baselines, or config. Artifact/doc churn and source changes go in separate commits.
+- **Owning slug required.** Every commit touching `src/**` names its task slug or ticket id in the subject/body. "cleanup", "restore", "rename", "fix review comments" are not exemptions.
+- **No debug residue.** Do not commit `= true` debug flags, commented-out blocks, or unused exports.
+- **Spike ≠ ship.** A `spike`/`research` task does not commit `src/**` behaviour.

package/presets/mavis/next/ai-local/rules-library/mcp-required-for-ui-layout.md

@@ -0,0 +1,41 @@
+globs: src/ui/**
+
+## Body
+
+# MCP access gate for UI layout work (strict)
+
+Before **any** markup/layout implementation or refactor under `src/ui/**` (JSX structure, Linaria/styled-components, breakpoints, spacing, alignment, CTA placement, card/panel geometry), the agent MUST verify the **session MCP catalog** — it is the source of truth, not this file, not `opencode.json`, not `.opencode/MCP.md`.
+
+Acknowledge: `Using .ai.local: mcp-required-for-ui-layout(, …)*`.
+
+## Categorical ban — layout implementation without Figma MCP **and** Storybook MCP
+
+Implementing or refactoring UI markup/layout is **FORBIDDEN** unless BOTH servers are fully available and usable **in the current session**:
+
+1. **Figma MCP** — can read the real design node: `get_design_context` / `get_metadata` / `get_screenshot` / `get_variable_defs` for the target frame(s). A static image, exported PNG, or someone's description is **not** full access.
+2. **Storybook MCP** — can read story instructions and run the visual/test gate. With `@storybook/addon-mcp` (served by the running dev server at `/mcp`) the real tools are: `get-storybook-story-instructions`, `stories-preview`, `test-run` (docs: `docs-list` / `docs-show`). Tool names differ per MCP implementation — discover them from the session catalog; do not assume names.
+
+If either server is missing, `error`, `needsAuth`, or `loading`:
+
+- **STOP.** Do not edit layout/markup/styles. Do not "approximate from memory".
+- Report exactly: `Blocked: <figma|storybook> MCP unavailable — layout implementation banned (mcp-required-for-ui-layout).`
+- Ask the operator to configure/authenticate the MCP, or to **explicitly change this rule**. The agent MUST NOT self-waive.
+
+A running Storybook dev server (e.g. `localhost:6006`) reached through a browser MCP (chrome-devtools / Playwright) is **not** a substitute for Storybook MCP tooling.
+
+## Playwright MCP — mandatory warning + confirmation
+
+If Playwright MCP is unavailable during UI work:
+
+- Emit a **visible warning** in the turn output (do not bury it).
+- Do **not** start layout work or its verification until the operator confirms (`yes` / `no`).
+- Rationale: Playwright is the fallback for composed-frame, breakpoint, and interaction checks that Storybook MCP cannot cover.
+
+## Scope
+
+- **Banned:** writing/editing layout, markup, styles, breakpoints, spacing, alignment, CTA placement under `src/ui/**`.
+- **Allowed without the gate:** read-only investigation, comparing an existing implementation against a mockup, writing review artifacts (`mockup-review.md`, `perf-report.md`, …). The ban is on implementation, not on analysis.
+
+## Reference
+
+Project strict rule: `.ai.local/rules/00-strict-rules.md`. Adapt the path for your repo (this seed uses `.ai.local`).

package/presets/mavis/next/ai-local/rules-library/no-test-driven-behavior-change.md

@@ -0,0 +1,14 @@
+globs: src/**/*.{ts,tsx}
+
+## Body
+
+# Tests adapt to the product, not the reverse
+
+When editing `src`, tests, or stories, acknowledge: `Using .ai.local: no-test-driven-behavior-change(, …)*`.
+
+## Rules
+
+- Do not change production behaviour (`src/**`) to make a test, story, or e2e case reachable. Fix the test, the fixture, or the mock instead.
+- If a test reveals a genuine product gap, file it as a task; do not silently ship the behaviour change inside a "test stabilisation" commit.
+- Never rewrite `*.cases.md` / QA prose to match an unintended behaviour change. Prose changes that hide a behaviour change are a `blocker` for `code-reviewer`.
+- Removing a `test`/`snapshot` tag or commenting out `play` to go green is forbidden.

package/presets/mavis/next/ai-local/rules-library/pre-pr-checklist.md

@@ -0,0 +1,16 @@
+glob: always
+
+## Body
+
+# Pre-PR checklist
+
+Before opening a PR / finishing a branch, acknowledge: `Using .ai.local: pre-pr-checklist(, …)*`.
+
+## Checklist
+
+- [ ] Commits split: source / artifacts / docs; one area each; no mixed trees
+- [ ] `git status` clean of temp dumps, `* (1).*` copies, debug flags
+- [ ] Lint + type-check + targeted unit + storybook vitest green
+- [ ] e2e plan executed for user-flow AC; mock-path regexes match ≥1 route
+- [ ] L2/L3 `proposal.md` claims reconcile with the shipped diff
+- [ ] Review artifacts cite the reviewed revision (sha)

package/presets/mavis/next/ai-local/rules-library/router-pages.md

@@ -0,0 +1,23 @@
+override: kill next-app-router
+globs: src/pages/**/*.{ts,tsx},src/ui/**/*.{ts,tsx},next.config.ts
+
+## Body
+
+# Routing — Pages Router (not App Router)
+
+When doing routing / page / navigation work, acknowledge: `Using .ai.local: router-pages(, …)*`.
+
+This rule drops the preset's `next-app-router` rule from context for repos using the **Next.js Pages Router**. Enable by moving this file into `.ai.local/rules/` (it is staged-inactive in `.ai.local/rules-library/` by default).
+
+## Rules
+
+- Route files live in `src/pages/<route>/index.tsx` (or `<route>.tsx`), thin wrappers.
+- Domain UI lives in `src/ui/pages/<Name>Page`; route files do not contain layout/business logic.
+- Navigation: `next/router` (`useRouter`) and `next/link`. **Never** `next/navigation`.
+- `_app.tsx` / `_document.tsx` stay in `src/pages/`.
+
+## Forbidden
+
+- Creating App Router files (`src/app/**`, `page.tsx`, `layout.tsx`, `loading.tsx`, `error.tsx`, `route.ts`).
+- Importing `next/navigation` or App Router server APIs (`cookies()`, `headers()`, `redirect()`).
+- `getServerSideProps` / `getStaticProps` — the app is a client-rendered static export; data goes through the store/`@/api`.

package/presets/mavis/next/ai-local/rules-library/single-source-copy-constants.md

@@ -0,0 +1,16 @@
+globs: src/**/*.{ts,tsx}
+
+## Body
+
+# Single source for copy, constants, enums, routes
+
+When editing `src/**`, acknowledge: `Using .ai.local: single-source-copy-constants(, …)*`.
+
+Copy (button labels, headings, alt text, aria-labels), constants, enums, and route paths live in **one** owner module. Components import from that module — they do not redeclare literals.
+
+## Rules
+
+- User-visible copy: inline unless the same string is used in ≥2 distinct places OR is consumed by tests/stories that need a shared reference. Multi-instance refactors belong to a dedicated task.
+- Numeric / pixel / token aliases: inline directly; do not re-wrap into a named constant when used exactly once in the same file.
+- Counters and derived single-use values: inline (`array.length`, computed expressions).
+- Layout sizes of one component (skeleton `height`/`width`/`maxWidth`, one-off `px`) stay as literals in the JSX prop or in `styles.ts`. Do not hoist them into named constants or a `*.data.ts`, even when the same number is repeated in that component's JSX and its styles.