From fcc464b56c854e1af19e8ce502bd4f18fe83e4a1 Mon Sep 17 00:00:00 2001 From: Travis James Date: Sat, 26 Sep 2026 01:27:21 -0500 Subject: [PATCH] docs: document UI routing catalog and team installation Assisted-by: Codex:GPT-6 [Git, Node.js, Playwright] --- README.md | 20 ++++ docs/agent-teams.md | 19 ++++ docs/generated/runtime-reference.md | 2 +- docs/guide/08-skills-overview.md | 3 +- docs/guide/24-agent-teams.md | 20 +++- docs/guide/25-ui-ux-routing.md | 103 ++++++++++++++++++++ docs/guide/README.md | 7 ++ docs/reference/ui-ux-routing.md | 78 +++++++++++++++ site/docs/operations/generated-reference.md | 2 +- site/docusaurus.config.js | 1 + 10 files changed, 251 insertions(+), 4 deletions(-) create mode 100644 docs/guide/25-ui-ux-routing.md create mode 100644 docs/reference/ui-ux-routing.md diff --git a/README.md b/README.md index 10fcdb3eb..fb3977c7e 100644 --- a/README.md +++ b/README.md @@ -33,6 +33,7 @@ flow, sequence, and C4 diagrams throughout. This README is the quick tour; the g | Understand the loops | [Loop Architecture](docs/guide/03-loop-architecture.md) · [Four-Layer Pipeline](docs/guide/04-four-layer-pipeline.md) | | Know the substrate | [MCP Servers](docs/guide/05-mcp-substrate.md) · [Memory & Learning](docs/guide/06-memory-and-learning.md) · [Sycophancy Correction](docs/guide/07-sycophancy-correction.md) | | Browse every skill | [Skills Overview](docs/guide/08-skills-overview.md) · [Process Skills](docs/guide/09-process-skills.md) · [Language Skills](docs/guide/10-language-skills.md) · [Artifact Refiner](docs/guide/11-artifact-refiner.md) · [Native Agent Generator](docs/guide/12-native-agent-generator.md) | +| Route UI work | [UI/UX routing guide](docs/guide/25-ui-ux-routing.md) · [Command reference](docs/reference/ui-ux-routing.md) | | Coordinate agents | [Agent teams guide](docs/guide/24-agent-teams.md) · [Requests, exports and ownership](docs/agent-teams.md) | | Reference the engine room | [Tools](docs/guide/13-tools-reference.md) · [Rust Toolchain](docs/guide/14-rust-toolchain.md) · [Hooks & Lifecycle](docs/guide/15-hooks-and-lifecycle.md) · [CLI & Scripts](docs/guide/16-cli-and-scripts.md) | | Install, run, contribute | [Platform Support](docs/guide/17-platform-support.md) · [Plugins & Marketplace](docs/guide/18-plugins-and-marketplace.md) · [Installation](docs/guide/19-installation.md) · [Updating](docs/guide/20-updating.md) · [Contributing](docs/guide/21-contributing.md) | @@ -107,6 +108,25 @@ service. See the [guide](docs/guide/24-agent-teams.md) for the novice flow and [request reference](docs/agent-teams.md) for exact JSON examples, model and memory limits, and the distinction between skill distribution and native teams. +## UI/UX routing + +Use `prometheus-ui-ux` for UI, interaction, tokens, motion and on-screen copy. It +selects project context, focused Pro Max data, craft and platform guidance while +preserving design authority. New work and authorized redesign may use taste; +refinement and review do not. The catalog has 41 entries, including 40 portable +entries shared with mini. Full-only Impeccable engine execution requires a +preinstalled `IMPECCABLE_BIN`; the portable core does not claim engine parity. + +Adopt existing teams through creator `install-project`: it preserves an explicit +selection, adopts a sole team and requires a choice when ambiguous. Relevant team +roles then apply to all code work; UI guidance activates only for UI work. Existing +native configuration stays intact, and unavailable delegation uses a disclosed +sequential fallback. `export` remains proposal-only. + +The completed-phase helper returns an evidence checklist, not a review result. +See the [guide](docs/guide/25-ui-ux-routing.md) for commands, independent review and +the remaining Windows, live-harness, Electron and release-certification gaps. + ## Native Agent Generator The skill pack includes `/create-native-agent` — a project scaffold that generates diff --git a/docs/agent-teams.md b/docs/agent-teams.md index 44dfc33f0..9359e36b2 100644 --- a/docs/agent-teams.md +++ b/docs/agent-teams.md @@ -109,6 +109,25 @@ Claude and Kimi have verified agent plugin/marketplace exports. Install either t UAR defaults require explicit review of tool policy and bundles before registration; skill preference is not a deny policy. BossFang's native `skills=[]` means all unless `skills_disabled=true`; an empty portable role skill list exports the disabled form. Supply an approved service URL and credential reference for registration, retain returned IDs, and account for partial success. Hand activation can start autonomous schedules. Neither export nor discovery establishes authorization to mutate a service. +## Install or adopt a project team + +After reviewing the export, finish normal project-team creation with `install-project`. For a new team, save `{"project":"/path/to/project","team":}` as `install-request.json`, then run: + +```text +node skills/process/agent-team-creator/scripts/cli.mjs install-project --input install-request.json --dry-run +node skills/process/agent-team-creator/scripts/cli.mjs install-project --input install-request.json +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --check +``` + +For an existing team, use `--project "/path/to/project"` without an input manifest. A recorded `.agent-team/project-routing.json` selection wins; otherwise a sole `.agent-team//team.json` is adopted. Multiple candidates require `--team `; stale selections fail rather than silently switching. Intentional manifest replacement requires `updateTeam: true` in the request. Creator check exits 2 for drift and 1 for errors. + +Installation writes managed discovery pointers to both instruction entrypoints, the active routing record and missing native definitions. Existing native files, role IDs, ownership, model policies, permissions and concurrency remain intact; differing configuration is reported for deliberate merge. Recovery records retain prior instruction bytes. Export stages proposals; installation establishes discovery. Neither starts execution or activates UAR/BossFang registration. + +All code tasks use the selected team’s relevant roles. UI roles conditionally use `prometheus-ui-ux`; UI review uses `prometheus-ui-review` after the whole implementation phase, without taste or user-only skill preloads. Backend work loads no UI guidance. Use native delegation only if available, otherwise disclose sequential role execution; builder self-review is not independent review. Zed receives the pointer in its effective existing instruction file. External ACP agents keep native configuration, and Zed parallel threads are not a delegation API. + +See [UI/UX routing](guide/25-ui-ux-routing.md) for the selective workflow. + + ## Choose models from evidence `models-discover` accepts `kind: "openai"` with a configured `baseUrl`, or `kind: "uar"`/`"bossfang"` with an explicit `discoveryUrl`. Authentication uses `auth.env` referencing a local environment variable; do not embed tokens in JSON. The OpenAI-compatible route is `/v1/models`, UAR uses `/api/uar/providers/{id}/models`, and BossFang uses `/api/models`. Native discovery describes configured availability, not successful inference. diff --git a/docs/generated/runtime-reference.md b/docs/generated/runtime-reference.md index 587ff1939..9dc7ca139 100644 --- a/docs/generated/runtime-reference.md +++ b/docs/generated/runtime-reference.md @@ -8,7 +8,7 @@ Release: **1.10.0** Generated by: `npm run docs:sync` -Skill definitions: **153** +Skill definitions: **194** Plugin targets: **14** diff --git a/docs/guide/08-skills-overview.md b/docs/guide/08-skills-overview.md index b9aeca327..c1c7d708b 100644 --- a/docs/guide/08-skills-overview.md +++ b/docs/guide/08-skills-overview.md @@ -1,6 +1,6 @@ # 08 · Skills Overview -A skill is a self-contained, portable unit of capability: a `SKILL.md` manifest with YAML frontmatter, optionally accompanied by `scripts/`, `references/`, and `assets/`. The prometheus-skill-pack ships 35 top-level skills across 13 categories — 95+ skills counting sub-skills — and every one of them is documented in the three pages that follow this one. This page explains the model: how skills are structured, how they are discovered, the standard they conform to, and where to find each category. +A skill is a self-contained, portable unit of capability: a `SKILL.md` manifest with YAML frontmatter, optionally accompanied by `scripts/`, `references/`, and `assets/`. The generated full distribution index currently lists 215 skills. The UI/UX routing catalog contributes 41 entries, with a 40-entry portable subset shared with mini; its native Impeccable integration is full-only. Use the generated catalogs for current inventories and the [UI/UX guide](25-ui-ux-routing.md) for selective loading. This page explains the model: how skills are structured, how they are discovered, the standard they conform to, and where to find each category. ## The skills model @@ -80,6 +80,7 @@ Every native skill conforms strictly to the [AgentSkills.io specification](https | **Research** | 1 | deep-research (10 sub-skills) | [10](10-language-skills.md) | | **Documentation** | 1 | llm-wiki | [10](10-language-skills.md) | | **Flint** | 6 | flint-sdk-csharp, -dart, -go, -kotlin, -swift, -ts | [10](10-language-skills.md) | +| **UI/UX routing catalog** | 41 | Context, Pro Max, craft, taste, platform and review guidance; 40 portable entries | [25 · UI/UX routing](25-ui-ux-routing.md) | | **Imported (submodules)** | 2 | artifact-refiner, sycophancy-correction | [11](11-artifact-refiner.md), [07](07-sycophancy-correction.md) | ## Native, imported, and forge-rs skills diff --git a/docs/guide/24-agent-teams.md b/docs/guide/24-agent-teams.md index 807a630eb..235ad1ec5 100644 --- a/docs/guide/24-agent-teams.md +++ b/docs/guide/24-agent-teams.md @@ -11,7 +11,7 @@ The four procedures are available as ordinary skills through the process plugin | Procedure | Use it to | | --- | --- | -| `agent-team-creator` | Describe an outcome, edit the proposed roles and stage native definitions. | +| `agent-team-creator` | Describe an outcome, stage native definitions, then install or adopt the project team. | | `agent-team-manage` | Assign and track revisioned tasks, dependencies and evidence. | | `agent-team-models` | Compare configured models against explicit capabilities, tiers and price ceilings. | | `agent-team-handoff` | Prepare fresh context and transfer ownership after destination acceptance. | @@ -52,6 +52,24 @@ Targets are UAR, Codex, Claude Code, Copilot, Kimi Code, MiniMax, OpenCode, Deep Native role overrides, team options and opaque files preserve settings beyond the common manifest, with source/version provenance. Preservation does not certify a setting against an installed tool. The [native contract reference](https://github.com/Prometheus-AGS/prometheus-skill-system/blob/main/skills/process/agent-team-creator/references/native-harnesses.md) links official sources and explains which options become proposed config files and which remain sidecar data for deliberate application. +## Install or adopt a project team + +After reviewing the export, finish normal project-team creation with `install-project`. For a new team, save `{"project":"/path/to/project","team":}` as `install-request.json`, then run: + +```text +node skills/process/agent-team-creator/scripts/cli.mjs install-project --input install-request.json --dry-run +node skills/process/agent-team-creator/scripts/cli.mjs install-project --input install-request.json +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --check +``` + +For an existing team, use `--project "/path/to/project"` without an input manifest. A recorded `.agent-team/project-routing.json` selection wins; otherwise a sole `.agent-team//team.json` is adopted. Multiple candidates require `--team `; stale selections fail rather than silently switching. Intentional manifest replacement requires `updateTeam: true` in the request. Creator check exits 2 for drift and 1 for errors. + +Installation writes managed discovery pointers to both instruction entrypoints, the active routing record and missing native definitions. Existing native files, role IDs, ownership, model policies, permissions and concurrency remain intact; differing configuration is reported for deliberate merge. Recovery records retain prior instruction bytes. Export stages proposals; installation establishes discovery. Neither starts execution or activates UAR/BossFang registration. + +All code tasks use the selected team’s relevant roles. UI roles conditionally use `prometheus-ui-ux`; UI review uses `prometheus-ui-review` after the whole implementation phase, without taste or user-only skill preloads. Backend work loads no UI guidance. Use native delegation only if available, otherwise disclose sequential role execution; builder self-review is not independent review. Zed receives the pointer in its effective existing instruction file. External ACP agents keep native configuration, and Zed parallel threads are not a delegation API. + +See [UI/UX routing](25-ui-ux-routing.md) for the selective workflow. + ## Models, ownership and continuity Model selection combines team, role, skill and task policy. Strength tiers are explicit annotations; they are not inferred from a model's name. Unknown prices cannot satisfy a cost ceiling, and unavailable capability metadata remains unknown. Discovery is not a successful inference test. Review the selected exact model ID before updating policy and exporting it. diff --git a/docs/guide/25-ui-ux-routing.md b/docs/guide/25-ui-ux-routing.md new file mode 100644 index 000000000..3dd6dc932 --- /dev/null +++ b/docs/guide/25-ui-ux-routing.md @@ -0,0 +1,103 @@ +--- +title: UI/UX routing +description: Install selective UI guidance, preserve design authority, and collect completed-phase evidence with the project team. +--- + +# UI/UX routing + +Use `prometheus-ui-ux` when work changes rendered UI, interaction, styles, tokens, motion or on-screen copy. Describe the affected application and whether you are creating, redesigning, refining or reviewing it. The router returns context to read and a small set of relevant skills. Backend-only work uses the selected project team without loading UI guidance. + +The canonical UI catalog contains **41 entries**. The portable project installer and mini pack carry **40**; full distribution also includes the optional native Impeccable integration. The full pack's generated distribution index currently lists **215 skills** across all domains. These are different inventories: the site catalog currently enumerates 194 source manifests excluding imported submodules, while the distribution index enumerates 215 packaged skills. See the [generated catalog](/docs/catalog/ui-ux) and [distribution index](https://github.com/Prometheus-AGS/prometheus-skill-system/blob/main/SKILLS.md). + +## Add UI guidance to a project + +Run these commands from the full pack checkout, replacing the project path with an existing authorized directory. For installed skills, use the actual skill directory reported by your harness. Node.js 22 or newer runs the shipped helpers without a TypeScript installation or network service. + +```text +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" --dry-run +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" --check +``` + +The installer copies portable skills into `.agents/skills` and `.claude/skills`, installs a protocol if none exists, and adds managed pointers to both instruction entrypoints. It preserves project protocol overrides, unrelated prose and in-project linked entrypoints. It checks marker pairs and path containment before writing and retains recovery records for changed instructions. Malformed markers or escaping links must be resolved before installation; repeatedly forcing a bootstrap is not a repair procedure. + +Full-pack context bootstrap, including legacy and v4 layouts, and the existing UI rules injector call this same helper. Use the direct Node commands above when only UI routing is needed. Broader bootstrap has its own shell/tool prerequisites and changes beyond UI routing. In projects whose instruction files are generated, add the routing instructions to `rules/src/routing.md` before regenerating; do not rely on an edit to generated output. Exact [bootstrap and injector examples](https://github.com/Prometheus-AGS/prometheus-skill-system/blob/main/docs/reference/ui-ux-routing.md) are in the command reference. + +## Preserve the project's design decisions + +Read the project override `.agents/UI_UX_PROTOCOL.md` when present, otherwise the bundled protocol. Load `PRODUCT.md`, `DESIGN.md`, `.impeccable.md`, the affected application's surface brief, existing components and tokens before choosing direction. A missing design document does not turn an existing application into a blank canvas. + +Pro Max supplies focused domain and stack recommendations. Its TypeScript 7 source ships as Node ESM with pinned data; the full and mini portable helpers use identical bytes. Ordinary refinement and review use focused search. Generate a complete design system only when establishing or explicitly replacing direction. Persisted Pro Max output stays under `design-system//`; Stitch uses `DESIGN.stitch.md`. Neither overrides approved `DESIGN.md` or incumbent tokens. + +Full-only Impeccable engine execution requires an explicitly configured, preinstalled `IMPECCABLE_BIN`. The launcher never downloads an engine. When unavailable, read project context directly and continue with permitted guidance. Mini uses `prometheus-impeccable-core`, an explicitly bounded context and craft adaptation. It does not provide native detector hooks, engine heuristics or live-browser parity. The proposed Node engine port remains deferred. + +## Route a task + +Save this request as `ui-request.json`, using your actual affected paths and model: + +```json +{ + "project": "/path/to/project", + "affected": ["apps/web/src/Settings.tsx"], + "operation": "refine", + "surface": "app", + "model": "gpt-6", + "focus": "accessibility", + "ui": true +} +``` + +```text +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs route --input ui-request.json +``` + +Use returned context paths first, then load the selected skills in order. Missing skills are reported gaps, not authorization to install dependencies. The model value is the actual model identifier; a Codex harness name does not establish that the model is GPT. + +| Operation | Direction guidance | +| --- | --- | +| `new` | `gpt-taste` for actual GPT-family models; otherwise `design-taste-frontend`. | +| `redesign` | `redesign-existing-projects` after explicit redesign authorization. | +| `refine` | Preserve identity; no taste implementation or overlay. This is the default. | +| `review` | Objective scope and evidence review through `prometheus-ui-review`; no taste. Reviewer, verifier and auditor roles force this route. | + +New work and redesign allow at most one direction implementation and one explicitly chosen overlay. Experimental/v1 taste identities remain distinct. Craft selection is narrow: layout → `better-layout`; typography → `better-typography`; color → `better-colors`; copy → `better-writing`; accessibility → `better-accessibility`; motion → `better-ui`; broad work → `better-interface`. + +Surface modes are Persuade for marketing, Operate for apps, Read for documentation and Experience for showcases. They provide starting ranges for variance, motion and density; existing design decisions and reduced-motion requirements win. + +Platform selection reads the nearest affected application's manifests, including nested applications. React/Vercel guidance applies to relevant components; Expo must match its declared SDK. Flutter, SwiftUI and Android retain their actual toolchain prerequisites and project versions. Tauri and Electron use the project's existing workflow. Portable guidance does not mean an unsupported host can build or profile native applications. + +Upstream `interface-review`, `break`, `variant` and `explain-interface` remain user-only. Automatic review uses the Prometheus reviewer and eligible craft guidance. Reading a user-only skill's source is not an invocation workaround. + +## Adopt the project team + +The UI installer and project-team installer are separate operations. For an existing team, run: + +```text +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --dry-run +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --check +``` + +An existing selection in `.agent-team/project-routing.json` wins. Without one, a sole `.agent-team//team.json` is adopted. Multiple candidates require an explicit `--team ` selection; a stale selection is an error. The installed pointer makes relevant selected roles the default for **all code tasks**. UI roles receive conditional routing; backend tasks stay free of UI guidance. + +Creator `export` stages a proposal into a new directory. `install-project` installs discovery instructions, the routing record and missing native definitions. Normal project-team creation finishes with installation after inspection. Existing native files, permissions, model settings, concurrency and ownership are preserved; differences are reported for a deliberate merge. Neither command starts a team or activates a service registration. + +Use native delegation only when the active harness exposes it. Otherwise follow the selected role instructions sequentially and disclose that limitation. Builder-context review is not independent review. Zed receives the pointer in its first effective existing instruction file as well as the standard entrypoints; external ACP agents retain their own configuration. Zed's parallel-thread UI does not establish a delegation API. See [agent teams](24-agent-teams.md) for creation and handoff. + +## Finish the phase, then collect evidence + +Complete the entire authorized production phase before verification. Change the request operation to `review` and run: + +```text +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs phase-boundary --input ui-request.json +``` + +The response is `status: "evidence-required"` and `executed: false`. It supplies routing, a checklist and a Node hook descriptor. It accepts no evidence fields, captures no screenshots, launches no browser and cannot certify PASS. Exit 0 means the request was processed. Wire it to an existing completed-phase runner, never a per-edit event. + +Collect applicable device widths, theme states, real-content captures, keyboard focus and reduced-motion evidence with available platform tools. Obtain independent read-only review in a separate context, then use one batched correction and confirmation cycle. Record reviewer identity, evidence paths, unresolved findings and platform gaps. Missing independent review stays unverified; unresolved blockers stay blocking. + +## What the existing evidence establishes + +The [delivery record](https://github.com/Prometheus-AGS/prometheus-skill-system/blob/main/docs/research/ui-ux-routing/DELIVERY.md) separates shipped implementation from acceptance gaps. Recorded local evidence includes macOS and offline Linux Node 22 bootstrap/creator/routing scenarios, full bootstrap/injector coverage, pinned Pro Max comparisons, distribution checks and a separate skill-contract judge. These are prior implementation receipts, not new certification by this guide. + +Native Windows execution, live invocation of every supported harness and a full installed Electron application run remain unverified. The native engine port is deferred. Catalog author review is self-review, and skill-contract review does not complete the ten-stage research review/export pipeline. Release certification remains open. No hosted CI result is used as validation evidence. diff --git a/docs/guide/README.md b/docs/guide/README.md index 1e393fe2e..868d46dbb 100644 --- a/docs/guide/README.md +++ b/docs/guide/README.md @@ -70,6 +70,13 @@ The guide is built in layers. Read it top to bottom the first time; use it as a | 22 | [Advantages & Impact](22-advantages-and-impact.md) | What changes about your development process, and why | | 23 | [Glossary & Sources](23-glossary.md) | Every term defined, every external claim cited | +### UI and team workflows + +| # | Page | What it covers | +|---|---|---| +| 24 | [Agent teams](24-agent-teams.md) | Create, export, install and adopt teams; preserve native configuration and ownership | +| 25 | [UI/UX routing](25-ui-ux-routing.md) | Context authority, selective skills, portable installation and completed-phase evidence | + ### Operational | Document | What it covers | diff --git a/docs/reference/ui-ux-routing.md b/docs/reference/ui-ux-routing.md new file mode 100644 index 000000000..cb42b6009 --- /dev/null +++ b/docs/reference/ui-ux-routing.md @@ -0,0 +1,78 @@ +# UI/UX routing command reference + +Use Node.js 22+ and the shipped helpers. Paths below are relative to the full pack checkout; installed users substitute the actual skill directory. See the [user guide](../guide/25-ui-ux-routing.md) for design authority, routing choices and evidence limits. + +## Portable commands + +```text +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" --dry-run +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs install --project "/path/to/project" --check +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs route --input ui-request.json +node skills/ui-ux/prometheus-ui-ux/scripts/cli.mjs phase-boundary --input ui-request.json +``` + +Both routing commands accept the same request: + +```json +{"project":"/path/to/project","ui":true,"affected":["apps/web/src/Settings.tsx"],"operation":"refine","surface":"app","model":"gpt-6","focus":"layout"} +``` + +| Field | Contract | +| --- | --- | +| `project` | Required existing directory; relative paths use the invocation directory. | +| `ui` | Boolean, default true; false loads no UI skills. | +| `affected` | Project-contained paths; omitted/empty resolves the root. Future files use their ancestors. | +| `operation` | `new`, `redesign`, `refine` (default), `review`. | +| `surface` | Marketing/landing/pricing/campaign → Persuade; docs/reading/articles/changelogs → Read; showcase/portfolio → Experience; otherwise Operate. | +| `model` | Actual identifier; GPT-family selection applies only to new work. | +| `focus` | Layout, typography, colors, copy, accessibility or motion selects one craft skill; otherwise better-interface. | +| `overlay` | Explicit high-end-visual-design, minimalist-ui or industrial-brutalist-ui; ignored for refine/review. | +| `role` | Reviewer/verifier/auditor identifiers force review. | +| `stack` | Pro Max query hint; does not override manifest detection. | + +Do not supply manifests or evidence fields. The [runtime API](../../skills/ui-ux/prometheus-ui-ux/references/runtime-api.md) defines all aliases and result fields. Phase-boundary returns an evidence checklist with `executed: false`, not an acceptance receipt. + +| Operation | Exit behavior | +| --- | --- | +| UI install `--check` | 0 current; 1 drift; 2 usage/preflight failure. | +| Route / phase-boundary | 0 request processed; 2 invalid input, command or path. | +| Creator install-project `--check` | 0 current; 2 drift; 1 error. | + +## Full bootstrap and existing injector + +These broader full-pack commands require their existing shell dependencies. Preview first. The v4 bootstrap additionally requires Python 3; that prerequisite does not apply to the portable Node UI helper. + +```text +bash skills/process/prometheus-context-bootstrap/scripts/bootstrap.sh --path "/path/to/project" --dry-run +bash skills/process/prometheus-context-bootstrap/scripts/bootstrap.sh --path "/path/to/project" --layout v4 --dry-run +``` + +Remove `--dry-run` only when applying the broader context installation within the authorized scope. Both layouts preflight the same canonical UI installer. Existing generated projects must retain routes in their source `rules/src/routing.md`. Do not use `--force` merely to add UI guidance. + +For the existing injector, set `KBD_ORCHESTRATOR_ROOT` to the actual installed orchestrator directory (the default is `$HOME/.claude/skills/kbd-process-orchestrator`). From the checkout, an example for a Bash-capable host is: + +```text +KBD_ORCHESTRATOR_ROOT="$PWD/skills/process/kbd-process-orchestrator" bash skills/process/kbd-process-orchestrator/skills/kbd-inject-agent-rules/kbd-inject-agent-rules.sh --pack uiux-routing --path "/path/to/project" --target both --dry-run +``` + +Remove `--dry-run` to apply. The `uiux-routing` pack delegates to the Node installer; it does not add a second protocol implementation. Direct Node installation is the portable route. + +## Install project-team discovery + +```text +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --dry-run +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" +node skills/process/agent-team-creator/scripts/cli.mjs install-project --project "/path/to/project" --check +``` + +Use `--team ` for ambiguity or an intentional selection change. To install a new manifest, `--input install-request.json` accepts `{"project":"/path/to/project","team":}`. Intentional replacement of a differing manifest also requires `updateTeam: true`. Export remains proposal-only. The [project installation contract](../../skills/process/agent-team-creator/references/project-installation.md) defines preservation, recovery, native targets and Zed precedence; the [team request reference](../agent-teams.md) covers initial creation and handoff. + +## Focused Pro Max retrieval + +```text +node skills/ui-ux/ui-ux-pro-max/scripts/search.mjs "operational dashboard accessible forms" --domain ux --json +node skills/ui-ux/ui-ux-pro-max/scripts/search.mjs "keyboard navigation React 19" --stack react --json +``` + +Use the actual framework version and a focused query. Full design-system generation and persistence are for establishing authorized direction; see the [Pro Max contract](../../skills/ui-ux/ui-ux-pro-max/SKILL.md). Existing recommendations remain advisory. A full-only preinstalled Impeccable engine must be explicitly selected with `IMPECCABLE_BIN`; no download or mini native-engine parity is implied. diff --git a/site/docs/operations/generated-reference.md b/site/docs/operations/generated-reference.md index 8985c0f94..02a6bc0b9 100644 --- a/site/docs/operations/generated-reference.md +++ b/site/docs/operations/generated-reference.md @@ -13,7 +13,7 @@ Release: **1.10.0** Generated by: `npm run docs:sync` -Skill definitions: **153** +Skill definitions: **194** Plugin targets: **14** diff --git a/site/docusaurus.config.js b/site/docusaurus.config.js index d3089832a..81f84e00f 100644 --- a/site/docusaurus.config.js +++ b/site/docusaurus.config.js @@ -130,6 +130,7 @@ const config = { position: 'left', label: 'Core', items: [ + { type: 'doc', docId: 'ui-ux-routing', docsPluginId: 'guide', label: 'UI/UX routing' }, { type: 'docSidebar', sidebarId: 'agentContextSidebar',