Loading...
Loading...
Found 10,205 Skills
꿈 해몽 앱 첫 사용자 온보딩 5단계 패턴 (환영·기능 소개·맥락별 권한 요청·동의·첫 꿈 입력 안내). react-joyride·intro.js-react·shepherd.js·@reactour/tour·직접 구현 비교, 마이크/알림 *맥락 시점* 권한 요청, 학술 한계(의학·심리학 진단 아님 / 민속학적 자료) 사용자 친화 변환, 위기 자원 사전 안내, 페르소나 분기(일반·청소년·전문가), 스킵·재방문 UX, 접근성, 측정 지표, 흔한 함정을 다룬다. <example>사용자: "꿈 해몽 앱에 첫 사용자 온보딩을 어떤 라이브러리로 만들지?"</example> <example>사용자: "온보딩에 학술 한계 고지를 어떻게 부드럽게 넣을 수 있어?"</example> <example>사용자: "권한 요청을 온보딩 어디에 배치해야 거부율이 낮아져?"</example>
OpenTelemetry in .NET — DI/builder SDK setup (OpenTelemetry.Extensions.Hosting, AddOpenTelemetry, UseOtlpExporter, OpenTelemetrySdk.Create), native .NET instrumentation APIs (ActivitySource, System.Diagnostics.Metrics Meter) plus logging abstractions (ILogger), zero-code CLR-profiler agent, contrib instrumentation packages, performance tuning, and breaking-change audits. Use when adding, reviewing, or configuring OpenTelemetry in a .NET or ASP.NET Core service. Triggers on "setup otel in dotnet", "dotnet telemetry", ".net tracing", "ASP.NET Core opentelemetry", "AddOpenTelemetry", "UseOtlpExporter", "OpenTelemetrySdk.Create", "ActivitySource", "System.Diagnostics.Metrics Meter", "ILogger opentelemetry", "OpenTelemetry.Extensions.Hosting", "opentelemetry-dotnet-instrumentation", or any C# OTel question.
Simplify an already-bounded code or documentation area without changing intended behavior. Use for deletion, direct-flow refactors, wrapper or branch reduction, clearer data models, reduced mutable state, or concrete simplification findings; use improve-architecture when the opportunity or design is still unclear.
Use this skill when constructing visual hierarchy through color and tone (value, contrast, saturation) — picking which elements get full-color emphasis and which recede into greys, building a tone ladder, and deciding when color should *be* the hierarchy versus when it should *support* a size/weight hierarchy. Trigger when picking the primary color, building a neutral palette, designing a status badge system, or fixing a UI where color is "too loud" or "too flat." Sub-aspect of the broader `hierarchy` principle; read that first if you haven't already.
Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP / verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. Sub-aspect of `chunking`; read that first.