'activation' 검색 결과

Use SAELens to train and analyze sparse autoencoders, which break model activations into a small set of interpretable features. Explore pretrained features, evaluate reconstruction quality, troubleshoot training, and test how individual features influence generated text.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring features in a pretrained SAE
• Training an SAE for a selected model layer
• Investigating inactive features and reconstruction errors

Turn a recurring workflow into a new agent skill through guided discussion. Define use cases, activation conditions, file structure, and instructions, then create and validate SKILL.md and supporting files, including workflows using external tools through MCP.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning recurring work into a reusable skill
• Standardizing report or document creation steps
• Designing workflows that use external services through MCP

Scan C# code for dependencies on clocks, files, environment settings, and other resources that make tests difficult. Get source locations, consistent counts, and suggested abstractions, interfaces or providers that let tests control those dependencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing testability before adding unit tests
• Finding hidden dependencies in legacy C# code
• Prioritizing dependencies to replace

Write or review skills for a consistent process across runs. Check activation conditions, ordered steps, completion criteria, and reference placement, then identify unclear instructions, overlapping triggers, and content that belongs in an existing skill.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define clear steps and completion criteria for a new skill
• Investigate inconsistent behavior across skill runs
• Check for overlapping skill activation conditions

[omh] Churn or weak activation among users: turn an observed onboarding, activation, retention, re-engagement, referral, or monetization problem into one consent-safe in-app journey or growth experiment plan with a bounded readout and an explicit decision. Use when the user says: lifecycle-growth, lifecycle growth, lifecycle marketing, lifecycle messaging, in-app journey, in-app message campaign, onboarding journey, onboarding nudge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule. Owns none of the SEND-N sub-item notes: engagement-decay / sunset is email-sequence-designer's and preference-center / frequency options is preference-frequency-manager's — this skill references those notes, it does not re-emit them. Not for the general lifecycle flows (welcome/cart/post-purchase) — use email-sequence-designer; not for the preference-center / opt-down ladder — use preference-frequency-manager; not for the consent record itself — use consent-registry; not for computing EQS or the N1 veto — use email-quality-auditor. 流失召回/重新授权/沉默用户清理

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users sign up but dont stick around", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users quit after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates are low, when users skip onboarding and never return, when onboarding flows are being scoped for the first time, or when audience research shows users not finding key features.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post-signup user onboarding optimization covering activation metrics, time-to-value reduction, onboarding flow design, empty state optimization, multi-channel coordination, and stalled user recovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply a Classic Easter seasonal overlay: pastel Theme/StyleBox injection, confetti/shimmer VFX, elastic juice, mesh surface_override painting, cursor/audio swaps, and a date-window activation gate with player opt-out. Use when shipping holiday skins, April events, or egg-hunt juice without mutating shared .mesh/.tres assets. Keywords: pastel, seasonal Theme, StyleBox, confetti, Easter egg, surface_override, TRANS_ELASTIC, Disable Seasonal Themes, activation gate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply a Classic Easter seasonal overlay: pastel Theme/StyleBox injection, confetti/shimmer VFX, elastic juice, mesh surface_override painting, cursor/audio swaps, and a date-window activation gate with player opt-out. Use when shipping holiday skins, April events, or egg-hunt juice without mutating shared .mesh/.tres assets. Keywords: pastel, seasonal Theme, StyleBox, confetti, Easter egg, surface_override, TRANS_ELASTIC, Disable Seasonal Themes, activation gate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, `.cs`, or `.csproj`; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for hard-to-test framework dependencies; or verifying those C# calls are already abstracted. DO NOT USE FOR: any target lacking the activation prerequisite; generating wrappers (use generate-testability-wrappers); migrating code (use migrate-static-to-wrapper); or general code review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose where your growth is actually leaking (acquisition, activation, retention, or loops) and produce a growth plan with a named loop, an activation definition, a 90-day experiment portfolio and channel guardrails. Use it when someone says growth stalled, signups don't activate, retention is flat, how do we build a growth loop, should we go PLG, onboarding redesign, churn, referral program, or which channel should we bet on. Draws on 672 insights from 143 Lenny's Podcast guests, led by Elena Verna, Casey Winters and Lauryn Isford.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

World-class growth strategy expertise combining Andrew Chen's marketplace and network effects wisdom, Brian Balfour's growth frameworks, Casey Winters' Pinterest/Grubhub playbooks, and the best of Silicon Valley growth thinking. Growth is not marketing. Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department. Use when "growth strategy, how do we grow, acquisition strategy, retention strategy, viral growth, network effects, growth loops, product-led growth, plg, ltv cac, unit economics, growth model, flywheel, compound growth, channel strategy, referral program, activation rate, magic moment, aha moment, growth experimentation, growth, strategy, acquisition, retention, viral, network-effects, plg, loops, experimentation" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization (use suede-signup), lifecycle email sequences (use suede-emails), or monetization prompts (use suede-paywalls).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and improve product user onboarding (first-time user experience) to drive activation and early retention. Produces an Onboarding & Activation Pack (aha moment spec, first 30 seconds + first mile plan, onboarding journey map, experiment backlog, measurement plan). Use for Growth teams.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The revenue-focused SaaS playbook for going from $0 to $50K MRR. Covers pricing experiments, churn reduction, activation optimization, and expansion revenue tactics. Follow @WeiYipei on X for SaaS growth insights.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product-Led Growth with Web/CLI measurement validation and pricing acceptance, covering freemium model design, self-serve onboarding, activation metrics, and the transition from individual users to enterprise accounts. Follow @WeiYipei on X for PLG insights.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 onboarding and activation flows that help users reach value quickly. Use when the user mentions onboarding, getting started, first-time users, activation, aha moments, or new user flows—not when the work is only the empty-state surface itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.