What problem does it solve?
Adding a new per-model pricing field to Bifrost requires touching roughly eight disconnected places (Go structs, DB migrations, sync upserts, cost calculation, overrides, OpenAPI, docs, UI), and missing any one produces a field that compiles but silently fails to bill, resync, or accept overrides.
Core Features & Use Cases
- End-to-end wiring checklist: Guides edits across the Options struct, TableModelPricing, gorm migrations, datasheet sync upsert columns, patchPricing overrides, and cost.go calculation functions.
- Silent-failure prevention: Explicitly guards the most-missed step (pricingSyncUpdateColumns in rdb.go) whose omission only breaks on the second 24h datasheet resync, plus regression tests for the ON CONFLICT DO UPDATE path.
- Semantics-first workflow: Forces confirmation of whether a field is additive, a threshold tier, or a rate substitute before writing billing logic, including cache-hit billing behavior.
- Use Case: When a provider datasheet adds a key like cost_per_request, invoke the skill to propagate it through the Go backend, OpenAPI bundle, MDX docs, TypeScript types, and the pricing override form, then verify with a repo-wide probe.
Quick Start
Ask the assistant to run /add-pricing-field cost_per_request to wire that new datasheet pricing field through Bifrost's entire pricing engine.