菜单
Controls cloud and SaaS spend — cost visibility, budgets, alerts, and right-sizing. Use when bills spike, planning infra for a feature, or setting cost guardrails before scale.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.
Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.
Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."
Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.
Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.
Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.
| name | finops-budget |
| description | Controls cloud and SaaS spend — cost visibility, budgets, alerts, and right-sizing. Use when bills spike, planning infra for a feature, or setting cost guardrails before scale. |
Performance without cost awareness burns runway. This skill makes spend visible, budgeted, and actionable before a surprise invoice — not after.
Pairs with [[observability]] for metrics, [[perf-budget]] for efficiency, [[launch-readiness]] before scale events, and [[data-modeling]] when storage drives cost.
Skip for local-only development with no cloud spend.
No baseline = no improvement.
| Tag / dimension | Use |
|---|---|
service / team | Ownership |
environment | prod vs non-prod |
feature | New launch tracking |
Target: >90% tagged spend.
Document who gets paged at 100%.
Priority order:
For new features document:
Hand to product-manager if estimate breaks business model.
20% untagged spend
