product-tour-onboarding-ui Weapon
Procedural arsenal for product-tour-onboarding-ui-guardian, the Angel that owns the in-app guided-experience layer.
This weapon is organized around the seven action verbs from the Command Brief: qualify the tour stack, select a platform, implement components, wire segment triggers, build the checklist UI, establish a maintenance protocol, and produce a tour health report.
The weapon's three non-negotiables (from guides/00-principles.md):
- Stable anchors first. Never target an element by CSS class or text if you can add a
data-tour attribute. Classes change; data-tour attributes are a contract.
- Qualify before recommending. Run the four-axis decision framework (cost, code-depth, team size, DOM stability) before naming a platform.
- Tour maintenance is code maintenance. A tour without a selector registry and CI smoke test is technical debt from day one.
When this weapon applies
Load this weapon when product-tour-onboarding-ui-guardian is invoked. Trigger scenarios:
- User wants to add a product tour to a React/Next.js app.
- User is deciding between Userpilot, Appcues, Userflow, Pendo, Driver.js, or Shepherd.js.
- Tours are breaking after UI changes (selector drift problem).
- User wants to show different tours to different user segments.
- User wants to add an onboarding checklist with progress gamification.
- User wants to audit existing tours for health and effectiveness.
Do NOT load for:
- Onboarding email sequences (out of scope — no Angel owns this yet).
- User authentication flows (auth-guardian).
- Design token system for tour tooltip styling (ux-ui-guardian).
- Analytics funnel instrumentation for tour events (posthog/mixpanel Angels).
- Database schema for user-progress storage (db-guardian).
First action when this weapon is loaded
Read these files in order before producing any output:
guides/00-principles.md — the three non-negotiables and the foreman's boundary; read on every invocation.guides/01-platform-selection.md — the four-axis decision framework for tool selection; required before any platform recommendation.- The guide(s) that match the user's specific task (see the guide index below).
Guide index
| Guide |
When to read |
guides/00-principles.md |
Every invocation |
guides/01-platform-selection.md |
Any platform recommendation or comparison |
guides/02-tooltip-modal-hotspot.md |
Implementing tour component UI (tooltips, modals, hotspots, spotlights) |
guides/03-driver-js-shepherd-js.md |
Code-first open-source implementation (Driver.js or Shepherd.js) |
guides/04-segment-triggers.md |
Wiring tour trigger logic or segment conditions |
guides/05-checklist-activation.md |
Onboarding checklist UI, progress gamification, activation milestones |
guides/06-maintenance-and-drift.md |
Tour breakage diagnosis, selector hygiene, CI integration |
Worked examples
examples/happy-path-driver-js.md — end-to-end implementation of a three-step product tour with Driver.js 9.x + React + data-tour anchors + localStorage persistence.examples/saas-platform-audit.md — walkthrough of the qualification checklist applied to a 2,000-MAU SaaS startup choosing between Userpilot, Userflow, and Driver.js.
Output templates
templates/tour-audit-report.md — the tour health report template; produced for every standalone audit.templates/data-tour-registry.json — the selector registry template; populate one entry per interactive element targeted by any tour.
Critical directives (lifted from the Command Brief)
- Select stable element anchors (
data-tour attributes) over class or text selectors. CSS class names change with every CSS-in-JS rebuild; data-tour is a durable engineering contract. See guides/06-maintenance-and-drift.md.
- Never recommend a tour platform without running the qualification checklist first. Wrong-tool selection costs months of migration. The checklist lives in
guides/01-platform-selection.md.
- Treat tour maintenance as code maintenance. A tour without a CI smoke test and selector registry will break silently. The maintenance protocol is
guides/06-maintenance-and-drift.md.
- Route visual polish to
ux-ui-guardian. Tour tooltip/modal CSS must consume the product's design tokens; a parallel custom-CSS system in the tour layer is a maintenance trap.
- Do not instrument analytics yourself. Flag what needs tracking; route to the appropriate analytics Angel.
Research foundation
All factual claims in this weapon's guides trace to files in research/external/. The research index is at research/index.md. The summary of the five most influential sources is at research/research-summary.md. Refresh annually or on a major platform version bump.
Key sources:
- Platform pricing + features:
research/external/2026-05-20-saas-platform-comparison.md
- OSS library comparison:
research/external/2026-05-20-oss-tour-libraries.md
- Maintenance + drift prevention:
research/external/2026-05-20-tour-maintenance-unbreakable.md
- Segment triggers:
research/external/2026-05-20-segment-triggers-feature-flags.md
- Checklist activation:
research/external/2026-05-20-checklist-activation-gamification.md
- Shepherd.js integration:
research/external/2026-05-20-shepherdjs-react-integration.md
- Driver.js integration:
research/external/2026-05-20-driverjs-react-integration.md
- Tour analytics ROI:
research/external/2026-05-20-tour-analytics-effectiveness.md
Forged by weapon-forge from product-tour-onboarding-ui-guardian-command-brief.md and research/. Part of the Legion AI Tools Factory.
1---2name: product-tour-onboarding-ui-weapon3description: In-app product tour and onboarding UI specialist. Selects the right tour tool (Userpilot, Appcues, Userflow, Pendo Guides, Driver.js, Shepherd.js, Intro.js), implements tooltip/modal/hotspot/checklist components, wires segment-based trigger logic, and establishes a tour maintenance protocol that survives iterative UI changes. Invoke when the user says "set up a product tour", "build an onboarding checklist", "compare Driver.js vs Shepherd.js", "our tours keep breaking after deploys", "which product tour tool should we use", "add segment-based tour triggers", or "our tour is showing to the wrong users". Do NOT invoke for broader onboarding email sequences (lifecycle-email Angel), user-auth flows (auth-guardian), design token work (ux-ui-guardian), or analytics instrumentation (posthog/mixpanel Angels).4license: MIT5---67# product-tour-onboarding-ui Weapon89Procedural arsenal for `product-tour-onboarding-ui-guardian`, the Angel that owns the in-app guided-experience layer.1011This weapon is organized around the seven action verbs from the Command Brief: qualify the tour stack, select a platform, implement components, wire segment triggers, build the checklist UI, establish a maintenance protocol, and produce a tour health report.1213**The weapon's three non-negotiables (from `guides/00-principles.md`):**14151. **Stable anchors first.** Never target an element by CSS class or text if you can add a `data-tour` attribute. Classes change; `data-tour` attributes are a contract.162. **Qualify before recommending.** Run the four-axis decision framework (cost, code-depth, team size, DOM stability) before naming a platform.173. **Tour maintenance is code maintenance.** A tour without a selector registry and CI smoke test is technical debt from day one.1819---2021## When this weapon applies2223Load this weapon when `product-tour-onboarding-ui-guardian` is invoked. Trigger scenarios:2425- User wants to add a product tour to a React/Next.js app.26- User is deciding between Userpilot, Appcues, Userflow, Pendo, Driver.js, or Shepherd.js.27- Tours are breaking after UI changes (selector drift problem).28- User wants to show different tours to different user segments.29- User wants to add an onboarding checklist with progress gamification.30- User wants to audit existing tours for health and effectiveness.3132Do NOT load for:33- Onboarding email sequences (out of scope — no Angel owns this yet).34- User authentication flows (auth-guardian).35- Design token system for tour tooltip styling (ux-ui-guardian).36- Analytics funnel instrumentation for tour events (posthog/mixpanel Angels).37- Database schema for user-progress storage (db-guardian).3839---4041## First action when this weapon is loaded4243Read these files in order before producing any output:44451. **`guides/00-principles.md`** — the three non-negotiables and the foreman's boundary; read on every invocation.462. **`guides/01-platform-selection.md`** — the four-axis decision framework for tool selection; required before any platform recommendation.473. The guide(s) that match the user's specific task (see the guide index below).4849---5051## Guide index5253| Guide | When to read |54|---|---|55| `guides/00-principles.md` | Every invocation |56| `guides/01-platform-selection.md` | Any platform recommendation or comparison |57| `guides/02-tooltip-modal-hotspot.md` | Implementing tour component UI (tooltips, modals, hotspots, spotlights) |58| `guides/03-driver-js-shepherd-js.md` | Code-first open-source implementation (Driver.js or Shepherd.js) |59| `guides/04-segment-triggers.md` | Wiring tour trigger logic or segment conditions |60| `guides/05-checklist-activation.md` | Onboarding checklist UI, progress gamification, activation milestones |61| `guides/06-maintenance-and-drift.md` | Tour breakage diagnosis, selector hygiene, CI integration |6263---6465## Worked examples6667- `examples/happy-path-driver-js.md` — end-to-end implementation of a three-step product tour with Driver.js 9.x + React + `data-tour` anchors + localStorage persistence.68- `examples/saas-platform-audit.md` — walkthrough of the qualification checklist applied to a 2,000-MAU SaaS startup choosing between Userpilot, Userflow, and Driver.js.6970---7172## Output templates7374- `templates/tour-audit-report.md` — the tour health report template; produced for every standalone audit.75- `templates/data-tour-registry.json` — the selector registry template; populate one entry per interactive element targeted by any tour.7677---7879## Critical directives (lifted from the Command Brief)8081- **Select stable element anchors (`data-tour` attributes) over class or text selectors.** CSS class names change with every CSS-in-JS rebuild; `data-tour` is a durable engineering contract. See `guides/06-maintenance-and-drift.md`.82- **Never recommend a tour platform without running the qualification checklist first.** Wrong-tool selection costs months of migration. The checklist lives in `guides/01-platform-selection.md`.83- **Treat tour maintenance as code maintenance.** A tour without a CI smoke test and selector registry will break silently. The maintenance protocol is `guides/06-maintenance-and-drift.md`.84- **Route visual polish to `ux-ui-guardian`.** Tour tooltip/modal CSS must consume the product's design tokens; a parallel custom-CSS system in the tour layer is a maintenance trap.85- **Do not instrument analytics yourself.** Flag what needs tracking; route to the appropriate analytics Angel.8687---8889## Research foundation9091All factual claims in this weapon's guides trace to files in `research/external/`. The research index is at `research/index.md`. The summary of the five most influential sources is at `research/research-summary.md`. Refresh annually or on a major platform version bump.9293Key sources:94- Platform pricing + features: `research/external/2026-05-20-saas-platform-comparison.md`95- OSS library comparison: `research/external/2026-05-20-oss-tour-libraries.md`96- Maintenance + drift prevention: `research/external/2026-05-20-tour-maintenance-unbreakable.md`97- Segment triggers: `research/external/2026-05-20-segment-triggers-feature-flags.md`98- Checklist activation: `research/external/2026-05-20-checklist-activation-gamification.md`99- Shepherd.js integration: `research/external/2026-05-20-shepherdjs-react-integration.md`100- Driver.js integration: `research/external/2026-05-20-driverjs-react-integration.md`101- Tour analytics ROI: `research/external/2026-05-20-tour-analytics-effectiveness.md`102103---104105*Forged by weapon-forge from `product-tour-onboarding-ui-guardian-command-brief.md` and `research/`. Part of the Legion AI Tools Factory.*
The-Notorious-Avengers