prowler-tour
Report-only. This skill never edits tour files or UI files; it inspects
the change, reports drift it finds between tours and the covered UI, and
recommends actions for the developer to apply.
Early-exit rule
Run this check first. Most UI edits are not tour-related — exit cheaply.
Glob ui/lib/tours/*.tour.ts.
For each tour, check whether any coversFiles glob pattern matches any
file in the current change.
If no tour matches, respond exactly:
No tour affected — skipping alignment check
and exit. Do not proceed to the checklist.
If at least one tour matches, continue to "Drift checklist" for that tour.
Drift checklist
For each affected tour, evaluate every item. Skip items that obviously do
not apply, but list explicitly which items were checked.
- Orphan selectors — every step's
target (which composes to
data-tour-id="<tour-id>-<step.target>") must resolve to a real element
in the codebase. Grep ui/ for the expected attribute value; report
any step whose target is missing.
- Renamed selectors — a
data-tour-id attribute was edited in this
change. Match it back to any tour step referencing the old value.
- Outdated copy — a popover
title/description references a button
label, heading, or term that no longer exists on the covered page.
- Obsolete steps — a step describes a section, panel, or workflow
that was removed.
- Missing steps — a new feature was added on the covered surface
without a corresponding step (e.g. a new panel, a new primary action,
a new wizard stage).
- Reordered flow — the user's path through the feature changed (e.g.
query builder moved before scan selection) and the step order no
longer reflects it.
Version-bump decision tree
Apply per tour after listing drift:
- NO bump when the change is cosmetic. Examples: fix a typo, soften
copy, rename a
data-tour-id selector while keeping the same step,
swap one screenshot for another, tighten wording.
- BUMP
version when the user-visible flow changes materially.
Examples: a new step was added or removed; the order changed; an
anchored target was retargeted to a different panel; the tour now
covers a new feature on the surface.
When in doubt, ask: "Would a user who already saw the previous version
miss something useful by not seeing this one?" If yes, bump.
Output format
When emitting a report, follow the exact structure in
references/output-format.md. The structure is mandatory because the
report is consumed downstream and tolerates no field reordering.
What this skill MUST NOT do
- Do not edit
*.tour.ts files. This skill is report-only.
- Do not edit UI files to add or rename
data-tour-id attributes.
- Do not invent new tours. Authoring a new tour is a separate, deliberate
decision — the developer makes it, not the skill.
- Do not flag drift in tours whose
coversFiles do not match any file
in the current change. Stick to the early-exit rule.
See also
references/output-format.md — exact report template (read when
emitting a report).references/tours-architecture.md — code map for the tour abstraction
under ui/lib/tours/.assets/tour-template.ts — boilerplate for authoring a new *.tour.ts.
1---2name: prowler-tour3description: Keeps product-tour definitions aligned with the UI features they describe. Trigger: When modifying UI components that have associated tours, editing tour definition files, or renaming data-tour-id attributes.4license: Apache-2.05---6
7# prowler-tour
8
9**Report-only.** This skill never edits tour files or UI files; it inspects
10the change, reports drift it finds between tours and the covered UI, and
11recommends actions for the developer to apply.
12
13## Early-exit rule
14
15Run this check first. Most UI edits are not tour-related — exit cheaply.
16
171. Glob `ui/lib/tours/*.tour.ts`.
182. For each tour, check whether any `coversFiles` glob pattern matches any
19 file in the current change.
203. If no tour matches, respond **exactly**:
21
22 > No tour affected — skipping alignment check
23
24 and exit. Do not proceed to the checklist.
254. If at least one tour matches, continue to "Drift checklist" for that tour.
26
27## Drift checklist
28
29For each affected tour, evaluate every item. Skip items that obviously do
30not apply, but list explicitly which items were checked.
31
321. **Orphan selectors** — every step's `target` (which composes to
33 `data-tour-id="<tour-id>-<step.target>"`) must resolve to a real element
34 in the codebase. Grep `ui/` for the expected attribute value; report
35 any step whose target is missing.
362. **Renamed selectors** — a `data-tour-id` attribute was edited in this
37 change. Match it back to any tour step referencing the old value.
383. **Outdated copy** — a popover `title`/`description` references a button
39 label, heading, or term that no longer exists on the covered page.
404. **Obsolete steps** — a step describes a section, panel, or workflow
41 that was removed.
425. **Missing steps** — a new feature was added on the covered surface
43 without a corresponding step (e.g. a new panel, a new primary action,
44 a new wizard stage).
456. **Reordered flow** — the user's path through the feature changed (e.g.
46 query builder moved before scan selection) and the step order no
47 longer reflects it.
48
49## Version-bump decision tree
50
51Apply per tour after listing drift:
52
53- **NO bump** when the change is cosmetic. Examples: fix a typo, soften
54 copy, rename a `data-tour-id` selector while keeping the same step,
55 swap one screenshot for another, tighten wording.
56- **BUMP `version`** when the user-visible flow changes materially.
57 Examples: a new step was added or removed; the order changed; an
58 anchored target was retargeted to a different panel; the tour now
59 covers a new feature on the surface.
60
61When in doubt, ask: "Would a user who already saw the previous version
62miss something useful by not seeing this one?" If yes, bump.
63
64## Output format
65
66When emitting a report, follow the exact structure in
67`references/output-format.md`. The structure is mandatory because the
68report is consumed downstream and tolerates no field reordering.
69
70## What this skill MUST NOT do
71
72- Do not edit `*.tour.ts` files. This skill is report-only.
73- Do not edit UI files to add or rename `data-tour-id` attributes.
74- Do not invent new tours. Authoring a new tour is a separate, deliberate
75 decision — the developer makes it, not the skill.
76- Do not flag drift in tours whose `coversFiles` do not match any file
77 in the current change. Stick to the early-exit rule.
78
79## See also
80
81- `references/output-format.md` — exact report template (read when
82 emitting a report).
83- `references/tours-architecture.md` — code map for the tour abstraction
84 under `ui/lib/tours/`.
85- `assets/tour-template.ts` — boilerplate for authoring a new `*.tour.ts`.
prowler-cloud