onboard

Design onboarding flows and guidelines with YAML frontmatter and resource directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design or improve onboarding experiences that help users understand and adopt the product quickly, reducing time-to-value and confusion.

Core Features & Use Cases

  • Onboarding audits and design guidelines to identify friction points in new-user journeys.
  • Principles (Show, Don't Tell; Time to Value; Context Over Ceremony; Respect User Intelligence) applied to real product contexts.
  • Design strategies for Initial Product Onboarding, Feature Discovery & Adoption, Guided Tours, Interactive Tutorials, and Empty State Design.

Quick Start

Draft a targeted onboarding plan, define welcome and core concepts, and test with real users.

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 time-to-value for new users?

Design onboarding flows by applying principles like Show Don't Tell and Time to Value to accelerate user value. This involves auditing new-user journeys to identify friction points and creating targeted strategies for initial product onboarding and feature adoption.

What is the best way to improve empty state design and feature discovery adoption?

Improve empty state design and feature adoption by applying Context Over Ceremony and Respect User Intelligence principles. Design interactive tutorials and guided tours that provide immediate context, helping users understand core concepts without unnecessary overhead.

How do I audit an existing product onboarding journey to find friction points?

Audit onboarding journeys by mapping new-user flows against established design guidelines to pinpoint confusion. Evaluate initial product onboarding, feature discovery, and first-use moments to identify where users drop off or experience delayed value realization.

Can I use this onboarding design approach for both initial product onboarding and feature discovery?

Yes, you can use this approach for both initial product onboarding and feature discovery. The design guidelines cover guided tours, interactive tutorials, and empty state design, ensuring consistent user experience strategies across various feature adoption and first-use moments.

Do I need specific scripts or assets to define onboarding guidelines for my product?

You need a YAML frontmatter with at least a name and description to define onboarding guidelines. The approach optionally supports loading operational instructions from resource directories including scripts, references, and assets to help draft your targeted onboarding plan.

Why does my new user activation drop off during first-use moments?

New user activation drops during first-use moments when onboarding lacks clear context or delays time-to-value. Applying design principles like Show Don't Tell helps create interactive tutorials and empty states that quickly demonstrate core product value and reduce confusion.