Results for “onboarding”

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Scans legacy codebases to extract implicit coding conventions across architecture dimensions, resolves conflicts interactively, and generates an enforceable style rules file.

Conversion-focused product copy for Nick's apps. Use when writing landing page copy, CTA text, onboarding copy, trust-building messaging, feature explanations, pricing language, or microcopy that needs to drive clarity and action.

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.

Write user-facing copy following Sentry's brand guidelines, covering Plain Speech and Sentry Voice tones for UI text, documentation, and marketing content.

Maps, documents, and onboards into an existing codebase by generating seven structured documents covering stack, structure, architecture, conventions, integrations, testing, and concerns.

Sync Claude Code AI tooling (skills, MCP servers, rules) across Warp, Cursor, and VSCode. Idempotent — safe to re-run. Use when onboarding a new editor, after adding MCP servers, or when standards files change.

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

Full project analysis for an unfamiliar Sage/Acorn/Lando project — discovers CPTs, routes, ACF field groups, Livewire components, Service Providers, active plans, installed packages; produces a structured project overview with health status and recommended next steps. Invoke for: "/onboarding", "I'm new to this project", "what does this project do", "show me what exists", "project overview", "orient me to this codebase", "what exists in this project". Skip when: you already know the project — the session-start hook already provided basic stack info; invoke the target skill directly instead.

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

Guides Directors and senior product leaders through the transition to VP or CPO with adaptive coaching across preparing, interviewing, landing, and recalibrating.

Systematic analysis of Google Ads and Meta advertising spend to identify wasted budget. Produces actionable exclusion lists with thematic categorization and statistical validation. Use when onboarding new accounts, performing monthly hygiene, or preparing for budget optimization.

Use when designing AI product first-run or blank-slate UX — chat empty state, example prompts, capability discovery, templates, nudges, or follow-ups. Trigger on "users don't know what to ask", onboarding, suggestion chips, or discoverability.

Generates structured summaries of Non-Disclosure Agreements, extracting parties, confidential information scope, permitted disclosures, term/survival, breach remedies, and risk flags. Use when summarizing NDAs, reviewing confidentiality agreements, distilling NDA obligations, or onboarding stakeholders to NDA terms.

Guides users through an interactive tour of the context-matic MCP server, explaining its purpose and demonstrating all available APIs with live tool calls.

Design user journeys and task flows for a product concept or MVP. Use when the team needs primary flows, branch conditions, edge cases, onboarding paths, and end-to-end user movement before screen planning or UI implementation.

At the start of a session, reads the session baton file to restate the goal and next task, and opens any doc listed under "Read first" before confirming the next step with the user.

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email...

Configure Warp terminal to share Claude Code's MCP servers and AI rules via File-based MCP + AGENTS.md. One-time UI toggles plus file sync. Use when onboarding Warp or after a Warp update resets settings.

COO planning lead. Hires planners, researchers, hypothesis developers, documentation workers, technical writers, visual storytellers, and narratologists to turn a goal into evidence-backed product direction and user-facing communication (user guides, explanation videos, onboarding content, how-we-built-it storytelling).

Drafts U.S. employee non-disclosure/confidentiality agreements that protect employer trade secrets and proprietary information while preserving employee mobility. Triggers on: employee NDA, confidentiality agreement, non-disclosure agreement, trade secret protection, proprietary information, onboarding confidentiality clause, pre-employment NDA.

Use when the team needs a repeatable multi-step workflow, pipeline, or operating sequence that connects multiple skills, systems, or product stages. Trigger on requests to design a workflow from idea to launch, onboarding to retention, or request to execution.

Design product-led growth loops, activation paths, and expansion mechanics for a software product. Use when the team needs onboarding-to-value planning, sharing or collaboration loops, retention hooks, or realistic post-launch growth motions tied to product usage.

Sets up Google's agents-cli toolkit and guides through the full agent development lifecycle: scaffold, build, evaluate, deploy, publish, and monitor on Gemini Enterprise Agent Platform.

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

Guide for the first days with a new human. Use when: the `init` memory block exists (pointing you here), you have no persona/communication blocks yet, or a human explicitly asks about setup. This skill is about having good conversations — not filling out forms.

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

Analyze codebase structure, generate domain-specific sub-skills (UI, Backend, Database, etc.), and create agent-guidance files to help AI agents navigate and develop consistently within a project. Use when onboarding to a new codebase, creating project documentation, or setting up agent guidance systems.

Drafts a Proprietary Information and Inventions Agreement (PIIA) for employment or consulting relationships. Covers confidentiality, invention assignment with state-law carve-outs, DTSA immunity notice, and prior inventions disclosure. Trigger when onboarding employees/consultants, drafting IP assignment agreements, or creating confidentiality and invention assignment contracts.

Discover and inventory privileged accounts across enterprise infrastructure, including domain admins, local admins, service accounts, database admins, cloud IAM roles, and application admin accounts, with automated scanning, risk classification, and PAM onboarding.

Audit documentation against actual code behavior and plan corrections — no rewrites in this pass. Use when asked to "docs drift", "sync docs with code", "audit documentation", "stale README", "onboarding docs broken", "doc sync plan", "phantom docs", or "docs out of date". Why-we-chose-X / ADRs → docs-adr.

Use to map support contacts onto the product lifecycle, interpret contact as a lifecycle signal, and avoid journey-map theatre. Trigger for "customer journey map support", "contact by lifecycle stage", onboarding support drivers, churn and support overlap, stage-specific contact reasons, or when journey mapping is worth doing.

Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity, or when a SOUL.md is missing. Also trigger for updates such as "update my SOUL.md", "change my AI's personality", or "tweak the soul".

Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.