Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
889건 · 관련도순
Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Welcome and set up a new Claude for Financial Advisors user. Gets to know the advisor's RIA, learns their day-to-day pain points and tech stack, walks them through connecting their tools, explains the plugin and how skills work, runs a live pre-meeting demo, shows them how to customize skills, and closes with a personalized recommendation for which skill to try next. Use when the advisor is getting started or says any of: "onboarding," "/onboarding," "get started," "help me get started," "set up claude for financial advisors," "claude for financial advisors setup," "what can this plugin do," "I'm new to this," "show me around," or is in their first session with the plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design client onboarding for insurance. TRIGGERS - Use when user needs help with insurance-onboarding-client related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design client onboarding processes for insurance. TRIGGERS - Use when user needs help with client-onboarding-insurance related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit the developer onboarding experience — measure TTFC and find friction points. Use when asked "why do developers drop off", "audit our onboarding", or "measure time to first call".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert customer onboarding guidance for accelerating time-to-value and ensuring successful implementations. Use when designing onboarding programs, creating kickoff frameworks, building implementation plans, or optimizing customer activation. Use for training delivery, go-live readiness, sales-to-CS handoffs, early warning detection, and tech-touch automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checkout conversion', 'paywall optimization', 'activation rate', 'funnel analysis', 'why are users dropping off', 'registration flow', 'trial conversion', 'free to paid', 'upgrade flow', 'user journey', or wants to improve any multi-step user journey. If they mention steps, screens, or a sequence that leads to signup, payment, or activation, this is the skill. Even casual mentions like 'users aren't finishing signup' or 'our onboarding sucks' should trigger this. Use this instead of page-cro when the problem spans multiple screens rather than a single page.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build AI employee onboarding assistants. TRIGGERS - Use when user needs help with ai-onboarding-assistant related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design onboarding flows for AI products. TRIGGERS - Use when user needs help with ai-onboarding-flow related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create structured employee onboarding plans using the 30-60-90 day framework aligned with SHRM best practices. Cover pre-boarding, Day 1, Week 1, and monthly milestones with task owners, success criteria, and buddy assignments. Use when hiring new employees or revamping the onboarding process.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages GKE application onboarding, covering containerization, deployment manifests, and migration. Use when onboarding or deploying an application to GKE for the first time, or containerizing an app for GKE. Don't use for general GKE cluster administration or upgrades (use gke-basics or gke-upgrades instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When shaping employee onboarding — time-to-productivity, role-by-role program, mentor pairing, 30/60/90 milestones. Triggers on 'design our onboarding', 'why are new hires ramping slow'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing customer onboarding — time-to-first-value, milestone design, friction audit, drop-off diagnosis. Triggers on 'fix onboarding', 'why do new accounts churn fast'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quando o usuário quer criar ou otimizar uma sequência de email, drip campaign, fluxo de email automatizado ou programa de lifecycle email. Também use quando o usuário mencionar "sequência de email", "drip campaign", "sequência de nutrição", "emails de onboarding", "sequência de boas-vindas", "emails de reengajamento", "automação de email" ou "emails de lifecycle". Para onboarding in-app, veja onboarding-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value — "activation rate," "empty states," "onboarding checklist," "aha moment," "users sign up but don't use the product." Use when users sign up but don't stick around. For signup/registration optimization, see signup-flow-cro. For email sequences, see email-sequence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a DRAFT 30-60-90 day onboarding plan for a new hire from the role, the team context and the systems list: phase outcomes traced to the role, activities with a named owner and due window, an access and equipment request table, learning items, manager checkpoints and the items the manager must confirm. Use when the user asks to "build an onboarding plan for our new hire", "draft the induction plan for this role", "write a first 90 days plan", "put together a new starter plan with owners", "create a ramp plan from this job description" or "plan the integration of an internal mover". Do not use for writing the job description itself, use job-description-drafter instead; for interview questions or a scorecard, use interview-scorecard-builder. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Anbieterneutrales Onboarding-Protokoll für einen neuen, neu aufgesetzten oder ausgetauschten Arbeitsplatzrechner. Es richtet Betriebssystemvoraussetzungen, Agentenlaufzeiten, gemeinsame Regelflächen, portable Skills, verifizierte Konfiguration und Nachweise nach der Installation ein, ohne Zugangsdaten, private Prompts oder host-spezifische Konfiguration in ein Repository zu kopieren.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.