Results for “onboarding”

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

The English summary is being prepared. Showing the original description.

Creates comprehensive developer onboarding documentation and materials including step-by-step setup guides, first-task assignments, expected time per step, common troubleshooting, team introductions, and code walkthrough tours. Use when preparing "new developer onboarding", "first day setup", "junior dev training", or "team member onboarding".

The English summary is being prepared. Showing the original description.

Create CodeTour files that guide readers through a codebase step by step, with verified file and line references. Tailor the walkthrough to new contributors, architecture readers, PR reviewers, or investigators tracing a failure or security boundary.

• Creating onboarding walkthroughs for new maintainers
• Explaining architecture and feature execution paths
• Guiding reviewers through PR changes

Explore an unfamiliar codebase and turn its structure, request flow, and development conventions into a concise onboarding guide. Create or update CLAUDE.md with project-specific instructions, preserving existing guidance and identifying findings that remain uncertain.

• Understanding an unfamiliar project when joining a team
• Setting up Claude Code in an existing repository
• Creating CLAUDE.md from detected project conventions

Map a mobile app journey across three or four phone frames in one HTML board. Simple gray content blocks, dashed arrows, numbered actions, and short annotations show how users move between screens before detailed visual design.

• Mapping onboarding through the home screen
• Reviewing the path from item details to confirmation
• Discussing screen transitions before visual design

Create an HTML workshop deck for new users of a project management app. Organize training around first useful results and ongoing habits, using a warm pastel template with hand-drawn decorations.

• Preparing onboarding workshops for new customers
• Explaining the path to a first useful result
• Teaching habits for continued app use

Create an onboarding guide for new project members from a knowledge graph, a map of project components. The Markdown guide covers architecture, key concepts, a suggested learning path, important files, and areas that need extra care.

• Preparing a guide for new team members
• Organizing project architecture and key files
• Planning a codebase walkthrough

Review account registration and free trial signup flows to find obstacles in fields, authentication, and error messages. Get prioritized recommendations and test ideas to reduce abandonment and help more people complete registration.

• Investigating where users abandon registration
• Reducing required signup fields
• Improving mobile signup forms

Apply a firm's customer verification and anti-money-laundering rules to structured onboarding records. Produce risk ratings, rule-by-rule findings, missing-document lists, and review routing with supporting evidence, while leaving approval to human reviewers.

• Rating onboarding risk under firm rules
• Checking for missing or expired documents
• Recording evidence for each rule outcome

Extract identity, ownership, control, and source-of-funds details from investor or client onboarding documents into a structured JSON record. Inventory the submitted documents and flag obvious missing or expired items before passing the information to KYC screening rules.

• Organize investor onboarding documents
• Extract beneficial owners and controlling persons
• Check for missing or expired documents

Review signup and trial registration flows to identify obstacles to completion. The skill produces prioritized recommendations for fields, authentication, wording, and layout, plus measurement plans and A/B test ideas for checking proposed improvements.

• Investigating signup drop-off
• Reviewing required registration fields
• Improving mobile signup usability

Turn applications into a ranked shortlist using only the job’s stated criteria, with evidence for each score. Prepare candidate replies, coordinate interview times, and create an onboarding checklist while leaving hiring decisions to the owner.

• Shortlisting applicants against the job’s stated criteria
• Drafting interview invitations and rejection replies
• Coordinating interview times

Create a role-specific onboarding plan for a new hire, covering accounts, equipment, a buddy, and the first week's activities. Include key contacts, required tool access, and goals for the first 30, 60, and 90 days.

• Preparing a checklist before a new hire starts
• Planning Day 1 and the first week
• Setting goals for the first 30, 60, and 90 days

Write and maintain technical documents for different readers, including READMEs, API references, operational procedures, architecture explanations, and onboarding guides. Organize practical examples, setup steps, design decisions, and recovery instructions around what each audience needs.

• Create a README with a quick start
• Document API requests and responses
• Write operational and rollback procedures

Write and review interface text, including button labels, error messages, empty screens, and onboarding instructions. Get recommended wording, alternatives, and explanations tailored to the user's situation, tone, and character limits.

• Choosing clear button labels
• Rewriting error messages with recovery steps
• Guiding users through empty screens

Design email sequences for welcoming subscribers, nurturing leads, following up after purchases, or re-engaging inactive readers. Produce complete drafts with subject lines, send timing, audience conditions, and a measurement plan, then check sequence quality.

• Creating welcome emails for new subscribers
• Planning a lead nurture sequence
• Re-engaging inactive subscribers

Map repeatable business processes by owner and analyze time spent working, waiting, or reworking. Using stage-level timing data, produce a process diagram, ranked bottlenecks, and cycle-time measures to focus improvements on the main constraint.

• Documenting procurement and employee onboarding workflows
• Identifying bottlenecks in slow business processes
• Making waits between teams visible

Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.

• Setting up a local NemoClaw development environment
• Checking readiness before starting development
• Repairing local dependency, build, or hook problems

Guides an application’s first deployment to GKE, Google’s managed Kubernetes service. Covers application assessment, container creation, image storage, deployment configuration, security settings, health checks, and verification that the application is running.

• Deploying an existing application to GKE for the first time
• Creating a Dockerfile and registering a container image
• Preparing deployment configuration with health checks

Set up Wren Engine through guided steps covering environment checks, installation, database connection, and project creation. Prepare data definitions and validate the setup, then suggest initial questions to help the user begin exploring their data.

• Installing Wren Engine for the first time
• Connecting a new database to Wren
• Creating a project and preparing data definitions

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

• Reproducing a first-run setup problem
• Inspecting menus in a narrow terminal
• Checking help text and command visibility

Prepare an existing codebase for GSD planning by mapping its structure, ingesting documentation, and initializing project records. The workflow creates or confirms planning files and produces an onboarding summary with findings and the next command to run.

• Preparing an existing project for GSD
• Organizing code findings and existing documentation
• Setting up requirements and a roadmap before implementation

Write and review interface text, including button labels, error messages, empty screens, and onboarding instructions. Get recommended wording, alternatives, and explanations tailored to the user's situation, tone, and character limits.

• Choosing clear button labels
• Rewriting error messages with recovery steps
• Guiding users through empty screens

Write and maintain technical documents for different readers, including READMEs, API references, operational procedures, architecture explanations, and onboarding guides. Organize practical examples, setup steps, design decisions, and recovery instructions around what each audience needs.

• Create a README with a quick start
• Document API requests and responses
• Write operational and rollback procedures