@bonesofspring/ai-rules 0.2.13 → 0.2.14

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

@@ -0,0 +1,38 @@
+---
+name: code-review
+description: Reviews pull requests, merge requests, git diffs, and branch changes using the preset's architecture, import, UI, API, and testing standards. Use when the user asks for review or when code-reviewer runs in an agent pipeline.
+---
+
+# Code Review
+
+## Inputs
+
+Use the local repository as the source of truth: `git status`, `git diff`, task artifacts under `.claude/team/tasks/<slug>/` when present, and opened files. Do not invent hosting metadata such as labels, CI status, or reviewers.
+
+## Review Order
+
+1. Understand the intent and affected layers.
+2. Check correctness and regressions first.
+3. Verify architecture boundaries: UI does not know DTO/transport, store does not depend on UI, API services do not pull UI/store.
+4. Check public imports through `@/types` and `@/api`, plus barrel updates for new public symbols.
+5. Review UI consistency, styling conventions, and prop shape.
+6. Check tests: unit for mapper/domain logic, behavior tests for HTTP client changes, e2e plan/spec updates for user flows.
+7. **Reuse lens:** flag new helpers that duplicate existing utilities; prefer adjacent shared modules over copy-paste.
+8. **Efficiency lens:** unnecessary work, sequential ops that should be parallel, hot-path bloat, no-op store updates, overly broad reads.
+9. Report validation gaps: lint, stylelint, typecheck, or relevant tests not run.
+
+## Output
+
+Lead with findings ordered by severity. Required shape (also in `code-review-mr`):
+
+- Each finding: **`path:line`** — problem — impact — concrete fix direction.
+- Severity: **`blocker` | `important` | `nit`** (list blocker → nit).
+- Vague («looks risky») is not a finding — cite evidence or ask for surrounding context.
+- End with a verdict line: **`Safe to merge | needs changes | reject`**.
+- If there are no findings, say so and call out remaining test or validation risk.
+
+For agent team tasks, write `.claude/team/tasks/<slug>/review.md` and set `status.json` to `completed` or `changes_requested`.
+
+## Design guidance
+
+- Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.

package/presets/claude/nuxt/skills/debug-investigation/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: debug-investigation
+description: Investigates bugs, failing tests, crashes, and incorrect behavior with runtime evidence before applying minimal fixes. Use for bugfix tasks, debugger agent runs, regressions, and flaky test diagnosis.
+---
+
+# Debug Investigation
+
+## Process
+
+1. Reproduce the issue or collect the closest available evidence: error output, failing test, browser snapshot, logs, or user steps.
+2. Define expected vs actual behavior in one sentence.
+3. Trace the failing path through the smallest relevant slice of the codebase.
+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 test when the behavior is user-facing or likely to recur.
+7. Run the narrow failing check first, then relevant lint/type/test validation.
+
+## Artifacts
+
+For agent team tasks, write `.claude/team/tasks/<slug>/debug-report.md` with:
+
+- Reproduction steps or evidence source.
+- Root cause.
+- Fix scope.
+- Regression coverage.
+- Remaining risk.
+
+Update `status.json` when complete.
+
+## Design guidance
+
+- Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.

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

@@ -0,0 +1,34 @@
+---
+name: feature-delivery
+description: Delivers Nuxt 3 frontend features end-to-end across domain types, API services, store, UI, mocks, tests, and validation. Use when implementing or extending a feature, especially through /task or feature-developer.
+---
+
+# Feature Delivery
+
+1. Read task brief, acceptance criteria, and decomposition if present.
+2. Read **`rules/architecture/feature-delivery-workflow.md`** and **`rules/architecture/reference-features.md`** — follow layer order and mirror closest reference feature.
+3. Add or update focused tests for changed behavior.
+4. Validation from repository root: **invoke** **`rules/tooling-and-review/post-change-lint.md`** after code edits (requestable, not session-start — but mandatory when code changed). Pipeline: scoped lint OK if next step is `build-verifier`.
+
+## Scope discipline
+
+Implement only the current AC / decomposition task. Clarify ambiguity before coding; do not add unrelated hardening, polish, or refactors. See `feature-developer` → **Zero improvisation**.
+
+## Handoff
+
+Summarize by layer, validation results, and known gaps. Agent team: update `.claude/team/tasks/<slug>/status.json`.
+
+## Design guidance
+
+- Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Anti-hallucination
+
+- When editing app TS/TSX, load `vue-nuxt-anti-hallucination` (phantom Next/React/RTK imports).
+
+
+## Stack notes (Nuxt)
+
+- Layers: pages/components → composables → stores (Pinia) → api → http; server/api Nitro.
+- Anti-hallucination: `vue-nuxt-anti-hallucination`.
+- Scripts cwd: repository root; gates: `lint:js`, `lint:css`, `typecheck`.

package/presets/claude/nuxt/skills/playwright-e2e/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: playwright-e2e
+description: Plans, generates, and heals Playwright e2e tests using this preset's tests/e2e layout, *.cases.md plans, page objects, and shared helpers. Use for e2e planning, test generation, or fixing failing browser tests.
+---
+
+# Playwright E2E
+
+## Project Layout
+
+- Test root: `tests/e2e`.
+- Test plans: `*.cases.md` files under the matching feature folder.
+- Executable specs: `*.spec.ts` files in the same folder.
+- Seed/setup reference: `tests/e2e/seed.spec.ts`.
+
+Do not introduce top-level `specs/` or `tests/` folders for real coverage unless the user explicitly asks for a sandbox.
+
+## Planner
+
+Create or update the relevant `*.cases.md` file. Each scenario should include title, preconditions, steps, and expected result. Cover happy path, important edge cases, validation, and error states.
+
+## Generator
+
+Generate specs from `*.cases.md` into the same folder. Reuse existing page objects and `_shared/` helpers. Keep test names aligned with scenario names.
+
+## Healer
+
+Fix selectors, waits, setup, or page-object details without weakening business assertions. Use the matching `*.cases.md` file as the behavior contract.
+
+## Validation
+
+Run the affected spec when feasible. If the environment blocks execution, report the command that should be run and the blocker.
+
+
+## Stack notes (Nuxt)
+
+- E2E root: `tests/e2e/`.
+- Default baseURL `http://localhost:3000`; prefer `webServer` → `nuxt dev` or `nuxt preview`.

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

@@ -0,0 +1,54 @@
+---
+name: technical-retro
+description: Facilitates technical retrospectives for tasks, sprints, incidents, releases, and agent-team pipelines. Use when the user asks for retro, postmortem, process review, or action items after delivery.
+---
+
+# Technical Retro
+
+## Inputs
+
+Ask for missing period, focus, task slug, participants, or format constraints. If a slug is provided, read `.claude/team/tasks/<slug>/` artifacts and local git status/diff. Do not invent facts not present in artifacts or the user's message.
+
+## Facilitation Principles
+
+- Focus on process and system behavior, not blame.
+- Separate facts, interpretations, and proposed actions.
+- Balance what worked with what slowed delivery.
+- Keep action items concrete, owned, and measurable.
+
+## Default Structure
+
+1. Goal and scope.
+2. Timeline or factual observations.
+3. What worked.
+4. What hurt quality, speed, or confidence.
+5. Root causes for the top one or two issues.
+6. Experiments and action items.
+
+## Agent Team Block
+
+For `/task` pipelines, include router, analyst, developer, **build-verifier**, reviewer, QA/e2e, hooks, and rules.
+
+## Wrong-turn taxonomy (optional)
+
+When artifacts or the user mention agent mistakes, tag incidents:
+
+| Kind | Signal |
+|------|--------|
+| `correction` | User pushback («no», «don't», «actually») |
+| `retry` | Same tool/approach 2+ times before success |
+| `waste` | Many searches before the right file |
+| `reversal` | Edit then revert / delete |
+| `dead-end` | Env/tool failure (missing binary, wrong path) |
+
+Severity: **high** (explicit correction / large waste) · **med** · **low**. Confidence 0–100 — be honest; low-confidence items are optional.
+
+## Preset feedback loop
+
+If the same issue appeared in **2+** tasks (or **3+** for packaging a new rule/skill — Rule of Three), add section **Preset updates**:
+
+- Proposed change to `.claude/rules/`, `.claude/agents/`, `.claude/skills/`, or **`.claude/team/conventions.md`** (prefer conventions for project gotchas)
+- One concrete snippet or file path
+- Whether it belongs in session-start vs `paths:` vs skill vs conventions (see `PRESET-CONTRIBUTION` → Building blocks)
+
+Do not apply preset or conventions changes without user approval.

package/presets/claude/nuxt/skills/unit-testing/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: unit-testing
+description: Plans, generates, and heals unit tests for mappers, Pinia actions, HTTP client behavior, and Vue components using colocated *.spec.ts files and tests-unit rules. Use for unit test planning, generation, or fixing failing unit tests.
+---
+
+# Unit Testing
+
+## Project Layout
+
+- Specs colocated with source: `*.spec.ts` / `*.spec.ts` next to the module under test.
+- Legacy `*.test.ts` / `*.test.tsx` — do not rename without a separate task.
+- Runner: Jest or Vitest as configured in the target repo; components use `@vue/test-utils`.
+
+Follow **`rules/testing/tests-unit.md`**.
+
+## Planner
+
+Write or update `.claude/team/tasks/<slug>/unit-test-plan.md`.
+
+Each scenario needs a Russian `it()` title (capital letter after each sentence). Cover mappers, Pinia actions, client behavior branches, and component interactions per AC.
+
+## Generator
+
+Implement specs from `unit-test-plan.md`. Reuse project test-store, HTTP mocks, and existing test utilities. Do not change production code.
+
+## Healer
+
+Fix mocks, async timing, selectors, and setup — preserve business assertions. Use `unit-test-plan.md` and `brief.md` as the behavior contract.
+
+## Validation
+
+Run affected unit tests from repository root when feasible. Report command, pass/fail, and remaining gaps vs plan.

package/presets/claude/nuxt/skills/vue-performance/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: vue-performance
+description: Nuxt Vue performance checklist for implementers — bundle, lazy routes, defineAsyncComponent, payload, hydration, Core Web Vitals. Use while coding a nuxt feature; not a substitute for the performance-auditor agent when the user asks for an audit report.
+---
+
+# Vue performance (nuxt)
+
+On-demand checklist for **implementers** shipping Nuxt/Vue UI. For a formal diff audit report, use the **`performance-auditor`** agent instead — this skill does not replace it.
+
+**No RSC model** — Nuxt uses SSR/payload/hydration; do not apply Next Server Component guidance.
+
+## Bundle
+
+- Prefer route-level lazy pages (Nuxt file routing code-splits pages by default) and `defineAsyncComponent` for heavy UI (charts, editors).
+- Avoid importing large libraries into `layouts` / plugins that run globally; keep client entry points small.
+- Check that barrel files do not re-export heavy modules into every consumer.
+
+## Lazy routes & async components
+
+- Heavy feature UI: lazy via async component or separate page/route.
+- Do not eagerly import large optional widgets into the default layout.
+- Prefer Nuxt lazy patterns already used in the repo over inventing a second loader.
+
+## Payload & data
+
+- Avoid duplicate fetches that hydrate the same payload keys.
+- Prefer `useAsyncData` / `useFetch` key discipline already in the feature; dedupe with existing keys.
+- Lift shared fetches when multiple children need the same data — follow reference feature patterns.
+- Store (Pinia) for client-mutable server state; do not invent a second cache layer.
+
+## Hydration
+
+- Keep SSR markup consistent with client first paint; avoid `window` in setup without client guards.
+- Prefer `<ClientOnly>` for browser-only widgets that break hydration.
+- Do not ship large client-only state into the critical SSR path without need.
+
+## Memoization discipline
+
+- Do **not** add computed/memo wrappers by default for trivial derived state.
+- Prefer fixing state placement and `v-for` keys over blanket memoization.
+- Follow Vue reactivity patterns used by neighbors.
+
+## Core Web Vitals (quick)
+
+| Metric | Implementer checks |
+|--------|--------------------|
+| LCP | Hero/media not blocked by unnecessary client JS; sensible image sizing (`NuxtImg` if used) |
+| INP | Click handlers lean; avoid long sync work on the main thread |
+| CLS | Reserve space for images/skeleton; stable fonts |
+
+## Handoff
+
+If the user asks for a **performance audit report** of a diff/deliverable, route to **`performance-auditor`** (readonly `perf-report.md`), not this skill alone.

package/presets/claude/nuxt/skills/write-adr/SKILL.md

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

package/presets/claude/nuxt/team/README.md

@@ -0,0 +1,136 @@
+# Agent team artifacts
+
+Каталог артефактов пайплайна «команда агентов» Claude.
+
+## Layout
+
+```
+.claude/team/
+  active-task.json
+  fixtures/                  # pipeline profile examples (feature-full, feature-light, bugfix-standard)
+  tasks/
+    <slug>/
+      pipeline.json
+      status.json
+      metrics.json             # schema-v1 append-only event ledger (see Local metrics ledger)
+      brief.md
+      decomposition.md
+      debug-report.md          # fixApplied: true/false
+      validation-report.md     # build-verifier: PASS | FAIL
+      architecture.md
+      migration-plan.md
+      ci-report.md
+      a11y-review.md
+      perf-report.md
+      security-review.md
+      api-contract-review.md
+      unit-test-plan.md
+      documentation.md
+      review.md
+```
+
+## pipeline.json schema
+
+```json
+{
+  "slug": "order-history-date-filter",
+  "intent": "feature",
+  "summary": "Add date filter to Order History",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify and decompose" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate" },
+    { "agent": "code-reviewer", "label": "Code review" },
+    { "agent": "qa-tester", "label": "E2E", "scope": "e2e-only" }
+  ],
+  "humanGates": ["after:task-analyst"],
+  "autoChain": true,
+  "skipped": []
+}
+```
+
+### Step fields
+
+| Field | Description |
+|-------|-------------|
+| `agent` | kebab-case name or array when `parallel: true` |
+| `label` | Human-readable step name |
+| `scope` | Passed to agents (e.g. `unit-in-dev`, `e2e-only`) |
+| `skipIf` | `debugger.fixed` \| `ci-investigator.resolved` |
+| `parallel` | Invoke all `agent` values in one parent turn |
+
+## status.json (pipeline mode)
+
+```json
+{
+  "slug": "order-history-date-filter",
+  "intent": "feature",
+  "pipelineIndex": 0,
+  "currentAgent": "task-analyst",
+  "phase": "executing",
+  "state": "in_progress",
+  "awaitingHumanGate": false,
+  "retryAfterFix": null,
+  "activeAttempts": {},
+  "lastCompletedAttempt": null,
+  "parallelCompleted": [],
+  "parallelOutcomes": {},
+  "updatedAt": "2026-05-29T12:00:00.000Z"
+}
+```
+
+### phase
+
+Prefer **`executing`** for pipeline mode. Legacy: `analysis`, `development`, `review`, `testing`, `done`.
+
+### state
+
+| Value | Description |
+|-------|-------------|
+| `in_progress` | Current step running |
+| `completed` | Current step finished |
+| `awaiting_approval` | Human gate; use `/task-continue` |
+| `changes_requested` | Reviewer requires fixes |
+| `validation_failed` | build-verifier failed |
+| `approved` | Legacy continue |
+
+## Workflow entry
+
+```bash
+/task <описание задачи>
+/task-continue <slug>
+/technical-retro <slug>
+```
+
+Legacy: `/feature-start`, `/feature-continue`.
+
+## Git
+
+Commit task artifacts if you want them to survive `ai-rules clean claude`. Or copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.
+
+## Artifact manifest and receipts
+
+Each slug stores one context index at `.claude/team/tasks/<slug>/artifact-manifest.json`. Schema v1 is defined by shared core `agent-team/agent-artifact-contracts.md`: every entry declares its producer, status, authoritative paths, acceptance-criteria IDs, decomposition task IDs, timestamps, and a terminal completion receipt.
+
+Producer/consumer rules:
+
+- Read the manifest first and use only the authoritative inputs needed by the current step; fall back to `brief.md`, `decomposition.md`, and `pipeline.json` when it is missing or stale, and report that gap.
+- Producers upsert only their stable entry IDs, preserve foreign entries, and finish with `completed`, `blocked`, `changes_requested`, or `validation_failed` receipt evidence.
+- The router owns `pipeline.json` and its routing entry; analyst, developer, verifier, and reviewer own their named outputs and receipts. Consumers do not edit another producer's receipt.
+- Agents do not mutate `status.json` or `metrics.json`. The orchestration runtime/hook is their single writer. Parallel receipt merges are serialized by the parent/orchestrator.
+
+## Local metrics ledger
+
+`metrics.json` is an append-only schema-v1 event ledger for one task run. It contains only allowlisted IDs, task dimensions, timestamps, outcomes, and attribution confidence—never prompts, secrets, file paths, or contents. Policy SoT: `presets/_shared/core/agent-team/agent-task-metrics.md`. The orchestration runtime writes `task_started` / `attempt_started`; the hook records host-clock completion and human-gate edges under a per-task lock with temp-and-rename.
+
+`status.json.activeAttempts` is a transient timing bridge keyed by `attemptId`; `lastCompletedAttempt` is diagnostic; `parallelOutcomes` holds per-agent outcomes for the current parallel join until the step advances. For parallel stops, the hook must use a stable payload identity or the sole active attempt. Otherwise an explicit `.metrics-receipts.json` receipt is fallback data marked `source: agent`, `attributionConfidence: fallback`; it must never guess from `currentAgent`.
+
+After a human gate, `/task-continue` closes wait via the installed hook (do not hand-edit `pipelineIndex` first):
+
+```bash
+printf '%s\n' '{"status":"completed","action":"end_human_gate","activateNext":true}' | bash .claude/hooks/chain-team-phases.sh
+```
+
+That appends `human_gate_ended` before the next `attempt_started`. Cursor twin uses the same payload against `.cursor/hooks/chain-team-phases.sh`. Other installable stacks ship the same ledger contract in their `team/README.md`.
+
+Aggregate with `node packages/ai-rules/scripts/aggregate-agent-task-metrics.mjs --team-root .claude/team`. It reports role/agent count, completed count, total/average duration, distinct completed run IDs, separate human-gate wait, and incomplete artifacts. For retros, see `/technical-retro` → **Metrics evidence**.

package/presets/claude/nuxt/team/conventions.md

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

package/presets/claude/nuxt/team/fixtures/artifact-manifest.example.json

@@ -0,0 +1,61 @@
+{
+  "schemaVersion": 1,
+  "slug": "order-history-date-filter",
+  "updatedAt": "2026-07-31T12:20:00.000Z",
+  "artifacts": [
+    {
+      "id": "routing",
+      "producer": "task-router",
+      "status": "completed",
+      "authoritativePaths": ["pipeline.json"],
+      "acceptanceCriteriaIds": [],
+      "taskIds": [],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:00:00.000Z",
+        "updatedAt": "2026-07-31T12:00:00.000Z",
+        "completedAt": "2026-07-31T12:00:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "The feature pipeline and routing evidence are authoritative.",
+        "evidencePaths": ["pipeline.json"]
+      }
+    },
+    {
+      "id": "analysis",
+      "producer": "task-analyst",
+      "status": "completed",
+      "authoritativePaths": ["brief.md", "decomposition.md"],
+      "acceptanceCriteriaIds": ["AC-1", "AC-2"],
+      "taskIds": ["T1", "T2"],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:01:00.000Z",
+        "updatedAt": "2026-07-31T12:05:00.000Z",
+        "completedAt": "2026-07-31T12:05:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "The acceptance criteria and implementation tasks are ready.",
+        "evidencePaths": ["brief.md", "decomposition.md"]
+      }
+    },
+    {
+      "id": "implementation",
+      "producer": "feature-developer",
+      "status": "completed",
+      "authoritativePaths": ["implementation.md"],
+      "acceptanceCriteriaIds": ["AC-1", "AC-2"],
+      "taskIds": ["T1", "T2"],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:06:00.000Z",
+        "updatedAt": "2026-07-31T12:20:00.000Z",
+        "completedAt": "2026-07-31T12:20:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "Implementation and focused unit coverage are complete.",
+        "evidencePaths": ["implementation.md"]
+      }
+    }
+  ]
+}

package/presets/claude/nuxt/team/fixtures/bugfix-standard.json

@@ -0,0 +1,25 @@
+{
+  "slug": "example-bugfix-standard",
+  "intent": "bugfix",
+  "profile": "standard",
+  "routingDecision": {
+    "complexity": "moderate",
+    "riskFlags": ["behavior-regression"],
+    "routingReasons": [
+      "The regression needs root-cause evidence before deciding whether a separate fix pass is necessary.",
+      "The bounded behavior change still requires validation and independent review."
+    ],
+    "estimatedWorkPackages": 1,
+    "openDecisionCount": 0
+  },
+  "summary": "Regression fix with review",
+  "steps": [
+    { "agent": "debugger", "label": "Root cause" },
+    { "agent": "feature-developer", "label": "Fix if needed", "skipIf": "debugger.fixed" },
+    { "agent": "build-verifier", "label": "Validation gate" },
+    { "agent": "code-reviewer", "label": "Code review" }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": []
+}

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

@@ -0,0 +1,28 @@
+{
+  "slug": "example-feature-full",
+  "intent": "feature",
+  "profile": "full",
+  "routingDecision": {
+    "complexity": "high",
+    "riskFlags": ["cross-layer", "public-contract", "broad-test-surface"],
+    "routingReasons": [
+      "The feature spans UI, state, and API boundaries, so architecture and implementation checkpoints are required.",
+      "The public contract and e2e acceptance surface require independent validation and review."
+    ],
+    "estimatedWorkPackages": 2,
+    "openDecisionCount": 1
+  },
+  "summary": "Multi-layer feature with e2e coverage",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify and decompose" },
+    { "agent": "solution-architect", "label": "Design boundaries", "model": "strong" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate", "model": "cheap" },
+    { "agent": "security-reviewer", "label": "Security review", "model": "strong" },
+    { "agent": "code-reviewer", "label": "Code review", "model": "cheap" },
+    { "agent": "qa-tester", "label": "E2E", "scope": "e2e-only" }
+  ],
+  "humanGates": ["after:task-analyst"],
+  "autoChain": true,
+  "skipped": []
+}

package/presets/claude/nuxt/team/fixtures/feature-light.json

@@ -0,0 +1,27 @@
+{
+  "slug": "example-feature-light",
+  "intent": "feature",
+  "profile": "light",
+  "routingDecision": {
+    "complexity": "low",
+    "riskFlags": [],
+    "routingReasons": [
+      "The request has explicit acceptance criteria and a reversible single-file scope.",
+      "No public contract, cross-layer coordination, or open decision requires analysis or architecture."
+    ],
+    "estimatedWorkPackages": 1,
+    "openDecisionCount": 0
+  },
+  "summary": "Trivial single-file change with explicit AC",
+  "steps": [
+    { "agent": "feature-developer", "label": "Implement", "model": "cheap" },
+    { "agent": "build-verifier", "label": "Validation gate", "model": "cheap" }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    { "agent": "task-analyst", "reason": "Explicit AC and single-file scope" },
+    { "agent": "code-reviewer", "reason": "Light profile — non-trivial app changes should use standard" },
+    { "agent": "qa-tester", "reason": "No e2e AC" }
+  ]
+}

package/presets/claude/nuxt/team/tasks/.gitkeep

@@ -0,0 +1 @@
+# Keep the task artifact directory in the published preset.

package/presets/claude/php-hexagonal/agents/build-verifier.md

@@ -36,7 +36,7 @@ Hard gates for the **php-hexagonal** stack (and peers):
 
 Also document:
 
-1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java|mcp-ts|php-hexagonal`) must ship `REPO_AGENTS.md` → **FAIL** if missing.
+1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|nuxt|svelte|ios-swift|go|java|mcp-ts|php-hexagonal|php-laravel`) must ship `REPO_AGENTS.md` → **FAIL** if missing.
 2. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
 3. **No react-performance / Playwright / a11y on backend stacks:** skill directory / required handoff must be absent under go, java, php-hexagonal, php-laravel, mcp-ts → **FAIL** (leakage). Prefer `check:preset-leakage`.
 4. **Shared-core drift (hard in `check:preset-structure`):** `check-shared-core-drift` with `AI_RULES_DRIFT_FAIL=1`.

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

@@ -9,6 +9,7 @@ paths:
 
 <!-- shared-core: meta/preset-layering.md -->
 
+
 # Preset layering
 
 Правила для **авторов пресетов** (`packages/ai-rules/presets/**`). Не always-on в consumer apps.
@@ -24,7 +25,7 @@ paths:
 ## Куда класть новое правило
 
 1. Общие принципы для всех стеков → **core** + адаптеры с `<!-- shared-core: … -->`.
-2. Только один из installable стеков (`next` / `ios-swift` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (не в `_shared`).
+2. Только один из installable стеков (`next` / `nuxt` / `svelte` / `ios-swift` / `go` / `java` / `mcp-ts` / `php-hexagonal` / `php-laravel`) → **stack-specific** (не в `_shared`).
 3. Только Cursor или только Claude packaging → platform artifact / frontmatter, не дублировать семантику.
 
 ## SoT