App conventions
App-side patterns cover onboarding, auth, settings, workspace flows, and product navigation. The system should feel more utility-led than marketing while still clearly belonging to the same brand.
Onboarding belongs to the app surface because the user is completing a task, not being persuaded.
Use shared fields, shared spacing, and calm helper copy.
Set the onboarding direction for the workspace.
Surface note
Use the app layer for onboarding, auth, workspace, settings, billing, and task-oriented flows.
Default to calmer tone, tighter spacing, and stronger form clarity than marketing surfaces.
Document onboarding and auth as app patterns, not marketing patterns.
Favor shared app primitives such as `PageHeader`, `SectionCard`, `Field`, and `InlineNotice`.