Skill Detail
Turn shipped features into clear, trusted customer journeys.
A customer-experience skill for UX/UI clarity, friction, trust, first-success paths, onboarding, setup sequencing, recoverable states, docs coherence, and proof routing.
Problem
Features can work technically while users still miss the value, distrust the flow, hesitate on the next action, grant permissions in the wrong order, skip setup without recovery, or never reach the first meaningful success moment.
Outcome
You get an end-user contract that explains the target user, first-success path, UX/UI clarity, friction, trust, state semantics, recovery paths, onboarding/setup impact, proof route, and docs/editorial impact.
Why It Matters
End-user clarity is product leverage. It helps every user, technical or not, understand what to do next, trust the path, and see why the product was built for them.
Arguments
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
audit [scope]Finds evidence-backed comprehension, friction, trust, state, and recovery issues in an existing journey.
Routes each finding to the proper owner and proof lane.
flow [feature-or-flow]Creates an End-User Contract with first success, states, recovery, documentation impact, and proof route.
Useful before implementation or after a shipped change.
onboarding [feature-or-flow]Plans first-run setup, progressive disclosure, dependency order, optionality, and re-entry.
Loads the overlay pattern only for an explicitly requested stepped overlay.
recovery [feature-or-state]Creates a safe resume, defer, and recheck path for blocked, revoked, failed, or lost-context states.
Keeps a user in control without hiding permission, billing, privacy, or data consequences.
Related Skills
One design skill, with explicit modes and rigorous playbooks.
The single public design entrypoint for system creation, playgrounds, UI/token/component/accessibility audits, implementation, proof, verification, and shipping.
Open skill pageRun non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill pageGuide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Open skill pageCreate or repair documentation so the repo stays navigable for both humans and agents.
A documentation skill for maintaining docs, metadata, and governance-layout compliance across project surfaces.
Open skill pageManage content work through one lifecycle instead of guessing which writing, audit, docs, or SEO skill to launch.
A master content lifecycle skill for routing strategy, repurposing, drafting, enrichment, audits, public-content governance, validation, and ship readiness through the right owner skills.
Open skill pageOpen a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.