القائمة
Modeling Autumn pricing or reasoning about features, plans, plan items, customers/entities, trials, or billing controls.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Performing Autumn billing actions — attaching plans, updating or canceling subscriptions, creating schedules, customizing terms, previewing charges, and applying billing changes. Use when the user wants to bill a customer, change a subscription, schedule plan changes, or preview billing impact.
Investigating Autumn request logs and Stripe webhook deliveries — debugging unexpected charges, plan-change history, denied feature checks, balance and usage discrepancies, failed API calls, and out-of-sync subscriptions. Use when the user asks why something happened to a customer — a charge, a state change, a denied check, missing or unreset usage — or wants to see a customer's request timeline or log analytics.
Designing or changing an Autumn pricing model — features, plans, plan items, and how usage is granted or billed (in autumn.config.ts, the API, or the dashboard). Use when the user discusses pricing, plans, tiers, credits, seats, overage, prepaid, or trials.
Write integration tests for Autumn billing. Covers initScenario setup, billing/attach/track/check endpoints, subscription updates, assertion utilities, and common billing test patterns. Use when creating tests, writing test scenarios, debugging test failures, or when the user asks about testing.
Build and manage percentage-based rolling rollouts with cache staleness detection. Use when adding new rollout features, debugging rollout bucket routing, working with the rollout edge config, or handling cache staleness during forward/rollback migrations.
Understand and create S3-backed edge configs with poll-based caching. Use when adding new runtime configs (feature rollouts, request blocking, operational toggles), debugging edge config polling, or working with the EdgeConfigStore factory.
| name | autumn-concepts |
| description | Modeling Autumn pricing or reasoning about features, plans, plan items, customers/entities, trials, or billing controls. |
Autumn is a database for your application billing state: features, plans, customers, subscriptions, purchases, balances, flags, and billing controls. It helps you iterate on pricing, manage credit access and usage, control overage, and keep billing behavior connected to product access.
Autumn is a layer above Stripe; Stripe still handles subscription management, invoicing, and payment processing. Autumn provisions and updates Stripe subscriptions, schedules, invoices, and related billing objects for you.
Organization
- features[] -> Feature
- plans[] -> Plan
- customers[] -> Customer
Configuration model:
Feature
- referenced by -> Plan Item
Plan
- items[] -> Plan Item
- feature_id -> Feature
- optional price -> usage_based or prepaid feature price
- price -> base recurring or one-off price
Plan Item
- feature_id -> Feature
- optional price -> usage_based or prepaid feature price
Runtime model:
Customer
- subscriptions[] -> Subscription -> Plan
- purchases[] -> Purchase -> Plan
- balances[feature_id] -> Balance -> Feature
- flags[feature_id] -> Flag -> Feature
- billing_controls -> customer-level usage controls
- entities[] -> Entity -> same runtime shape scoped under Customer
Entity
- belongs to -> Customer
- subscriptions[] -> Subscription -> Plan
- purchases[] -> Purchase -> Plan
- balances[feature_id] -> Balance -> Feature
- flags[feature_id] -> Flag -> Feature
- billing_controls -> entity-level controls where supported
From config to customer state:
Plan + Customer --billing.attach--> Subscription or Purchase
Plan + Customer + entity_id --billing.attach--> Entity-scoped Subscription or Purchase
Subscription/Purchase -> Balance or Flag provisioning
Use these definitions as the mental model when designing or changing Autumn pricing. Reason in terms of features, plans, plan items, customers/entities, and billing controls before writing any config or calling the API — most modeling mistakes come from conflating a feature with a plan item, or a plan-level price with a per-feature price.
Load the matching definition when reasoning about that object.
For defining a feature — the atomic unit Autumn gates, tracks, or bills, and its types, read references/feature.md.
For defining a plan — the attachable package of items and pricing, read references/plan.md.
For modeling plan items, or when you need concrete API request-body examples (included usage, prepaid, usage-based, tiers), read references/plan-items.md.
For using customize, reading plan update previews, or representing a small diff from a base plan, read references/customize.md.
For reasoning about free trials and when billing begins, read references/trials.md.
For distinguishing a customer from an entity (seats, sub-accounts) and their runtime billing state, read references/customer-entity.md.
For reasoning about billing controls — runtime caps, alerts, overage, and top-ups, read references/billing-controls.md.