Results for “user-journey-audit”

Use this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.

Manage user journey mapper operations. Auto-activating skill for Visual Content. Triggers on: user journey mapper, user journey mapper Part of the Visual Content skill category. Use when working with user journey mapper functionality. Trigger with phrases like "user journey mapper", "user mapper", "user".

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Create user acceptance test journeys from a target user's perspective, with role-based scenarios, acceptance criteria, and evidence capture

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Exploratory ("monkey") QA of a live app as GUEST then LOGGED-IN, then diff. Headed playwright-cli, junk inputs, nav abuse. Use when "monkey test the app", "exploratory QA", "wander like a confused user", or "guest vs logged in". Story CRUD → test-qa. Hostile sweep → test-red-team. This-diff PDCA → test-playwright.

Trace every user-facing button through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI inconsistent.

Audits WordPress plugin or theme PHP code for common security mistakes including missing nonce checks, capability checks, input sanitization, output escaping, SQL preparation, AJAX exposure, file traversal, and unsafe redirects.