diff --git a/docs/cli/intent-exclude.md b/docs/cli/intent-exclude.md
index 1c1d4db2..1d29d554 100644
--- a/docs/cli/intent-exclude.md
+++ b/docs/cli/intent-exclude.md
@@ -1,43 +1,74 @@
----
-title: intent exclude
-id: intent-exclude
----
-
-`intent exclude` manages `package.json#intent.exclude` entries.
-
-```bash
-npx @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
-```
-
-## Options
-
-- `--json`: print the configured exclude patterns as JSON
-
-## Actions
-
-1. `list` (default): print current excludes
-2. `add <pattern>`: append one exclude pattern
-3. `remove <pattern>`: remove one exclude pattern
-
-## Examples
-
-```bash
-npx @tanstack/intent@latest exclude
-npx @tanstack/intent@latest exclude list --json
-npx @tanstack/intent@latest exclude add @tanstack/router#experimental-*
-npx @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
-```
-
-## Behavior
-
-- Reads and writes the current working directory `package.json`
-- Creates `intent.exclude` when missing
-- Keeps existing excludes and appends new patterns in order
-- Validates pattern syntax before writing
-- Refuses invalid `package.json` structures for `intent` and `intent.exclude`
-
-## Related
-
-- [Configuration](../concepts/configuration)
-- [intent list](./intent-list)
-- [intent load](./intent-load)
+---
+title: intent exclude
+id: intent-exclude
+---
+
+`intent exclude` manages `package.json#intent.exclude` entries.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+solid: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+vue: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+svelte: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+angular: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+lit: @tanstack/intent@latest exclude [list|add|remove] [pattern] [--json]
+
+<!-- ::end:tabs -->
+
+## Options
+
+- `--json`: print the configured exclude patterns as JSON
+
+## Actions
+
+1. `list` (default): print current excludes
+2. `add <pattern>`: append one exclude pattern
+3. `remove <pattern>`: remove one exclude pattern
+
+## Examples
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest exclude
+react: @tanstack/intent@latest exclude list --json
+react: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+react: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+solid: @tanstack/intent@latest exclude
+solid: @tanstack/intent@latest exclude list --json
+solid: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+solid: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+vue: @tanstack/intent@latest exclude
+vue: @tanstack/intent@latest exclude list --json
+vue: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+vue: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+svelte: @tanstack/intent@latest exclude
+svelte: @tanstack/intent@latest exclude list --json
+svelte: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+svelte: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+angular: @tanstack/intent@latest exclude
+angular: @tanstack/intent@latest exclude list --json
+angular: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+angular: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+lit: @tanstack/intent@latest exclude
+lit: @tanstack/intent@latest exclude list --json
+lit: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+lit: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+```
+
+<!-- ::end:tabs -->
+
+## Behavior
+
+- Reads and writes the current working directory `package.json`
+- Creates `intent.exclude` when missing
+- Keeps existing excludes and appends new patterns in order
+- Validates pattern syntax before writing
+- Refuses invalid `package.json` structures for `intent` and `intent.exclude`
+
+## Related
+
+- [Configuration](../concepts/configuration)
+- [intent list](./intent-list)
+- [intent load](./intent-load)
diff --git a/docs/cli/intent-hooks.md b/docs/cli/intent-hooks.md
index ccdd4167..b2e4c2d4 100644
--- a/docs/cli/intent-hooks.md
+++ b/docs/cli/intent-hooks.md
@@ -5,9 +5,16 @@ id: intent-hooks
 
 `intent hooks install` installs lifecycle hooks that surface available Intent skills and gate supported edit tools until they observe an Intent guidance check.
 
-```bash
-npx @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+solid: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+vue: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+svelte: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+angular: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+lit: @tanstack/intent@latest hooks install [--scope project|user] [--agents copilot,claude,codex|all]
+
+<!-- ::end:tabs -->
 
 ## Options
 
diff --git a/docs/cli/intent-install.md b/docs/cli/intent-install.md
index 91fcc85c..27b93c30 100644
--- a/docs/cli/intent-install.md
+++ b/docs/cli/intent-install.md
@@ -5,9 +5,16 @@ id: intent-install
 
 `intent install` confirms skill-source permissions on first use, then creates or updates an `intent-skills` guidance block in a project guidance file.
 
-```bash
-npx @tanstack/intent@latest install [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+solid: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+vue: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+svelte: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+angular: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+lit: @tanstack/intent@latest install [--maintainer] [--review] [--map] [--dry-run] [--print-prompt] [--global] [--global-only] [--no-notices]
+
+<!-- ::end:tabs -->
 
 ## Options
 
@@ -29,6 +36,17 @@ npx @tanstack/intent@latest install [--map] [--dry-run] [--print-prompt] [--glob
 
 ## Behavior
 
+### Maintainer workflow
+
+For the full command workflow, use [`intent maintainer setup`](./intent-maintainer). `install --maintainer` remains available when only the repository instruction block is needed.
+
+`install --maintainer` enables initial skill batches and source-aware skill maintenance in repository agent instructions. It works without an interactive terminal or existing consumer permissions. It writes a separate `intent-maintainer` block, preserves consumer guidance, and is idempotent. `--dry-run` previews the block.
+
+Run it from the library root. The block loads the packaged authoring procedure for substantial library work; that procedure covers the cumulative domain map, spec, and skill tree, source review, task checks, and revision-bound outcomes. It updates the file that already contains either Intent managed block, or creates `AGENTS.md` when neither exists. It cannot be combined with `--review`, `--map`, `--print-prompt`, `--global`, or `--global-only`. See [Quick Start for Maintainers](../getting-started/quick-start-maintainers).
+
+> [!NOTE] Maintainer installation writes guidance
+> It does not add Intent to `package.json`, configure consumer skill permissions, install agent hooks, or add CI. The managed block uses the detected package manager's runner with `@tanstack/intent@latest`.
+
 ### Default install
 
 If `intent.skills` is already configured, including through workspace inheritance, `install` only updates guidance. It does not prompt or change `package.json`. Run `intent install --review` to change permissions.
@@ -73,9 +91,16 @@ After permissions are saved, Intent updates an existing managed guidance block i
 
 ### Review existing permissions
 
-```bash
-npx @tanstack/intent@latest install --review
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest install --review
+solid: @tanstack/intent@latest install --review
+vue: @tanstack/intent@latest install --review
+svelte: @tanstack/intent@latest install --review
+angular: @tanstack/intent@latest install --review
+lit: @tanstack/intent@latest install --review
+
+<!-- ::end:tabs -->
 
 Review starts from the current `intent.skills` rules. Continue with them, add packages/scopes/individual skills, remove explicit rules, or review individual skills within enabled packages. Existing rules stay intact unless you change them, including rules for packages or skills that are **not discovered**. Removing a rule requires unchecking it; Intent never removes it automatically.
 
@@ -103,34 +128,11 @@ Supported config files: `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, `.github/copil
 
 ## Default output
 
-The default block tells agents to discover skills and load matching guidance on demand:
-
-```markdown
-<!-- intent-skills:start -->
-## Skill Loading
-
-Before editing files for a substantial task:
-- Run `npx @tanstack/intent@latest list` from the workspace root to see available local skills.
-- If a listed skill matches the task, run `npx @tanstack/intent@latest load <package>#<skill>` before changing files.
-- Use the loaded `SKILL.md` guidance while making the change.
-- Monorepos: when working across packages, run the skill check from the workspace root and prefer the local skill for the package being changed.
-- Multiple matches: prefer the most specific local skill for the package or concern you are changing; load additional skills only when the task spans multiple packages or concerns.
-<!-- intent-skills:end -->
-```
+The managed `intent-skills` block instructs agents to discover skills with `intent list`, load matching guidance with `intent load`, and apply it before editing. It tells agents to work from the workspace root, prefer the most specific local skill, and load additional skills only when the task spans multiple concerns. Generated commands use the detected package manager's runner with `@tanstack/intent@latest`.
 
 ## Mapping output
 
-`--map` writes compact skill identities and commands:
-
-```yaml
-<!-- intent-skills:start -->
-# TanStack Intent - before editing files, run the matching guidance command.
-tanstackIntent:
-  - id: "@tanstack/query#fetching"
-    run: "npx @tanstack/intent@latest load @tanstack/query#fetching"
-    for: "Query data fetching patterns"
-<!-- intent-skills:end -->
-```
+`--map` writes a `tanstackIntent` list inside the managed `intent-skills` block. Each mapping contains:
 
 - `id`: portable skill identity in `<package>#<skill>` format
 - `run`: package-manager-aware command agents should run before editing
diff --git a/docs/cli/intent-list.md b/docs/cli/intent-list.md
index 7fe6438e..3d4d4d46 100644
--- a/docs/cli/intent-list.md
+++ b/docs/cli/intent-list.md
@@ -5,9 +5,16 @@ id: intent-list
 
 `intent list` discovers skill-enabled packages and shows the skills available under the project's permissions and exclusions. It does not change permissions or write guidance.
 
-```bash
-npx @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+solid: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+vue: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+svelte: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+angular: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+lit: @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [--show-hidden] [--no-notices]
+
+<!-- ::end:tabs -->
 
 ## Options
 
@@ -25,6 +32,9 @@ npx @tanstack/intent@latest list [--json] [--debug] [--global] [--global-only] [
 
 ## Behavior
 
+> [!NOTE]
+> `list` is the consumer catalog for skills shipped by project and workspace dependencies. Library maintainers load Intent's packaged authoring procedures through `intent meta` or the installed maintainer block; `intent maintainer` handles setup, registration, synchronization, and checks.
+
 ### Default list
 
 Intent scans project and workspace dependencies, applies `package.json#intent.skills`, then removes packages and skills matched by `intent.exclude`. It uses project `node_modules` when available and Yarn's PnP API in PnP projects without usable `node_modules`.
@@ -81,7 +91,7 @@ Text output includes:
 - A skill tree grouped by package, with descriptions and commands to load each skill.
 - Version conflicts and discovery warnings, when present.
 
-Load commands use the detected package manager and preserve the selected global scan scope. `SOURCE` distinguishes local discovery from explicit global scanning.
+Load commands use the detected package manager's `@tanstack/intent@latest` runner and preserve the selected global scan scope. `SOURCE` distinguishes local discovery from explicit global scanning.
 
 Text output and discovery warnings go to stdout. Policy notices and `--debug` details go to stderr.
 
@@ -99,7 +109,8 @@ Text output and discovery warnings go to stdout. Policy notices and `--debug` de
       "packageVersion": "5.0.0",
       "packageSource": "local",
       "skillName": "fetching",
-      "description": "Query data fetching patterns",
+      "description": "Use when fetching and caching server data with TanStack Query.",
+      "purpose": "Query data fetching patterns",
       "type": "core",
       "framework": "react"
     }
@@ -124,6 +135,8 @@ Text output and discovery warnings go to stdout. Policy notices and `--debug` de
 | Field | Meaning |
 | --- | --- |
 | `skills` | Available skills. `use` is the portable `<package>#<skill>` identity; `type` and `framework` are optional. |
+| Skill `description` | Standard agent-discovery text describing when to use the skill. Also used in the text listing. |
+| Skill `purpose` | Optional descriptive explanation from `metadata.purpose`, kept separate from activation guidance. Omitted from JSON when absent. |
 | `packages` | Selected packages, their source and location, and permitted skill counts. |
 | `hiddenSourceCount` | Number of packages hidden by the explicit allowlist. |
 | `hiddenSources` | Objects with `name` and `skillCount` in human sessions, even without `--show-hidden`. Always empty in agent sessions. |
@@ -156,6 +169,7 @@ JSON includes diagnostics in the object instead of printing separate warning or
 
 - [intent install](./intent-install)
 - [intent load](./intent-load)
+- [intent meta](./intent-meta)
 - [intent exclude](./intent-exclude)
 - [Configuration](../concepts/configuration)
 - [Trust model](../concepts/trust-model)
diff --git a/docs/cli/intent-load.md b/docs/cli/intent-load.md
index 48fc0654..8e36876c 100644
--- a/docs/cli/intent-load.md
+++ b/docs/cli/intent-load.md
@@ -5,10 +5,19 @@ id: intent-load
 
 `intent load` loads a compact skill identity from the current install and prints the matching `SKILL.md` content.
 
-```bash
-npx @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+solid: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+vue: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+svelte: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+angular: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
+lit: @tanstack/intent@latest load <package>#<skill> [--path] [--json] [--debug] [--global] [--global-only]
 ```
 
+<!-- ::end:tabs -->
+
 ## Options
 
 - `--path`: print the resolved skill path instead of the file content
@@ -44,12 +53,34 @@ The package can be scoped or unscoped. The skill can include slash-separated sub
 
 Examples:
 
-```bash
-npx @tanstack/intent@latest load @tanstack/query#fetching
-npx @tanstack/intent@latest load @tanstack/query#core/fetching
-npx @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
-npx @tanstack/intent@latest load some-lib#core --path
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest load @tanstack/query#fetching
+react: @tanstack/intent@latest load @tanstack/query#core/fetching
+react: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+react: @tanstack/intent@latest load some-lib#core --path
+solid: @tanstack/intent@latest load @tanstack/query#fetching
+solid: @tanstack/intent@latest load @tanstack/query#core/fetching
+solid: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+solid: @tanstack/intent@latest load some-lib#core --path
+vue: @tanstack/intent@latest load @tanstack/query#fetching
+vue: @tanstack/intent@latest load @tanstack/query#core/fetching
+vue: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+vue: @tanstack/intent@latest load some-lib#core --path
+svelte: @tanstack/intent@latest load @tanstack/query#fetching
+svelte: @tanstack/intent@latest load @tanstack/query#core/fetching
+svelte: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+svelte: @tanstack/intent@latest load some-lib#core --path
+angular: @tanstack/intent@latest load @tanstack/query#fetching
+angular: @tanstack/intent@latest load @tanstack/query#core/fetching
+angular: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+angular: @tanstack/intent@latest load some-lib#core --path
+lit: @tanstack/intent@latest load @tanstack/query#fetching
+lit: @tanstack/intent@latest load @tanstack/query#core/fetching
+lit: @tanstack/intent@latest load @tanstack/router-core#auth-and-guards
+lit: @tanstack/intent@latest load some-lib#core --path
+
+<!-- ::end:tabs -->
 
 ## JSON output
 
diff --git a/docs/cli/intent-maintainer.md b/docs/cli/intent-maintainer.md
new file mode 100644
index 00000000..74626f2c
--- /dev/null
+++ b/docs/cli/intent-maintainer.md
@@ -0,0 +1,168 @@
+---
+title: intent maintainer
+id: intent-maintainer
+---
+
+`intent maintainer` provides one command workflow for creating, maintaining, and distributing library skills. Skills stay in their owning packages. The commands keep registrations and generated metadata consistent; maintainers and coding agents supply the task knowledge and review conclusions.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `maintainer setup` | Install repository guidance, create missing planning records, and save the distribution choice. |
+| `maintainer add <name>` | Create a skill skeleton or register an existing skill in the cumulative record. |
+| `maintainer status` | Show authoring gaps, stale generated files, and pending source reviews. |
+| `maintainer sync` | Align tree metadata, package publishing entries, plugin manifests, and consumer install commands. |
+| `maintainer review` | Inspect Git changes and record supplied outcomes against content fingerprints. |
+| `maintainer check` | Check skill structure, registration, generated metadata, and recorded reviews locally or in CI. |
+
+The former `scaffold` command is removed. Use `maintainer setup` and `maintainer add` for file creation, and `meta generate-skill` for the authoring procedure.
+
+## Setup
+
+Run from a Git working tree containing the library's package manifest:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup
+solid: @tanstack/intent@latest maintainer setup
+vue: @tanstack/intent@latest maintainer setup
+svelte: @tanstack/intent@latest maintainer setup
+angular: @tanstack/intent@latest maintainer setup
+lit: @tanstack/intent@latest maintainer setup
+
+<!-- ::end:tabs -->
+
+Setup preserves existing documents and repository instructions. Standalone packages use `skills/_artifacts/`; monorepos share `_artifacts/` at the repository root. An existing custom location is retained. If several locations exist, select one with `--artifacts <repository-relative-directory>`.
+
+The three records have separate jobs:
+
+| Record | Owns |
+| --- | --- |
+| `domain_map.yaml` | Domains, developer tasks, supported failure modes, and knowledge gaps. |
+| `skill_spec.md` | Coverage, maintainer decisions, check results, and batch history. |
+| `skill_tree.yaml` | Skill identities, owning packages, paths, source mappings, prerequisites, and the distribution choice. |
+
+Generated skeletons remain unfinished. Author their contents and remove the `intent:needs-authoring` marker after completing that work. A successful setup command does not mean the skills are ready to publish.
+
+## Add a skill
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+solid: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+vue: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+svelte: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+angular: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+lit: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+
+<!-- ::end:tabs -->
+
+Omit `--package` for a standalone package or a repository-owned discovery skill. The default path is `skills/<name>/SKILL.md` within that package. Use `--path <package-relative-path>/SKILL.md` for an established layout. Repeat `--source` and `--requires` to supply multiple paths or prerequisites.
+
+To register existing guidance, supply its name, domain, package, and path. The command reads its frontmatter and preserves the file. To change an already registered skill, edit its guidance and run `maintainer sync`.
+
+Registration updates the tree and domain map and appends an entry to the spec. Write the task coverage, source-backed guidance, and consequential decisions; the command does not infer them.
+
+## Choose repository distribution
+
+Package skills can also be offered through GitHub installers and native plugins. Select the registered skills explicitly:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+solid: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+vue: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+svelte: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+angular: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+lit: @tanstack/intent@latest maintainer setup --distribution repo --repository owner/library --skill discover-library --skill retries
+
+<!-- ::end:tabs -->
+
+The repository is inferred from package metadata when available. `--plugin-name <name>` can choose the initial plugin name. New skills are never added to the selection automatically, and local prerequisites must be selected explicitly.
+
+To keep the package distribution workflow without generating repository exports:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup --distribution none
+solid: @tanstack/intent@latest maintainer setup --distribution none
+vue: @tanstack/intent@latest maintainer setup --distribution none
+svelte: @tanstack/intent@latest maintainer setup --distribution none
+angular: @tanstack/intent@latest maintainer setup --distribution none
+lit: @tanstack/intent@latest maintainer setup --distribution none
+
+<!-- ::end:tabs -->
+
+Setup remembers this choice. `maintainer check` reports an unconfigured choice until either option is recorded.
+
+After authoring, `maintainer sync` updates Claude and Cursor plugin manifests and marketplace entries that point to the existing skill directories. It preserves unrelated plugin fields and other marketplace entries. It writes `.intent/skill-distribution.json` with source paths and install arguments, and prints commands consumers can copy. Conflicting plugin identities or source roots require resolution before synchronization writes anything.
+
+Opting out after exports exist clears the selected paths and Intent's marketplace entry on the next sync. Other plugin features and source skills remain. This does not revoke installed copies or hide public GitHub files.
+
+### Consumer choices
+
+- Use the generated `npx skills add owner/library --skill <names>` command for a selected set, or `gh skill add owner/library <exact-SKILL.md-path>` for an individual skill.
+- Install the generated marketplace through Claude Code or Cursor's native plugin flow.
+- Install the npm package and use Intent's existing `list`, `install`, and `load` commands for its bundled version of the guidance.
+
+Repository location and installation scope are separate choices. The skill installers default to project scope; consumers can explicitly choose user scope with `--global` for `skills` or `--scope user` for `gh`. Third-party tools retain their own discovery behavior: a full scan or `--all` may expose other public skills. Use the generated selection or exact paths for a curated subset.
+
+A discovery skill can help someone decide whether a library fits before they install it. Keep that guidance about supported tasks and setup choices, respect the project's chosen stack, and hand API implementation to the installed package's skills and source. Avoid maintaining another copy of version-sensitive API instructions in the discovery skill.
+
+## Maintain and check
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer status
+react: @tanstack/intent@latest maintainer sync
+react: @tanstack/intent@latest maintainer review --json
+solid: @tanstack/intent@latest maintainer status
+solid: @tanstack/intent@latest maintainer sync
+solid: @tanstack/intent@latest maintainer review --json
+vue: @tanstack/intent@latest maintainer status
+vue: @tanstack/intent@latest maintainer sync
+vue: @tanstack/intent@latest maintainer review --json
+svelte: @tanstack/intent@latest maintainer status
+svelte: @tanstack/intent@latest maintainer sync
+svelte: @tanstack/intent@latest maintainer review --json
+angular: @tanstack/intent@latest maintainer status
+angular: @tanstack/intent@latest maintainer sync
+angular: @tanstack/intent@latest maintainer review --json
+lit: @tanstack/intent@latest maintainer status
+lit: @tanstack/intent@latest maintainer sync
+lit: @tanstack/intent@latest maintainer review --json
+
+<!-- ::end:tabs -->
+
+Status accepts `--json` and an actual Git comparison base with `--base <ref>`. Sync copies descriptions, purpose, sources, and prerequisites from the registered skills into the tree. It also adds the package discovery keyword and includes skill directories in existing `files` allowlists. An absent allowlist stays absent, preserving npm's default contents. Inspect the actual packed archive in the library's release checks.
+
+Save the review report under `.intent/`, annotate completed items with an outcome, reason, and actual evidence, then record and check:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer review --record .intent/review.json
+react: @tanstack/intent@latest maintainer check
+solid: @tanstack/intent@latest maintainer review --record .intent/review.json
+solid: @tanstack/intent@latest maintainer check
+vue: @tanstack/intent@latest maintainer review --record .intent/review.json
+vue: @tanstack/intent@latest maintainer check
+svelte: @tanstack/intent@latest maintainer review --record .intent/review.json
+svelte: @tanstack/intent@latest maintainer check
+angular: @tanstack/intent@latest maintainer review --record .intent/review.json
+angular: @tanstack/intent@latest maintainer check
+lit: @tanstack/intent@latest maintainer review --record .intent/review.json
+lit: @tanstack/intent@latest maintainer check
+
+<!-- ::end:tabs -->
+
+The [source-review reference](./intent-review) describes the report format, fingerprints, and baseline recovery. `maintainer review` supports its `--base`, `--json`, and `--record` options. The standalone `review` command also remains available for workflow reminder output and review-only checks.
+
+`maintainer check --base <pull-request-base>` runs the same maintainer checks in CI. It does not publish, install consumer skills, or certify that an agent's recorded conclusion is correct. Missing task evidence remains a review responsibility.
+
+## Related
+
+- [Maintainer quick start](../getting-started/quick-start-maintainers)
+- [Source review](./intent-review)
+- [CI setup](./intent-setup)
+- [Publishing and registry discovery](../registry)
diff --git a/docs/cli/intent-meta.md b/docs/cli/intent-meta.md
index 041daae7..2cae9327 100644
--- a/docs/cli/intent-meta.md
+++ b/docs/cli/intent-meta.md
@@ -5,11 +5,25 @@ id: intent-meta
 
 `intent meta` lists bundled meta-skills or prints one meta-skill file.
 
-```bash
-npx @tanstack/intent@latest meta
-npx @tanstack/intent@latest meta <name>
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest meta
+react: @tanstack/intent@latest meta <name>
+solid: @tanstack/intent@latest meta
+solid: @tanstack/intent@latest meta <name>
+vue: @tanstack/intent@latest meta
+vue: @tanstack/intent@latest meta <name>
+svelte: @tanstack/intent@latest meta
+svelte: @tanstack/intent@latest meta <name>
+angular: @tanstack/intent@latest meta
+angular: @tanstack/intent@latest meta <name>
+lit: @tanstack/intent@latest meta
+lit: @tanstack/intent@latest meta <name>
 ```
 
+<!-- ::end:tabs -->
+
 ## Arguments
 
 - `<name>` is a meta-skill directory under `node_modules/@tanstack/intent/meta/`
@@ -30,5 +44,5 @@ npx @tanstack/intent@latest meta <name>
 
 - Meta directory not found
 - Invalid `<name>` format
-- Unknown `<name>` (message suggests running `npx @tanstack/intent meta`)
+- Unknown `<name>` (message suggests listing the available meta-skills)
 - Read failure for target `SKILL.md`
diff --git a/docs/cli/intent-review.md b/docs/cli/intent-review.md
new file mode 100644
index 00000000..e89314e8
--- /dev/null
+++ b/docs/cli/intent-review.md
@@ -0,0 +1,262 @@
+---
+title: intent review
+id: intent-review
+---
+
+`intent review` shows which library skills and planning records need review after source changes. Completed reviews are remembered until their source or guidance changes again.
+
+For the full maintainer pipeline, use [`intent maintainer review`](./intent-maintainer) with `--base`, `--json`, or `--record`. It uses the same source-review implementation and report format described here. `intent maintainer check` combines review with registration, skill validation, distribution, and generated-file checks. The standalone command remains available for review-only checks and generated workflow reminders.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+solid: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+vue: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+svelte: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+angular: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+lit: @tanstack/intent@latest review [dir] [--base <ref>] [--json] [--check] [--record <report.json>] [--github-review] [--package-label <label>]
+```
+
+<!-- ::end:tabs -->
+
+For the normal coding-agent workflow, run [maintainer setup](./intent-maintainer#setup) once. The installed guidance instructs the agent to review guidance and maintain the planning documents before handoff.
+
+## Quick start
+
+1. Run `intent review` from your library repository to see pending work.
+2. Ask your agent to review those items using the current source change. It updates the skills and planning record, then runs the relevant checks.
+3. Keep the resulting `.intent/review-state.json` with the source, skills, and planning documents in your change.
+4. Run `intent review --check` to confirm that no unreviewed items remain.
+
+A justified no-op is a completed review. Missing evidence remains pending.
+
+## Options
+
+### Comparison and output
+
+| Option | Behavior |
+| --- | --- |
+| `[dir]` | Locate the Git working tree. The review covers that repository, including its packages. |
+| `--base <ref>` | Compare against an available Git commit or ref, such as the actual PR base. |
+| `--json` | Print the complete structured report for an agent or script. |
+| `--check` | Exit nonzero when review items remain. |
+
+### Recording and reminders
+
+| Option | Behavior |
+| --- | --- |
+| `--record <report.json>` | Record completed outcomes from an annotated JSON report. |
+| `--github-review` | Write `review-items.json`, a `pr-body.md` reminder when needed, and GitHub step output/summary when configured. |
+| `--package-label <label>` | Set the library label in generated reminder items. |
+
+`--record` cannot be combined with `--base`, `--json`, or `--check`. `--github-review` cannot be combined with `--record`, `--json`, or `--check`.
+
+## Behavior
+
+### What appears in a review
+
+| Item | Why it appears | What to do |
+| --- | --- | --- |
+| Skill (`skill`) | No recorded review, changed source, or changed skill/reference content. | Compare the guidance with the source and update it when needed. |
+| Planning records (`planning`) | The domain map, spec, or tree needs initial review, or its source/skill evidence changed. | Reconcile all three documents, preserving earlier decisions and remaining work. |
+| Unmapped change (`source`) | A changed file is outside declared skill sources, or a skill was removed. | Decide whether existing guidance, a new skill, or an exclusion is appropriate. |
+
+An unmapped file does not automatically require a new skill. A planning review can be needed even when nobody edited the planning documents.
+
+### Comparison scope
+
+Git and an initial commit are required. The default command is read-only.
+
+| Setting | Comparison |
+| --- | --- |
+| Explicit `--base` | The commit selected by that ref. |
+| Existing review state | The first recorded baseline, plus each item's recorded content hashes. |
+| No review state | `HEAD` and the current working tree. |
+
+The comparison includes committed changes since the base and staged, unstaged, and untracked files visible to Git. Renames appear as removals and additions. It reviews final working-tree content; a partially staged index is not separately certified.
+
+Recorded hashes detect later edits even when a review happened before a commit. The state retains hashes rather than earlier source text. Default review fails closed when its stored baseline is no longer available; it does not infer a replacement from rewritten history.
+
+### Recover an unavailable baseline
+
+A squash merge, shallow clone, or history rewrite can remove the commit stored as the review baseline. Choose an available commit that covers the changes you intend to review, then create an explicit-base report:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+solid: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+vue: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+svelte: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+angular: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+lit: @tanstack/intent@latest review --base <available-commit> --json > .intent/review.json
+```
+
+<!-- ::end:tabs -->
+
+Review and resolve every item in that report, then record it:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest review --record .intent/review.json
+solid: @tanstack/intent@latest review --record .intent/review.json
+vue: @tanstack/intent@latest review --record .intent/review.json
+svelte: @tanstack/intent@latest review --record .intent/review.json
+angular: @tanstack/intent@latest review --record .intent/review.json
+lit: @tanstack/intent@latest review --record .intent/review.json
+
+<!-- ::end:tabs -->
+
+When the previous stored baseline is unavailable, recording this fully resolved explicit-base report adopts the report's base as the new durable baseline. An empty report can also adopt the new base because it records that the selected comparison has no pending items. A partial report, an omitted or `unresolved` outcome, unresolved source or planning evidence, or a changed fingerprint cannot replace the missing baseline. When the stored baseline is still available, recording an explicit-base report does not replace it.
+
+> [!WARNING] Select the recovery base deliberately
+> The selected base sets the Git comparison boundary. Fetch missing history when possible. Otherwise choose a reachable commit old enough to include every intended change; a base that is too recent can omit earlier unreviewed changes.
+
+### Source mappings
+
+Discovery covers first-party `skills/**/SKILL.md` files in the repository and its packages, custom roots containing `_artifacts/`, exact paths declared in the skill tree, and previously reviewed skill paths. An unrelated `SKILL.md` elsewhere does not automatically become a library skill. Review excludes `node_modules`, even without a Git ignore rule.
+
+| Source entry | Resolution |
+| --- | --- |
+| `src/request.ts` | Relative to the owning package, including skills in custom directories. |
+| `owner/repository:src/request.ts` | Relative to the Git root; the repository identity must match the origin or root package metadata. |
+| `src/**/*.ts` | Git glob syntax: `*`, `?`, character classes, and `**`. |
+
+Brace expansion and extglobs are unsupported. Ignored files, submodules, external source repositories, and symbolic links require manual review. Missing or unsupported mappings remain unresolved.
+
+### Required planning documents
+
+The maintainer workflow keeps a cumulative record across batches:
+
+| Document | Records |
+| --- | --- |
+| `domain_map.yaml` | Domains, developer tasks, relationships, failure modes, and gaps. |
+| `skill_spec.md` | Readable coverage, maintainer decisions, batch history, and remaining work. |
+| `skill_tree.yaml` | Skill identities, paths, package placement, prerequisites, and source mappings. |
+
+Review finds existing planning locations from these filenames, including custom directories. Without one, installed maintainer guidance requires `_artifacts/` at a monorepo root or `skills/_artifacts/` for a standalone library. Previously recorded locations remain required if their files are deleted.
+
+All three files must be present, nonempty, readable, and visible to Git. Each YAML document must contain an object with a `skills` array. Missing or invalid records remain unresolved.
+
+The planning snapshot includes the documents and the discovered skill/source evidence. Changes reopen planning review without reopening an otherwise unchanged individual skill. The check establishes file presence, YAML shape, and reviewed content hashes; the agent and maintainer still assess whether the written record is accurate and complete.
+
+## Record a completed review
+
+The installed maintainer procedure handles these steps. For manual use:
+
+1. Review the pending items, edit guidance and planning records as needed, and run the relevant checks.
+2. Regenerate the report after those edits. Save it outside source paths:
+
+   ```bash
+   mkdir -p .intent
+   ```
+
+   <!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+   ```text
+   react: @tanstack/intent@latest review --json > .intent/review.json
+   solid: @tanstack/intent@latest review --json > .intent/review.json
+   vue: @tanstack/intent@latest review --json > .intent/review.json
+   svelte: @tanstack/intent@latest review --json > .intent/review.json
+   angular: @tanstack/intent@latest review --json > .intent/review.json
+   lit: @tanstack/intent@latest review --json > .intent/review.json
+   ```
+
+   <!-- ::end:tabs -->
+
+3. Add an outcome, reason, and evidence to each item you completed. Preserve the report's identities, baseline, and fingerprints.
+4. Record the report and check remaining work:
+
+   <!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+   react: @tanstack/intent@latest review --record .intent/review.json
+   react: @tanstack/intent@latest review --check
+   solid: @tanstack/intent@latest review --record .intent/review.json
+   solid: @tanstack/intent@latest review --check
+   vue: @tanstack/intent@latest review --record .intent/review.json
+   vue: @tanstack/intent@latest review --check
+   svelte: @tanstack/intent@latest review --record .intent/review.json
+   svelte: @tanstack/intent@latest review --check
+   angular: @tanstack/intent@latest review --record .intent/review.json
+   angular: @tanstack/intent@latest review --check
+   lit: @tanstack/intent@latest review --record .intent/review.json
+   lit: @tanstack/intent@latest review --check
+
+   <!-- ::end:tabs -->
+
+### Outcomes
+
+| Outcome | Meaning | Clears the item? |
+| --- | --- | --- |
+| `updated` | Guidance or planning records were corrected and checked. | Yes, with current fingerprints and resolved evidence. |
+| `no-change` | The existing content was checked and remains accurate. | Yes, with a reason and evidence. |
+| `out-of-scope` | A skill or source item is outside the reviewed guidance scope. | Yes, with a reason and evidence. Not accepted for planning records. |
+| `unresolved` | Required evidence or a decision is still missing. | No. |
+| No outcome | The item has not been reviewed. | No. |
+
+For example, add these fields to an existing report item; this is not a complete report:
+
+```json
+{
+  "outcome": "no-change",
+  "reason": "Only the internal cache changed; the documented retry bound and errors remain the same.",
+  "evidence": ["src/request.ts", "test/request.test.ts: passed"]
+}
+```
+
+For a planning item, the reason and evidence must cover all three documents. Preserve prior tasks, decisions, and future work when extending them with a new batch.
+
+### Saved state
+
+`--record` writes `.intent/review-state.json` containing the baseline, source/guidance hashes, reviewed revision, outcomes, reasons, and evidence. It does not commit, publish, or change skill versions. `.intent/` is reserved for review state and working reports and is excluded from unmapped-change items.
+
+Identical recorded content suppresses repeat reminders. Later edits reopen review. The saved state does not replace the planning documents, execute evidence strings, or verify the truth of a recorded conclusion.
+
+## Default and JSON output
+
+Text output shows the pending count and up to 20 items, with changed paths, unresolved problems, and the next step. Use `--json` for the full report.
+
+| JSON field | Meaning |
+| --- | --- |
+| `schemaVersion` | Report format version; currently `1`. |
+| `root`, `head`, `base` | Working-tree identity and compared Git revisions. |
+| `items` | Pending skill, planning, and source review items. |
+| Item `id`, `kind`, `path` | Stable item identity, category, and location. |
+| Item `changedFiles` | Paths changed since the relevant comparison. Can be empty for initial review. |
+| Item `snapshot`, `fingerprint` | Current content hashes and item fingerprint used when recording. |
+| Item `problems` | Unresolved evidence that prevents recording completion. |
+
+## Automated checks
+
+The optional version 5 [setup workflow](./intent-setup) connects review to PRs and releases:
+
+| Trigger | Check |
+| --- | --- |
+| Pull request with maintainer guidance or review state | `maintainer check --base <PR-base-sha>` |
+| Release/manual run with review state | `review --github-review` |
+| Release/manual run without review state | Existing `stale --github-review` fallback |
+
+This catches skipped review recording and missing planning documents. It does not run an authoring model in CI. Your coding agent handles the reminder using the same maintainer procedure.
+
+## Status and errors
+
+| Result | Behavior or next step |
+| --- | --- |
+| No pending items | `--check` exits `0`. |
+| Pending review | `--check` exits nonzero; review and record the remaining items. |
+| Missing, empty, or invalid planning document | Restore or repair the record before recording completion. |
+| Source or guidance changed after the report | Regenerate `--json` after editing; stale fingerprints are rejected. |
+| Missing recorded baseline | Fetch the referenced history, or create and fully resolve an explicit `--base` report to adopt a deliberate available baseline. |
+| Missing or option-like explicit base | Pass a reachable commit or ref; explicit bases remain strict and are never inferred. |
+| Corrupt review state | Restore or repair the state; Intent does not silently discard it. |
+| Existing recording lock | Wait for the current recording. Remove the reported `.intent/review-state.json.lock` only after confirming no recording is running, then regenerate the report and retry. |
+| Wrong working tree | Regenerate the report in the repository being reviewed. |
+| Git/setup failure | Normal review exits nonzero. `--github-review` writes a failure reminder so the missing evidence stays visible. |
+
+## Related
+
+- [Maintainer quick start](../getting-started/quick-start-maintainers)
+- [intent install](./intent-install)
+- [intent validate](./intent-validate)
+- [intent stale](./intent-stale)
diff --git a/docs/cli/intent-scaffold.md b/docs/cli/intent-scaffold.md
deleted file mode 100644
index 5477cf5b..00000000
--- a/docs/cli/intent-scaffold.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: intent scaffold
-id: intent-scaffold
----
-
-`intent scaffold` prints a phased scaffold prompt for generating skills.
-
-```bash
-npx @tanstack/intent@latest scaffold
-```
-
-## Behavior
-
-- Prints prompt text to stdout
-- Does not create files
-
-## Output
-
-The printed prompt defines three ordered phases:
-
-1. `domain-discovery`
-2. `tree-generator`
-3. `generate-skill`
-
-Each phase includes a stop gate before continuing.
-
-The prompt also includes a post-generation checklist:
-
-- Run `npx @tanstack/intent@latest validate` and fix issues
-- Commit generated `skills/` and `skills/_artifacts/`
-- Ensure `@tanstack/intent` is in `devDependencies`
-- Run setup commands as needed:
-  - `npx @tanstack/intent@latest edit-package-json`
-  - `npx @tanstack/intent@latest setup`
-
-## Related
-
-- [intent validate](./intent-validate)
-- [setup commands](./intent-setup)
diff --git a/docs/cli/intent-setup.md b/docs/cli/intent-setup.md
index 96f8fb9e..124b7dd4 100644
--- a/docs/cli/intent-setup.md
+++ b/docs/cli/intent-setup.md
@@ -1,58 +1,79 @@
----
-title: setup commands
-id: intent-setup
----
-
-Intent exposes publishing setup as two commands.
-
-```bash
-npx @tanstack/intent@latest edit-package-json
-npx @tanstack/intent@latest setup
-```
-
-## Commands
-
-- `edit-package-json`: add or normalize `package.json` entries needed to publish skills
-- `setup`: copy workflow templates to `.github/workflows`
-- `setup-github-actions`: legacy alias for `setup`
-
-## What each command changes
-
-### `edit-package-json`
-
-- Requires a valid `package.json` in the current directory
-- Ensures `keywords` includes `tanstack-intent`
-- Ensures `files` includes required publish entries
-- Preserves existing indentation
-
-### `setup`
-
-- Copies the `check-skills.yml` workflow template from `@tanstack/intent/meta/templates/workflows` to `.github/workflows`
-- Applies variable substitution (`PACKAGE_NAME`, `PACKAGE_LABEL`, `PAYLOAD_PACKAGE`, `REPO`, `DOCS_PATH`, `SRC_PATH`, `WATCH_PATHS`)
-- Detects the workspace root in monorepos and writes repo-level workflows there
-- Skips files that already exist at the destination
-
-## Required `files` entries
-
-`edit-package-json` enforces different `files` sets based on package location:
-
-- Monorepo package: `skills`
-- Non-monorepo package: `skills`, `!skills/_artifacts`
-
-## Common errors
-
-- Missing or invalid `package.json` when running `edit-package-json`
-- Missing template source when running `setup`
-
-## Notes
-
-- `setup` skips existing files
-- `check-skills.yml` validates skills on PRs and opens review PRs from release/manual runs
-- To adopt updated workflow templates, delete or move the old generated workflow files first, then rerun `setup`
-- If your repo has an older generated `validate-skills.yml`, remove it after adopting the current `check-skills.yml`; PR validation now lives in `check-skills.yml`
-- In monorepos, run `setup` from either the repo root or a package directory; Intent writes workflows to the workspace root
-
-## Related
-
-- [intent validate](./intent-validate)
-- [intent scaffold](./intent-scaffold)
+---
+title: setup commands
+id: intent-setup
+---
+
+For the complete authoring workflow, use [`intent maintainer setup` and `intent maintainer sync`](./intent-maintainer). These existing commands remain available for package configuration and optional CI installation.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest edit-package-json
+react: @tanstack/intent@latest setup
+solid: @tanstack/intent@latest edit-package-json
+solid: @tanstack/intent@latest setup
+vue: @tanstack/intent@latest edit-package-json
+vue: @tanstack/intent@latest setup
+svelte: @tanstack/intent@latest edit-package-json
+svelte: @tanstack/intent@latest setup
+angular: @tanstack/intent@latest edit-package-json
+angular: @tanstack/intent@latest setup
+lit: @tanstack/intent@latest edit-package-json
+lit: @tanstack/intent@latest setup
+
+<!-- ::end:tabs -->
+
+## Commands
+
+- `edit-package-json`: add or normalize `package.json` entries needed to publish skills
+- `setup`: copy workflow templates to `.github/workflows`
+- `setup-github-actions`: legacy alias for `setup`
+
+## What each command changes
+
+### `edit-package-json`
+
+- Requires a valid `package.json` in the current directory
+- Ensures `keywords` includes `tanstack-intent`
+- Ensures `files` includes required publish entries
+- Preserves existing indentation
+
+### `setup`
+
+- Copies the `check-skills.yml` workflow template from `@tanstack/intent/meta/templates/workflows` to `.github/workflows`
+- Applies variable substitution (`PACKAGE_NAME`, `PACKAGE_LABEL`, `PAYLOAD_PACKAGE`, `REPO`, `DOCS_PATH`, `SRC_PATH`, `WATCH_PATHS`)
+- Detects the workspace root in monorepos and writes repo-level workflows there
+- Skips files that already exist at the destination
+
+> [!NOTE]
+> `setup` installs the generated repository workflow, not Intent's maintainer or consumer guidance. Run `maintainer setup` for persistent instructions and cumulative records.
+
+## Required `files` entries
+
+`edit-package-json` enforces different `files` sets based on package location:
+
+- Monorepo package: `skills`
+- Non-monorepo package: `skills`, `!skills/_artifacts`
+
+## Common errors
+
+- Missing or invalid `package.json` when running `edit-package-json`
+- Missing template source when running `setup`
+
+## Notes
+
+- `setup` skips existing files
+- On every pull request, `check-skills.yml` runs structural validation
+- On pull requests with `.intent/review-state.json` or an `intent-maintainer` block, it also runs `intent maintainer check --base <pull-request-base-sha>`
+- On release and manual runs with review state, it runs `intent review --github-review`; without review state, it falls back to `intent stale --github-review`
+- Release and manual runs create or update one review-reminder pull request only when the selected check reports review work
+- To adopt updated workflow templates, delete or move the old generated workflow files first, then rerun `setup`
+- If your repo has an older generated `validate-skills.yml`, remove it after adopting the current `check-skills.yml`; PR validation now lives in `check-skills.yml`
+- In monorepos, run `setup` from either the repo root or a package directory; Intent writes workflows to the workspace root
+
+## Related
+
+- [intent validate](./intent-validate)
+- [intent review](./intent-review)
+- [intent stale](./intent-stale)
+- [intent maintainer](./intent-maintainer)
+- [Maintainer quick start](../getting-started/quick-start-maintainers)
diff --git a/docs/cli/intent-stale.md b/docs/cli/intent-stale.md
index 70e35a6b..99fb2ef1 100644
--- a/docs/cli/intent-stale.md
+++ b/docs/cli/intent-stale.md
@@ -1,123 +1,150 @@
----
-title: intent stale
-id: intent-stale
----
-
-`intent stale` reports whether shipped skills may need review.
-
-```bash
-npx @tanstack/intent@latest stale [--json]
-```
-
-## Options
-
-- `--json`: print JSON array of staleness reports
-
-## Behavior
-
-### Scope
-
-- Checks the current package by default
-- From a monorepo root, checks workspace packages that ship skills and also reports public workspace packages with no skill or artifact coverage
-- Applies the `package.json#intent.skills` allowlist when falling back to installed dependencies; workspace packages are first-party and checked regardless. See [Configuration](../concepts/configuration).
-- When `dir` is provided, scopes the check to the targeted package or skills directory
-- Computes one staleness report per package
-
-### Coverage
-
-- Reads repo-root `_artifacts/*domain_map.yaml` and `_artifacts/*skill_tree.yaml` when present
-- Flags public workspace packages that are not represented by generated skills or artifact coverage
-- Skips workspace packages with `"private": true`
-
-### Output and workflow state
-
-- Prints text output by default or JSON with `--json`
-- Prints a non-failing workflow update reminder when `.github/workflows/check-skills.yml` is missing the current `intent-workflow-version` stamp
-- If no packages are found, prints `No intent-enabled packages found.`
-
-Artifact coverage ignores can be recorded in `_artifacts/*skill_tree.yaml` or `_artifacts/*domain_map.yaml`:
-
-```yaml
-coverage:
-  ignored_packages:
-    - '@tanstack/internal-tooling'
-    - name: packages/devtools-fixture
-      reason: test fixture only
-```
-
-Ignored packages are excluded from missing coverage signals. Private workspace packages are excluded automatically.
-
-## JSON report schema
-
-`--json` outputs an array of reports:
-
-```json
-[
-  {
-    "library": "string",
-    "currentVersion": "string | null",
-    "skillVersion": "string | null",
-    "versionDrift": "major | minor | patch | null",
-    "skills": [
-      {
-        "name": "string",
-        "reasons": ["string"],
-        "needsReview": true
-      }
-    ],
-    "signals": [
-      {
-        "type": "missing-package-coverage",
-        "library": "string",
-        "subject": "string",
-        "reasons": ["string"],
-        "needsReview": true,
-        "packageName": "string",
-        "packageRoot": "string"
-      }
-    ]
-  }
-]
-```
-
-Report fields:
-
-| Field | Meaning |
-| --- | --- |
-| `library` | Package name |
-| `currentVersion` | Latest version from npm registry, or `null` if unavailable |
-| `skillVersion` | `library_version` from skills, or `null` |
-| `versionDrift` | `major`, `minor`, `patch`, or `null` |
-| `skills` | Per-skill checks |
-| `signals` | Artifact and workspace coverage checks |
-
-Skill fields:
-
-- `name`
-- `reasons`: one or more staleness reasons
-- `needsReview`: boolean (`true` when reasons exist)
-
-Reason generation:
-
-- `version drift (<skillVersion> → <currentVersion>)`
-- `new source (<path>)` when a declared source has no stored sync SHA
-- artifact parse warnings, unresolved artifact skill paths, source drift, artifact library version drift, and missing workspace package coverage
-
-## Text output
-
-- Report header format: `<library> (<skillVersion> → <currentVersion>) [<versionDrift> drift]`
-- When no skill reasons exist: `All skills up-to-date`
-- Otherwise: one warning line per stale skill or review signal (`⚠ <name>: <reason1>, <reason2>, ...`)
-
-## Common errors
-
-- Package scan failure: prints a scanner error
-- Registry fetch failures do not crash command; `currentVersion` may be `null`
-
-## Notes
-
-- Source staleness checking is conservative: it flags missing source SHAs in sync-state, not remote content differences.
-
-## Related
-
-- [intent list](./intent-list)
+---
+title: intent stale
+id: intent-stale
+---
+
+`intent stale` reports whether shipped skills may need review.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+solid: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+vue: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+svelte: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+angular: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+lit: @tanstack/intent@latest stale [dir] [--json] [--github-review] [--package-label <label>]
+```
+
+<!-- ::end:tabs -->
+
+## Options
+
+- `--json`: print JSON array of staleness reports
+- `--github-review`: write review-reminder files and GitHub Actions output for the generated setup workflow
+- `--package-label <label>`: set the fallback library label in generated reminder items
+
+## Behavior
+
+### Scope
+
+- Checks the current package by default
+- From a monorepo root, checks workspace packages that ship skills and also reports public workspace packages with no skill or artifact coverage
+- Applies the `package.json#intent.skills` allowlist when falling back to installed dependencies; workspace packages are first-party and checked regardless. See [Configuration](../concepts/configuration).
+- When `dir` is provided, scopes the check to the targeted package or skills directory
+- Computes one staleness report per package
+
+### Coverage
+
+- Reads repo-root `_artifacts/*domain_map.yaml` and `_artifacts/*skill_tree.yaml` when present
+- Flags public workspace packages that are not represented by generated skills or artifact coverage
+- Skips workspace packages with `"private": true`
+
+### Output and workflow state
+
+- Prints text output by default or JSON with `--json`
+- Text output lists flagged skills and review signals with their reasons; JSON contains only report data
+- Prints a non-failing workflow update reminder when `.github/workflows/check-skills.yml` is missing the current `intent-workflow-version` stamp
+- If no packages are found, prints `No intent-enabled packages found.`
+
+Artifact coverage ignores can be recorded in `_artifacts/*skill_tree.yaml` or `_artifacts/*domain_map.yaml`:
+
+```yaml
+coverage:
+  ignored_packages:
+    - '@tanstack/internal-tooling'
+    - name: packages/devtools-fixture
+      reason: test fixture only
+```
+
+Ignored packages are excluded from missing coverage signals. Private workspace packages are excluded automatically.
+
+## JSON report schema
+
+`--json` outputs an array of reports:
+
+```json
+[
+  {
+    "library": "string",
+    "currentVersion": "string | null",
+    "skillVersion": "string | null",
+    "versionDrift": "major | minor | patch | null",
+    "skills": [
+      {
+        "name": "string",
+        "reasons": ["string"],
+        "needsReview": true
+      }
+    ],
+    "signals": [
+      {
+        "type": "missing-package-coverage",
+        "library": "string",
+        "subject": "string",
+        "reasons": ["string"],
+        "needsReview": true,
+        "packageName": "string",
+        "packageRoot": "string"
+      }
+    ]
+  }
+]
+```
+
+Report fields:
+
+| Field | Meaning |
+| --- | --- |
+| `library` | Package name |
+| `currentVersion` | Local package version when available; otherwise latest from npm, or `null` if unavailable |
+| `skillVersion` | `library_version` from skills, or `null` |
+| `versionDrift` | `major`, `minor`, `patch`, or `null` |
+| `skills` | Per-skill checks |
+| `signals` | Artifact and workspace coverage checks |
+
+Skill fields:
+
+- `name`
+- `reasons`: one or more staleness reasons
+- `needsReview`: boolean (`true` when reasons exist)
+
+Reason generation:
+
+- `version drift (<skillVersion> → <currentVersion>)`
+- `new source (<path>)` when a declared source has no stored sync SHA
+- artifact parse warnings, unresolved artifact skill paths, source drift, artifact library version drift, and missing workspace package coverage
+
+## Text output
+
+- Report header format: `<library> (<skillVersion> → <currentVersion>) [<versionDrift> drift]`
+- When no skill reasons exist: `All skills up-to-date`
+- Otherwise: one warning line per stale skill or review signal (`⚠ <name>: <reason1>, <reason2>, ...`)
+
+## Generated review files
+
+The existing `--github-review` workflow mode writes `review-items.json` and, when there are items, `pr-body.md`. Its Agent Review instructions route to `generate-skill` and its conditional review-signals reference. The command itself does not create a remote PR or edit skills; the installed GitHub workflow handles the review reminder.
+
+Version drift and missing stored source SHAs do not prove that guidance is wrong. Review actual source changes before editing. Missing evidence stays unresolved, and an evidence-backed no-op may leave a signal flagged. Failed checks require logs; workflow advisories are separate maintenance items. Neither is a reason to rewrite skills.
+
+### `stale` and `review` serve different checks
+
+| Command | Evidence | Persistent result |
+| --- | --- | --- |
+| `intent stale` | Installed or registry package versions, stored source sync SHAs, artifacts, workflow version, and workspace package coverage. | Reports conservative signals; it does not record semantic review. |
+| `intent review` | Git changes plus recorded source, skill, and planning-record fingerprints. | Records evidence-backed outcomes in `.intent/review-state.json` and reopens them when tracked content changes. |
+
+## Common errors
+
+- Package scan failure: prints a scanner error
+- Registry fetch failures do not crash command; `currentVersion` may be `null`
+
+## Notes
+
+- Source staleness checking is conservative: it flags missing source SHAs in sync-state, not remote content differences.
+
+## Related
+
+- [Maintainer quick start](../getting-started/quick-start-maintainers)
+- [intent review](./intent-review)
+- [intent list](./intent-list)
diff --git a/docs/cli/intent-validate.md b/docs/cli/intent-validate.md
index 634b4b0e..0a2e5c15 100644
--- a/docs/cli/intent-validate.md
+++ b/docs/cli/intent-validate.md
@@ -1,97 +1,120 @@
----
-title: intent validate
-id: intent-validate
----
-
-`intent validate` checks `SKILL.md` files and artifacts for structural problems.
-
-```bash
-npx @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
-```
-
-## Arguments
-
-- `<dir>`: directory containing skills; default is `skills`
-- Relative paths are resolved from the current working directory
-
-## Options
-
-- `--github-summary`: write a GitHub Actions step summary when `GITHUB_STEP_SUMMARY` is set
-- `--check`: fail if any `SKILL.md` has fixable frontmatter migrations pending, without writing files
-- `--fix`: rewrite fixable `SKILL.md` frontmatter migrations, then validate the result
-
-## Frontmatter migration fixes
-
-Use `--check` in CI to detect mechanical frontmatter migrations that have not been applied:
-
-```bash
-npx @tanstack/intent@latest validate --check
-```
-
-Use `--fix` locally to apply the mechanical frontmatter migrations:
-
-```bash
-npx @tanstack/intent@latest validate --fix
-```
-
-`--fix` only rewrites unambiguous frontmatter migrations:
-
-- `name` values are rewritten to the parent directory leaf when the parent directory is already a legal skill name
-- Top-level string fields `type`, `library`, `library_version`, and `framework` are moved under `metadata`
-
-`--fix` does not rewrite authoring-judgment validation errors:
-
-- Missing or invalid `description`
-- Length-limit failures
-- Invalid `metadata` shape or non-string `metadata` values
-- Missing `requires` for framework skills
-- Artifact validation failures
-
-## Validation checks
-
-### File structure
-
-- Frontmatter delimiter and structure are valid
-- YAML frontmatter parses successfully
-- Required fields exist: `name`, `description`
-- `name` is a single leaf segment matching the skill's parent directory (no slashes); the namespace is carried by the directory path
-- `name` uses only lowercase letters, numbers, and hyphens and is at most 64 characters
-
-### Field rules
-
-- Only spec top-level keys are allowed (`name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools`); Intent-specific scalars (`type`, `library`, `library_version`, `framework`) must live under `metadata`
-- `metadata`, when present, is a mapping of string values
-- `description` length is at most 1024 characters
-- `type: framework` requires `requires` to be an array
-- Total file length is at most 500 lines
-
-### Artifacts
-
-When `<dir>/_artifacts` exists, Intent also checks:
-
-- Required files: `domain_map.yaml`, `skill_spec.md`, `skill_tree.yaml`
-- Required files must be non-empty
-- `.yaml` artifacts must parse successfully
-
-## Packaging warnings
-
-Packaging warnings are always computed from `package.json` in the current working directory:
-
-- `@tanstack/intent` missing from `devDependencies`
-- Missing `tanstack-intent` in keywords array
-- Missing `files` entries when `files` array exists:
-  - `skills`
-  - `!skills/_artifacts`
-
-Warnings are informational; they are printed on both pass and fail paths.
-
-## Common errors
-
-- Missing target directory: `Skills directory not found: <abs-path>`
-- No skill files discovered: `No SKILL.md files found`
-- Validation failures: aggregated file-specific errors and count
-
-## Related
-
-- [intent scaffold](./intent-scaffold)
-- [setup commands](./intent-setup)
+---
+title: intent validate
+id: intent-validate
+---
+
+`intent validate` checks `SKILL.md` files and artifacts for structural problems.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+solid: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+vue: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+svelte: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+angular: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+lit: @tanstack/intent@latest validate [<dir>] [--github-summary] [--fix] [--check]
+```
+
+<!-- ::end:tabs -->
+
+## Arguments
+
+- `<dir>`: directory containing skills; default is `skills`
+- Relative paths are resolved from the current working directory
+
+## Options
+
+- `--github-summary`: write a GitHub Actions step summary when `GITHUB_STEP_SUMMARY` is set
+- `--check`: fail if any `SKILL.md` has fixable frontmatter migrations pending, without writing files
+- `--fix`: rewrite fixable `SKILL.md` frontmatter migrations, then validate the result
+
+## Frontmatter migration fixes
+
+Use `--check` in CI to detect mechanical frontmatter migrations that have not been applied:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest validate --check
+solid: @tanstack/intent@latest validate --check
+vue: @tanstack/intent@latest validate --check
+svelte: @tanstack/intent@latest validate --check
+angular: @tanstack/intent@latest validate --check
+lit: @tanstack/intent@latest validate --check
+
+<!-- ::end:tabs -->
+
+Use `--fix` locally to apply the mechanical frontmatter migrations:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest validate --fix
+solid: @tanstack/intent@latest validate --fix
+vue: @tanstack/intent@latest validate --fix
+svelte: @tanstack/intent@latest validate --fix
+angular: @tanstack/intent@latest validate --fix
+lit: @tanstack/intent@latest validate --fix
+
+<!-- ::end:tabs -->
+
+`--fix` only rewrites unambiguous frontmatter migrations:
+
+- `name` values are rewritten to the parent directory leaf when the parent directory is already a legal skill name
+- Top-level string fields `type`, `library`, `library_version`, and `framework` are moved under `metadata`
+
+`--fix` does not rewrite authoring-judgment validation errors:
+
+- Missing or invalid `description`
+- Length-limit failures
+- Invalid `metadata` shape or non-string `metadata` values
+- Missing `requires` for framework skills
+- Artifact validation failures
+
+## Validation checks
+
+### File structure
+
+- Frontmatter delimiter and structure are valid
+- YAML frontmatter parses successfully
+- Required fields exist: `name`, `description`
+- `name` is a single leaf segment matching the skill's parent directory (no slashes); the namespace is carried by the directory path
+- `name` uses only lowercase letters, numbers, and hyphens and is at most 64 characters
+
+### Field rules
+
+- Only spec top-level keys are allowed (`name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools`); Intent-specific scalars (`type`, `library`, `library_version`, `framework`) must live under `metadata`
+- `metadata`, when present, is a mapping of string values
+- `description` length is at most 1024 characters
+- `type: framework` requires `requires` to be an array
+- Total file length is at most 500 lines
+
+### Artifacts
+
+When `<dir>/_artifacts` exists, Intent also checks:
+
+- Required files: `domain_map.yaml`, `skill_spec.md`, `skill_tree.yaml`
+- Required files must be non-empty
+- `.yaml` artifacts must parse successfully
+
+## Packaging warnings
+
+Packaging warnings are always computed from `package.json` in the current working directory:
+
+- `@tanstack/intent` missing from `devDependencies`
+- Missing `tanstack-intent` in keywords array
+- Missing `files` entries when `files` array exists:
+  - `skills`
+  - `!skills/_artifacts`
+
+Warnings are informational; they are printed on both pass and fail paths.
+
+## Common errors
+
+- Missing target directory: `Skills directory not found: <abs-path>`
+- No skill files discovered: `No SKILL.md files found`
+- Validation failures: aggregated file-specific errors and count
+
+## Related
+
+- [intent maintainer](./intent-maintainer)
+- [setup commands](./intent-setup)
diff --git a/docs/concepts/configuration.md b/docs/concepts/configuration.md
index 8e8b17fe..c996a607 100644
--- a/docs/concepts/configuration.md
+++ b/docs/concepts/configuration.md
@@ -117,10 +117,22 @@ See [Default install](../cli/intent-install#default-install) for picker controls
 
 Use `--no-notices` to suppress non-critical notices on stderr for one run:
 
-```bash
-npx @tanstack/intent@latest list --no-notices
-npx @tanstack/intent@latest install --map --no-notices
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list --no-notices
+react: @tanstack/intent@latest install --map --no-notices
+solid: @tanstack/intent@latest list --no-notices
+solid: @tanstack/intent@latest install --map --no-notices
+vue: @tanstack/intent@latest list --no-notices
+vue: @tanstack/intent@latest install --map --no-notices
+svelte: @tanstack/intent@latest list --no-notices
+svelte: @tanstack/intent@latest install --map --no-notices
+angular: @tanstack/intent@latest list --no-notices
+angular: @tanstack/intent@latest install --map --no-notices
+lit: @tanstack/intent@latest list --no-notices
+lit: @tanstack/intent@latest install --map --no-notices
+
+<!-- ::end:tabs -->
 
 For CI or wrapper scripts, set `INTENT_NO_NOTICES=1` to suppress notices without changing command arguments.
 
@@ -132,12 +144,31 @@ Discovery and resolution warnings are separate from policy notices and are not s
 
 Use `intent exclude` to manage this list from the CLI:
 
-```bash
-npx @tanstack/intent@latest exclude add @tanstack/router#experimental-*
-npx @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
-npx @tanstack/intent@latest exclude list
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+```text
+react: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+react: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+react: @tanstack/intent@latest exclude list
+solid: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+solid: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+solid: @tanstack/intent@latest exclude list
+vue: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+vue: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+vue: @tanstack/intent@latest exclude list
+svelte: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+svelte: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+svelte: @tanstack/intent@latest exclude list
+angular: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+angular: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+angular: @tanstack/intent@latest exclude list
+lit: @tanstack/intent@latest exclude add @tanstack/router#experimental-*
+lit: @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
+lit: @tanstack/intent@latest exclude list
 ```
 
+<!-- ::end:tabs -->
+
 ```json
 {
   "intent": {
diff --git a/docs/config.json b/docs/config.json
index 11e09090..1f7128a3 100644
--- a/docs/config.json
+++ b/docs/config.json
@@ -68,8 +68,8 @@
           "to": "cli/intent-meta"
         },
         {
-          "label": "intent scaffold",
-          "to": "cli/intent-scaffold"
+          "label": "intent maintainer",
+          "to": "cli/intent-maintainer"
         },
         {
           "label": "intent validate",
@@ -82,6 +82,10 @@
         {
           "label": "intent stale",
           "to": "cli/intent-stale"
+        },
+        {
+          "label": "intent review",
+          "to": "cli/intent-review"
         }
       ]
     }
diff --git a/docs/getting-started/quick-start-consumers.md b/docs/getting-started/quick-start-consumers.md
index f3f581de..313ab51f 100644
--- a/docs/getting-started/quick-start-consumers.md
+++ b/docs/getting-started/quick-start-consumers.md
@@ -5,13 +5,18 @@ id: quick-start-consumers
 
 ## 1. Run install
 
-```bash
-npx @tanstack/intent@latest install
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
 
-Run this in an interactive terminal. On first use, Intent helps you choose which installed packages and skills your agent may use, then creates or updates skill-loading guidance.
+react: @tanstack/intent@latest install
+solid: @tanstack/intent@latest install
+vue: @tanstack/intent@latest install
+svelte: @tanstack/intent@latest install
+angular: @tanstack/intent@latest install
+lit: @tanstack/intent@latest install
 
-Examples use `npx` for npm projects. In pnpm, Yarn, or Bun projects, use the matching runner: `pnpm dlx`, `yarn dlx`, or `bunx`.
+<!-- ::end:tabs -->
+
+Run this in an interactive terminal. On first use, Intent helps you choose which installed packages and skills your agent may use, then creates or updates skill-loading guidance.
 
 1. **Choose what to enable.** Pick **Enable all**, **Choose packages or scopes**, or **Choose individual skills**. Package and skill lists support search.
 2. **Confirm and finish.** Check the saved rules and destination `package.json`. Choose **Continue with all selected skills** to save, or **Review individual skills** to pick which selected packages to inspect before confirming. Intent writes permissions and guidance, verifies the guidance, and shows a command to list available skills.
@@ -27,34 +32,33 @@ Canceling before confirmation writes neither file. `--dry-run` previews the flow
 If an `intent-skills` block already exists, Intent updates that file in place.
 If no block exists, `AGENTS.md` is the default target.
 
-Intent creates guidance like:
+The managed block instructs agents to run `intent list` from the workspace root, load the most specific matching skill with `intent load`, and apply its guidance before editing. Intent generates those commands using the detected package manager's runner. See [Default output](../cli/intent-install#default-output) for the installed instructions and [Mapping output](../cli/intent-install#mapping-output) for explicit task mappings.
 
-```markdown
-<!-- intent-skills:start -->
-## Skill Loading
-
-Before editing files for a substantial task:
-- Run `pnpm dlx @tanstack/intent@latest list` from the workspace root to see available local skills.
-- If a listed skill matches the task, run `pnpm dlx @tanstack/intent@latest load <package>#<skill>` before changing files.
-- Use the loaded `SKILL.md` guidance while making the change.
-- Monorepos: when working across packages, run the skill check from the workspace root and prefer the local skill for the package being changed.
-- Multiple matches: prefer the most specific local skill for the package or concern you are changing; load additional skills only when the task spans multiple packages or concerns.
-<!-- intent-skills:end -->
-```
+To enforce loading guidance before edits in supported agents, opt in to hooks:
 
-Intent detects the package manager when generating this block, so the runner may be `npx`, `pnpm dlx`, `yarn dlx`, or `bunx`.
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
 
-To enforce loading guidance before edits in supported agents, opt in to hooks:
+react: @tanstack/intent@latest hooks install
+solid: @tanstack/intent@latest hooks install
+vue: @tanstack/intent@latest hooks install
+svelte: @tanstack/intent@latest hooks install
+angular: @tanstack/intent@latest hooks install
+lit: @tanstack/intent@latest hooks install
 
-```bash
-npx @tanstack/intent@latest hooks install
-```
+<!-- ::end:tabs -->
 
 Project-scoped hooks are installed for Claude Code and Codex. `intent install` can write project guidance to `.github/copilot-instructions.md`, but GitHub Copilot CLI hook enforcement is user-scoped, so configure it explicitly:
 
-```bash
-npx @tanstack/intent@latest hooks install --scope user --agents copilot
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest hooks install --scope user --agents copilot
+solid: @tanstack/intent@latest hooks install --scope user --agents copilot
+vue: @tanstack/intent@latest hooks install --scope user --agents copilot
+svelte: @tanstack/intent@latest hooks install --scope user --agents copilot
+angular: @tanstack/intent@latest hooks install --scope user --agents copilot
+lit: @tanstack/intent@latest hooks install --scope user --agents copilot
+
+<!-- ::end:tabs -->
 
 Cursor and generic `AGENTS.md` agents use the guidance block only.
 
@@ -86,9 +90,16 @@ When permissions already exist, including inherited workspace permissions, `inst
 
 Load a skill when it matches the task:
 
-```bash
-npx @tanstack/intent@latest load @tanstack/react-query#core
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest load @tanstack/react-query#core
+solid: @tanstack/intent@latest load @tanstack/react-query#core
+vue: @tanstack/intent@latest load @tanstack/react-query#core
+svelte: @tanstack/intent@latest load @tanstack/react-query#core
+angular: @tanstack/intent@latest load @tanstack/react-query#core
+lit: @tanstack/intent@latest load @tanstack/react-query#core
+
+<!-- ::end:tabs -->
 
 This prints the skill content for the installed package version.
 
@@ -96,38 +107,71 @@ Intent cannot guarantee that an agent selected the correct skill or followed its
 
 If you want explicit task-to-skill mappings in your agent config, opt in:
 
-```bash
-npx @tanstack/intent@latest install --map
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest install --map
+solid: @tanstack/intent@latest install --map
+vue: @tanstack/intent@latest install --map
+svelte: @tanstack/intent@latest install --map
+angular: @tanstack/intent@latest install --map
+lit: @tanstack/intent@latest install --map
+
+<!-- ::end:tabs -->
 
 ## 4. Keep skills up-to-date
 
-```bash
-npm update @tanstack/react-query
-```
+Update the library through your project's dependency-update workflow.
 
 Skills version with library releases. Updating a library also updates its packaged skills, so the skill version matches the installed code. If a package is installed both locally and globally and global scanning is enabled, Intent prefers the local version.
 
 List the installed skills:
 
-```bash
-npx @tanstack/intent@latest list
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list
+solid: @tanstack/intent@latest list
+vue: @tanstack/intent@latest list
+svelte: @tanstack/intent@latest list
+angular: @tanstack/intent@latest list
+lit: @tanstack/intent@latest list
+
+<!-- ::end:tabs -->
 
 Use `--json` for machine-readable output:
 
-```bash
-npx @tanstack/intent@latest list --json
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list --json
+solid: @tanstack/intent@latest list --json
+vue: @tanstack/intent@latest list --json
+svelte: @tanstack/intent@latest list --json
+angular: @tanstack/intent@latest list --json
+lit: @tanstack/intent@latest list --json
+
+<!-- ::end:tabs -->
 
 Global package scanning is opt-in:
 
-```bash
-npx @tanstack/intent@latest list --global
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list --global
+solid: @tanstack/intent@latest list --global
+vue: @tanstack/intent@latest list --global
+svelte: @tanstack/intent@latest list --global
+angular: @tanstack/intent@latest list --global
+lit: @tanstack/intent@latest list --global
+
+<!-- ::end:tabs -->
 
 You can also check if any skills reference outdated source documentation:
 
-```bash
-npx @tanstack/intent@latest stale
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest stale
+solid: @tanstack/intent@latest stale
+vue: @tanstack/intent@latest stale
+svelte: @tanstack/intent@latest stale
+angular: @tanstack/intent@latest stale
+lit: @tanstack/intent@latest stale
+
+<!-- ::end:tabs -->
diff --git a/docs/getting-started/quick-start-maintainers.md b/docs/getting-started/quick-start-maintainers.md
index e91c9443..7b477558 100644
--- a/docs/getting-started/quick-start-maintainers.md
+++ b/docs/getting-started/quick-start-maintainers.md
@@ -1,218 +1,182 @@
----
-title: Quick Start for Maintainers
-id: quick-start-maintainers
----
-
-Get started scaffolding, validating, and shipping skills for your library.
-
-## Install
-
-<!-- ::start:tabs variant="package-manager" mode="dev-install" -->
-react: @tanstack/intent
-solid: @tanstack/intent
-vue: @tanstack/intent
-svelte: @tanstack/intent
-angular: @tanstack/intent
-lit: @tanstack/intent
-<!-- ::end:tabs -->
-
-Or run commands without installing:
-
-```bash
-npx @tanstack/intent@latest scaffold
-```
-
----
-
-## Initial Setup (With Agent)
-
-### 1. Scaffold skills
-
-Start the scaffolding process **with your AI agent**:
-
-```bash
-npx @tanstack/intent@latest scaffold
-```
-
-This prints a comprehensive prompt that walks you and your agent through three phases:
-
-**Phase 1: Domain Discovery**
-- Scans your documentation, source code, and GitHub issues
-- Conducts an interactive interview to surface implicit knowledge
-- Produces `domain_map.yaml` and `skill_spec.md` artifacts
-
-**Phase 2: Tree Generation**
-- Designs a skill taxonomy based on the domain map
-- Creates a hierarchical skill structure
-- Produces `skill_tree.yaml` artifact
-
-**Phase 3: Skill Generation**
-- Writes complete SKILL.md files for each skill
-- Includes patterns, failure modes, and API references
-- Validates against the Intent specification
-
-> [!NOTE]
-> Plan for multiple review rounds and regular context compaction. The agent scans documentation, recent issues, and discussions, then asks targeted questions about implicit knowledge and common failure modes. Provide concrete patterns, pitfalls, and real-world usage problems to improve the generated skills.
-
-### 2. Validate skills
-
-After scaffolding, validate that all SKILL.md files are well-formed:
-
-```bash
-npx @tanstack/intent@latest validate
-```
-
-This checks skill structure:
-
-- Valid YAML frontmatter in every SKILL.md
-- Required fields (`name`, `description`) are present
-- Skill `name` is a leaf segment matching its parent directory
-- Description length <= 1024 characters
-- Line count limits (500 lines max per skill)
-
-It also checks Intent metadata and artifacts:
-
-- Intent-specific scalars (`type`, `library`, `library_version`, `framework`) live under `metadata`, not at the top level
-- Framework skills have a `requires` array
-- Required artifact files exist and are non-empty; YAML artifacts parse successfully
-
-### 3. Commit skills and artifacts
-
-Commit both generated skills and the artifacts used to create them:
-
-```
-skills/
-  core/SKILL.md
-  react/SKILL.md
-  _artifacts/
-    domain_map.yaml
-    skill_spec.md
-    skill_tree.yaml
-```
-
-Artifacts enforce a consistent skill structure across versions, making it easier to audit, refresh, or extend the skill set without starting from scratch.
-
----
-
-## Publish Configuration
-
-### 4. Configure your package for publishing
-
-Run these commands to prepare your package for skill publishing:
-
-```bash
-# Update package.json with required fields
-npx @tanstack/intent@latest edit-package-json
-
-# Copy the CI workflow template
-npx @tanstack/intent@latest setup
-```
-
-**What these do:**
-
-- `edit-package-json` adds:
-  - `tanstack-intent` keyword (used for package detection and registry discovery)
-  - `files` array entries for `skills/`
-  - For single packages: also adds `!skills/_artifacts` to exclude artifacts from npm
-  - For monorepos: skips the artifacts exclusion (artifacts live at repo root)
-- `setup` copies `check-skills.yml` to `.github/workflows/` for automated validation and staleness checking
-
-`setup` does not overwrite existing workflow files. To pick up newer generated workflows, delete or move the old generated files in `.github/workflows/`, then rerun `npx @tanstack/intent@latest setup`.
-
-If your repo already has an older generated `validate-skills.yml`, remove it after adopting the current `check-skills.yml`; PR validation now runs from `check-skills.yml`.
-
-### 5. Ship skills with your package
-
-Skills ship inside your npm package. When you publish:
-
-```bash
-npm publish
-```
-
-Consumers who install your library automatically get the skills. They discover local installed skills with `intent list`, add loading guidance with `intent install`, and load matching skills with `intent load`.
-
-**Version alignment:**
-- Skills version with your library releases
-- `intent load` returns skill content from the installed package version
-- Packaging code and skills together keeps their versions aligned
-
----
-
-## Ongoing Maintenance (Manual or Agent-Assisted)
-
-### 6. Set up the CI workflow
-
-After running `setup`, you'll have `check-skills.yml` in `.github/workflows/`:
-
-**check-skills.yml** (runs on PRs touching skills/artifacts, release, or manual trigger)
-
-Validation:
-
-- Validates SKILL.md frontmatter and structure
-- Ensures files stay under 500 lines
-- Automatically detects stale skills and coverage gaps after you publish a new release
-
-Review handoff:
-
-- Opens one grouped review PR with an agent-friendly prompt
-- Includes the reason each skill or package was flagged
-- Requires you to copy the prompt into Claude Code, Cursor, or your agent to update skills
-
-### 7. Update stale skills
-
-When you publish a new release, `check-skills.yml` automatically opens a PR flagging skills that need review.
-
-Manually check which skills need updates with:
-
-```bash
-npx @tanstack/intent@latest stale
-```
-
-When run from a package, this checks that package's shipped skills. When run from a monorepo root, it checks workspace packages with skills and flags public workspace packages missing skill or `_artifacts` coverage.
-
-This detects:
-- **Version drift** — skill targets an older library version than currently installed
-- **New sources** — sources declared in frontmatter that weren't tracked before
-- **Artifact drift** — `_artifacts` entries that no longer match generated skills
-- **Missing package coverage** — public workspace packages not represented by generated skills or artifact coverage
-
-If a public workspace package is intentionally out of scope for skills, record that decision in repo-root `_artifacts`:
-
-```yaml
-coverage:
-  ignored_packages:
-    - '@tanstack/internal-tooling'
-    - name: packages/devtools-fixture
-      reason: test fixture only
-```
-
-Private workspace packages are skipped automatically.
-
-**Prepare the update:**
-
-1. Review the PR opened by `check-skills.yml`
-2. Copy the agent prompt from the PR description
-3. Paste it into Claude Code, Cursor, or your coding agent
-4. The agent reads the stale skills and updates them based on library changes
-
-**Finish the update:**
-
-5. Run `npx @tanstack/intent@latest validate` locally to verify
-6. Commit and merge the PR
-
-> [!NOTE]
-> Skills are updated through agent assistance, not full automation. The workflow detects what's stale and provides the prompt — your agent handles the actual updates.
-
-Use `--json` output for CI integration or scripting.
-
-### 8. Maintain and iterate
-
-As your library evolves:
-
-1. **When APIs change:** Update relevant SKILL.md files with new patterns
-2. **When docs change:** Run `intent stale` to identify affected skills
-3. **When issues are filed:** Check if the failure mode should be added to "Common Mistakes"
-4. **After major releases:** Consider re-running domain discovery to catch new patterns
-
-> [!TIP]
-> Create GitHub issue labels matching your skill names (`skill:core`, `skill:react`). When users file issues, tag them with the relevant skill label to track which areas need the most improvement.
+---
+title: Quick Start for Maintainers
+id: quick-start-maintainers
+---
+
+After setup, request library changes as usual; Intent’s maintainer commands keep skill metadata consistent and record source-review evidence before handoff.
+
+## Install
+
+<!-- ::start:tabs variant="package-manager" mode="dev-install" -->
+
+react: @tanstack/intent
+solid: @tanstack/intent
+vue: @tanstack/intent
+svelte: @tanstack/intent
+angular: @tanstack/intent
+lit: @tanstack/intent
+
+<!-- ::end:tabs -->
+
+## Enable the maintainer workflow
+
+Run `maintainer setup` from the library repository:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup
+solid: @tanstack/intent@latest maintainer setup
+vue: @tanstack/intent@latest maintainer setup
+svelte: @tanstack/intent@latest maintainer setup
+angular: @tanstack/intent@latest maintainer setup
+lit: @tanstack/intent@latest maintainer setup
+
+<!-- ::end:tabs -->
+
+This creates missing planning records and an `intent-maintainer` block in `AGENTS.md`, or updates the file that already contains an Intent maintainer or consumer block. It preserves surrounding instructions and a separate `intent-skills` consumer block. Review this setup diff and keep it in the repository so later agent sessions receive the same authoring and review procedure.
+
+> [!NOTE]
+> Setup preserves existing records and instructions. It creates skeletons for missing records; their task knowledge still needs authoring. The runner uses `@tanstack/intent@latest`. CI installation remains a separate command.
+
+## Create the first useful batch
+
+Ask your coding agent for the developer tasks the library should support. For example:
+
+> Create a skill batch covering safe retries, cancellation, and pagination. Use our public examples and tests, and include executable checks for the important failure cases.
+
+The installed instructions load Intent's `generate-skill` procedure. The agent reads the relevant source, tests, examples, docs, and existing skills; proposes a bounded batch when its scope is undecided; and creates or updates the guidance owned by those tasks. A focused batch does not require a full-library interview or a fixed number of skills.
+
+Use `maintainer add` to create or register each agreed skill, keeping the file beside the owning package:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+solid: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+vue: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+svelte: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+angular: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+lit: @tanstack/intent@latest maintainer add retries --package packages/client --domain requests --description "Use when configuring retries with this client." --source "src/retry.ts"
+
+<!-- ::end:tabs -->
+
+Omit `--package` for a standalone library. For existing guidance, supply its name, domain, package, and path; the command preserves the file and reads its frontmatter. The [maintainer command reference](../cli/intent-maintainer) covers custom paths and prerequisites.
+
+Every skill batch also creates or incrementally updates three planning documents. These records preserve prior scope, maintainer decisions, exclusions, source mappings, and remaining work across later batches.
+
+<!-- ::start:tabs variant="files" -->
+
+```text title="Standalone package"
+skills/
+  task-name/
+    SKILL.md
+  _artifacts/
+    domain_map.yaml
+    skill_spec.md
+    skill_tree.yaml
+```
+
+```text title="Monorepo"
+_artifacts/
+  domain_map.yaml
+  skill_spec.md
+  skill_tree.yaml
+packages/
+  client/
+    skills/
+      task-name/
+        SKILL.md
+```
+
+<!-- ::end:tabs -->
+
+Existing custom skill and artifact locations are retained when supported. The domain map records domains and developer tasks, the spec records readable coverage and decisions, and the tree records skill placement, prerequisites, and source mappings.
+
+Review the resulting skills, planning documents, and checks as one batch:
+
+| Check | Evidence |
+| --- | --- |
+| Structure | Frontmatter, required fields, and line limits; inspect reference paths and reading conditions separately. |
+| Developer task | Executable checks accept a working solution and reject a plausible mistake. |
+| Discovery | Realistic matching and adjacent nonmatching requests exercise the skill description. |
+| Fresh consumer | An isolated agent attempts the task with the candidate skills and protected checks grade the result. |
+| Bundled scripts, when present | Documented commands run from the installed package layout with valid and invalid inputs. |
+
+A missing runtime or independent run remains explicitly unverified. Structural validation alone does not establish task correctness, skill discovery, or fresh-consumer behavior.
+
+## Keep guidance current during library work
+
+Continue requesting library changes normally. Before handoff, the installed guidance instructs the agent to run `intent maintainer review --json`, examine affected skills, the planning record, and changed files outside existing source mappings, then record each completed decision with its evidence.
+
+`intent maintainer review` uses Git changes and content fingerprints to find work that has not been reviewed. Intent identifies candidates; the agent and maintainer decide whether the guidance should change. A new file does not automatically require a new skill. A justified `no-change` outcome records why accurate guidance stayed unchanged, while missing evidence remains pending.
+
+Completed outcomes are saved in `.intent/review-state.json`. Keep that file with the source, skill, and planning-record changes it describes. Run `intent maintainer sync` after authoring to align metadata, then regenerate the report with `intent maintainer review --json` so it covers the final files. Annotate the completed outcomes and record them with `intent maintainer review --record <report.json>`. Finish with `intent maintainer check` to check authoring gaps, generated files, and pending reviews together.
+
+See [`intent review`](../cli/intent-review) for comparison rules, report fields, recording, and failure recovery.
+
+## Choose how consumers install the skills
+
+Setup explains repository distribution until you record a choice. Select the public skills explicitly:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+solid: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+vue: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+svelte: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+angular: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+lit: @tanstack/intent@latest maintainer setup --distribution repo --skill discover-library --skill retries
+
+<!-- ::end:tabs -->
+
+Use the actual registered names. This records the selection in the skill tree. `maintainer sync` generates plugin metadata pointing to the existing package directories and prints consumer commands for `npx skills add` and `gh skill add`. Consumers can also use the native Claude or Cursor plugin flow. No second copy of the skill text is created, and later skills are not added automatically.
+
+To keep the package-only workflow, record the opt-out once:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup --distribution none
+solid: @tanstack/intent@latest maintainer setup --distribution none
+vue: @tanstack/intent@latest maintainer setup --distribution none
+svelte: @tanstack/intent@latest maintainer setup --distribution none
+angular: @tanstack/intent@latest maintainer setup --distribution none
+lit: @tanstack/intent@latest maintainer setup --distribution none
+
+<!-- ::end:tabs -->
+
+A repository discovery skill can help developers decide whether the library fits before installation. Respect their existing stack and hand implementation to the installed package's version of the guidance. Repository skills can be installed at project or user scope; those are consumer choices, separate from where the source files live. See [repository distribution](../cli/intent-maintainer#choose-repository-distribution).
+
+For direct authoring guidance, load `meta generate-skill`. Explicitly requested full-library design still uses `meta domain-discovery`, then `meta tree-generator`, then `meta generate-skill`.
+
+## Configure publishing
+
+Run the same synchronization command after skill edits. Add the optional CI workflow when the repository is ready for it:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer sync
+react: @tanstack/intent@latest setup
+solid: @tanstack/intent@latest maintainer sync
+solid: @tanstack/intent@latest setup
+vue: @tanstack/intent@latest maintainer sync
+vue: @tanstack/intent@latest setup
+svelte: @tanstack/intent@latest maintainer sync
+svelte: @tanstack/intent@latest setup
+angular: @tanstack/intent@latest maintainer sync
+angular: @tanstack/intent@latest setup
+lit: @tanstack/intent@latest maintainer sync
+lit: @tanstack/intent@latest setup
+
+<!-- ::end:tabs -->
+
+`maintainer sync` aligns the tree, adds the `tanstack-intent` keyword, updates existing package `files` allowlists, and generates selected repository exports. It preserves authored decisions and an absent npm allowlist. Inspect the packed archive as part of the library’s release checks, including whether planning records should be excluded.
+
+`setup` copies `check-skills.yml` to the workspace root's `.github/workflows/` directory and skips an existing destination file. The workflow validates skills and recorded source reviews on pull requests. After a release or manual run, it creates or updates a review-reminder pull request when recorded review state or conservative staleness signals require attention. See [setup commands](../cli/intent-setup).
+
+> [!NOTE]
+> `intent setup` copies CI templates; `intent maintainer setup` initializes the maintainer workflow. To replace an older generated workflow, move or delete it before rerunning `setup`; Intent skips existing files.
+
+Publish through the library's normal release process. Skills in the package's published `skills/` directory version with that library release. Consumers install the library, configure permitted skill sources with consumer [`intent install`](../cli/intent-install#default-install), discover the installed skills with [`intent list`](../cli/intent-list), and load matching guidance with `intent load`.
+
+## Check package and release signals
+
+[`intent stale`](../cli/intent-stale) remains the conservative package-level check for version drift, missing source sync SHAs, artifact warnings, and workspace package coverage. It does not compare source diffs or prove that guidance changed. Use `intent maintainer review` for source-aware, recorded maintenance in repositories that enabled the maintainer workflow.
diff --git a/docs/overview.md b/docs/overview.md
index 0b1d65f2..79fbe7de 100644
--- a/docs/overview.md
+++ b/docs/overview.md
@@ -1,88 +1,154 @@
----
-title: Overview
-id: overview
----
-
-`@tanstack/intent` is a CLI for shipping and consuming Agent Skills as package artifacts.
-
-Skills are markdown documents that teach AI coding agents how to use your library correctly. Intent versions them with your releases and ships them inside npm packages. It discovers skills from project and workspace dependencies, then provides commands and guidance for loading them.
-
-## What Intent does
-
-Intent provides tooling for two workflows:
-
-**For consumers:**
-
-- Discover skills from your project and workspace dependencies
-- Control which packages' skills are surfaced with an allowlist
-- Add lightweight skill loading guidance to your agent config
-- Add session catalogs and edit gates for supported agents
-- Use skills packaged with installed library versions
-
-**For maintainers (library teams):**
-
-- Scaffold skills through AI-assisted domain discovery
-- Validate SKILL.md format and packaging
-- Ship skills in the same release pipeline as code
-- Review version, source, artifact, and package coverage signals
-
-## How it works
-
-### Discovery and installation
-
-Use the runner for your package manager:
-
-| Tool | Pattern                                      |
-| ---- | -------------------------------------------- |
-| npm  | `npx @tanstack/intent@latest <command>`      |
-| pnpm | `pnpm dlx @tanstack/intent@latest <command>` |
-| Yarn | `yarn dlx @tanstack/intent@latest <command>` |
-| Bun  | `bunx @tanstack/intent@latest <command>`     |
-
-```bash
-npx @tanstack/intent@latest list
-```
-
-Scans the current project's installed dependencies for intent-enabled packages, including `node_modules`, workspace dependencies, and Yarn PnP projects without `node_modules`. You can narrow which packages are surfaced with `package.json#intent.skills`. See the [Trust model](./concepts/trust-model) and [Configuration](./concepts/configuration) for how the allowlist works.
-Global package scanning is explicit; pass `--global` to include global packages or `--global-only` to ignore local packages.
-When both local and global packages are scanned, local packages take precedence.
-
-```bash
-npx @tanstack/intent@latest install
-```
-
-Creates or updates lightweight `intent-skills` guidance in your config files (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`, etc.). Existing guidance is updated in place; otherwise `AGENTS.md` is the default target. Pass `--map` to opt in to explicit task-to-skill mappings.
-
-```bash
-npx @tanstack/intent@latest hooks install
-```
-
-Installs session catalogs and edit gates for supported agents. Project-scoped hooks are available for Claude Code and Codex. GitHub Copilot CLI project guidance can live in `.github/copilot-instructions.md`, while blocking hooks are user-scoped. Cursor and generic `AGENTS.md` agents use guidance only. See [intent hooks](./cli/intent-hooks) for what hooks can observe.
-
-```bash
-npx @tanstack/intent@latest load @tanstack/query#fetching
-```
-
-Loads the matching `SKILL.md` content for the installed package version. Pass `--path` when you need the resolved skill file path for debugging.
-
-### Scaffolding and validation
-
-```bash
-npx @tanstack/intent@latest scaffold
-```
-
-Guides your agent through domain discovery, tree generation, and skill authoring with interactive maintainer interviews.
-
-```bash
-npx @tanstack/intent@latest validate
-```
-
-Enforces SKILL.md format rules and packaging requirements before publish.
-
-### Staleness tracking
-
-```bash
-npx @tanstack/intent@latest stale
-```
-
-Reports version drift and source, artifact, or package coverage signals that may require skill review.
+---
+title: Overview
+id: overview
+---
+
+`@tanstack/intent` is a CLI for shipping and consuming Agent Skills as package artifacts.
+
+Skills are markdown documents that teach AI coding agents how to use your library correctly. Intent versions them with your releases and ships them inside npm packages. It discovers skills from project and workspace dependencies, then provides commands and guidance for loading them.
+
+## What Intent does
+
+Intent provides tooling for two workflows:
+
+**For consumers:**
+
+- Discover skills from your project and workspace dependencies
+- Control which packages' skills are surfaced with an allowlist
+- Add lightweight skill loading guidance to your agent config
+- Add session catalogs and edit gates for supported agents
+- Use skills packaged with installed library versions
+
+**For maintainers (library teams):**
+
+- Add a persistent skill-authoring and review procedure to repository instructions
+- Create or update focused skill guidance with an existing coding agent
+- Record source-aware review outcomes as the library changes
+- Validate SKILL.md format and packaging
+- Ship skills in the same release pipeline as code
+- Review version, source, artifact, and package coverage signals
+
+## Keep the workflow boundaries clear
+
+| Stage | Who runs it | Result |
+| --- | --- | --- |
+| Maintainer enablement | Library maintainer | `maintainer setup` creates missing records and installs persistent authoring instructions. |
+| Authoring and maintenance | Library maintainer and coding agent | `meta generate-skill` guides a focused batch; `maintainer review` records evidence-backed outcomes for later source changes. |
+| Package publishing | Library release process | `maintainer sync` updates package and selected repository exports; `setup` optionally adds CI. |
+| Consumer setup | Developer using the published library | Consumer `install` configures permitted skill sources and skill-loading guidance; `list` and `load` use skills from installed dependencies. |
+
+> [!NOTE]
+> Maintainer installation and consumer installation write separate managed guidance blocks. Neither command publishes a package or installs a dependency.
+
+## How it works
+
+### Discovery and installation
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest list
+solid: @tanstack/intent@latest list
+vue: @tanstack/intent@latest list
+svelte: @tanstack/intent@latest list
+angular: @tanstack/intent@latest list
+lit: @tanstack/intent@latest list
+
+<!-- ::end:tabs -->
+
+Scans the current project's installed dependencies for intent-enabled packages, including `node_modules`, workspace dependencies, and Yarn PnP projects without `node_modules`. You can narrow which packages are surfaced with `package.json#intent.skills`. See the [Trust model](./concepts/trust-model) and [Configuration](./concepts/configuration) for how the allowlist works. Global package scanning is explicit; pass `--global` to include global packages or `--global-only` to ignore local packages. When both local and global packages are scanned, local packages take precedence.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest install
+solid: @tanstack/intent@latest install
+vue: @tanstack/intent@latest install
+svelte: @tanstack/intent@latest install
+angular: @tanstack/intent@latest install
+lit: @tanstack/intent@latest install
+
+<!-- ::end:tabs -->
+
+Creates or updates lightweight `intent-skills` guidance in your config files (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`, etc.). Existing guidance is updated in place; otherwise `AGENTS.md` is the default target. Pass `--map` to opt in to explicit task-to-skill mappings.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest hooks install
+solid: @tanstack/intent@latest hooks install
+vue: @tanstack/intent@latest hooks install
+svelte: @tanstack/intent@latest hooks install
+angular: @tanstack/intent@latest hooks install
+lit: @tanstack/intent@latest hooks install
+
+<!-- ::end:tabs -->
+
+Installs session catalogs and edit gates for supported agents. Project-scoped hooks are available for Claude Code and Codex. GitHub Copilot CLI project guidance can live in `.github/copilot-instructions.md`, while blocking hooks are user-scoped. Cursor and generic `AGENTS.md` agents use guidance only. See [intent hooks](./cli/intent-hooks) for what hooks can observe.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest load @tanstack/query#fetching
+solid: @tanstack/intent@latest load @tanstack/query#fetching
+vue: @tanstack/intent@latest load @tanstack/query#fetching
+svelte: @tanstack/intent@latest load @tanstack/query#fetching
+angular: @tanstack/intent@latest load @tanstack/query#fetching
+lit: @tanstack/intent@latest load @tanstack/query#fetching
+
+<!-- ::end:tabs -->
+
+Loads the matching `SKILL.md` content for the installed package version. Pass `--path` when you need the resolved skill file path for debugging.
+
+### Maintainer authoring and review
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer setup
+solid: @tanstack/intent@latest maintainer setup
+vue: @tanstack/intent@latest maintainer setup
+svelte: @tanstack/intent@latest maintainer setup
+angular: @tanstack/intent@latest maintainer setup
+lit: @tanstack/intent@latest maintainer setup
+
+<!-- ::end:tabs -->
+
+Creates missing planning records and installs the authoring procedure in repository instructions. It explains the distribution choice and remembers selected public skills or an opt-out. Skills stay in their owning packages. See the [maintainer quick start](./getting-started/quick-start-maintainers).
+
+Use `maintainer add` to create or register an agreed skill, then author its guidance and task evidence with your coding agent. During later library work:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer status
+react: @tanstack/intent@latest maintainer sync
+react: @tanstack/intent@latest maintainer review --json
+solid: @tanstack/intent@latest maintainer status
+solid: @tanstack/intent@latest maintainer sync
+solid: @tanstack/intent@latest maintainer review --json
+vue: @tanstack/intent@latest maintainer status
+vue: @tanstack/intent@latest maintainer sync
+vue: @tanstack/intent@latest maintainer review --json
+svelte: @tanstack/intent@latest maintainer status
+svelte: @tanstack/intent@latest maintainer sync
+svelte: @tanstack/intent@latest maintainer review --json
+angular: @tanstack/intent@latest maintainer status
+angular: @tanstack/intent@latest maintainer sync
+angular: @tanstack/intent@latest maintainer review --json
+lit: @tanstack/intent@latest maintainer status
+lit: @tanstack/intent@latest maintainer sync
+lit: @tanstack/intent@latest maintainer review --json
+
+<!-- ::end:tabs -->
+
+The commands identify work, align generated metadata, and prepare source-review evidence. Record justified outcomes with `maintainer review --record <report.json>` and finish with `maintainer check`. Content changes reopen review. The [maintainer command reference](./cli/intent-maintainer) covers the full workflow, package ownership, and consumer installer choices. Full-library research remains available through the meta-skills when requested.
+
+### Staleness tracking
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest stale
+solid: @tanstack/intent@latest stale
+vue: @tanstack/intent@latest stale
+svelte: @tanstack/intent@latest stale
+angular: @tanstack/intent@latest stale
+lit: @tanstack/intent@latest stale
+
+<!-- ::end:tabs -->
+
+Reports version drift and source, artifact, or package coverage signals that may require skill review. Flagged text reports and generated review PR prompts route your agent to the same focused authoring procedure. The agent checks the source evidence before deciding whether guidance needs to change.
diff --git a/docs/registry.md b/docs/registry.md
index ceb7ade3..bcfa5bd3 100644
--- a/docs/registry.md
+++ b/docs/registry.md
@@ -10,59 +10,121 @@ The registry periodically searches npm for packages with the `tanstack-intent` k
 
 ## Ship skills in 4 steps
 
-### 1. Generate skills
+### 1. Create a skill batch
 
-Tell your AI coding agent to run:
+For repository-wide maintenance, enable the maintainer workflow once:
 
-```bash
-npx @tanstack/intent@latest scaffold
-```
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
 
-This walks the agent through domain discovery, skill tree generation, and skill creation. You review at each stage. Skills land in a `skills/` directory at your package root — each as a `SKILL.md` file in its own subdirectory.
+react: @tanstack/intent@latest maintainer setup
+solid: @tanstack/intent@latest maintainer setup
+vue: @tanstack/intent@latest maintainer setup
+svelte: @tanstack/intent@latest maintainer setup
+angular: @tanstack/intent@latest maintainer setup
+lit: @tanstack/intent@latest maintainer setup
 
-### 2. Validate
+<!-- ::end:tabs -->
 
-```bash
-npx @tanstack/intent@latest validate
-```
+Register agreed skills with `maintainer add`, then ask your coding agent to author the developer tasks they cover. The installed instructions load the focused authoring procedure, maintain the shared planning record, and run source-aware review before handoff.
 
-Catches structural issues, missing frontmatter, and broken source references before you publish.
+For a one-off authoring session, tell the agent to run:
 
-### 3. Add the keyword
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
 
-Add `"tanstack-intent"` to the `keywords` array in your `package.json`:
+react: @tanstack/intent@latest meta generate-skill
+solid: @tanstack/intent@latest meta generate-skill
+vue: @tanstack/intent@latest meta generate-skill
+svelte: @tanstack/intent@latest meta generate-skill
+angular: @tanstack/intent@latest meta generate-skill
+lit: @tanstack/intent@latest meta generate-skill
 
-```json
-{
-  "keywords": ["tanstack-intent"]
-}
-```
+<!-- ::end:tabs -->
 
-This is how the registry finds your package on npm.
+Give the agent a developer task or concrete code/docs change. The focused procedure creates or updates the relevant guidance and validates it for review; full-library discovery remains available when explicitly requested. Skills use the owning package's `skills/` directory or its existing custom root. Record the [repository distribution choice](./cli/intent-maintainer#choose-repository-distribution) during setup: select public skills or use `maintainer setup --distribution none` for the package-only workflow. See the [maintainer quick start](./getting-started/quick-start-maintainers).
+
+### 2. Synchronize metadata
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer sync
+solid: @tanstack/intent@latest maintainer sync
+vue: @tanstack/intent@latest maintainer sync
+svelte: @tanstack/intent@latest maintainer sync
+angular: @tanstack/intent@latest maintainer sync
+lit: @tanstack/intent@latest maintainer sync
+
+<!-- ::end:tabs -->
+
+This adds the `tanstack-intent` keyword and registered skill directories to existing `files` allowlists. It preserves npm’s default contents when no allowlist exists. It also synchronizes selected repository exports. Review the diff and inspect the packed archive through the library’s release checks.
+
+### 3. Review and check
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer review --json
+solid: @tanstack/intent@latest maintainer review --json
+vue: @tanstack/intent@latest maintainer review --json
+svelte: @tanstack/intent@latest maintainer review --json
+angular: @tanstack/intent@latest maintainer review --json
+lit: @tanstack/intent@latest maintainer review --json
+
+<!-- ::end:tabs -->
+
+Save the report under `.intent/`, assess the pending items, and annotate completed outcomes with their reasons and actual evidence. Record the report with `intent maintainer review --record <report.json>`, then run `intent maintainer check`. This checks skill structure, registration, generated files, and pending reviews together. See the [source-review reference](./cli/intent-review) for report fields and recording.
 
 ### 4. Publish
 
-```bash
-npm publish
-```
+Publish through your library's normal release process.
 
 The registry discovers your package on its next sync cycle. Your skills, version history, and download stats appear on the registry automatically.
 
+A passing structural check alone does not establish that the consumer can complete the task. Include that task evidence in the library's release review.
+
 ## Keeping skills current
 
-Skills derived from docs drift when docs change. Two commands keep them honest:
+Use `maintainer review` and `stale` as separate checks as the library changes. `setup` optionally installs their CI workflow:
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest maintainer review
+solid: @tanstack/intent@latest maintainer review
+vue: @tanstack/intent@latest maintainer review
+svelte: @tanstack/intent@latest maintainer review
+angular: @tanstack/intent@latest maintainer review
+lit: @tanstack/intent@latest maintainer review
+
+<!-- ::end:tabs -->
+
+Uses Git changes and recorded content fingerprints to identify skills, planning records, and unmapped source areas that need semantic review. Record completed outcomes with their evidence in `.intent/review-state.json`; missing evidence remains pending.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
+
+react: @tanstack/intent@latest stale
+solid: @tanstack/intent@latest stale
+vue: @tanstack/intent@latest stale
+svelte: @tanstack/intent@latest stale
+angular: @tanstack/intent@latest stale
+lit: @tanstack/intent@latest stale
+
+<!-- ::end:tabs -->
+
+Reports conservative package and release signals: version drift, missing stored source SHAs, artifact warnings, and package coverage. It does not compare source diffs. Flagged text reports include the focused authoring command so your agent can investigate the evidence and return a reviewable update or an explained no-op.
+
+<!-- ::start:tabs variant="package-manager" mode="local-install" -->
 
-```bash
-npx @tanstack/intent@latest stale
-```
+react: @tanstack/intent@latest setup
+solid: @tanstack/intent@latest setup
+vue: @tanstack/intent@latest setup
+svelte: @tanstack/intent@latest setup
+angular: @tanstack/intent@latest setup
+lit: @tanstack/intent@latest setup
 
-Flags skills whose source docs have changed since the skill was last updated.
+<!-- ::end:tabs -->
 
-```bash
-npx @tanstack/intent@latest setup
-```
+Copies the generated CI workflow into your repository. Pull requests validate skills and check recorded source reviews when maintainer guidance or review state exists. Release and manual runs use recorded review state when available, with conservative `stale` signals as the fallback.
 
-Copies CI workflow templates into your repo so validation and staleness checks run in GitHub Actions. Catch drift before it ships.
+> [!NOTE]
+> Maintainers use `maintainer setup`, `add`, `status`, `sync`, `review`, and `check` throughout the workflow. Consumers choose their installer: Intent for installed package guidance, or the generated GitHub/plugin commands for selected repository skills. See [repository distribution](./cli/intent-maintainer#choose-repository-distribution).
 
 ## Requesting a library