Bootstrap a prepaid credit billing system in a Phoenix 1.8 app with Stripe and Oban.
npx skills add https://github.com/agoodway/GoodSkills --skill bootstrap-credits
Please help me install this Agent Skill. Skill: bootstrap-credits Source: https://github.com/agoodway/GoodSkills/tree/main/skills/bootstrap-credits Command: npx skills add https://github.com/agoodway/GoodSkills --skill bootstrap-credits
Building a prepaid credit system with Stripe billing, webhooks, async fulfillment, and UI can be complex and error-prone, especially when parts may already exist in the app.
Use it when you want to add a prepaid credit system (pack purchase, balance + transaction history, and optional usage tracking) to a Phoenix 1.8 multi-tenant app without duplicating existing components.
Tell the AI to run the bootstrap credits workflow for your Phoenix app by mounting the endpoint at /dashboard/credits and enabling Stripe pack purchases.
High-intent search queries and answers about installing and using this skill.
To implement a prepaid credit billing system in Phoenix, this Skill bootstraps Stripe-backed pack purchases, webhook-driven fulfillment, and LiveView purchase/history pages. It generates per-account balances with optimistic locking and an append-only transaction history for multi-tenant apps.
Handling Stripe webhooks for credit fulfillment requires signature verification and idempotent processing. This Skill discovers existing migrations and schemas, then generates missing components and configures Oban for secure, async webhook-driven fulfillment in your Phoenix app.
Tracking account balances and transaction history in a multi-tenant Phoenix app is done via an append-only credit ledger with optimistic locking. This Skill generates immutable transaction records and optional usage event tracking to ensure data integrity across accounts.
Yes, Oban is required for async webhook processing and fulfillment in this Phoenix 1.8 setup. The Skill configures Oban alongside Stripe to handle background job processing for credit pack purchases and idempotent webhook event handling.
Yes, you can use existing migrations and schemas when adding a Stripe credit pack system. The Skill requires discovery of existing modules and schemas, generating only the missing components to avoid duplication in your multi-tenant billing setup.
Stripe billing for Phoenix credits supports optional usage event tracking alongside user-facing LiveView purchase and history pages. The Skill generates a Stripe.js hook for Payment Element mounting to deliver a complete end-to-end Phoenix UX.
agoodwayGenerate a Phoenix 1.8 event notification system with PubSub, Oban, and webhooks.
wangzeping114Manage investor wallet balances and log transactions for dividends, credits, and withdrawals.
layeddieImplement Phoenix LiveView UI patterns for real-time interfaces.
mattwoodcoImplement Stripe credit-based billing with Drizzle ORM for subscriptions and usage metering.
