Prima Get an API key

Module kit

One recipe per capability. A recipe explains to an agent how one feature is built on the Prima stack, under fourteen fixed headings, so that Primacode builds it the same way every time and a citation can name the file, the heading and the line. Recipes are grouped by domain; the manifest indexes them and records which frontend renders which backend, because a recipe with no rendering is not accepted.

The recipes are being written. Every domain below lists 0 until its first recipe lands, and the thirteen foundation files that every recipe includes by reference exist as headings without prose.

Domains

DomainWhat it coversRecipes
identity-auth Sign-in, sessions, keys and scopes, workspaces and their members. 0
forms-leads Hosted forms, embeds, submissions and what happens to a lead after it lands. 0
calendar-booking Meeting types, availability, the booking shell and confirmations. 0
commerce-payments Products, checkout, the payment provider seam and orders. 0
billing-credits Prepaid balance, top-ups, metering and receipts. 0
ai-gateway The OpenAI-compatible endpoints, model aliases, the meter and the error envelope. 0
agent-runtime Tool calling, confirm gates, agent keys and the surfaces that show an agent working. 0
knowledge-stone The stone repository, search, engrave and citations. 0
analytics-tracking First-party events, sessions, conversions and the pages that read them. 0
ads Ad platform connections, campaigns, audiences and their sync. 0
messaging-email-sms Transports, templates, sequences and delivery state. 0
review-signoff Content review requests, reviewer tokens, diffs and approval. 0
service-desk Tickets, queues, notes, client replies and status. 0
bookkeeping Journal entries, invoices, receipts, reconciliation and reports. 0
content-cms Site content, blocks, media shapes and the editing surfaces. 0
files-storage Uploads, storage backends and the file picker. 0
ui-design-system The token source, the component library, the app shell and the showcase. 0
monitoring-ops Health checks, probes, the status page and operator alerts. 0
infra-deploy How a service, a Worker or a static site is built, shipped and rolled back. 0
prospecting Lead sources, enrichment, drafts and the confirm gate before outreach. 0
media-audio-design Image, audio and design generation and the surfaces that request it. 0
primacode The coding tool: intake, the questlog, the claim record, the brain and its skills. 0
other Capabilities that fit no domain above. 0

Foundations

Thirteen files under _shared/, included by reference from every other recipe. Written first, because every frontend recipe renders through the first three and every backend recipe assumes the rest.

FoundationApplies toState
Design system and tokens
_shared/design-system-and-tokens
frontend headings only
React app skeleton
_shared/react-app-skeleton
frontend headings only
Astro site skeleton
_shared/astro-site-skeleton
frontend headings only
FastAPI project layout
_shared/fastapi-project-layout
backend headings only
Auth dependency pattern
_shared/auth-dependency-pattern
backend headings only
Workspace scoping
_shared/workspace-scoping
backend headings only
Error envelope
_shared/error-envelope
backend headings only
Alembic migrations
_shared/alembic-migrations
backend headings only
Test layout
_shared/test-layout
both headings only
HMAC seam pattern
_shared/hmac-seam-pattern
backend headings only
Outbox pattern
_shared/outbox-pattern
backend headings only
Scheduler and background work
_shared/scheduler-and-background-work
backend headings only
Cloudflare Worker and estate deploy
_shared/cloudflare-worker-and-estate-deploy
backend headings only

Content synced from the prima-modules repository at 34b1701 on 2026-09-11. The manifest is the source; this page is a rendering of it.