Recipes
Capability packs
Nobody forks 'product reviews'. They fork a shop — and a shop turns out to mean a catalog, variants, a cart, discounts, tax, orders, and a payment provider, on top of accounts. A pack names that grouping and computes what it would cost you.
Brochure site
Pages, a contact inbox, and the search engines finding it.
11 capabilities6 ready5 on a fallbackA fresh project would set 9 provider variables to run everything for real; 9 unset here.
Regardless of providers: A Postgres database — pages, media, inquiries, and revisions live there.
What it containsAccounts
Sign in, prove the email, own your rows.
11 capabilities7 ready4 on a fallbackA fresh project would set 3 provider variables to run everything for real; 3 unset here.
Regardless of providers: A Postgres database — accounts, sessions, tokens, and the audit log.
What it containsShop
Catalog, cart, variants, discounts, tax, orders, payment.
14 capabilities11 ready3 on a fallbackSits on top of Accounts.
A fresh project would set 10 provider variables to run everything for real, 11 inherited capabilities included; 7 unset here.
Regardless of providers: A Postgres database — catalog, carts, orders, and inventory.
What it containsCommunity
Threads, replies, and the moderation that makes them survivable.
7 capabilities5 ready2 on a fallbackSits on top of Accounts.
A fresh project would set 5 provider variables to run everything for real, 10 inherited capabilities included; 3 unset here.
Regardless of providers: A Postgres database — threads, comments, reports, and the moderation queue.
What it containsText game
Save slots, a server-computed score, and a board nobody can forge.
5 capabilities5 readySits on top of Accounts.
A fresh project would set 3 provider variables to run everything for real, 10 inherited capabilities included.
Regardless of providers: A Postgres database — save slots and the leaderboard.
What it containsOperations
What you need the first time something breaks at 2am.
8 capabilities6 ready2 on a fallbackA fresh project would set 3 provider variables to run everything for real; 2 unset here.
Regardless of providers: A scheduler that calls the cron routes with CRON_SECRET (Vercel cron, or anything that can send a header on a timer).
What it contains
How to read these
The counts come from the same registry the Stack page reads, computed against this deployment. A capability reads live only when someone has watched its real provider path succeed on the deployed site — so a pack that is entirely ready is code that exists and has never met a real provider. That is a useful thing to know before you build a business on it.
The full inventory