'ref' 검색 결과

Use this skill when the user is operating the DOCA Firefly Service container on BlueField — picking the four PTP configuration axes (role / profile / domain / interface), wiring the BlueField PHC + host follower + consumer workload pairing, deciding whether PTP-grade time is even needed (vs. chrony / NTP), or debugging a Firefly deployment where PTP isn't syncing or the host clock isn't following. Trigger even when the user does not explicitly mention "DOCA Firefly" or "PTP" — typical implicit phrasings include "container green but PTP never advances past LISTENING", "Firefly says synced but the host clock still drifts", "sync acquired but offset is tens of microseconds", "my Rivermax SMPTE workload needs PTP", or "is chrony good enough". Refuse and route elsewhere for installing DOCA, host-side chrony / ptp4l config bodies, PTP topology / boundary-clock design, building DOCA apps that read the disciplined PHC, or other DOCA services (DMS, Flow-Inspector, HBN) — those belong to other skills.

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

When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn", "viral loop", "viral coefficient", "K-factor", "double-sided rewards", "give X get X", "referral rewards", "invite link", "share sheet", "Branch referrals", "in-app invites", or "how to make my app go viral". For deep link infrastructure that referrals depend on, see attribution-setup. For organic content-driven virality (UGC, creator), see creator-ugc-marketing.

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

Use when checking whether a manuscript's references are real. Audits each citation against PubMed and CrossRef, flags fabricated or mismatched entries and writes qc/reference_audit.json. Audit-only; never edits references or refs.bib. Citation-key checks are /manage-refs.

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

Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named refactorings, and the full suite re-run after every step. Use when the user wants to refactor, restructure, clean up, simplify, or improve the design of existing code, or to apply refactoring recommendations from a code-review or architectural-analysis report. This skill changes code; it does not review code (use code-review), assess architecture (use architectural-analysis), plan a multi-module restructure before executing it (use plan-a-change), map domain boundaries before restructuring along them (use ddd-analysis), or build new behavior test-first (use tdd). Do not use it on code inside an active tdd loop; the refactor step of tdd owns that cleanup. Runs its planned sequence to completion without pausing for review; to review each named refactoring as it lands, use pairing.

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

Fix Riverpod "Cannot use Ref or modify other providers inside life-cycles/selectors" crash in @riverpod provider bodies. Use when: (1) Crash during provider disposal with this exact error message, (2) Using keepAlive() with timer-based disposal, (3) Async callbacks (.then, .catchError) try to use ref.read() or ref.invalidateSelf(), (4) Error occurs after ref.onCancel/onResume/onDispose callbacks fire. Solution: wrap ref operations in try-catch or avoid using ref in async callbacks entirely.

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

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

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

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

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

Find and fix broken internal links, dead external URLs, stale imports, missing cross-references, and orphaned files. Ensures all project references remain valid and up-to-date. Use when documentation contains broken internal links, external URLs return 404 errors, import statements reference moved or deleted modules, cross-references between files are out of sync, or files exist but are never referenced anywhere in the project. Also use in index mode for a directory of markdown notes with a designated index, such as an agent-memory store, where an orphan is a file the index does not link to.

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

Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.

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

Use this skill when configuring Health Cloud referral management: setting up ClinicalServiceRequest-based referrals, provider search, referral status workflows, and network management. NOT for referrals in Financial Services Cloud — use admin/fsc-referral-management. NOT for care team workflow and transition-of-care design — use admin/care-coordination-requirements.

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

Use when designing or reviewing Salesforce sandbox topology, refresh cadence, masking, and environment purpose. Triggers: 'Developer sandbox', 'Developer Pro', 'Partial Copy', 'Full sandbox', 'sandbox refresh', 'data masking', 'test environment', 'Gov Cloud sandbox'. NOT for how many environments a program needs and how they map to branches - use devops/environment-strategy. NOT for re-seeding reference data after a refresh - use data/sandbox-refresh-data-strategies. Also covers: SandboxPostCopy Apex class, SandboxInfo and SandboxProcess Tooling API, SandboxSettings metadata, sandbox topology table, refresh calendar.

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

Prefab / Scene / Asset を壊さず編集する。preflight 診断 → dry-run 差分 → confirm + change_reason 監査 → runtime 検証の 4 段ゲートを 1 経路で踏む。 トリガー: パッチ適用、Prefab Variant 編集、`set_property` / `patch_apply` / `revert_overrides` を伴う変更全般。

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

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

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

Help teams prepare materials for an SCF referral. Use when a team wants to approach a referrer (SCF Pilot, SDF staff, alumni who completed deliverables, ambassador, or ecosystem partner) with a strong package that makes it easy for the referrer to evaluate and endorse them. Covers the referral form fields, what referrers assess, and how to present your project for referral.

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

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy.

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

Git履歴から作業セッションを自動検出し、ブロック単位で振り返りサマリーを生成する。 日付境界でなく、コミット間隔の空白（ギャップ）から自然な作業ブロックを識別する。 「振り返り」「作業履歴」「/dev:git-reflect」で起動。 Trigger: 振り返り, 作業振り返り, git-reflect, git振り返り, /dev:git-reflect, 最近何やった

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

このブランチ、またはこのセッションで書いた差分の全体を読み直し、用語の揺れ・古いまま残ったコメント・追従し損ねた実装 (呼び出し元・対になる箇所・テスト・文書) を探して、裏の取れたものを直す。「差分全体を見直して」「用語の揺れや更新漏れが無いか見て」「refresh-on-session」「/refresh-on-session」で発火。バグ探しは code-review、ディレクトリの文書と実体の一括照合は claude-md-refresh、issue 本文の書き戻しは issue-writeback の担当。

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

ディレクトリ・レイヤーごとに置いた CLAUDE.md と README.md が実体 (コード・コマンド・構成) とずれていないかを点検し、裏の取れた乖離だけを直す。引数で対象のディレクトリを任意に指定できる (省略時は repo 全体)。「CLAUDE.md を refresh して」「README が古くないか見て」「claude-md-refresh」「/claude-md-refresh」で発火。issues/ の更新漏れは issue-writeback / issue-sync の担当で、この skill は扱わない。

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

Coordinate code refactoring, restructuring code while preserving its behavior. Check existing tests before changes, work in small steps, review the result, and pause for approval of the plan and before committing.

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

• Extracting a module without changing behavior
• Removing duplicate or unused code
• Reducing nesting and clarifying names

가중치가 공개된 언어 모델의 응답 거부 원리를 분석하고 재학습 없이 가중치를 수정하는 실험을 돕습니다. 환경에 맞는 모델과 방법을 선택하고 수정 전후의 거부율과 답변 품질을 비교합니다.

• 언어 모델의 응답 거부 원리 연구
• 재학습 없이 가중치 수정 실험
• 계산 환경에 맞는 모델과 방법 선택

화면 배치와 정보 순서를 검토할 흑백 SVG 와이어프레임을 만들고, 여러 화면의 흐름과 주석, 한곳에서 확대해 볼 수 있는 정적 검토 페이지도 제공합니다.

• 구현 전에 화면 배치를 검토합니다
• 모바일과 데스크톱 화면 구성을 확인합니다
• 여러 화면에 걸친 흐름을 정리합니다

화면 구성을 검토할 수 있도록 손으로 그린 듯한 HTML 와이어프레임을 만듭니다. 모눈종이, 메모지, 대략적인 차트와 안별 탭 라벨로 초기 구상을 시각화합니다.

• 포털이나 대시보드의 초기 구성을 검토합니다
• 여러 안을 탭 라벨로 표시합니다
• 화면 초안에 검토용 주석을 붙입니다

Check and fix hreflang tags, which identify language and regional versions of web pages for search engines. Review rendered HTML and HTTP responses to find missing reciprocal links, incorrect language codes, and fallback settings.

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

• Auditing language and regional page settings
• Checking reciprocal links between language versions
• Reviewing fallback page settings

Review HTML to find important fonts, images, and scripts discovered late during loading. Suggest resource hints, instructions that start fetching or connecting earlier, and check the final markup delivered to the browser.

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

• Reviewing preload hints for important fonts and images
• Checking early connections to third-party domains
• Auditing resource hints in rendered HTML