onboard

Design onboarding flows and empty-state guidance for first-run experiences.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Gyanano/Bower --skill onboard-gyanano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/Gyanano/Bower/tree/main/.agents/skills/onboard
Command: npx skills add https://github.com/Gyanano/Bower --skill onboard-gyanano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often suffer from drop-off because onboarding flows, empty states, and first-run guidance overload users or feel unnecessary, so new customers never reach the aha moment and activation falters. This Skill refocuses onboarding on the minimal, contextual learning that unlocks product value quickly while keeping advanced features discoverable later.

Core Features & Use Cases

  • Assess Onboarding Needs: Invoke /frontend-design and, if no context exists, /teach-impeccable before gathering the user challenge, desired aha moment, experience level, motivation, and time commitment to tailor the first-run experience.
  • Principles & Empty-State Messaging: Follow show-don't-tell storytelling, make onboarding optional, prioritize time-to-value, respect user intelligence, and turn empty states into invitations with clear value statements, CTAs, and optional templated starts.
  • Implementation Patterns & Validation: Recommend targeted tooltips, progressive disclosures, guided tours, interactive tutorials, or contextual help, and describe how to measure success via completion rate, skip rate, and time-to-value metrics.

Quick Start

Describe the onboarding context, the aha moment you want, and the user experience level to onboard so it can craft the next steps.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I design onboarding flows that reduce activation drop-off?

Design onboarding flows by focusing on minimal, contextual learning that unlocks product value quickly. Prioritize time-to-value, make guidance optional, and use progressive disclosures to keep advanced features discoverable later without overloading new users.

What is the best way to turn empty states into actionable user guidance?

Turn empty states into invitations by providing clear value statements, strong calls-to-action, and optional templated starts. Effective empty-state messaging respects user intelligence and guides users toward their aha moment rather than just displaying a blank screen.

How do I measure the success of first-run experiences and guided tours?

Measure first-run experience success by tracking completion rate, skip rate, and time-to-value metrics. These validation metrics reveal whether your guided tours, targeted tooltips, and interactive tutorials are effectively helping users reach the desired aha moment.

What context do I need to provide before generating onboarding principles and CTAs?

Provide explicit context about the target user, their experience level, the desired aha moment, and any confusing spots. This context is required to tailor the first-run experience and recommend appropriate instructional patterns and activation sequences.

When should I use progressive disclosure instead of a full guided tour for user activation?

Use progressive disclosure and targeted tooltips when you need to prioritize time-to-value and make onboarding optional. Reserve full guided tours and interactive tutorials for complex workflows requiring sequential context, ensuring advanced features remain discoverable later.