@bonesofspring/ai-rules 0.2.26 → 0.2.28

package/presets/mavis/nuxt/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/nuxt-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/vue-ui.md`
+- `.mavis/rules/store-pinia.md`
+- `.mavis/rules/vue-nuxt-anti-hallucination.md`
+- `.mavis/rules/no-v-bind-spread.md`
+- `.mavis/rules/no-type-assertion-as-import-export.md`
+- `.mavis/rules/architecture-boundaries-ui.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/nuxt-pages-routing.md`
+- `.mavis/rules/vue-a11y-coding.md`
+- `.mavis/rules/types-jsdoc.md`
+- `.mavis/rules/script-setup-conventions.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 Nuxt 3 TypeScript frontend. Use the **`debug-investigation` skill** for the investigation loop.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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/vue-ui.md`
+- `.mavis/rules/store-pinia.md`
+- `.mavis/rules/vue-nuxt-anti-hallucination.md`
+- `.mavis/rules/no-v-bind-spread.md`
+- `.mavis/rules/no-type-assertion-as-import-export.md`
+- `.mavis/rules/architecture-boundaries-ui.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/nuxt-pages-routing.md`
+- `.mavis/rules/vue-a11y-coding.md`
+- `.mavis/rules/types-jsdoc.md`
+- `.mavis/rules/script-setup-conventions.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 Nuxt 3 monorepo with strict layer boundaries.
 
 ## Before coding

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 frontend with strict layer boundaries.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 Vue 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/nuxt/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/nuxt-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/nuxt/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/nuxt-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 Nuxt 3 Vue application.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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/nuxt/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/nuxt-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/nuxt/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/nuxt-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 Nuxt 3 frontend.
 
 ## Project structure

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 frontend with Jest unit tests and Playwright e2e.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 TypeScript application.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 frontend with strict layer boundaries (types, api, store, ui).
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 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/nuxt/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/nuxt-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 Nuxt 3 frontend agent team. You **do not** implement tasks — you classify intent and plan the agent pipeline.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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 Nuxt 3 frontend team.
 
 ## Inputs

package/presets/mavis/nuxt/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/nuxt-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/nuxt/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/nuxt-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/nuxt/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/nuxt-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 Nuxt 3 frontend with Jest/Vitest and Testing Library.
 
 Use the **`unit-testing` skill** and **`tests-unit.md`**.

package/presets/mavis/nuxt/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/nuxt/commands/task.md

@@ -1,10 +1,10 @@
 # Task — single entry point (router + pipeline)
 
-Main command for filing a task. 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 a task. 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 the natural-language task description.
+Everything after `/task` is the 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) — 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` by hand;
    - invoke the subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
 6. **After each agent** — wait for hook handoff / reconciliation 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 busy
 
-- `awaitingHumanGate` / `state: awaiting_approval` → suggest reviewing artifacts or continue `<slug>` using `.mavis/commands/task-continue.md`.
+- `awaitingHumanGate` / `state: awaiting_approval` → suggest reviewing artifacts or `/task-continue <slug>`.
 - `in_progress` → ask: continue or a 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/nuxt/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/nuxt/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,10 @@ 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 existing Vue/Nuxt UI code and project packages.
+- Public API: index/barrel files and explicitly exported entities (`public-imports`, `layer-barrel-exports`).
+- Allowed examples: shared composable/utility; typing `any`/`unknown`; splitting a large SFC; CSS tokens instead of “magic” values.
+- Lint/stylelint — only **`post-change-lint`**; ESLint (vue) + Stylelint configs at repo root (e.g. `eslint.config.mjs`, `.stylelintrc*`). Disabling a rule (`eslint-disable`) — only **locally** with a short “why” comment.

package/presets/mavis/nuxt/rules/code-review-mr.md

@@ -38,3 +38,16 @@ 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. **Procedure and output format:** skill `code-review`.
+
+### Checklist references
+
+- Architecture layers: `architecture-boundaries.mdc`, `nuxt-app-core.mdc`; network: `http-client.mdc`
+- Imports: `public-imports.mdc`, `layer-barrel-exports.mdc`
+- UI: `vue-ui.mdc`
+- Security: `security-nuxt.mdc`
+- Tests: `tests-unit.mdc`, `playwright-agents.mdc`, `tests-e2e-structure.mdc`
+- Lint gate before final report: `post-change-lint.mdc`

package/presets/mavis/nuxt/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 hooks/mappers over HOC or new pattern names when the repo already extracts that way.
+- Suggest Strategy/Adapter only when ports or policy branching already exist in `**`.