1.1천건 · 관련도순
Alpha Vantage — Financial Market Data workflow skill. Use this skill when the user needs Access 20+ years of global financial data: equities, options, forex, crypto, commodities, economic indicators, and 50+ technical indicators and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add runtime UI options (select/checkbox/switch/input) to MaaFramework option surfaces such as `assets/interface.json` or `assets/resource/tasks/**/*.json`. Use when adding a user-facing toggle, selector, checkbox, or input; wiring options to `pipeline_override`; aligning option paths with Python `context.get_node_data()` or CustomAction params; or reviewing option behavior across Pipeline JSON and Python.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prices FX options and exotic structures with Garman-Kohlhagen, local volatility, and stochastic volatility models. Use when pricing FX derivatives, evaluating FX options, or modeling cross-currency products.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds pricing models for barrier, Asian, lookback, and other path-dependent options with Monte Carlo simulation. Use when pricing exotic options, modeling complex payoffs, or evaluating structured product components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-Earnings Analysis — earnings date, analyst consensus estimates, 8-quarter historical surprise pattern, post-earnings price move history, options-implied expected move vs historical, key metrics to watch, and trade setup recommendations. Triggered by "trade earnings <TICKER>".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when upgrading an existing TypeScript codebase from Inngest SDK v3 to v4, or when fixing mixed v3/v4 API usage. Covers detecting current SDK usage, moving triggers into createFunction options, replacing EventSchemas with eventType/staticSchema, moving serve options to the client, updating realtime imports, rewriting step.invoke string IDs, checkpointing/serverless runtime settings, Connect option changes, and verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Apply real options analysis to value managerial flexibility embedded in investment decisions. Use this skill when the user needs to evaluate projects with significant uncertainty and flexibility, assess the value of deferring or expanding investments, compare traditional NPV with expanded NPV, or when they ask 'should we wait to invest', 'what is the option to abandon worth', or 'why does NPV undervalue this project'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when designing the checkout experience for a Salesforce B2B or D2C Commerce storefront — covering runtime model selection (LWR Managed Checkout vs Aura Flow Builder), cart and line-item requirements, payment option scoping, shipping rule definition, and guest vs. registered buyer experience design. Trigger keywords: checkout flow design, checkout UX requirements, LWR vs Aura checkout, guest checkout design, payment options design, shipping rules, checkout experience planning. NOT for configuring the checkout in Setup once designed — use admin/commerce-checkout-configuration. NOT for choosing B2B vs D2C Commerce — use admin/b2b-vs-b2c-requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Timeboxed ideation on a topic where lens-driven proposers generate structurally different ideas, blind critics cull them, and pairwise judges rank the survivors on a tournament ladder instead of 1-10 scores, evolving the leaders until the clock runs out. Use when the user wants to brainstorm, explore ideas, discover features, generate options, or think through possibilities for a specified duration. Triggers on requests like "brainstorm X for 30 minutes", "ideate on X", "spend an hour thinking about X", "what features should we build", "explore options for X". Not for executing a task over time (timeboxed-iterating) or optimizing a measurable metric (autoresearch).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstorm), extracting user intent (elicit), or reviewing already-written code (quality-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate from manual configuration binding to ASP.NET Core IOptions pattern
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a raw idea into ONE honest recommendation: interview one question at a time until the problem, requirements, goals, non-goals, and constraints are CONFIRMED, then deliver a single verdict — do, don't, cheaper alternatives, trade-offs, ordered checklist, success metrics. Required: the user wants exactly ONE recommendation — not options, not a debate — and their framing is open to challenge (advise may answer a different question than the one asked). Triggers on "what should I do about X", "advise me on X", "am I approaching this right", "is this the right move". Do NOT use to be interrogated with no recommendation (→ mk:grill) — advise also interviews one question at a time, but only to reach a verdict. Do NOT use when the framing is settled and only the options are open (→ mk:brainstorming). Do NOT use to decide whether something is worth building (→ mk:office-hours). Do NOT use when you want several perspectives to argue it out (→ mk:party).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
外部連携カタログを参照して候補を選択肢化したいとき、purpose.json を基に options.json を生成したいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Per-surface tech stack decision tables and development tooling options. Use during /create-prd-stack to present constraint-filtered options to the user.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user provides multiple options and wants a specific 16-minds (MBTI) personality to make the decision in that personality's judgment style. Triggers on Japanese phrases like 「ENTJで決めて」「INFPならどっち選ぶ」「INTJとして判断して」, English equivalents like "decide as ESTJ" / "which would ENFP pick", or 16-minds commands with a `--decide` flag. Requires both a personality and 2+ options to be present or extractable from the request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Windows アプリ開発 (WinUI 3 / Windows App SDK 2.x) のライフサイクル・ウィンドウ・ 通知・リソース・ウィジェット・配置。AppInstance, 単一インスタンス化, RichActivation, PowerManager、 AppWindow, AppWindowPresenter, OverlappedPresenter, タイトルバー, DisplayArea, Win32 相互運用、 AppNotification, Toast, PushNotificationManager, バッジ通知、ResourceManager, MRT, PRI, ローカライズ、 WidgetProvider, WidgetManager, アダプティブカード、MSIX, 自己完結型, DeploymentManager, PackageVolume, IPackageValidator (パッケージ検証), RuntimeCompatibilityOptions, SemVer, サポート期間, リリースチャネル。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude Agent SDK (code.claude.com/docs/en/agent-sdk) の TypeScript / Python リファレンス。 query(), ClaudeAgentOptions / Options, fallbackModel, maxTurns, maxBudgetUsd, custom tools (in-process MCP), createSdkMcpServer, hooks, permissions (canUseTool), subagents, sessions (resume / fork), streaming, structured outputs, Agent Skills (SKILL.md), slash commands (/compact, /clear), tool search, hosting / observability。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.