Menu
面向ECC的以证据为先的收入、定价、退款、团队计费和计费模型真相工作流。当用户需要销售快照、定价比较、重复收费诊断或基于代码的计费现实而非通用支付建议时使用。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use after a complex task, failure, or when reviewing what was learned. Teaches how to write growth logs that extract reusable patterns — not diary entries.
Design a goal-oriented agent loop, and review it for the ways loops go wrong — spinning and burning tokens, Goodhart-gaming the verifier, or running a wrong answer to completion. Two actions: (1) WRITE a loop — gate whether to build it, define a machine-decidable goal, pick the loop type, pick a skeleton; (2) REVIEW a loop — run it past five failure modes plus decidability, boundaries, fallback, judge independence, and keep-judgment-with-the-human red lines. Use when designing an autonomous agent loop, or when you already have one and worry it will spin, cheat, or run a wrong answer to the end. Complements the mechanism-layer loop skills (autonomous-loops, continuous-agent-loop) by covering the judgment layer they don't. 中文触发：写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不会跑飞、可判定目标、五个崩法、plan build judge。English triggers: design an agent loop, write a loop, check a loop, loop review, prevent a runaway loop, goal-oriented loop, decidable goal, plan/build/judge.
Stop hook that blocks Claude from finishing until quality checks pass. Detects rationalization patterns (surface text heuristics), stale learning logs (filesystem mtime), and low disk space. Complements self-audit by mechanically enforcing learning capture habits.
React Native and Expo app patterns — Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage. Use when building or editing React Native / Expo screens, components, navigation, or data layers.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
| name | finance-billing-ops |
| description | 面向ECC的以证据为先的收入、定价、退款、团队计费和计费模型真相工作流。当用户需要销售快照、定价比较、重复收费诊断或基于代码的计费现实而非通用支付建议时使用。 |
| origin | ECC |
当用户想要了解资金、定价、退款、团队席位逻辑，或产品是否真的如网站和销售文案所暗示的那样运作时，使用此技能。
此技能比 customer-billing-ops 更广泛。该技能用于客户补救。此技能用于运营者真相：收入状态、定价决策、团队计费以及基于代码的计费行为。
在相关时，将这些 ECC 原生技能引入工作流程：
customer-billing-ops 用于特定客户的补救和跟进research-ops 当竞争对手定价或当前市场证据重要时market-research 当答案应以定价建议结束时github-ops 当计费真相取决于兄弟仓库中的代码、待办事项或发布状态时verification-loop 当答案取决于验证结账、席位处理或权限行为时优先使用实时计费数据。如果数据不是实时的，请明确说明快照时间戳。
规范化视图：
如果问题是针对特定客户的，请先分类：
然后将其与更广泛的产品问题分开：
如果答案取决于实现真相，请检查代码路径：
报告：
快照
- 时间戳
- 收入 / 订阅 / 异常
客户影响
- 谁受影响
- 发生了什么
产品真相
- 代码实际执行的操作
- 网站或销售文案声称的内容
决策
- 退款 / 保留 / 转化 / 无操作
产品差距
- 需要构建或修复的具体后续事项