bootstrap-events

Generate a Phoenix 1.8 event notification system with PubSub, Oban, and webhooks.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/agoodway/GoodSkills --skill bootstrap-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootstrap-events
Source: https://github.com/agoodway/GoodSkills/tree/main/skills/bootstrap-events
Command: npx skills add https://github.com/agoodway/GoodSkills --skill bootstrap-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need a production-ready, tenant-scoped event notification system that reliably routes business events to email, SMS, and webhooks without hand-wiring schemas, delivery workers, logging, and real-time UI.

Core Features & Use Cases

  • Event Bus + Tenant Topics: broadcast events through PubSub for account-scoped listeners and delivery orchestration.
  • Database-backed Subscriptions: manage which users or static destinations receive which event types, including webhook channels with signed requests.
  • Delivery Orchestration via Oban: process email, SMS, webhook, and in-app delivery asynchronously with delivery status logging for auditability.
  • Webhook Signing (Standard Webhooks style): generate secrets and sign webhook payloads with HMAC-SHA256-compatible headers.
  • LiveView Integration + Multi-tenancy: support real-time updates with correct account scoping.

Quick Start

Run the skill in your Phoenix 1.8 project, then follow the prompts to confirm your app module prefix, PubSub module, mailer, tenant scoping field, and the event types you want to support.

Frequently Asked Questions about bootstrap-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up multi-tenant event notifications in Phoenix?

To set up multi-tenant event notifications in Phoenix, you can use a system that broadcasts business events through PubSub to email, SMS, webhooks, and in-app listeners while enforcing account scoping. It generates the necessary schemas, migrations, and workers automatically.

What's the best way to manage webhook subscriptions in a Phoenix application?

The best way to manage webhook subscriptions in Phoenix is using a database-backed system that generates secrets and signs payloads with HMAC-SHA256-compatible headers. This approach uses Standard Webhooks-style signing to ensure secure outbound HTTP callbacks.

Can I use Oban for asynchronous email and SMS delivery in Phoenix 1.8?

Yes, you can use Oban for asynchronous email and SMS delivery in Phoenix 1.8. Oban orchestrates delivery workers to process email, SMS, webhook, and in-app events asynchronously, logging delivery statuses for auditability.

How do I wire Phoenix PubSub topics for account-scoped LiveView updates?

Wiring Phoenix PubSub topics for account-scoped LiveView updates involves generating event structs and topic wiring that broadcasts business events to real-time listeners. This ensures LiveView integration enforces correct tenant scoping.

Does this event notification system require database-managed event subscriptions?

Yes, this event notification system requires database-managed event subscriptions to track which users or static destinations receive specific event types. It generates the necessary subscription and log migrations and schemas for this functionality.