1.8 KiB
1.8 KiB
type, title, description, tags, timestamp, story_id, status
| type | title | description | tags | timestamp | story_id | status | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| User Story | Complete first-time onboarding | New users establish their preferred identity and first Minecraft account. |
|
2026-08-01T18:43:58Z | US-003 | verified |
User Story
As a newly authenticated player, I want a guided setup flow, so that my preferred name, Minecraft identity, and Discord nickname are configured correctly.
Acceptance Criteria
- Given a new Discord user, when they enter the portal, then they receive a personalized welcome.
- Given the first onboarding step, when the user enters a valid preferred name, then it is stored for their profile.
- Given the Minecraft step, when a valid Java username is submitted from an allowed network, then it is verified and added as primary.
- Given an unverifiable but syntactically valid username, then the user must explicitly confirm before continuing.
- Given a name and primary account, then the expected Discord nickname is previewed before any guild update.
- Given confirmation and a successful Discord update, then onboarding is marked complete and the dashboard opens.
Implementation
apps/web/src/app/welcome/page.tsxapps/web/src/app/welcome/minecraft/page.tsxapps/web/src/app/welcome/discord/page.tsxapps/web/src/app/welcome/actions.ts
Validation
Onboarding routes are protected by database-backed sessions and included in production route generation.