diff --git a/README.md b/README.md
index e6498600..d1eed402 100644
--- a/README.md
+++ b/README.md
@@ -18,36 +18,31 @@ available. On Windows both run in **Docker**; on macOS and Linux they run
 exactly as they do in the source pack today. Everything else that was a daemon
 is gone.
 
-> **Status: the foundation is built and verified; the KBD lifecycle, adversarial review,
-> ideation-mindmap, Karpathy progress memory, plugin distribution, and the Docker services
-> are ported and real.**
+> **Current inventory: 97 distributed skills, including 40 portable UI/UX entries.**
+> The shared full/mini catalog has 41 UI/UX entries; its full-only Impeccable native engine
+> is excluded from mini. Mini ships the bounded `prometheus-impeccable-core` adaptation,
+> shared UI routing and review, TypeScript 7/Node Pro Max, and automatic project-team adoption.
 >
-> Phase `platform-foundation` is complete: `lib/platform/` (paths, CRLF-tolerant text
-> reading, atomic write with a bounded Windows rename retry, an exclusive-create lock,
-> shell-free process spawning), a `package.json` with the OpenSpec CLI pinned, and a
-> three-OS CI matrix. **88 tests pass on `windows-latest`, `ubuntu-latest` and
-> `macos-latest` across Node 22 and 24, with nothing skipped on Windows** — every Windows
-> claim about that phase is observed, not reasoned from macOS. Per-claim evidence:
-> [`evidence/windows.md`](.kbd-orchestrator/phases/platform-foundation/evidence/windows.md).
->
-> A later phase ("port the KBD process orchestrator and 49 skills to Windows-native Node")
-> closed the gap this section used to describe as not-yet-started: **53 skills** now live
-> under `skills/`, including the full 24-skill KBD family (`kbd-process-orchestrator` plus
-> 22 sub-skills, `kbd-evolve`, `kbd-goal-check`), `adversarial-review`, `ideation-mindmap`,
-> `karpathy-progress-memory`, 20 artifact-refiner skills, 5 scaffold/convert skills, and the
-> plugin/marketplace distribution generator (`lib/distribution/`, `skill-system.json`).
-> **1,000+ tests pass**, `docker/compose.yaml` runs SurrealDB + surreal-memory + liter-llm
-> as three loopback-bound, digest-pinned containers, and `scripts/services.mjs` wraps their
-> lifecycle. **Windows verification for this later batch is still owed** — it ran on macOS
-> only, the same caveat recorded for every phase before it; `platform-foundation`'s own
-> Windows claims remain the ones with real CI evidence. See the
-> [Docusaurus site](#documentation-site) for full-coverage documentation of every skill and
-> `lib/` module, and [`docs/reference/comparison-with-full-pack`](site/docs/reference/comparison-with-full-pack.md)
-> for what remains a genuine gap versus what was always a deliberate exclusion.
->
-> Still open: `deep-research` (planned as a checkpoint-only Node port; not yet a skill in
-> this checkout), the knowledge-sources registry, and Windows hardware verification of the
-> Docker services and the Phase C skill batch.
+> The KBD lifecycle, adversarial review, Karpathy progress memory and plugin distribution
+> are implemented. Verification belongs to a specific phase and environment: the historical
+> [platform-foundation Windows evidence](.kbd-orchestrator/phases/platform-foundation/evidence/windows.md)
+> does not certify later UI/team work. The [UI/team delivery record](docs/research/ui-ux-routing/DELIVERY.md)
+> records macOS and offline Linux-container integration evidence. Native Windows execution,
+> live invocation of every harness and full Electron installed-app acceptance remain unverified.
+> This documentation does not claim release certification.
+
+## UI/UX routing
+
+Use `prometheus-ui-ux` for rendered UI, styles, tokens, interaction, motion or on-screen copy.
+Read project context first; `.agents/UI_UX_PROTOCOL.md` overrides the bundled protocol.
+The router chooses a focused Pro Max query, one craft skill and relevant platform guidance.
+New work may use taste based on the **actual model**; refinement and review exclude taste.
+Completed UI phases use independent `prometheus-ui-review` with real evidence. Upstream
+`interface-review`, `break`, `variant` and `explain-interface` remain user-only.
+
+Start with the [UI/UX routing how-to](docs/ui-ux-routing.md), including project installation,
+request examples, platform limits, offline use and troubleshooting. Helpers ship as Node ESM;
+no Python, engine download, extra service or runtime dependency installation is needed.
 
 ## Agent teams
 
@@ -59,8 +54,14 @@ producing an editable manifest.
 
 The shared full/mini runtime stages native artifacts for **UAR, Codex, Claude Code, GitHub
 Copilot CLI, Kimi Code, MiniMax CLI (`mcode`), OpenCode, and DeepSeek Harness**. **BossFang**
-is a separate registration/export target. Export does not install agents, register services,
-or launch teams. Native options retain source/version provenance and explicit limitations.
+is a separate registration/export target. Export stages proposals. Normal project-team creation continues with `install-project`, which
+installs discovery instructions and missing native project definitions. Neither operation launches
+agents or registers services. Native options retain source/version provenance and explicit limitations.
+
+For all code tasks, preserve the explicit active team; adopt a sole existing team, and ask when
+several remain ambiguous. Use relevant roles with their existing ownership and native permissions.
+When delegation is unavailable, use role instructions sequentially and disclose that limit. Zed
+instruction discovery is supported; its parallel-thread UI is not a delegation API.
 
 Task state uses revision checks and local atomic writes; cross-harness handoffs transfer
 ownership only after acceptance. Model selection uses declared tiers and explicit price
@@ -85,7 +86,8 @@ conversion, plugin distribution, Docker services, and OpenSpec integration — i
 
 ```bash
 cd site
-npm install
+npm ci
+npm run generate:catalog
 npm start
 ```
 
@@ -100,7 +102,7 @@ that touches `site/`, `docs/`, or any `skills/**/SKILL.md` — the same build 
 
 | # | Constraint | What it means in practice |
 |---|---|---|
-| C1 | **Windows without WSL for anything the pack runs** | Hooks, scripts, and the installer run from `cmd.exe` / PowerShell on a stock Windows 10/11 box. Git Bash may be present but is never required. Docker's own backend is the one exception — see the note below the table. **Verified for everything built so far** on `windows-latest`, no Git Bash, no WSL. |
+| C1 | **Windows without WSL for anything the pack runs** | Hooks, scripts, and the installer run from `cmd.exe` / PowerShell on a stock Windows 10/11 box. Git Bash may be present but is never required. Docker's own backend is the one exception — see the note below the table. Historical Windows evidence covers `platform-foundation`; later UI/team native Windows acceptance remains open. |
 | C2 | **Node.js LTS is the only script runtime** | Every hook, state script, and installer is a `.mjs` file run as `node <script>`. Node ≥ 22 LTS required, 24 LTS recommended. |
 | C3 | **No shell-script hooks** | No `.sh`. A `.ps1` is allowed only alongside an equivalent for the other platforms, and only when Node genuinely cannot do the job. The goal is zero of either. |
 | C4 | **No Python** | Not as a runtime, not as a build step, not in rendered templates. |
@@ -121,7 +123,7 @@ same backend requirement, so they do not change this.
 
 ---
 
-## 2. What `openspec init` created
+## 2. What `openspec init` created (historical setup)
 
 Run with OpenSpec CLI **1.10.0**:
 
@@ -145,7 +147,7 @@ runtime. Start the first change with `/opsx:propose "<idea>"`.
 
 ---
 
-## 3. Why this is a port and not a repackage
+## 3. Why this is a port and not a repackage (original analysis)
 
 The source pack (v1.10.0) states its own Windows posture in `skill-system.json`:
 
@@ -186,8 +188,8 @@ that is not Node.
 > "**high**") are now **done** — see [§4](#documentation-site)'s docs site, specifically
 > [`docs/kbd/overview`](site/docs/kbd/overview.md), [`docs/review/adversarial-review`](site/docs/review/adversarial-review.md),
 > and [`docs/reference/comparison-with-full-pack`](site/docs/reference/comparison-with-full-pack.md),
-> for the current, verified state of each item. The actual on-disk layout also diverged from §5.1's
-> plan below in one significant way: **skills are flat** (`skills/<name>/`, 53 directories), not
+> for current capability descriptions and their evidence limits. The actual on-disk layout also diverged from §5.1's
+> plan below in one significant way: **skills are flat** (`skills/<name>/`, now 97 distributed skill directories), not
 > grouped into `skills/kbd/`, `skills/pmpo/`, `skills/karpathy/`, `skills/rust/` subdirectories as
 > planned — and no `pmpo-*` family, `templates/`, or `tests/` top-level directory exists in this
 > checkout. Treat this section as intent-at-the-time, not current fact; treat §4.1 in the docs site
@@ -677,9 +679,10 @@ only, prefer a small dependency set for stdio MCP servers (`rmcp` +
 
 ---
 
-## 8. Roadmap as OpenSpec changes
+## 8. Roadmap as OpenSpec changes (historical plan)
 
-Each line is one `/opsx:propose`. Order matters — later changes build on
+This original roadmap is retained as intent at the time, not a current completion ledger.
+Use `openspec list` and phase evidence for current status. Each line was one `/opsx:propose`. Order matters — later changes build on
 `lib/platform`.
 
 1. `platform-foundation` — `lib/platform/` (paths, atomic write, lock, spawn with `.cmd` resolution), `node:test` harness, 3-OS CI, `.gitattributes`.
@@ -704,7 +707,7 @@ Each line is one `/opsx:propose`. Order matters — later changes build on
 
 ---
 
-## 9. Open questions and unverified claims
+## 9. Open questions and unverified claims (historical analysis)
 
 - **Hook cold-start on Windows.** Whether a Node process fits the source's 1 s hook budgets on typical Windows hardware is untested. If it does not, raise the budgets before reaching for a compiled dispatcher.
 - **Neither container stack has been run on Windows.** The Compose design in §5.6 is derived from reading the source pack's Dockerfiles and Compose files on macOS. Image build time, VM memory during the build, and first-start model download for local embeddings are all unmeasured.
@@ -722,4 +725,4 @@ Node's atomic-write, locking, CRLF handling and shell-free CLI spawning work on
 repository survives a `core.autocrlf=true` checkout; and that Node 22 and 24 both work. Node 26 —
 what this machine runs — is still untested and unclaimed.
 - **Harness hook support on Windows.** Exec-form hooks with `${CLAUDE_PLUGIN_ROOT}` are taken from the source pack's Claude Code configuration; equivalent behaviour in Codex, Cursor, and OpenCode on Windows needs checking per harness.
-- **`ideation-mindmap`** is deferred, not rejected — decide once the core loop works.
+- **`ideation-mindmap`** was deferred in the original analysis and has since been ported; see the current documentation site.
diff --git a/docs/agent-teams.md b/docs/agent-teams.md
index 3f06c8da..fa76f762 100644
--- a/docs/agent-teams.md
+++ b/docs/agent-teams.md
@@ -22,7 +22,7 @@ not claims that those skills are installed or bundled in mini.
 
 | Skill | Use it for |
 | --- | --- |
-| `agent-team-creator` | Guided selection or an expert manifest, validation, and native artifact staging |
+| `agent-team-creator` | Guided selection or an expert manifest, validation, native artifact staging, and project installation |
 | `agent-team-manage` | Assignment, status, dependencies, cancellation, reassignment, and KBD-linked completion |
 | `agent-team-models` | Model discovery, catalog interpretation, and explicit policy selection |
 | `agent-team-handoff` | Context capture and acceptance when work moves to another owner or harness |
@@ -60,13 +60,15 @@ Save `guide.json`:
 node skills/agent-team-creator/scripts/cli.mjs guide --input guide.json
 ```
 
-The response contains a proposed `team`, role reasons, and single-agent alternatives. Missing
-inputs return questions rather than creating state. `review` is a JSON boolean; `complexity`
+The response includes role reasons and single-agent alternatives. Missing inputs return
+questions rather than creating state. Once scope is known, it returns `proposedRoles` and
+ownership questions; only `ready: true` returns a `team`. `review` is a JSON boolean; `complexity`
 is `simple` or `complex`, and `budget` is `economy`, `balanced`, or `quality`. The budget answer
 sets a declared tier preference, not a dollar budget or a verified model ranking.
 
-Inspect the returned roles. Remove unnecessary specialists, choose available skills, and set
-`owns` paths before parallel work. Empty ownership is not permission to edit the whole project.
+Inspect `proposedRoles`. Supply `ownership` for every proposed role, for example
+`{"implementer": ["docs/**"], "reviewer": ["reviews/docs.md"]}`, then rerun `guide`.
+Remove unnecessary specialists and choose available skills before accepting the ready team. Empty ownership is not permission to edit the whole project.
 Expert users can write a manifest directly and skip `guide`.
 
 ## Initialize and stage an export
@@ -122,7 +124,78 @@ Read the returned diagnostics, instructions, source/version verification, and ex
 Export stages proposals; it does not install native files, register service agents, or execute
 a team. Existing files and path collisions are refused. Inspect the artifacts and native
 permissions, validate them with the intended installed harness, then deliberately install or
-register the chosen deployment form. Source-verified export is not live native acceptance.
+register the chosen deployment form. For normal project creation, continue below with
+`install-project`. Source-verified export is not live native acceptance.
+
+## Install the project team
+
+Normal project-team creation continues after export inspection with `install-project`.
+Save `install-request.json` with the accepted manifest as `team` (the same manifest used
+in `init.json`) and the authorized project path:
+
+```json
+{
+  "project": "../My Project",
+  "team": {
+    "schemaVersion": 1,
+    "id": "docs-team",
+    "outcome": "Clarify the setup guide and verify its examples",
+    "scope": "project",
+    "harness": "codex",
+    "roles": [{
+      "id": "implementer",
+      "description": "Owns the documentation change",
+      "prompt": "Update the assigned guide and report evidence and remaining work.",
+      "skills": [], "owns": ["docs/**"],
+      "inputs": ["Requested setup clarification"],
+      "outputs": ["Updated guide", "Verification notes"],
+      "dependsOn": []
+    }],
+    "modelPolicy": {"tier": "medium"}
+  }
+}
+```
+
+```text
+node skills/agent-team-creator/scripts/cli.mjs install-project --input install-request.json --dry-run
+node skills/agent-team-creator/scripts/cli.mjs install-project --input install-request.json
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --check
+```
+
+The installer writes `.agent-team/docs-team/team.json`, `.agent-team/project-routing.json`,
+managed discovery instructions and missing native project definitions. The earlier
+`.agent-teams/docs-team.json` file is the separate mutable task ledger; installation does
+not turn its filename into a discovery manifest. `export` remains proposal-only.
+
+For an existing team, omit the JSON manifest and use `--project`. An explicit recorded
+selection wins; a sole `.agent-team/<id>/team.json` is adopted automatically. If several
+remain ambiguous, choose with `--team <id>`. A stale selection raises an error. Intentional
+replacement of a differing manifest requires `updateTeam: true` in the request.
+
+For **all code tasks**, read the active record and real manifest, then use relevant existing
+roles. Preserve IDs, ownership, model policy, native permissions and concurrency. Existing
+native files are kept byte-for-byte; differences are reported for a deliberate merge. The
+installer creates definitions and instructions, not running agents or new permission grants.
+Where native delegation is unavailable, use role instructions sequentially and disclose that
+limitation. Independent review requires a separate context after the production phase.
+
+UI roles conditionally bind `prometheus-ui-ux`; UI reviewers bind `prometheus-ui-review`.
+Backend-only work does not load UI guidance. Project `.agents/UI_UX_PROTOCOL.md` wins over
+the bundled protocol; refinement/review exclude taste. User-only `interface-review`,
+`break`, `variant` and `explain-interface` are not automatically preloaded or read to
+bypass their invocation restriction. Explicit conflicting native preload overrides retain
+diagnostics for resolution before invocation.
+
+Zed's first effective existing instruction file also receives the discovery pointer, in
+addition to `AGENTS.md` and `CLAUDE.md`. Inspect `instructionFiles` in the active record.
+External ACP agents retain their native configuration; parallel threads are not a delegation
+API. Local recovery records preserve prior instruction bytes, including CRLF and supported
+in-project links. The installer never creates links. Creator `--check` exits 2 for drift
+and 1 for errors; dry-run/check write nothing.
+
+See [UI/UX routing](ui-ux-routing.md) for installation, routing requests, Zed precedence,
+platform limits and troubleshooting, and the [project installation contract](../skills/agent-team-creator/references/project-installation.md)
+for all request fields and recovery behavior.
 
 ## Eight execution harnesses and a separate BossFang target
 
@@ -233,5 +306,3 @@ without either. Live model discovery and remote publication need their configure
 The runtime is shipped as portable Node modules, but native harness availability, installed
 configuration acceptance, service authentication, and Windows execution require separate
 live evidence. No new Windows or cross-harness live certification is claimed by this guide.
-
-Guided creation resolves ownership before producing a ready team. For example, after reviewing proposed roles, add `"ownership": {"implementer": ["src/checkout/**"], "reviewer": ["reviews/checkout.md"]}` for a two-role checkout task. Use paths actually appropriate to the project and include every proposed role. Missing ownership returns `ready: false`, `proposedRoles`, and focused questions without a `team` value; it does not grant access to the whole repository.
diff --git a/docs/ui-ux-routing.md b/docs/ui-ux-routing.md
new file mode 100644
index 00000000..fe606294
--- /dev/null
+++ b/docs/ui-ux-routing.md
@@ -0,0 +1,197 @@
+# UI/UX routing and project-team adoption
+
+Mini distributes **97 skills**, including **40 portable UI/UX entries** from the shared
+41-entry full/mini catalog. The extra full-only entry is Impeccable's native engine.
+Catalog inclusion records provenance and suitability; it is not a claim that a skill is
+universally best. See the [catalog lock](../skills/prometheus-ui-ux/references/catalog.lock.json).
+
+## Install project routing
+
+Run these commands from the mini checkout with Node.js 22 or newer. Replace the quoted
+project path with an existing authorized project. On a machine with the full pack installed,
+use the full pack's bootstrap; mini belongs only in The Boss's internal data directory on
+that machine. These project commands do not waive the [install-scope rule](../site/docs/getting-started/installation.md#the-install-scope-rule).
+
+For layered context plus UI routing and adoption of existing teams:
+
+```text
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --dry-run
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project"
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --check
+```
+
+Bootstrap merges managed context, copies portable UI skills into project
+`.agents/skills` and `.claude/skills`, preserves an existing `.agents/UI_UX_PROTOCOL.md`,
+and adopts a resolvable existing team. For UI routing alone, use:
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project" --dry-run
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project"
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project" --check
+```
+
+The UI-only installer does not create the active-team record or native agents. Adopt an
+existing team separately:
+
+```text
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --dry-run
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project"
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --check
+```
+
+An explicit selection in `.agent-team/project-routing.json` wins; otherwise a sole
+`.agent-team/<id>/team.json` is adopted. When several teams remain, choose deliberately
+with `--team <id>`; stale selection is an error. For a new team, follow the
+[creation and installation guide](agent-teams.md#install-the-project-team).
+Proposal-only `export` does not complete project adoption.
+
+Managed instruction blocks preserve unrelated prose, CRLF, existing in-project linked
+entrypoints and local recovery information. Creator preserves existing native file bytes,
+including models, permissions and concurrency; it reports differences for a deliberate merge.
+A routing pointer grants no native permission and does not start agents. Read the active record
+and real manifest for every code task, select relevant roles, and preserve their ownership.
+Backend work still uses its team without activating UI skills.
+
+Creator also updates Zed's first effective existing instruction file, from `.rules`,
+`.cursorrules`, `.windsurfrules`, `.clinerules`, `.github/copilot-instructions.md`,
+`AGENT.md`, `AGENTS.md`, `CLAUDE.md`, then `GEMINI.md`; otherwise it uses `AGENTS.md`.
+Inspect `instructionFiles` in the record. External ACP agents retain their own native
+configuration. Zed's parallel-thread UI is not a delegation API. If the harness cannot delegate,
+use role instructions sequentially and disclose the limitation; builder review is not independent.
+
+## Route the actual UI task
+
+Read `PRODUCT.md`, `DESIGN.md`, `.impeccable.md`, the nearest surface brief, components and
+tokens before changing direction. Project `.agents/UI_UX_PROTOCOL.md` overrides the
+[bundled protocol](../skills/prometheus-ui-ux/references/UI_UX_PROTOCOL.md). Generated
+recommendations do not replace project authority.
+
+Save `ui-request.json` with paths relative to its `project` (the project itself resolves
+against the command's working directory):
+
+```json
+{
+  "project": "../My Project",
+  "ui": true,
+  "affected": ["apps/web/src/Settings.tsx"],
+  "operation": "refine",
+  "surface": "app",
+  "focus": "accessibility"
+}
+```
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs route --input ui-request.json
+```
+
+Use the returned context paths first and load the selected skill IDs in order. The helper
+returns a routing decision; it does not execute the selected skills. Set `ui: false` for
+backend-only requests. Missing skills are explicit gaps, never an automatic download.
+In an installed payload, resolve the actual skill directory instead of assuming this checkout.
+Copy the complete payload and required catalog siblings, not just a CLI entry file.
+
+| Operation | Direction and review behavior |
+| --- | --- |
+| `new` | Establish direction when needed. Actual GPT model IDs select `gpt-taste`; missing/non-GPT model uses `design-taste-frontend`. Set `model` to the model actually running, never the harness name. |
+| `redesign` | Explicitly authorized direction change uses `redesign-existing-projects`. |
+| `refine` | Preserve incumbent identity; no taste implementation or overlay; focused retrieval only. |
+| `review` | Objective evidence and project scope through `prometheus-ui-review`; no taste or redesign. Reviewer/verifier/auditor roles force review routing. |
+
+At most one taste implementation and one explicitly selected overlay apply to new/redesign
+work. The supported overlays are `high-end-visual-design`, `minimalist-ui` and
+`industrial-brutalist-ui`; refinement/review ignore overlays. Experimental/v1 identities remain
+separate catalog entries. One craft skill follows the task: layout, typography, colors, writing,
+accessibility, motion, or broad interface work. Relevant platform skills follow the nearest
+application manifests; a monorepo root is not evidence of every application's stack.
+
+Surface defaults are Persuade for marketing/landing/pricing, Operate for apps/tools, Read for
+docs/articles, and Experience for portfolios/showcases. Existing tokens and explicit design
+decisions override defaults. See the [request reference](../skills/prometheus-ui-ux/references/runtime-api.md)
+for exact modes, fields, focus aliases and dial ranges.
+
+## Use Pro Max selectively
+
+The shipped TypeScript 7 implementation runs directly as Node ESM with pinned data and assets.
+No Python, repository-root runtime dependencies, online catalog refresh or service is required.
+For an existing React app, for example:
+
+```text
+node skills/ui-ux-pro-max/scripts/search.mjs "keyboard navigation React 19" --stack react --json
+node skills/ui-ux-pro-max/scripts/search.mjs "accessible forms" --domain ux --json
+```
+
+Use the actual project framework version in the query. To establish a new design direction:
+
+```text
+node skills/ui-ux-pro-max/scripts/search.mjs "clinic appointment booking" --design-system --project-name "Clinic" --format markdown
+```
+
+Only persist when requested: `--persist --output-dir "../My Project" --page booking` writes
+`design-system/<project-slug>/MASTER.md` and page overrides. Existing files are preserved unless
+replacement is authorized and `--force` is supplied; forced writes retain recovery copies.
+`DESIGN.md` is never overwritten. Stitch output belongs in `DESIGN.stitch.md`.
+A zero-result query is an absence of advice, not a recommendation. Pinned catalog versions
+never authorize application upgrades. See [Pro Max port scope](../skills/ui-ux-pro-max/PORT.md).
+
+## Review once the production phase is complete
+
+Finish the authorized implementation before running the completed-phase evidence contract.
+Save a review request using the same fields, with `operation: "review"`, then run:
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs phase-boundary --input ui-review-request.json
+```
+
+This returns `status: "evidence-required"`, `executed: false`, a checklist and an exec-form
+Node descriptor. It accepts no evidence fields, captures no screenshots, launches no browser
+and cannot certify PASS. Exit 0 only means the request was processed. Use available platform
+tools to collect applicable device/theme states, keyboard/focus and reduced-motion evidence;
+obtain independent read-only review, then one batched correction and confirmation cycle.
+Record evidence paths, reviewer identity, unavailable checks and unresolved findings.
+Outstanding blockers remain blocking; unavailable independent review remains unverified.
+
+Automatic review uses `prometheus-ui-review` and auto-invocable craft guidance.
+`interface-review`, `break`, `variant` and `explain-interface` remain user-only.
+Do not read their files to bypass `disable-model-invocation`. No per-edit hook or native
+browser/detector engine is implied by this mini adaptation.
+
+## Platform and acceptance matrix
+
+| Surface or host | What mini supplies | What remains separate |
+| --- | --- | --- |
+| Web/React | Context, craft, relevant Vercel/React guidance and Pro Max stack data | Project runtime, browser captures and acceptance |
+| Expo/React Native | Selected native/UI/design/router/motion guidance | Match declared Expo SDK and installed platform prerequisites |
+| Flutter | Responsive layout, layout repair, routing and localization guidance | Flutter toolchain and real device/emulator execution |
+| SwiftUI | SwiftUI guidance and platform units | Apple toolchain, simulator/device captures and profiling |
+| Android | Adaptive Compose and edge-to-edge guidance | Declared Gradle/SDK prerequisites and native execution |
+| Tauri/Electron | Shared UI routing; reuse project-specific platform workflow | Desktop packaging and native app acceptance; no invented specialist endorsement |
+| Other stacks | Matching Pro Max data and current official documentation | Project-specific implementation and toolchain evidence |
+| macOS / Linux | Prior macOS integration and offline Linux Node 22 container evidence | Container evidence is not all Linux desktop/toolchain certification |
+| Native Windows | Node-only shipped helpers and portable assets | Native Windows UI/team execution remains unverified |
+| Full Impeccable engine | Excluded; bounded `prometheus-impeccable-core` context/workflow adaptation | Native detector, browser engine and engine parity are not shipped |
+| Native harnesses / The Boss | Definitions, routing records and packaged-helper evidence | Live invocation of every harness and full Electron installed-app acceptance remain open |
+
+Local installation/routing, bundled Pro Max retrieval, team state and exports work without
+surreal-memory or liter-llm. Their optional discovery/publication operations need configured
+services. No additional daemon or port is added. Offline helper evidence does not certify
+browser availability, platform SDKs or native harness invocation.
+
+The [delivery record](research/ui-ux-routing/DELIVERY.md) links the prior macOS/Linux and
+packaged-helper receipts and names remaining acceptance gaps. Historical platform CI and
+old test totals do not certify this feature or a release.
+
+## Troubleshooting
+
+| Symptom | Action |
+| --- | --- |
+| Ambiguous teams | Inspect real manifests, choose an existing ID with creator `--team <id>`, then rerun bootstrap. Do not choose arbitrarily. |
+| Stale active selection | Reconcile the routing record and existing manifest; use an intentional explicit selection. |
+| Corrupt managed markers or escaping paths | Inspect the named file and recovery record, restore a valid pair/path, then repeat dry-run. Do not replace the whole instruction file. |
+| Existing native definition differs | Keep its bytes and native permissions; deliberately merge after reading diagnostics. Definition presence alone does not prove invocation. |
+| UI install check reports drift | UI/bootstrap `--check` exits 1 for drift, 2 for errors; creator `--check` exits 2 for drift, 1 for errors. Inspect reported paths before applying. |
+| A helper/skill is missing | Resolve the installed directory and complete payload. Report the missing dependency; do not fetch or install implicitly. |
+| Full pack detected on the machine | Keep mini inside The Boss's internal data directory; use the full pack for native installation. Never delete or shadow existing full-pack skills. |
+| No independent reviewer/browser/device | Record the unavailable acceptance step. Sequential role use does not substitute for independent review or captures. |
+
+See [agent teams](agent-teams.md) and the [project installation contract](../skills/agent-team-creator/references/project-installation.md)
+for native artifacts, recovery and model/permission preservation.
diff --git a/openspec/changes/ui-ux-documentation-refresh/.openspec.yaml b/openspec/changes/ui-ux-documentation-refresh/.openspec.yaml
new file mode 100644
index 00000000..baf10909
--- /dev/null
+++ b/openspec/changes/ui-ux-documentation-refresh/.openspec.yaml
@@ -0,0 +1,3 @@
+schema: spec-driven
+created: 2026-09-26
+skip_specs: true
diff --git a/openspec/changes/ui-ux-documentation-refresh/design.md b/openspec/changes/ui-ux-documentation-refresh/design.md
new file mode 100644
index 00000000..d3be8b51
--- /dev/null
+++ b/openspec/changes/ui-ux-documentation-refresh/design.md
@@ -0,0 +1,29 @@
+## Context
+
+See proposal.md. The implementation PRs are merged: full pack #102, mini #3 and The Boss #4. Each documentation branch starts at current main in the existing isolated checkout. Full and mini own Docusaurus sources; The Boss owns Markdown reference/contributor docs and a generated index.
+
+## Goals / Non-Goals
+
+**Goals:** Readers can discover the new workflow from each README, follow source-accurate instructions and distinguish bundled functionality from deferred ports and execution gaps. The Boss uses its existing official logo and name.
+
+**Non-Goals:** No runtime or skill behavior changes, dependency or submodule upgrades, new website platform, redeployment, blanket upstream/API renaming, or renewed platform certification.
+
+## Decisions
+
+- One production documentation owner per repository, with disjoint paths; root owns this plan, final validation, commits and PR publication. This follows the repository team policy and preserves independent authoring without shared-file edits.
+- Hand-author narrative at existing documentation sources and run the existing index/catalog generators. Do not edit generated copies directly.
+- Treat runtime source and pinned catalog as factual authority. Describe 41 full UI catalog entries / 40 portable entries separately from total distributed skill counts. Avoid global claims based on older foundation tests.
+- Keep project design authority, role permissions and user-only skill restrictions explicit. The phase-boundary helper reports an evidence contract; it does not perform captures or independently certify review.
+- The Boss logo must be an inspected, tracked product asset, referenced locally. Replace upstream product marketing and links with verified The Boss destinations; retain legal attribution and existing technical identifiers.
+- Finish every production documentation edit before local site builds and documentation checks. Validate through the actual documentation production pipeline, then do one independent whole-change review and bounded corrections if needed. Do not poll or cite hosted test workflows.
+
+## Risks / Trade-offs
+
+- Generated catalog pages can expose pre-existing MDX or link defects → use existing generators and fix only defects that block the requested documentation output; disclose unrelated limitations.
+- Docs may imply release availability → say merged source/build integration unless published binary evidence specifically establishes availability.
+- Upstream branding appears in API names and legal notices → limit renaming to product-facing prose and preserve provenance.
+- Separate repositories drift → use the same workflow/compatibility distinctions and cross-link the companion guides and PRs.
+
+## Migration Plan
+
+Create one new documentation PR per repository against main after local validation. No deployment is performed. Each documentation commit can be reverted independently.
diff --git a/openspec/changes/ui-ux-documentation-refresh/proposal.md b/openspec/changes/ui-ux-documentation-refresh/proposal.md
new file mode 100644
index 00000000..44ff6fdb
--- /dev/null
+++ b/openspec/changes/ui-ux-documentation-refresh/proposal.md
@@ -0,0 +1,24 @@
+## Why
+
+The UI/UX routing and team-adoption implementation is merged across the full pack, mini pack and The Boss, but entrypoint documentation and documentation sites do not yet explain the shipped workflows. The Boss README still presents upstream Cherry Studio branding instead of its existing official identity.
+
+## What Changes
+
+- Refresh each repository README and its relevant guides/navigation/generated documentation to describe the merged implementation accurately.
+- Document routing, platform selection, safe project installation, team defaults, full/mini portability, packaged helpers and remaining acceptance gaps.
+- Use The Boss's real checked-in logo and product branding in its README; preserve upstream attribution, licensing and technical identifiers.
+- Validate locally after all documentation edits, then create one documentation-only PR per repository.
+
+## Capabilities
+
+### New Capabilities
+
+None. This documentation-only change uses skip_specs: true.
+
+### Modified Capabilities
+
+None. Runtime behavior, dependency pins, installed product releases and platform certification are unchanged.
+
+## Impact
+
+README.md, docs and Docusaurus content/navigation in the full and mini packs; README.md, documentation source metadata and generated docs index in The Boss. Existing documentation generators remain authoritative. No new runtime, service or public API.
diff --git a/openspec/changes/ui-ux-documentation-refresh/tasks.md b/openspec/changes/ui-ux-documentation-refresh/tasks.md
new file mode 100644
index 00000000..091e81a3
--- /dev/null
+++ b/openspec/changes/ui-ux-documentation-refresh/tasks.md
@@ -0,0 +1,10 @@
+## 1. Documentation production
+
+- [x] 1.1 Refresh full-pack README, guides and Docusaurus navigation/catalog sources; verify rendered output at the final documentation gate.
+- [x] 1.2 Refresh mini README, guides and Docusaurus navigation/catalog sources; verify rendered output and portable-command accuracy at the final documentation gate.
+- [x] 1.3 Refresh The Boss README using the inspected official logo, correct product branding, update guides and regenerate its documentation index; verify local asset/link rendering and docs checks at the final gate.
+
+## 2. Completed documentation boundary
+
+- [x] 2.1 Run local production documentation builds/checks and independent review after all edits; record results and fix blocking documentation defects in one batch.
+- [x] 2.2 Commit and push only scoped documentation changes and create three linked, non-draft documentation PRs; verify their URLs, bases and changed-file scope without using hosted test workflows as evidence.
diff --git a/openspec/changes/ui-ux-documentation-refresh/verification.md b/openspec/changes/ui-ux-documentation-refresh/verification.md
new file mode 100644
index 00000000..d3d6fb60
--- /dev/null
+++ b/openspec/changes/ui-ux-documentation-refresh/verification.md
@@ -0,0 +1,26 @@
+# Documentation boundary evidence
+
+Date: 2026-09-26. Documentation production in all three repositories completed before this local gate.
+
+## Passed
+
+- Mini: `npm run build:deploy` in `site/` generated the 97-skill catalog and built Docusaurus successfully. New UI/UX guide rendered from the built site.
+- Full: `npm run docs:sync:check` and `npm --prefix site run build` passed, including public-doc safety, API/examples/contracts prebuild checks. Generated catalog contains 194 source manifests; packaged inventory remains 215. New UI/UX guide and navigation rendered.
+- The Boss: `pnpm docs:index`, `pnpm docs:check-structure`, `pnpm docs:check-frontmatter` and `pnpm docs:check-index` passed. The stale release-guide source reference was corrected to IntegrationPage.tsx after the frontmatter gate identified it.
+- The Boss README rendered through the installed Markdown renderer. Its tracked build/logo.png loaded at natural width 1024; header, product links and upstream attribution were inspected.
+- `openspec validate ui-ux-documentation-refresh --strict` passed.
+- Fresh-context independent source review returned no findings. The REST gateway could not choose a distinct configured reviewer, so the harness-native fallback was used; no cross-model independence is claimed.
+
+## Existing gate limitation
+
+The Boss aggregate `pnpm docs:check` stops at its link checker: three relative links in the unchanged vendored Vercel AGENTS.md resolve outside its rules directory, and the checker interprets a Swift inline-code example as a link. These are outside the documentation diff. No validation code was weakened and no pinned skill payload was edited to suppress them. Remaining documentation checks were run explicitly as listed above; aggregate success is not claimed.
+
+## Scope and remaining acceptance
+
+No hosted test workflow was used. No product runtime, dependency, native configuration, submodule or distribution payload changed. Native Windows, every-harness invocation and installed Electron acceptance remain the implementation's stated gaps. This documentation boundary does not certify those platforms or a release.
+
+Three non-draft documentation PRs target main; URLs, bases, changed-file scope and absence of merge conflicts were verified through GitHub source metadata. No hosted test statuses were inspected. No deployment or merge was performed.
+
+[Full pack](https://github.com/Prometheus-AGS/prometheus-skill-system/pull/103), [mini](https://github.com/Prometheus-AGS/prometheus-skills-mini/pull/4), [The Boss](https://github.com/Prometheus-AGS/the-boss/pull/5).
+
+The normalized independent review had zero critical, warning or suggestion findings. The existing anti-theater screen returned PASS (score 0, strictness strict).
diff --git a/site/docs/agent-teams/overview.md b/site/docs/agent-teams/overview.md
index c8549adc..b35996f4 100644
--- a/site/docs/agent-teams/overview.md
+++ b/site/docs/agent-teams/overview.md
@@ -27,7 +27,7 @@ claims. Assign disjoint write ownership before parallel edits.
 
 | Skill | Responsibility |
 | --- | --- |
-| `agent-team-creator` | Guided or expert manifest creation, validation, and native export staging |
+| `agent-team-creator` | Guided or expert manifest creation, validation, native export staging and project installation |
 | `agent-team-manage` | Task assignment, dependencies, status, cancellation, and reassignment |
 | `agent-team-models` | Model discovery and explicit tier, capability, and cost policy |
 | `agent-team-handoff` | Fresh-context packets and explicit destination acceptance |
@@ -59,8 +59,9 @@ Save this as `guide.json` in the mini checkout:
 node skills/agent-team-creator/scripts/cli.mjs guide --input guide.json
 ```
 
-Inspect the proposed `team`, reasons, and alternatives. Edit roles and file ownership, confirm
-available skills, then place the team in an `init` request. Expert users may write the manifest
+Inspect `proposedRoles`, reasons and alternatives. Supply an `ownership` map for every
+proposed role and rerun `guide`; only `ready: true` returns `team`. Confirm available skills,
+then place that team in an `init` request. Expert users may write the manifest
 directly. Commands take JSON request files, so no shell-specific pipelines are needed.
 
 The [repository guide](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/docs/agent-teams.md)
@@ -68,6 +69,76 @@ includes complete initialization and export examples. Export creates a staging d
 receipts; it does not install agents, register services, or execute a team. Read the diagnostics,
 review native permissions, and validate with the intended installed harness before deployment.
 
+## Install the project team
+
+Normal project-team creation continues after export inspection with `install-project`.
+Save `install-request.json` with the accepted manifest as `team` (the same manifest used
+in `init.json`) and the authorized project path:
+
+```json
+{
+  "project": "../My Project",
+  "team": {
+    "schemaVersion": 1,
+    "id": "docs-team",
+    "outcome": "Clarify the setup guide and verify its examples",
+    "scope": "project",
+    "harness": "codex",
+    "roles": [{
+      "id": "implementer",
+      "description": "Owns the documentation change",
+      "prompt": "Update the assigned guide and report evidence and remaining work.",
+      "skills": [], "owns": ["docs/**"],
+      "inputs": ["Requested setup clarification"],
+      "outputs": ["Updated guide", "Verification notes"],
+      "dependsOn": []
+    }],
+    "modelPolicy": {"tier": "medium"}
+  }
+}
+```
+
+```text
+node skills/agent-team-creator/scripts/cli.mjs install-project --input install-request.json --dry-run
+node skills/agent-team-creator/scripts/cli.mjs install-project --input install-request.json
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --check
+```
+
+The installer writes `.agent-team/docs-team/team.json`, `.agent-team/project-routing.json`,
+managed discovery instructions and missing native project definitions. The earlier
+`.agent-teams/docs-team.json` file is the separate mutable task ledger; installation does
+not turn its filename into a discovery manifest. `export` remains proposal-only.
+
+For an existing team, omit the JSON manifest and use `--project`. An explicit recorded
+selection wins; a sole `.agent-team/<id>/team.json` is adopted automatically. If several
+remain ambiguous, choose with `--team <id>`. A stale selection raises an error. Intentional
+replacement of a differing manifest requires `updateTeam: true` in the request.
+
+For **all code tasks**, read the active record and real manifest, then use relevant existing
+roles. Preserve IDs, ownership, model policy, native permissions and concurrency. Existing
+native files are kept byte-for-byte; differences are reported for a deliberate merge. The
+installer creates definitions and instructions, not running agents or new permission grants.
+Where native delegation is unavailable, use role instructions sequentially and disclose that
+limitation. Independent review requires a separate context after the production phase.
+
+UI roles conditionally bind `prometheus-ui-ux`; UI reviewers bind `prometheus-ui-review`.
+Backend-only work does not load UI guidance. Project `.agents/UI_UX_PROTOCOL.md` wins over
+the bundled protocol; refinement/review exclude taste. User-only `interface-review`,
+`break`, `variant` and `explain-interface` are not automatically preloaded or read to
+bypass their invocation restriction. Explicit conflicting native preload overrides retain
+diagnostics for resolution before invocation.
+
+Zed's first effective existing instruction file also receives the discovery pointer, in
+addition to `AGENTS.md` and `CLAUDE.md`. Inspect `instructionFiles` in the active record.
+External ACP agents retain their native configuration; parallel threads are not a delegation
+API. Local recovery records preserve prior instruction bytes, including CRLF and supported
+in-project links. The installer never creates links. Creator `--check` exits 2 for drift
+and 1 for errors; dry-run/check write nothing.
+
+See [UI/UX routing](/docs/ui-ux/overview) for installation, routing requests, Zed precedence,
+platform limits and troubleshooting, and the [project installation contract](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/agent-team-creator/references/project-installation.md)
+for all request fields and recovery behavior.
+
 ## Native targets differ
 
 | Identifier | Native form or limit |
@@ -137,7 +208,5 @@ service is added beyond mini's existing surreal-memory and liter-llm integration
 team operations work without them; remote publication and live discovery need their endpoints.
 
 Source-linked exports do not certify native CLI acceptance, service authentication, or Windows
-execution. Those require separate live evidence. The feature does not automatically install,
-launch, activate, or authorize native teams.
-
-Guided creation resolves ownership before producing a ready team. For example, after reviewing proposed roles, add `"ownership": {"implementer": ["src/checkout/**"], "reviewer": ["reviews/checkout.md"]}` for a two-role checkout task. Use paths actually appropriate to the project and include every proposed role. Missing ownership returns `ready: false`, `proposedRoles`, and focused questions without a `team` value; it does not grant access to the whole repository.
+execution. Those require separate live evidence. Project installation writes native definitions
+and discovery instructions; it does not launch, activate or authorize native execution.
diff --git a/site/docs/context/prometheus-context-bootstrap.md b/site/docs/context/prometheus-context-bootstrap.md
index 8fd9b420..cae0ad9b 100644
--- a/site/docs/context/prometheus-context-bootstrap.md
+++ b/site/docs/context/prometheus-context-bootstrap.md
@@ -19,12 +19,31 @@ executable bit required.
 The implementation module backing this skill. It is invoked via:
 
 ```bash
-node scripts/prometheus-context-bootstrap.mjs          # install/refresh
-node scripts/prometheus-context-bootstrap.mjs --check   # verify without writing
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --dry-run
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project"
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --check
 ```
 
 Per `package.json`, these are wired as `npm run context:bootstrap` and `npm run context:check`.
 
+## UI routing and existing teams
+
+Bootstrap now installs the portable UI catalog into project `.agents/skills` and
+`.claude/skills`, merges UI routing pointers and preserves a project
+`.agents/UI_UX_PROTOCOL.md` override. It also adopts resolvable existing teams through
+creator's `install-project`: an explicit selection wins, a sole team is selected, and
+ambiguous teams require an explicit choice. It does not invent a new team.
+
+Select ambiguous teams with creator `--team <id>` before rerunning bootstrap. Existing
+native files, permissions and ownership are preserved; missing definitions and discovery
+instructions are installed. No native agents are launched. All code uses relevant team roles;
+only UI work loads UI guidance. With delegation unavailable, use sequential role instructions
+and report that limit.
+
+See [UI/UX routing and adoption](/docs/ui-ux/overview) for commands, Zed instruction precedence,
+recovery, optional-services behavior and the full-pack anti-shadowing constraint. Use the full
+pack's bootstrap on full-pack machines; mini belongs in The Boss's internal data directory there.
+
 ## Relationship to this repo's own rules layer
 
 This pack's own `CLAUDE.md`/`AGENTS.md` are themselves generated by `rules/build.mjs` from
diff --git a/site/docs/distribution/plugin-marketplace.md b/site/docs/distribution/plugin-marketplace.md
index 8c746d04..26476a73 100644
--- a/site/docs/distribution/plugin-marketplace.md
+++ b/site/docs/distribution/plugin-marketplace.md
@@ -7,7 +7,7 @@ sidebar_label: Overview
 
 `lib/distribution/` and the `skill-system.json` manifest at the repo root generate installable
 plugin packages and marketplace listings for Claude Code and Codex, purely from the real `skills/`
-tree (50 directories) — copy-mode throughout, never symlink.
+tree (97 distributed skill directories) — copy-mode throughout, never symlink.
 
 ## `lib/distribution/` modules
 
@@ -46,3 +46,14 @@ the one deliberate divergence from the full pack's own generator that this repo'
 
 - [Installation](/docs/getting-started/installation) — `skill-system.json`'s full shape and the install-scope rule.
 - [Doctor](/docs/platform/doctor) — checks the home-directory skill copies distribution produces.
+
+## Project UI routing and teams
+
+Distribution makes skill payloads available. Project adoption also needs managed instructions,
+the UI protocol and an active-team record. Follow [UI/UX routing and adoption](/docs/ui-ux/overview)
+for bootstrap or separate UI/creator commands. The current inventory includes 40 portable UI
+entries from the shared 41-entry catalog. Local helpers run directly with Node 22+ and bundled
+assets; they need neither optional service. The full-pack anti-shadowing constraint still applies.
+
+Proposal-only creator `export` does not install a project team; normal project creation finishes
+with `install-project`. Writing definitions does not prove native discovery or invocation.
diff --git a/site/docs/getting-started/installation.md b/site/docs/getting-started/installation.md
index 8c33813f..bef59be7 100644
--- a/site/docs/getting-started/installation.md
+++ b/site/docs/getting-started/installation.md
@@ -43,7 +43,7 @@ node scripts/generate-skill-system-distribution.mjs           # writes dist/ and
 node scripts/generate-skill-system-distribution.mjs --check   # verifies, exits non-zero on drift
 ```
 
-This reads `skill-system.json`, scans `skills/` (50 directories), and produces:
+This reads `skill-system.json`, scans `skills/` (97 distributed skill directories), and produces:
 
 - `.claude-plugin/marketplace.json` and `.agents/plugins/marketplace.json` — one plugin listed
   (itself), per `lib/distribution/marketplace.mjs`.
@@ -96,3 +96,14 @@ find them. Because this writes under the user's home directory, it only ever wri
 roots, only for names the pack actually has, refuses any name that is not a single plain directory
 component, never deletes, and refuses outright when `lib/platform/full-pack.mjs` detects a native
 full-pack install.
+
+## Project UI routing and teams
+
+Distribution makes skill payloads available. Project adoption also needs managed instructions,
+the UI protocol and an active-team record. Follow [UI/UX routing and adoption](/docs/ui-ux/overview)
+for bootstrap or separate UI/creator commands. The current inventory includes 40 portable UI
+entries from the shared 41-entry catalog. Local helpers run directly with Node 22+ and bundled
+assets; they need neither optional service. The full-pack anti-shadowing constraint still applies.
+
+Proposal-only creator `export` does not install a project team; normal project creation finishes
+with `install-project`. Writing definitions does not prove native discovery or invocation.
diff --git a/site/docs/intro.md b/site/docs/intro.md
index 77d00fce..2a981670 100644
--- a/site/docs/intro.md
+++ b/site/docs/intro.md
@@ -15,7 +15,7 @@ runs.
 
 ## Why a mini port exists
 
-The full pack's own `skill-system.json` states its Windows posture plainly: Windows is supported
+The original port analysis recorded that the full pack's `skill-system.json` stated its Windows posture plainly: Windows is supported
 only through Git Bash or WSL, and the "full" install profile is macOS/Linux only. The full pack's
 tree has 73 `.sh` files under `shared/scripts/`, 117 more under `skills/process/`, hooks that
 probe for `bash -c 'exit 0'` and fail with `MISSING_SHELL` when neither Git Bash nor a compiled
@@ -29,12 +29,16 @@ install or runtime path.
 
 ## What's actually ported today
 
-As of the `feat(kbd): port the KBD process orchestrator and 49 skills to Windows-native Node`
-commit, this is **not** a proposal document — the KBD lifecycle, adversarial review,
-ideation-mindmap, Karpathy progress memory, and the plugin distribution system are real, tested
-Node.js code:
+The current distribution contains **97 skills**, including **40 portable UI/UX entries**
+from the shared 41-entry catalog. Mini excludes the full-only Impeccable native engine and
+ships a bounded context/workflow adaptation. See the [Skills Catalog](/docs/catalog) for
+actual frontmatter descriptions and user-only invocation labels.
+
+- **UI/UX routing** — context-first selection, TypeScript 7/Node Pro Max, craft and platform
+  guidance, and independent completed-phase review. [UI/UX routing and adoption](/docs/ui-ux/overview).
+- **Agent teams** — proposal export plus project installation, active-team discovery and
+  preservation of native ownership/configuration. [Agent Teams](/docs/agent-teams/overview).
 
-- **50 skills** under [`skills/`](https://github.com/Prometheus-AGS/prometheus-skills-mini/tree/main/skills) — see the [Skills Catalog](/docs/catalog) for the full list with real frontmatter descriptions.
 - **`lib/kbd/`** — the 12-module KBD state-machine core (position, progress, waypoint, stage
   gates, hooks, memory, rollup, and more). See [KBD Overview](/docs/kbd/overview).
 - **`lib/review/`** — the adversarial-review judge/producer isolation pipeline. See
@@ -46,11 +50,12 @@ Node.js code:
 - **`lib/distribution/`** — the plugin/marketplace generator for Claude Code and Codex. See
   [Plugin Distribution](/docs/distribution/plugin-marketplace).
 
-Over 1,000 tests pass on macOS as of that commit. **Windows itself remains unverified for the
-Phase C work** — everything in that batch ran on macOS; Windows verification for the newest code
-is still owed, the same caveat the project has recorded for every phase before it. The
-`platform-foundation` phase's own Windows claims (atomic writes, locking, CRLF handling,
-shell-free spawning) *are* independently CI-verified on `windows-latest`.
+Verification is scoped to a recorded phase and environment. Historical platform-foundation
+Windows CI does not certify new UI/team behavior. The
+[UI/team delivery record](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/docs/research/ui-ux-routing/DELIVERY.md)
+records macOS and offline Linux-container integration evidence. Native Windows execution,
+live invocation of every harness and full Electron installed-app acceptance remain open;
+no release certification is claimed here.
 
 ## Two services, not eleven
 
@@ -71,6 +76,8 @@ to a durable local outbox, and review falls back to a fresh-context subagent rec
 
 - [Installation](/docs/getting-started/installation) — how this pack is distributed and installed.
 - [npm scripts](/docs/getting-started/npm-scripts) — every script in `package.json` explained.
+- [UI/UX routing and adoption](/docs/ui-ux/overview) — project installation, selective skills and evidence.
+- [Agent Teams](/docs/agent-teams/overview) — creation, project adoption and native limits.
 - [KBD Overview](/docs/kbd/overview) — the lifecycle state machine.
 - [Windows constraints](/docs/platform/windows-constraints) — the rules every contribution follows.
 - [Comparison with the full pack](/docs/reference/comparison-with-full-pack) — what's ported, what's deliberately excluded, what's still a gap.
@@ -79,7 +86,8 @@ to a durable local outbox, and review falls back to a fresh-context subagent rec
 
 ```bash
 cd site
-npm install
+npm ci
+npm run generate:catalog
 npm start
 ```
 
diff --git a/site/docs/platform/windows-constraints.md b/site/docs/platform/windows-constraints.md
index ad655bb6..80a085dd 100644
--- a/site/docs/platform/windows-constraints.md
+++ b/site/docs/platform/windows-constraints.md
@@ -78,6 +78,17 @@ mindmap/distribution port (1,000+ tests) ran on macOS only as of that commit; Wi
 for that batch is still owed, and this documentation states that plainly rather than implying
 otherwise.
 
+The newer UI/team work has separate
+[macOS and offline Linux-container evidence](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/docs/research/ui-ux-routing/DELIVERY.md).
+Native Windows execution remains unverified, as do live invocation of every harness and
+full Electron installed-app acceptance. A Windows-like path tested on macOS is not native
+Windows evidence. [The platform matrix](/docs/ui-ux/overview#platform-and-acceptance-matrix)
+separates portable helpers from SDK, browser and harness prerequisites.
+
+The project installers create copies, while preserving supported existing in-project linked
+instruction entrypoints. Preservation of an existing link does not make symlink creation a
+mini runtime requirement.
+
 ## See also
 
 - [Docker Services](/docs/services/docker-services)
diff --git a/site/docs/reference/comparison-with-full-pack.md b/site/docs/reference/comparison-with-full-pack.md
index ceed11e8..fbae7221 100644
--- a/site/docs/reference/comparison-with-full-pack.md
+++ b/site/docs/reference/comparison-with-full-pack.md
@@ -5,15 +5,35 @@ sidebar_label: Comparison
 
 # Comparison with `prometheus-skill-pack`
 
-This page reflects the tree as of commit `8497ae8` ("port the KBD process orchestrator and 49
-skills to Windows-native Node") — the Phase C port that closed the KBD/adversarial-review/
-ideation-mindmap/distribution gap. Every claim below is checked against the actual `skills/`,
-`lib/`, `scripts/`, and `docker/` trees, not against this repository's own earlier planning
-documents, which predate that commit and are stale in places (notably, an earlier `README.md`
-revision stated flatly "the foundation is built and verified; the port itself has not started" —
-that sentence is no longer true for the KBD family).
+The current mini distribution contains **97 skills**, including **40 portable UI/UX entries**
+from a shared 41-entry catalog. Selected React/Vercel and mobile UI guidance is now included;
+the broader entity-management, DevOps and testing families remain outside this port.
 
-## What is ported and real today
+## UI/UX and project teams
+
+| Capability | Current scope |
+| --- | --- |
+| Shared UI/UX protocol and router | Context first, project protocol override, focused Pro Max query, one craft selection and manifest-based platform guidance. |
+| Taste selection | New work uses the actual model family; explicit redesign uses redesign guidance. Refinement and review exclude taste and overlays. |
+| Pro Max | TypeScript 7 with shipped Node ESM and pinned assets; no Python, runtime download or extra service. |
+| Impeccable | Full-only native engine is excluded. Mini carries bounded `prometheus-impeccable-core` context/workflow guidance, without native detector/browser parity. |
+| Completed-phase review | `phase-boundary` emits an unexecuted evidence contract; `prometheus-ui-review` requires independent read-only review and real acceptance evidence. User-only skills remain user-only. |
+| Project teams | Creator `install-project` installs discovery records/instructions and missing native definitions. Explicit team selection wins, a sole team is adopted, and ambiguity requires a choice. Export alone remains proposal-only. |
+| Native authority | Existing files, role ownership, permissions, model configuration and concurrency are preserved. Zed instructions are supported; unavailable native delegation uses disclosed sequential role instructions. |
+
+Follow [UI/UX routing and adoption](/docs/ui-ux/overview) and [Agent Teams](/docs/agent-teams/overview).
+The [prior delivery record](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/docs/research/ui-ux-routing/DELIVERY.md)
+records macOS and offline Linux-container integration plus packaged-helper evidence. Native
+Windows execution, live invocation of every harness and full Electron installed-app acceptance
+remain unverified. These are implementation/evidence limits, not current release certification.
+
+## Historical process-port baseline
+
+The following process-port snapshot was recorded at commit `8497ae8` (the Phase C KBD port).
+Its module test totals and older platform gaps describe that boundary only. They do not report
+results from the current documentation change or certify the later UI/team implementation.
+
+### Process capabilities at the recorded boundary
 
 | Capability | Status |
 |---|---|
@@ -42,14 +62,14 @@ These are excluded by explicit constraint, not because porting them was deferred
 | Symlink-based installs | This pack's installer and distribution generator are copy-mode only — the full pack symlinks 11 of 13 install targets, which needs Developer Mode or elevation on Windows. |
 | The Rust execution substrate (`prometheus-exec`, `substrate/*`, the research daemon, the surface bridge) | Unix-socket daemons and sandbox machinery with no Windows-native design; explicitly out of scope for this pack's process-focused architecture. |
 | `prometheus-knowledge`'s HTTP companion (`pk-cherry`) and its learning-worker timer daemon | This pack replaced the timer/worker model with durable receipts flushed opportunistically at SessionStart — see [Karpathy Progress Memory](/docs/karpathy/progress-memory). |
-| React/entity-management skills, DevOps/GitOps skills, BDD/Cucumber testing skills | Deliberately out of this pack's scope; the full pack's breadth in these areas is not being replicated here. |
+| Entity-management, DevOps/GitOps and BDD/Cucumber families | Deliberately outside this port. Selected React/Vercel UI guidance is now included through the UI catalog; that does not add the full entity-development family. |
 | `karpathy-tokenizer` | Despite the name, it trains BPE tokenizers via Python (`rustbpe`, `tiktoken`) — unrelated to Karpathy *logging*, and a Python dependency either way. |
 | `native-agent` / `start-business-build` | Generates a full service stack by design (Docker + surreal-memory + `pk` + liter-llm as *application* dependencies, not this pack's own two services) — out of scope for a process-focused mini pack. |
 
-## Genuine remaining gaps
+## Recorded gaps and acceptance limits
 
-These are things the project has named as still missing, distinct from the deliberate exclusions
-above:
+The UI/team acceptance gaps are listed above. The historical process-port notes below remain
+boundary-scoped records, distinct from the deliberate exclusions:
 
 - **Deep research.** Planned as a checkpoint-only Node port (`openspec/config.yaml`: "deep-research
   ... runs in checkpoint mode only"; the Rust `prometheus-research` server is explicitly not
@@ -80,9 +100,9 @@ above:
 
 ## Skill count
 
-This pack ships **50 skill directories** under `skills/` (confirmed by direct directory listing),
+This pack ships **97 distributed skill directories** under `skills/`,
 versus the full pack's much larger multi-hundred-skill catalog spanning many domains this pack does
-not attempt to cover (React/entity development, DevOps/GitOps, BDD testing, Feynman learning,
+not attempt to cover (entity development, DevOps/GitOps, BDD testing, Feynman learning,
 broad multi-language guidance, native-agent generation, and more). See the
 [Skills Catalog](/docs/catalog) for the complete, generated list.
 
diff --git a/site/docs/ui-ux/overview.md b/site/docs/ui-ux/overview.md
new file mode 100644
index 00000000..2326b49e
--- /dev/null
+++ b/site/docs/ui-ux/overview.md
@@ -0,0 +1,202 @@
+---
+title: UI/UX Routing and Project Teams
+sidebar_label: Routing and Adoption
+---
+
+# UI/UX routing and project-team adoption
+
+Mini distributes **97 skills**, including **40 portable UI/UX entries** from the shared
+41-entry full/mini catalog. The extra full-only entry is Impeccable's native engine.
+Catalog inclusion records provenance and suitability; it is not a claim that a skill is
+universally best. See the [catalog lock](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/prometheus-ui-ux/references/catalog.lock.json).
+
+## Install project routing
+
+Run these commands from the mini checkout with Node.js 22 or newer. Replace the quoted
+project path with an existing authorized project. On a machine with the full pack installed,
+use the full pack's bootstrap; mini belongs only in The Boss's internal data directory on
+that machine. These project commands do not waive the [install-scope rule](/docs/getting-started/installation#the-install-scope-rule).
+
+For layered context plus UI routing and adoption of existing teams:
+
+```text
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --dry-run
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project"
+node scripts/prometheus-context-bootstrap.mjs --path "../My Project" --check
+```
+
+Bootstrap merges managed context, copies portable UI skills into project
+`.agents/skills` and `.claude/skills`, preserves an existing `.agents/UI_UX_PROTOCOL.md`,
+and adopts a resolvable existing team. For UI routing alone, use:
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project" --dry-run
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project"
+node skills/prometheus-ui-ux/scripts/cli.mjs install --project "../My Project" --check
+```
+
+The UI-only installer does not create the active-team record or native agents. Adopt an
+existing team separately:
+
+```text
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --dry-run
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project"
+node skills/agent-team-creator/scripts/cli.mjs install-project --project "../My Project" --check
+```
+
+An explicit selection in `.agent-team/project-routing.json` wins; otherwise a sole
+`.agent-team/<id>/team.json` is adopted. When several teams remain, choose deliberately
+with `--team <id>`; stale selection is an error. For a new team, follow the
+[creation and installation guide](/docs/agent-teams/overview#install-the-project-team).
+Proposal-only `export` does not complete project adoption.
+
+Managed instruction blocks preserve unrelated prose, CRLF, existing in-project linked
+entrypoints and local recovery information. Creator preserves existing native file bytes,
+including models, permissions and concurrency; it reports differences for a deliberate merge.
+A routing pointer grants no native permission and does not start agents. Read the active record
+and real manifest for every code task, select relevant roles, and preserve their ownership.
+Backend work still uses its team without activating UI skills.
+
+Creator also updates Zed's first effective existing instruction file, from `.rules`,
+`.cursorrules`, `.windsurfrules`, `.clinerules`, `.github/copilot-instructions.md`,
+`AGENT.md`, `AGENTS.md`, `CLAUDE.md`, then `GEMINI.md`; otherwise it uses `AGENTS.md`.
+Inspect `instructionFiles` in the record. External ACP agents retain their own native
+configuration. Zed's parallel-thread UI is not a delegation API. If the harness cannot delegate,
+use role instructions sequentially and disclose the limitation; builder review is not independent.
+
+## Route the actual UI task
+
+Read `PRODUCT.md`, `DESIGN.md`, `.impeccable.md`, the nearest surface brief, components and
+tokens before changing direction. Project `.agents/UI_UX_PROTOCOL.md` overrides the
+[bundled protocol](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/prometheus-ui-ux/references/UI_UX_PROTOCOL.md). Generated
+recommendations do not replace project authority.
+
+Save `ui-request.json` with paths relative to its `project` (the project itself resolves
+against the command's working directory):
+
+```json
+{
+  "project": "../My Project",
+  "ui": true,
+  "affected": ["apps/web/src/Settings.tsx"],
+  "operation": "refine",
+  "surface": "app",
+  "focus": "accessibility"
+}
+```
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs route --input ui-request.json
+```
+
+Use the returned context paths first and load the selected skill IDs in order. The helper
+returns a routing decision; it does not execute the selected skills. Set `ui: false` for
+backend-only requests. Missing skills are explicit gaps, never an automatic download.
+In an installed payload, resolve the actual skill directory instead of assuming this checkout.
+Copy the complete payload and required catalog siblings, not just a CLI entry file.
+
+| Operation | Direction and review behavior |
+| --- | --- |
+| `new` | Establish direction when needed. Actual GPT model IDs select `gpt-taste`; missing/non-GPT model uses `design-taste-frontend`. Set `model` to the model actually running, never the harness name. |
+| `redesign` | Explicitly authorized direction change uses `redesign-existing-projects`. |
+| `refine` | Preserve incumbent identity; no taste implementation or overlay; focused retrieval only. |
+| `review` | Objective evidence and project scope through `prometheus-ui-review`; no taste or redesign. Reviewer/verifier/auditor roles force review routing. |
+
+At most one taste implementation and one explicitly selected overlay apply to new/redesign
+work. The supported overlays are `high-end-visual-design`, `minimalist-ui` and
+`industrial-brutalist-ui`; refinement/review ignore overlays. Experimental/v1 identities remain
+separate catalog entries. One craft skill follows the task: layout, typography, colors, writing,
+accessibility, motion, or broad interface work. Relevant platform skills follow the nearest
+application manifests; a monorepo root is not evidence of every application's stack.
+
+Surface defaults are Persuade for marketing/landing/pricing, Operate for apps/tools, Read for
+docs/articles, and Experience for portfolios/showcases. Existing tokens and explicit design
+decisions override defaults. See the [request reference](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/prometheus-ui-ux/references/runtime-api.md)
+for exact modes, fields, focus aliases and dial ranges.
+
+## Use Pro Max selectively
+
+The shipped TypeScript 7 implementation runs directly as Node ESM with pinned data and assets.
+No Python, repository-root runtime dependencies, online catalog refresh or service is required.
+For an existing React app, for example:
+
+```text
+node skills/ui-ux-pro-max/scripts/search.mjs "keyboard navigation React 19" --stack react --json
+node skills/ui-ux-pro-max/scripts/search.mjs "accessible forms" --domain ux --json
+```
+
+Use the actual project framework version in the query. To establish a new design direction:
+
+```text
+node skills/ui-ux-pro-max/scripts/search.mjs "clinic appointment booking" --design-system --project-name "Clinic" --format markdown
+```
+
+Only persist when requested: `--persist --output-dir "../My Project" --page booking` writes
+`design-system/<project-slug>/MASTER.md` and page overrides. Existing files are preserved unless
+replacement is authorized and `--force` is supplied; forced writes retain recovery copies.
+`DESIGN.md` is never overwritten. Stitch output belongs in `DESIGN.stitch.md`.
+A zero-result query is an absence of advice, not a recommendation. Pinned catalog versions
+never authorize application upgrades. See [Pro Max port scope](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/ui-ux-pro-max/PORT.md).
+
+## Review once the production phase is complete
+
+Finish the authorized implementation before running the completed-phase evidence contract.
+Save a review request using the same fields, with `operation: "review"`, then run:
+
+```text
+node skills/prometheus-ui-ux/scripts/cli.mjs phase-boundary --input ui-review-request.json
+```
+
+This returns `status: "evidence-required"`, `executed: false`, a checklist and an exec-form
+Node descriptor. It accepts no evidence fields, captures no screenshots, launches no browser
+and cannot certify PASS. Exit 0 only means the request was processed. Use available platform
+tools to collect applicable device/theme states, keyboard/focus and reduced-motion evidence;
+obtain independent read-only review, then one batched correction and confirmation cycle.
+Record evidence paths, reviewer identity, unavailable checks and unresolved findings.
+Outstanding blockers remain blocking; unavailable independent review remains unverified.
+
+Automatic review uses `prometheus-ui-review` and auto-invocable craft guidance.
+`interface-review`, `break`, `variant` and `explain-interface` remain user-only.
+Do not read their files to bypass `disable-model-invocation`. No per-edit hook or native
+browser/detector engine is implied by this mini adaptation.
+
+## Platform and acceptance matrix
+
+| Surface or host | What mini supplies | What remains separate |
+| --- | --- | --- |
+| Web/React | Context, craft, relevant Vercel/React guidance and Pro Max stack data | Project runtime, browser captures and acceptance |
+| Expo/React Native | Selected native/UI/design/router/motion guidance | Match declared Expo SDK and installed platform prerequisites |
+| Flutter | Responsive layout, layout repair, routing and localization guidance | Flutter toolchain and real device/emulator execution |
+| SwiftUI | SwiftUI guidance and platform units | Apple toolchain, simulator/device captures and profiling |
+| Android | Adaptive Compose and edge-to-edge guidance | Declared Gradle/SDK prerequisites and native execution |
+| Tauri/Electron | Shared UI routing; reuse project-specific platform workflow | Desktop packaging and native app acceptance; no invented specialist endorsement |
+| Other stacks | Matching Pro Max data and current official documentation | Project-specific implementation and toolchain evidence |
+| macOS / Linux | Prior macOS integration and offline Linux Node 22 container evidence | Container evidence is not all Linux desktop/toolchain certification |
+| Native Windows | Node-only shipped helpers and portable assets | Native Windows UI/team execution remains unverified |
+| Full Impeccable engine | Excluded; bounded `prometheus-impeccable-core` context/workflow adaptation | Native detector, browser engine and engine parity are not shipped |
+| Native harnesses / The Boss | Definitions, routing records and packaged-helper evidence | Live invocation of every harness and full Electron installed-app acceptance remain open |
+
+Local installation/routing, bundled Pro Max retrieval, team state and exports work without
+surreal-memory or liter-llm. Their optional discovery/publication operations need configured
+services. No additional daemon or port is added. Offline helper evidence does not certify
+browser availability, platform SDKs or native harness invocation.
+
+The [delivery record](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/docs/research/ui-ux-routing/DELIVERY.md) links the prior macOS/Linux and
+packaged-helper receipts and names remaining acceptance gaps. Historical platform CI and
+old test totals do not certify this feature or a release.
+
+## Troubleshooting
+
+| Symptom | Action |
+| --- | --- |
+| Ambiguous teams | Inspect real manifests, choose an existing ID with creator `--team <id>`, then rerun bootstrap. Do not choose arbitrarily. |
+| Stale active selection | Reconcile the routing record and existing manifest; use an intentional explicit selection. |
+| Corrupt managed markers or escaping paths | Inspect the named file and recovery record, restore a valid pair/path, then repeat dry-run. Do not replace the whole instruction file. |
+| Existing native definition differs | Keep its bytes and native permissions; deliberately merge after reading diagnostics. Definition presence alone does not prove invocation. |
+| UI install check reports drift | UI/bootstrap `--check` exits 1 for drift, 2 for errors; creator `--check` exits 2 for drift, 1 for errors. Inspect reported paths before applying. |
+| A helper/skill is missing | Resolve the installed directory and complete payload. Report the missing dependency; do not fetch or install implicitly. |
+| Full pack detected on the machine | Keep mini inside The Boss's internal data directory; use the full pack for native installation. Never delete or shadow existing full-pack skills. |
+| No independent reviewer/browser/device | Record the unavailable acceptance step. Sequential role use does not substitute for independent review or captures. |
+
+See [agent teams](/docs/agent-teams/overview) and the [project installation contract](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/agent-team-creator/references/project-installation.md)
+for native artifacts, recovery and model/permission preservation.
diff --git a/site/scripts/generate-skills-catalog.mjs b/site/scripts/generate-skills-catalog.mjs
index a4fd2802..6a59ea0d 100644
--- a/site/scripts/generate-skills-catalog.mjs
+++ b/site/scripts/generate-skills-catalog.mjs
@@ -9,7 +9,7 @@
 //
 // Walks ../skills/*/SKILL.md, parses YAML frontmatter, and emits one Markdown page per category
 // plus an index into site/docs-catalog/ (generated, gitignored). Wired via `build:deploy` and
-// `generate:catalog`. Idempotent: output depends only on the SKILL.md inputs.
+// `generate:catalog`. Output derives from SKILL.md inputs and the shared UI catalog lock.
 
 import { readdirSync, readFileSync, lstatSync, mkdirSync, rmSync, writeFileSync } from 'node:fs';
 import { join, dirname, relative } from 'node:path';
@@ -20,6 +20,8 @@ const siteDir = dirname(dirname(fileURLToPath(import.meta.url)));
 const repoRoot = dirname(siteDir);
 const skillsRoot = join(repoRoot, 'skills');
 const outDir = join(siteDir, 'docs-catalog');
+const uiCatalog = JSON.parse(readFileSync(join(skillsRoot, 'prometheus-ui-ux/references/catalog.lock.json'), 'utf8'));
+const uiEntries = new Map(uiCatalog.skills.map((entry) => [entry.id, entry]));
 
 // Skill name -> category, for this repo's flat layout. Anything not listed falls into "other".
 const CATEGORY_OF = new Map(
@@ -82,7 +84,7 @@ const CATEGORY_OF = new Map(
 );
 
 function categoryFor(name) {
-  return CATEGORY_OF.get(name) || 'Other';
+  return uiEntries.has(name) ? 'UI & UX' : CATEGORY_OF.get(name) || 'Other';
 }
 
 /** Recursively find SKILL.md files under skillsRoot, one level deep per skill directory. */
@@ -144,7 +146,8 @@ for (const file of files) {
   const version = (fm && (fm.version || (fm.metadata && fm.metadata.version))) || '';
   const category = categoryFor(dirName);
   if (!byCategory.has(category)) byCategory.set(category, []);
-  byCategory.get(category).push({ name, description, tags, version, rel });
+  const invocation = uiEntries.get(dirName)?.invocation;
+  byCategory.get(category).push({ name, description, tags, version, rel, invocation });
   count += 1;
 }
 
@@ -164,11 +167,15 @@ for (const cat of categories) {
 
   let body = `---\ntitle: ${cat}\nsidebar_label: ${cat}\n---\n\n# ${cat}\n\n`;
   body += `${skills.length} skill${skills.length === 1 ? '' : 's'}. Source of truth: [\`skills/\`](https://github.com/Prometheus-AGS/prometheus-skills-mini/tree/main/skills).\n\n`;
+  if (cat === 'UI & UX') {
+    body += 'The shared catalog has 41 entries; mini carries 40 portable entries. Full-only Impeccable is excluded; prometheus-impeccable-core is a bounded adaptation, not native-engine parity. See [UI/UX routing](/docs/ui-ux/overview) for selective loading, project authority and completed-phase review. User-only entries are never invoked automatically.\n\n';
+  }
   for (const s of skills.sort((a, b) => a.name.localeCompare(b.name, 'en'))) {
     body += `## ${esc(s.name)}\n\n`;
     if (s.description) body += `${esc(s.description)}\n\n`;
     const meta = [];
     if (s.version) meta.push(`v${s.version}`);
+    if (s.invocation === 'user-only') meta.push('**User-only invocation**');
     if (s.tags.length) meta.push(s.tags.map((t) => `\`${t}\``).join(' '));
     meta.push(
       `[source](https://github.com/Prometheus-AGS/prometheus-skills-mini/blob/main/skills/${s.rel})`,
diff --git a/site/sidebars.js b/site/sidebars.js
index fd0d550a..bfc190e3 100644
--- a/site/sidebars.js
+++ b/site/sidebars.js
@@ -19,6 +19,11 @@ const sidebars = {
       label: 'Review & Ideation',
       items: ['review/adversarial-review', 'ideation/ideation-mindmap'],
     },
+    {
+      type: 'category',
+      label: 'UI/UX',
+      items: ['ui-ux/overview'],
+    },
     {
       type: 'category',
       label: 'Agent Teams',