From ticket-auto-pipeline
Navigation hint lookup for browser-based ticket work. Returns exact click-by-click paths to reach feature areas without direct URL navigation (which breaks Angular session state). Use when ticket-verify or ticket-reproduce needs to navigate the app, or when the user asks "how do I get to X in the app".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ticket-auto-pipeline:nav-hintsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have been given an area name as the argument (e.g. `progress`, `payments`, `correspondents`). Return the exact click-by-click navigation path to reach that area. **Never use `page.goto()` for in-app navigation** — always click through the UI because Angular loses session state on full page reload.
You have been given an area name as the argument (e.g. progress, payments, correspondents). Return the exact click-by-click navigation path to reach that area. Never use page.goto() for in-app navigation — always click through the UI because Angular loses session state on full page reload.
| Usage | Purpose |
|---|---|
/nav-hints <area> | Return the click path for <area>. Fuzzy matches if exact not found. |
/nav-hints add | Record a new hint. Prompts for area name, path, and steps. Appends to the project hints file. |
/nav-hints list | Print all known areas for the current project. |
If no argument: print all known areas.
Read {TICKETS_ROOT}/nav-hints.md in the current working directory. If missing, create it from the template below.
{TICKETS_ROOT} is the current working directory (must be tickets).
If <area> provided:
/nav-hints add after successful navigation to record it."If add:
/handover-progress/{id})"{TICKETS_ROOT}/nav-hints.md in the format below./nav-hints {area}."If list or no argument:
For the matched hint, print:
## {Area Name}
**URL pattern:** {path}
**How to reach:**
1. {step 1}
2. {step 2}
...
**Learned from:** {ticket IDs}
The calling skill (verify/reproduce) uses these steps verbatim to execute Playwright clicks.
{TICKETS_ROOT}/nav-hints.md:
# Navigation Hints — {PROJECT_NAME}
Hints are learned during ticket verification and reproduction sessions.
Never hand-edit — use `/nav-hints add` to append.
## {Area Name}
- **Path:** {URL pattern, e.g. `/handover-payment/{id}`}
- **How to reach:** {numbered click-by-click steps}
- **Learned from:** {TICKET-ID}
- **Date:** {YYYY-MM-DD}
Template for new files:
# Navigation Hints — {PROJECT_NAME}
Hints are learned during ticket verification and reproduction sessions.
Never hand-edit — use `/nav-hints add` to append.
## Handover List
- **Path:** `/handover`
- **How to reach:** Click "Handovers" in the nav bar. Default filter is "Active" (which = LEGAL state for Attorney users). If nav bar doesn't show Handovers link after login, log in again — first login sometimes fails to update nav (see app-knowledge Known Quirks).
- **Learned from:** CRE-39, CRE-43
- **Date:** 2026-05-05
page.goto().{TICKETS_ROOT}/nav-hints.md, one per tickets workspace.npx claudepluginhub willard-pro/claude-plugins --plugin ticket-auto-pipelineGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.