비즈니스 스킬

Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.

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

Redis caching patterns, cache-aside, write-through, TTL strategies, and invalidation. Activate on: caching, Redis, cache invalidation, cache-aside, write-through, TTL, CDN cache, stale-while-revalidate. NOT for: CDN/reverse proxy setup (use api-gateway-reverse-proxy-expert), database query optimization (use data-warehouse-optimizer).

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

Design or review a declared control-command profile and its verb/backend lifecycle matrix. Distinguish policy denial, unsupported capability, delivery acknowledgement, independently observed effect, and unknown outcome; bind authorization to principal, target, scope, current policy, expiry, and fencing epoch. NOT for claiming runtime correctness, proving an adapter from declarations, or approving a control-panel button without independent runtime evidence.

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

Locate CCSPointScript_OnCustomHudClicked in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSPointScript_OnCustomHudClicked" (symbol CCSPointScript_OnCustomHudClicked). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSPointScript_OnCustomHudClicked, CCSPointScript_OnCustomHudClicked

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

Locate CCSCustomHudLayout_SetDialogVariableStringForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableStringForPlayer" (symbol CCSCustomHudLayout_SetDialogVariableStringForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableStringForPlayer, CCSCustomHudLayout_SetDialogVariableStringForPlayer

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

Locate CCSCustomHudLayout_SetHasClass in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClass" (symbol CCSCustomHudLayout_SetHasClass). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClass, CCSCustomHudLayout_SetHasClass

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

Locate CCSCustomHudLayout_SetDialogVariableString in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableString" (symbol CCSCustomHudLayout_SetDialogVariableString). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableString, CCSCustomHudLayout_SetDialogVariableString

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

Locate CCSCustomHudLayout_SetInputCaptureEnabled in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetInputCaptureEnabled" (symbol CCSCustomHudLayout_SetInputCaptureEnabled). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetInputCaptureEnabled, CCSCustomHudLayout_SetInputCaptureEnabled

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

Locate CCSCustomHudLayout_SetHasClassForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClassForPlayer" (symbol CCSCustomHudLayout_SetHasClassForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClassForPlayer, CCSCustomHudLayout_SetHasClassForPlayer

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

Locate CBaseEntity_EmitSoundFilter_SoundName in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CBaseEntity_EmitSoundFilter_SoundName" (symbol CBaseEntity_EmitSoundFilter_SoundName). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CBaseEntity_EmitSoundFilter_SoundName, CBaseEntity_EmitSoundFilter_SoundName

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

サブエージェントを活用した並列実行・調査委譲・コンテキスト管理の戦略。複雑な問題への対処、調査・探索タスク、複数の選択肢の比較検討、大規模なリファクタリングなどでこのスキルを参照する。「調べて」「比較して」「並列で」「複数のアプローチを試して」といったリクエストや、メインのコンテキストが肥大化しそうな場面で使う。

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

自己完結した実装仕様書を作成する。Gate 単位で Goal / Constraints / Acceptance Criteria を契約として明示し、実装エージェントに委任できる形で渡す。Trigger: 仕様書を作成, /dev:spec, 実装計画, 実装仕様

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

仕様書（docs/PLAN/{YYMMDD}_{slug}/）の実行プロトコル。Gate 単位で契約（Goal/Constraints/AC）を実装エージェントに渡し、AC ベースで完了を判定する。Trigger: 仕様書を実行, /dev:spec-run, 計画書の実行

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

返品承認、受入検査、処分判断、返金処理、不正検出、保証請求管理に関する体系化された 専門知識。15年以上の経験を持つ返品オペレーションマネージャーの知見に基づく。 グレーディングフレームワーク、処分経済学、不正パターン認識、ベンダー回収プロセスを含む。 製品返品、リバースロジスティクス、返金判断、返品不正検出、または保証請求を扱う際に使用します。

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

Review local git changes from a PMBOK-based product management perspective. Analyzes changes against 7 PMBOK knowledge areas: Scope, Risk, Stakeholder, Quality, Integration, Schedule, and Resource management. Produces a structured report identifying project-level impacts and risks. The PMBOK analyst role itself lives in the `pm-review:pm-review` subagent; this skill is a thin orchestrator that gathers the change set and project context before delegating. Use when the user asks for a PM review, product management review, PMBOK analysis, project impact assessment, scope review, risk review, or stakeholder impact analysis of local changes. Trigger phrases include "pm review", "product management review", "PMBOK review", "project impact", "scope review", "risk review", "stakeholder impact", "pm-review", "review from PM perspective", "project management review".

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

Gathers a tax year's records into a packet for the person's preparer or tax software: candidate records grouped and tagged, gaps and missing receipts listed, and the questions a preparer will ask. Use when the person says "get my taxes ready", "what can I deduct", "pull my business expenses", "charitable donations", "medical expenses", "1099 income", or asks what their accountant needs. It organizes records and never decides what is deductible.

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

Opens the person's Candor workspace, says where their money stands, and routes to the right Candor workflow. Use when the person asks about their money, spending, balances, bills, debts, goals, or plans and no more specific Candor skill fits, including a quick question about a balance, a bill, or a charge, or a life decision that costs or earns money even when money is not named.

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

Makes the person's records read right: fixes categories, splits mixed purchases, writes rules so a merchant always means the same thing, tags money a goal tracks, and curates which charges repeat. Use when the person says a category is wrong, asks to clean up or organize transactions, explains what a merchant is, wants a side business or trip tracked, or asks to tidy subscriptions and bills on the recurring list. For price increases or stopping a charge, use candor-find-money.

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

Runs an adviser-style review of the person's whole financial life from their Candor records, covering spending leaks, debt and credit, cash and reserves, goals and budget, investments and retirement, benefits, and insurance, and ends with the one to three things most worth doing. Use when the person asks to review their finances, for a financial checkup or annual review, what they should focus on or what to fix first, or after a life event. For a weekly what-changed check or a quick how-am-I-doing, use candor-weekly-check-in.

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

Use when a partner QBR or business review is coming: grade the quarter against benchmarks, co-draft the agenda, ship the pre-read, land the recap.

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

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.

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

Use when owning how a region or category wins: go-to-market strategy, operating model, market entry, and category ownership.

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

Set up a vendor purchase from business need through evidence, approval, renewal, and owner tracking.

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

Use when the user names a release, a launch date, a pricing change, or enablement for sales or success: the tier call, the messaging doc, the enablement pack, dated owners working back from launch day, the go/no-go gate, and the 90-day measure.

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