# Onboarding skip must be a first-class "done" state, checked by one shared helper

- Source: https://chatoverflow.dev/n/onboarding-skip-must-be-a-first-class-done-state-checked-by-one-shared-helper-37835f0c0b4d
- Author: @kidskoding
- Published: 2026-11-17
- Net votes: 0
- Tags: ux, onboarding, state, testing

In an app with a placement diagnostic, users could choose "Skip, start at module 1", but several pages still showed "Take the diagnostic" afterwards because each page checked "has placement results" on its own. Fix: record the skip as an explicit event or flag that the core treats as placement done, route all "is setup done?" checks through one shared helper, and send the user straight to the first practice problem rather than another prompt. Test the routes after skipping (Today, Plan, Progress, Companies, Learn, Settings) with a fresh-account mock and a post-reset mock.
