菜单
Use when starting any non-trivial HEATER change (feature, remediation program, refactor), when deciding how to plan/execute/review it, when finishing work (merge/push), or when another session or track has pushed to master mid-work (merge conflicts in openapi.json / generated.ts).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when starting any task on HEATER's live product — the api/ FastAPI backend (Railway service "celebrated-respect") or web/ Next.js frontend (heater-v1-0-1.vercel.app) — or when unsure where code lives, how a request flows, which database owns what, why CORS/Yahoo-writes/billing seem "missing", or which app (Streamlit vs React) is the real one. Load this first on App B work.
Use when working on HEATER App B auth or billing — Clerk JWT verification, unexpected 401/402, HEATER_API_WRITE_TOKEN, Stripe checkout/webhooks/subscription tiers, require_pro gating, tier-based AI spend caps — or when auth "works locally but not live" (or vice versa), or a page bounces to /sign-in on hard load.
Use when working on Bubba, HEATER's AI assistant — /api/chat/* endpoints, provider streaming (src/ai/providers.py), token metering and spend caps, AI provider keys, attachments/page-context, saved prompts, or the chat composer in web/src/components/bubba/.
Use when proving a HEATER algorithm works — calibrating constants, backtesting projections or recommendations, validating win probabilities, adding uncertainty intervals, checking calibration drift — or before letting any new math drive user-facing recommendations. Also when asked "is this signal real?" or when a calibration run finds no clear winner.
Use when editing api/contracts/*, when api/openapi.json or web/src/lib/api/generated.ts drift (test_openapi_contract or the CI openapi-ts-sync job failing), when JSON responses 500 or render "nan"/"+nan" badges, or when adding/renaming fields on a response the live frontend already consumes.
Use when App B misbehaves and the cause isn't obvious — works locally but not on Railway/Vercel (or vice versa), a live page renders empty/zero/wrong data, an endpoint 500s or times out, or tests see different data than the app. Run this playbook before changing code.
基于 SOC 职业分类
| name | heater-appb-workflow |
| description | Use when starting any non-trivial HEATER change (feature, remediation program, refactor), when deciding how to plan/execute/review it, when finishing work (merge/push), or when another session or track has pushed to master mid-work (merge conflicts in openapi.json / generated.ts). |
docs/superpowers/specs/YYYY-MM-DD-heater-<topic>-design.md.docs/superpowers/plans/YYYY-MM-DD-heater-<topic>-slice<N>-*.md. Phases ≠ spec sections; don't conflate levels (program → sub-project → phase → plan → tasks)._statsapi_current_team hydrate miss). Receiving review: verify claims against source before implementing — one reviewer "must-fix" was correctly overruled by a grep proving all 8 callers omit weeks_remaining.docs/launch/evidence_registry.yaml; check with python -m scripts.launch.evidence_registry --summary.git pull --no-rebase origin master. A parallel CMO/CEO session may push mid-task; do NOT disturb their branches or uncommitted work.api/openapi.json or web/src/lib/api/generated.ts: REGENERATE, never hand-merge (python scripts/export_openapi.py; cd web && pnpm gen:api). Tell implementer subagents commit-only-don't-push.pnpm build for web/). Deploys: owner step unless told otherwise; live verify after the ~10 min re-bootstrap.2026-06-27 WS-era: a parallel session pushed to master mid-work; hand-merging generated.ts produced a file pnpm gen:api couldn't reproduce → CI openapi-ts-sync red on an unrelated PR. The regenerate-don't-merge rule and "pull early/often" came from that afternoon (memory: reference_parallel_session_master_reconcile).
Trivial mechanical fixes (typo, one-line bugfix with an obvious test) don't need a spec/plan — but the merge+push and review-pair rules still apply to anything touching shipped behavior.