Verified:GitHub

onboard

Design onboarding and first-run flows emphasizing progressive disclosure and optional skipping.

Updated Apr 3, 2026

Search Tags:#onboarding #progressive disclosure #empty states #user activation #first-run experience #product education #UX flows

Ready to run

npx skills add https://github.com/yahya-azeem/Pokedex --skill onboard-yahya-azeem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/yahya-azeem/Pokedex/tree/main/library/impeccable/skills/onboard
Command: npx skills add https://github.com/yahya-azeem/Pokedex --skill onboard-yahya-azeem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents users from getting stuck or dropping off during first-time setup by designing onboarding that rapidly leads them to an “aha moment.”

Core Features & Use Cases

Onboarding assessment: Clarifies user challenges, experience level, success metrics, and the minimum knowledge needed for time-to-value.
Experience design: Creates initial welcome/setup flows, progressive discovery, and empty-state guidance that nudges users toward first success.
Guidance systems: Plans walkthroughs and interactive tutorials that use progressive disclosure while respecting “Skip” and repeat visits.

Quick Start

Run this skill after you have design context by invoking frontend-design, then tell it what your product does and who your first-time users are.

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 that gets users to value quickly?▼

Define the target “aha moment” and apply progressive disclosure to minimize time-to-value. This approach guides users to their first success quickly, preventing drop-off during initial product setup.

What is progressive disclosure in first-run experience design?▼

Progressive disclosure in first-run experiences reveals features gradually as users need them, preventing information overload. It allows optional skipping and respects repeat visits by pacing interactive walkthroughs.

How do I create empty states that guide users toward activation?▼

Create empty states that nudge users toward first success by providing contextual guidance and clear calls to action. This transforms blank screens into productive starting points for user activation.

Can I use interactive walkthroughs for feature adoption with repeat visitors?▼

Interactive walkthroughs support feature adoption for both first-time users and repeat visitors. They use contextual guidance and progressive disclosure while respecting optional skipping to avoid disrupting returning users.

What do I need before designing onboarding flows?▼

You need design context from a frontend-design step and a clear definition of your product and first-time users. This context clarifies user challenges, experience level, and success metrics needed for effective onboarding.