guiding-users
Implements onboarding and help systems including product tours, interactive tutorials, tooltips, checklists, help panels, and progressive disclosure patterns. Use when building first-time experiences, feature discovery, guided walkthroughs, contextual help, setup flows, or user activation features. Provides timing strategies, accessibility patterns (keyboard, screen readers, reduced motion), and metrics for measuring onboarding success.
What this skill does
# Guiding Users Through Onboarding and Help Systems ## Purpose This skill provides systematic patterns for onboarding users and delivering contextual help, from first-time product tours to ongoing feature discovery. It covers the complete spectrum of user guidance mechanisms, ensuring optimal user activation, feature adoption, and self-service support. ## When to Use Activate this skill when: - Building first-time user experiences or product tours - Implementing feature discovery and announcements - Creating interactive tutorials or guided tasks - Adding tooltips, hints, or contextual help - Designing setup flows or completion checklists - Building help panels or documentation systems - Implementing progressive disclosure patterns - Measuring onboarding effectiveness and user activation - Ensuring onboarding accessibility ## Quick Decision Framework Select the appropriate guidance mechanism based on user state and content type: ``` First-time user → Product Tour (step-by-step) New feature launch → Feature Spotlight (tooltip + animation) Complex workflow → Interactive Tutorial (guided tasks) Account setup → Checklist (progress tracking) Contextual help needed → Tooltip/Hint system Ongoing support → Help Panel (sidebar/searchable) Feature unlock → Progressive Disclosure ``` Reference `references/selection-framework.md` for detailed selection criteria. ## Core Guidance Mechanisms ### Product Tours Step-by-step walkthroughs that guide users through key features: - Sequential spotlights with modal overlays - Progress indicators (Step 2 of 5) - Skip, Previous, and Next controls - Dismiss and resume capability - Context-sensitive activation **Implementation:** ```bash npm install react-joyride ``` See `examples/first-time-tour.tsx` for complete implementation. Reference `references/product-tours.md` for patterns and best practices. ### Feature Spotlights Announce new features to existing users: - Pulsing hotspot animations - Contextual tooltip with arrow - "Got it" acknowledgment - Auto-dismiss after first view - Non-blocking overlay See `examples/feature-spotlight.tsx` for implementation. Reference `references/tooltips-hints.md` for patterns. ### Interactive Tutorials Guided task completion with validation: - "Complete these tasks to get started" - Checkbox completion tracking - Celebration animations on completion - Sandbox mode with sample data - Undo and reset capabilities See `examples/guided-tutorial.tsx` for implementation. Reference `references/interactive-tutorials.md` for patterns. ### Setup Checklists Track multi-step onboarding progress: - Visual progress indicators (3/4 complete) - Direct links to each task - Profile completion percentages - Achievement badges and gamification - Persistent until completed See `examples/setup-checklist.tsx` for implementation. Reference `references/checklists.md` for patterns. ### Contextual Tooltips and Hints Just-in-time help when users need it: - Hover or click-triggered tooltips - Progressive hint levels (1, 2, 3) - "Need help?" assistance triggers - Context-aware suggestions - Keyboard-accessible See `examples/contextual-help.tsx` for implementation. Reference `references/tooltips-hints.md` for complete patterns. ### Help Panels Comprehensive help systems: - Sidebar or drawer interface - Contextual help based on current page - Search help articles and docs - Video tutorials and demos - Contact support integration - Collapsible and resizable See `examples/help-panel.tsx` for implementation. Reference `references/help-systems.md` for patterns. ## Timing and Triggering Strategies ### When to Show Onboarding Appropriate triggers: - First login (always) - Immediately after signup - New feature launch (to existing users) - User appears stuck (smart triggering based on inactivity) - User explicitly requests help ### When NOT to Show Onboarding Avoid showing when: - User is mid-task or focused - Shown in every session (becomes annoying) - Before allowing free exploration - Tour exceeds 7 steps (too long) - User already dismissed or completed **Auto-dismiss timing:** - Simple tooltips: 5-7 seconds - Feature announcements: 10-15 seconds or manual dismiss - Tours: User-controlled, no auto-dismiss - Persistent hints: Until user acknowledges Reference `references/timing-strategies.md` for detailed guidelines. ## Progressive Disclosure Patterns Show only what's needed, when it's needed: **Techniques:** 1. **Accordion Help**: Collapsed by default, expand for details 2. **"Learn More" Links**: Deep dive content optional 3. **Advanced Settings**: Hidden behind "Show advanced" toggle 4. **Gradual Feature Introduction**: Unlock features as user progresses 5. **Contextual Hints**: Show based on user actions Reference `references/progressive-disclosure.md` for implementation patterns. ## Accessibility Requirements ### Keyboard Navigation Essential keyboard support: - Tab through tour steps and controls - ESC to dismiss tours and tooltips - Arrow keys for Previous/Next navigation - Enter/Space to activate buttons - Focus visible indicators ### Screen Reader Support ARIA patterns for announcements: - Announce step number and total (Step 2 of 5) - Read tooltip and help content - Describe highlighted UI elements - Announce progress completion - Alert on errors or blockers ### Reduced Motion Respect `prefers-reduced-motion`: - Disable pulsing animations - Use instant transitions instead of animations - Remove parallax and complex effects - Maintain functionality without motion To validate accessibility: ```bash node scripts/validate_accessibility.js ``` Reference `references/accessibility-patterns.md` for complete implementation. ## Library Recommendations ### Primary: react-joyride (Feature-Rich, Accessible) **Library:** `/gilbarbara/react-joyride` **Trust Score:** 9.6/10 **Code Snippets:** 29+ Best for comprehensive product tours: - WAI-ARIA compliant out of the box - Full keyboard navigation support - Highly customizable styling - Programmatic control - Localization support - Active maintenance ```bash npm install react-joyride ``` See `examples/joyride-tour.tsx` for complete setup. ### Alternative: driver.js (Lightweight, Modern) Best for minimal bundle size: - Vanilla JavaScript (framework agnostic) - ~5KB gzipped - Modern API design - No dependencies ```bash npm install driver.js ``` ### Alternative: intro.js (Classic, Proven) Best for traditional tours: - Battle-tested library - Wide browser support - JSON-based tour configuration - Extensive plugin ecosystem ```bash npm install intro.js ``` Reference `references/library-comparison.md` for detailed analysis and selection criteria. ## Design Token Integration All onboarding components use the design-tokens skill for consistent theming: **Token categories used:** - **Colors**: Tour spotlight, overlay, tooltip backgrounds, hotspot colors - **Spacing**: Tour padding, tooltip spacing, arrow size - **Typography**: Title sizes, body text, help content - **Borders**: Border radius for modals and tooltips - **Shadows**: Elevation for tour spotlights and tooltips - **Motion**: Transition durations, pulse animations Supports light, dark, high-contrast, and custom brand themes. Reference the design-tokens skill for complete theming documentation. ## Measuring Success ### Key Metrics Track these indicators: - Tour completion rate (target: >60%) - Time to first value (faster = better) - Feature adoption rate post-tour - Support ticket reduction - User activation rate (completed key actions) - Drop-off points in tours ### Optimization Strategies Iterate based on data: - A/B test tour length (shorter often better) - Test different messaging and copy - Measure drop-off at each step - Simplify steps with high abandonment - Add skip options for returning users - Personalize based on user type To analyze onboarding metrics: ```bash python scripts/analyze_onboarding_met
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.