AI Emoji Generator

ai-emoji-generator

The AI Emoji Generator — Vercel's AI Emoji Generator template: type a prompt and get an emoji, the prompt checked by a safety classifier, drawn by an SDXL model fine-tuned on emojis, its background removed, and every emoji kept in a gallery with related emojis found by full-text search — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare. The models run on Replicate, an account the owner connects after the build. The emojis are in a Cloudflare D1 database, their images in an R2 bucket and each visitor's daily limit in a Workers KV namespace, all three provisioned by Terraform through Orun, the schema applied by migrations, and packaged as an Orun baseline: one command takes a new product from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing.

The template's Prisma/PlanetScale queries are D1 prepared statements now, its MySQL full-text search an FTS5 index, its Vercel Blob images R2 objects the Worker serves, and its Upstash rate limit a KV counter. Every webhook Replicate delivers is verified by its signature, its age and a per-emoji token before it is read. The site goes live with no Replicate account: the gallery serves, and the form says how to connect one. What the baseline adds is everything needed to make a copy of it somebody else's, built the way cirrus-baseline is. See specs/epics/ai-emoji-generator for the design, the milestones and the as-built status.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/ai-emoji-generator
cd ai-emoji-generator
orun new --blueprint repo-blueprint.yaml --out ~/sites/acme-emojis --run-hooks --resume \
  --set reponame=acme-emojis --set productname="Acme Emojis" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → ai-emoji-generator → Build). Two phases: 01-product creates the repository and lands the whole product as ONE pull request — intent, CI, tooling, the D1, R2 and KV roots, the migrations, the site and its tests — and one convergence, per environment, applies the database, the bucket and the namespace, then the migrations, then deploys the site bound to them; 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

The new repository receives the product only — the app, its D1, R2 and KV roots, its migrations and their runner, its tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Cloudflare Worker, database, bucket and namespace names. None of this repository's machinery ships.

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # render apps/web/wrangler.jsonc from the offline fixture
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # next build --webpack + opennextjs-cloudflare build → apps/web/.open-next

pnpm --filter @app/web db:migrate:local   # the emojis and the API secret in wrangler's local D1
pnpm --filter @app/web dev                # http://localhost:3000 — local D1, R2 and KV through wrangler's platform proxy
pnpm --filter @app/web preview            # wrangler dev over the built Worker, the same local bindings

How it maps to Vercel

How the bindings reach the Worker

infra/terraform/cloudflare-d1 ──apply──► orun secret WIRING_CLOUDFLARE_D1 (stage, prod)
infra/terraform/cloudflare-r2 ──apply──► orun secret WIRING_CLOUDFLARE_R2
infra/terraform/cloudflare-kv ──apply──► orun secret WIRING_CLOUDFLARE_KV
                                               │   (the landing's await checks they exist)
                                               ▼
infra/db-migrate  dependsOn cloudflare-d1 (enforced on main) · secretEnv WIRING_CLOUDFLARE_D1
  apply:  packages/db's runner → POST …/d1/database/<id>/query, each pending migration once
                                               ▼
apps/web  dependsOn cloudflare-d1, -r2, -kv + db-migrate (enforced on main) · secretEnv WIRING_CLOUDFLARE_*_<ENV>
  build:  tooling/wire/live.mjs → wrangler.jsonc with the environment's database, bucket and namespace
          (dev, verify-only, renders the fixture) → next build --webpack for the environment's origin
          → opennextjs-cloudflare → tooling/wire/worker-secrets.mjs: Replicate's token, when the
            environment has one, to the Worker as a Worker secret

wrangler.jsonc is committed as the fixture render of wrangler.template.jsonc, because the deploy lane's verify-app-structure step checks the config exists before it builds; testing/e2e.test.sh fails if the two disagree.

CI