onboard

Design onboarding experiences with empty states, tooltips, and guided tours.

Updated Aug 8, 2021
One-click install
npx skills add https://github.com/luanzeba/dotfiles --skill onboard-luanzeba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/luanzeba/dotfiles/tree/main/skills/onboard
Command: npx skills add https://github.com/luanzeba/dotfiles --skill onboard-luanzeba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding design that helps new users understand how to use the product, reduces confusion, and speeds up time-to-value by guiding them to early success.

Core Features & Use Cases

  • Assess onboarding needs and identify critical moments that drive activation.
  • Design empty states, contextual tooltips, progressive onboarding, guided tours, and interactive tutorials.
  • Provide in-product help, documentation patterns, and templates to support learning and adoption.

Quick Start

Identify the target user and define a concrete onboarding objective for the product.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I design onboarding experiences that reduce user drop-off?

Progressive onboarding incrementally reveals features through interactive tutorials and in-product help, preventing cognitive overload. It accelerates user adoption by guiding users to early success rather than overwhelming them with upfront documentation.

What is the best way to implement contextual tooltips for first-use guidance?

The best way to implement contextual tooltips is to assess onboarding needs and target critical moments that drive activation. This clarifies product value by providing in-product help exactly when users need it during complex workflows.

How do I create interactive tutorials and guided tours for product adoption?

Create interactive tutorials by defining a concrete onboarding objective for your target user, then applying scalable templates. These guided tours support learning and adoption by walking users through complex workflows to reduce confusion.

Can I use empty states to improve user adoption in complex workflows?

Yes, empty states improve user adoption by guiding users toward early success when they first encounter the product. Designing effective empty states clarifies value and reduces time-to-value across complex workflows without requiring external documentation.

When do I need progressive onboarding instead of standard guided tours?

You need progressive onboarding when complex workflows require contextual learning over time, rather than upfront tours. It reduces cognitive overload by incrementally revealing features through in-product help, driving activation without overwhelming new users.