uxd-prototype-export
/uxd-prototype-export
Export a prototype page or journey step as static HTML, a React component tree, or a PatternFly implementation spec, and install the Prototype Bar (Sources, Prototype|Eval, State, Export). Use when capturing the current view, batch-exporting journey screens and page scenarios, or wiring provenance/eval/scenario navigation into a prototype.
- Author
- rh-uxd ↗
- Repository
- ai-helpers ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 35
- Scripts
- 16
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 16 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/copy-eval-for-pages.sh, scripts/export-component-tree.js, scripts/export-current.sh, scripts/export-helper.mjs, scripts/export-journey.mjs, scripts/export-pf-spec.js, scripts/inject-prototype-bar-into-html.mjs, scripts/install-prototype-bar.sh
What it does and when to use it
Export a prototype page or journey step as static HTML, a React component tree, or a PatternFly implementation spec, and install the Prototype Bar (Sources, Prototype|Eval, State, Export). Use when capturing the current view, batch-exporting journey screens and page scenarios, or wiring provenance/eval/scenario navigation into a prototype.
Original author description
Export a prototype page or journey step as static HTML, a React component tree, or a PatternFly implementation spec, and install the Prototype Bar (Sources, Prototype|Eval, State, Export). Use when capturing the current view, batch-exporting journey screens and page scenarios, or wiring provenance/eval/scenario navigation into a prototype.
How it works
- Inputs
- Outputs
- Requirements
- Flags
- Conversational Guidance
- Step 1: Choose Path
- Step 2: Confirm Outputs
- Prototype Bar
- Guardrails
- Reference Docs
SKILL.md preview
---
name: uxd-prototype-export
version: 0.1.0
description: >-
Export a prototype page or journey step as static HTML, a React component
tree, or a PatternFly implementation spec, and install the Prototype Bar
(Sources, Prototype|Eval, State, Export). Use when capturing the current
view, batch-exporting journey screens and page scenarios, or wiring
provenance/eval/scenario navigation into a prototype.
---
# Export Prototype
Captures prototype screens as portable artifacts — from the running app (Prototype Bar) or in batch from journey + scenario files. Also installs the Prototype Bar (Sources, Prototype|Eval, State, Export).
Family: `uxd-prototype-create` writes `journeys.json` / `states.json` / `prototype-bar.json`; this skill captures them; `uxd-prototype-evaluate` reports can be opened from the bar; `uxd-prototype-publish` copies evals into static Pages.
## Inputs
| Input | Required | Source |
|-------|----------|--------|
| What to export (current page, journey batch, or install bar) | **Yes** | User; skill asks if omitted |
| Live prototype URL (`--base-url`) | Yes for capture | Running app |
| `journeys.json` + `states.json` | Yes for batch | `artifacts/{ID}/` from create |
| Prototype source path (`--source`) | Yes for `--install-bar` | Standalone dir or workspace root |
If the user says "export" without details, **stop and ask** which path (below).
## Outputs
Under `.artifacts/{ID}/exports/` unless `--out` is set:
| Output | Description |
|--------|-------------|
| `index.html` + `export-manifest.json` | Gallery and manifest |
| `{journeyId}/{stepId}--{scenarioId}.html` | Static HTML snapshot (inlined CSS; not a live React app) |
| `*.tree.json` / `*.tree.txt` | Component tree (when `tree` format) |
| `*.pf-spec.json` / `*.pf-spec.txt` + `implementation-spec.json` | PF implementation spec (when `pf-spec`) |
| `current/page-{timestamp}.*` | Ad-hoc / bar captures |
Formats: [references/export-formats.md](references/export-formats.md). Point implementation agents at `implementation-spec.json` (or per-capture `.pf-spec.json`).
## Requirements
Node.js 18+ (CLI and optional helper). Playwright for journey/batch export:
```bash
cd "${CLAUDE_SKILL_DIR}" && npm install
```
## Flags
$ARGUMENTS
Parse as: `[--install-bar] [--base-url <url>] [--journeys <path>] [--formats html,tree,pf-spec] …`
| Flag | Values | Default | Description |
|------|--------|---------|-------------|
| `--install-bar` | flag | off | Install Prototype Bar |
| `--config` | path | auto-detect | `prototype-bar.json` (with `--install-bar`) |
| `--base-url` | URL | — | Live prototype URL for Playwright |
| `--journeys` | path | `.artifacts/{ID}/journeys.json` | Journey definitions |
| `--scenarios` | path | sibling `states.json` | Page state catalog |
| `--out` | path | `.artifacts/{ID}/exports` | Output directory |
| `--formats` | `html`, `tree`, `pf-spec` | `html` | Export formats |
| `--source` | path | — | Prototype dir or workspace root (install bar) |
| `--mode` | `standalone`, `workspace` | auto-detect | Install target type |
## Conversational Guidance
> What should I export?
>
> - **Current page** — capture whatever is on screen (use the Prototype Bar, or give me a URL)
> - **Journey steps × states** — batch-export from `artifacts/{ID}/journeys.json` + `states.json`
> - **Install Prototype Bar** — add the sticky bar (Sources, Eval, State, Export)
## Step 1: Choose Path
**A. Install Prototype Bar**
With `--artifacts`, this syncs `prototype-bar.json`, installs bar assets, and copies the eval report for Pages when present.
```bash
bash "${CLAUDE_SKILL_DIR}/scripts/install-prototype-bar.sh" \
--artifacts ".artifacts/{ID}" \
--source "<prototype-or-workspace-path>" \
[--mode standalone|workspace]
```
Assets-only (no config sync): omit `--artifacts` and pass `--config` if you already have `prototype-bar.json`. Schema: [references/prototype-bar-config.md](references/prototype-bar-config.md). Scenario runtime (`?state=<id>`) is `uxd-scenario-runtime.js`.
If workspace/React auto-mount fails, copy `templates/PrototypeBar.tsx` + CSS and mount `<PrototypeBar />` in the app shell. Mock branching: create skill `references/state-mocks.md`.
**B. Export current URL**
```bash
bash "${CLAUDE_SKILL_DIR}/scripts/export-current.sh" \
--url "http://localhost:3000/some-route?state=empty" \
--out ".artifacts/{ID}/exports" \
[--formats html,tree,pf-spec]
```
**C. Batch-export journey steps × scenarios**
Requires [journeys-schema.md](references/journeys-schema.md) and optionally [states-schema.md](references/states-schema.md). For each `export: true` step, captures every scenario for that `route` (`?state=<id>`, then step `actions`).
```bash
node "${CLAUDE_SKILL_DIR}/scripts/export-journey.mjs" \
--base-url "http://localhost:3000" \
--journeys "artifacts/{ID}/journeys.json" \
--scenarios "artifacts/{ID}/states.json" \
--out "artifacts/{ID}/exports" \
--formats html,pf-spec
```
**D. Optional export helper** (artifact writes + local Eval)
```bash
node "${CLAUDE_SKILL_DIR}/scripts/export-helper.mjs" \
--out ".artifacts/{ID}/exports"
```
Listens on `127.0.0.1:9417`. Bar POSTs captures here when healthy; otherwise the browser downloads (including on Pages). `GET /evals/{ID}/` serves `.artifacts/{ID}/eval/evaluation-report.html`.
**E. Sync bar config for static Pages**
```bash
node "${CLAUDE_SKILL_DIR}/scripts/sync-prototype-bar-config.mjs" \
--artifacts ".artifacts/{ID}"
bash "${CLAUDE_SKILL_DIR}/scripts/copy-eval-for-pages.sh" \
--artifacts ".artifacts/{ID}" \
--pages-root public
```
Sync merges Sources and flattens `states.json` into `prototype-bar.json`. `copy-eval-for-pages` copies the report to `public/evals/{ID}/index.html` and sets `views.eval` to `/evals/{ID}/`.
## Step 2: Confirm Outputs
Report paths to the user. Static HTML is a **visual** snapshot — it does not rehydrate React. Point implementation agents at `implementation-spec.json`.
## Prototype Bar
| Zone | Controls |
|------|----------|
| Left | Brand + **Sources** (outcome / RFE / Figma / description) |
| Center | **Prototype \| Eval** + **State ▾** (enabled when ≥2 scenarios match the route) |
| Right | **Export** (Static HTML \| Component tree \| PF spec) + status |
Eval resolution: helper `/evals/{id}/` when healthy → else `views.eval` under `<base href>` then site root → else disabled. State switching sets `?state=<id>` and reloads; pages read `window.UxdScenario.get()`.
Shared capture: `scripts/serialize-page.js` and `templates/serialize-page.browser.js`.
## Guardrails
- **Ask which path** when the user only says "export."
- **Do not treat static HTML as a live app** — it is a snapshot.
- **Batch export needs a live URL** and Playwright; install-bar does not.
- **Eval on Pages** requires copying the report into `public/evals/{ID}/` — the Export menu is client-side capture, not those pre-baked files.
## Reference Docs
| Doc | When to load |
|-----|-------------|
| [export-formats.md](references/export-formats.md) | Format details |
| [journeys-schema.md](references/journeys-schema.md) | `journeys.json` |
| [states-schema.md](references/states-schema.md) | `states.json` |
| [prototype-bar-config.md](references/prototype-bar-config.md) | Bar config schema |
Files in this package (35)
- .gitignore 1 KB
- README.md 1 KB
- SKILL.md 7 KB
- package-lock.json 2 KB
- package.json 1 KB
- eval/eval.yaml 7 KB
- eval/cases/asks-export-path/annotations.yaml 1 KB
- eval/cases/asks-export-path/input.yaml 1 KB
- eval/cases/batch-export/annotations.yaml 1 KB
- eval/cases/batch-export/input.yaml 1 KB
- eval/cases/current-page-capture/annotations.yaml 1 KB
- eval/cases/current-page-capture/input.yaml 1 KB
- eval/cases/install-bar-pages/annotations.yaml 1 KB
- eval/cases/install-bar-pages/input.yaml 1 KB
- references/export-formats.md 4 KB
- references/journeys-schema.md 3 KB
- references/prototype-bar-config.md 7 KB
- references/states-schema.md 3 KB
- scripts/copy-eval-for-pages.sh 3 KB
- scripts/export-component-tree.js 6 KB
- scripts/export-current.sh 2 KB
- scripts/export-helper.mjs 8 KB
- scripts/export-journey.mjs 17 KB
- scripts/export-pf-spec.js 28 KB
- scripts/inject-prototype-bar-into-html.mjs 7 KB
- scripts/install-prototype-bar.sh 17 KB
- scripts/serialize-page.js 11 KB
- scripts/sync-prototype-bar-config.mjs 8 KB
- templates/PrototypeBar.tsx 24 KB
- templates/export-pf-spec.browser.js 24 KB
- templates/prototype-bar-standalone.js 24 KB
- templates/prototype-bar.css 5 KB
- templates/serialize-page.browser.js 14 KB
- templates/useUxdScenario.ts 1 KB
- templates/uxd-scenario-runtime.js 2 KB
Versions
The database has no other skills named uxd-prototype-export.
Database snapshot: 13.11.2026 · package version 4cd43da9a2cc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100uxd-prototype-create
Create or refine a UX prototype from a Jira ticket, Figma design, feature description, or rough idea. Enumerates user journeys and page states (empty/error/alternate conditions), wires mock data via ?state=, writes a design spec for QE test-plan ingest, and supports export of… - 100uxd-prototype-evaluate
Evaluate a running prototype against a Jira ticket's acceptance criteria, automatically fix what fails, then run persona-based usability walkthroughs. Produces an HTML evidence report with screenshots, scores, and findings. Use when you want to validate a prototype, check… - 100s02-09-prototype-package-export
把确认后的原型打包为可分发归档,并生成原型确认书等待用户签字确权。当用户确认原型通过、要求'打包原型/出确认书'时使用。产出 zip + 确认书 docx(G3 门禁输入)。 - 89prototype
Render a proposed redesign of a page on the current website as a self-contained static HTML file, then iterate via the impeccable craft loop. Per-page, idempotent, stale-aware. Use when the user asks for a redesign prototype, a before/after comparison, a design preview, a page… - 90prototype-design-interview
Guide a user from a vague idea to a buildable prototype design through structured interview questioning, then emit DESIGN_SPEC.md + PROMPT.md and hand off to prototype-workflow. Use this skill whenever the user wants a prototype but cannot yet describe it — e.g.… - 90prototype-guide
Defines evidence-grounded prototype quality and external-generator prompt construction. Use when generating or evaluating a prototype, or exporting a prompt for Lovable, v0, or a similar tool.