skills.rest
navikt
naviktOFFICIAL
Explore all skills by this author →
WebsiteGitHub

onboard

Design onboarding experiences with empty states, guided tours, and progressive disclosure.

1|1|Updated Feb 2, 2026
Search Tags:#onboarding#design-principles#progressive-disclosure#empty-states#guided-tours#contextual-help#user-onboarding
One-click install
npx skills add https://github.com/navikt/watson-sak-frontend --skill onboard-navikt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/navikt/watson-sak-frontend/tree/main/.agents/skills/onboard
Command: npx skills add https://github.com/navikt/watson-sak-frontend --skill onboard-navikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding design and optimization helps users understand, adopt, and realize value from your product quickly, reducing time-to-first-value and confusion.

Core Features & Use Cases

  • Empty state design: craft compelling first impressions and guides for new users.
  • Guided tours, contextual tooltips, and progressive disclosure to teach features at the moment of need.
  • Use case planning and templates to ensure consistent onboarding across product areas, teams, and user personas.

Quick Start

Outline a practical onboarding flow for a feature area and specify the first three user actions to guide adoption.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is progressive disclosure in user onboarding and when should I use it?▼

Progressive disclosure in user onboarding reveals features at the moment of need to prevent information overload. You should use it to teach complex product areas progressively, ensuring users adopt features without friction or confusion.

How do I design empty states that guide new users to value?▼

Design empty states by crafting compelling first impressions and actionable guides for new users. Use this onboarding space to outline practical flows and specify the first three user actions required to accelerate time-to-first-value.

What's the best way to plan onboarding flows across different product areas?▼

The best way to plan onboarding across product areas is using use case templates and documented principles. This ensures consistent, optional, and user-friendly onboarding across diverse teams and user personas.

How do I measure if my user onboarding experience is effective?▼

Measure user onboarding effectiveness by documenting measurable outcomes and tracking time-to-first-value. Evaluate guided tours and contextual hints against these metrics to ensure they consistently accelerate user value.

When should I not use guided tours for product onboarding?▼

Avoid guided tours when they disrupt user autonomy or fail to provide contextual help at the moment of need. Ensure onboarding remains optional and user-friendly, relying on progressive disclosure instead of forced linear sequences.

Related Skills

Explore More Design & Creative Skills→
Productfculty-aipmProductfculty-aipm
70

journey-mapping

Map end-to-end user journeys with touchpoints, emotions, and friction points.

Community
Advanced
alexzhang1030alexzhang1030

i-onboard

Design onboarding flows, empty states, and guided tours for mixed-experience users.

Community
Intermediate
brianiumbrianium

fx-bootstrap

Set up Sandestin effect dispatch wiring in a new Clojure project.

Community
Advanced
OneWave-AIOneWave-AI
245

knowledge-base-builder

Generate knowledge-base articles with FAQs and tutorials from support tickets.

Official
Basic