onboard

Design onboarding flows, empty states, and first-time user experiences for product interfaces.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/WeWake1/BSOMS --skill onboard-wewake1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/WeWake1/BSOMS/tree/main/.agents/skills/onboard
Command: npx skills add https://github.com/WeWake1/BSOMS --skill onboard-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users often abandon products because they cannot reach value quickly or understand core features. This Skill provides structured guidance for designing onboarding experiences, empty states, and feature discovery patterns that get users to their "aha moment" faster. ## Core Features & Use Cases - Onboarding Flow Design: Create welcome screens, account setup flows, and guided first-success experiences with progressive disclosure. - Empty State Design: Turn blank screens into actionable starting points with clear value propositions, CTAs, and templates. - Feature Discovery Patterns: Implement contextual tooltips, guided tours, and feature announcements using libraries like Intro.js, Shepherd.js, or React Joyride. - Use Case: A team building a project management app uses this Skill to design a three-step onboarding flow, an empty state for the projects page, and a dismissible tooltip system that tracks completion in localStorage. ## Quick Start Ask the AI to design an onboarding flow for your product's dashboard, including the welcome screen, first-user empty states, and a skippable guided tour.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I design an onboarding flow for a new product?▼

Start by identifying the aha moment users should reach, then build a welcome screen with a clear value proposition, minimal account setup, and a guided first success. Keep it to 1-3 core concepts, make it skippable, and front-load the 20% of features that deliver 80% of value.

What should an empty state include in a web app?▼

An empty state needs four elements: what will appear there, why it matters, a clear call to action like creating a first item or starting from a template, and visual interest such as an illustration. Optionally add contextual help like a short tutorial link.

Which JavaScript libraries work for product tours and tooltips?▼

For guided tours, use Intro.js, Shepherd.js, or React Joyride. For tooltips, Tippy.js and Popper.js are common choices. Keep tours to 3-7 steps, spotlight specific UI elements, and always include a skip option.

How do I prevent showing the same onboarding twice?▼

Track completion and dismissal state in localStorage, for example setting flags like onboarding-completed or per-feature tooltip-seen keys. Check these flags before rendering any tour or tooltip so returning users never see repeated onboarding.

When should I use a guided tour versus contextual tooltips?▼

Use guided tours for complex interfaces with many features or major product changes. Use contextual tooltips for individual feature discovery at the point of use. Prefer progressive, contextual teaching over upfront tours whenever possible.