Recipes
Each one answers a question people actually ask, and each is written to be handed straight to an AI assistant — Claude, Cursor, Lovable, v0, Bolt — with the repository. They ship inside the template, so the copy you clone is always current.
“I want my AI to build pages on this stack without breaking anything.”
The master prompt
The rules an AI must follow to produce correct, secure, on-brand pages here — tokens, the page pattern, the data rules, and the upgrade path. Paste it with the repo and your assistant inherits every guardrail.
Paste once, applies forever
“I built a front end (Lovable, v0, Bolt, Cursor, or by hand) — how do I give it a real backend?”
Connect a front end to the backend
Point your site at the API, prove the connection, and start reading and writing real business data — auth, contacts, orders, payments — without writing or hosting a backend.
10 minutes
“How do I rebrand this without touching the code?”
Make it your brand
Fill-in-the-blank prompt: name, colors, words. Tokens do the rest — the whole site recolors, and it stays on the upgrade path because you never edited a component.
15 minutes
“I want a totally custom homepage, not a template one.”
Own your homepage completely
Add your own route group and delete the framework home — a fully bespoke front page that still merges every future upstream release. This is exactly how Utah’s Events did it.
1 hour
“How do I add a page that reads real data and matches the rest of the site?”
Add a new page
The canonical page pattern — typed API client, query keys, loading/error/empty states, permission gating — so a new page looks and behaves like it shipped with the template.
30 minutes
“I want visitors to answer questions and get a personalized recommendation.”
Build a quiz or recommendation flow
Author a scored flow in the dashboard, publish a public link, and render it on your site. Branching and scoring are server-side; the result bands are your recommendations.
20 minutes, no engine code
“How do I write blog posts and FAQs without a developer or a rebuild?”
Publish content with no redeploy
Flip blog and FAQ to live mode and publish from the dashboard — the site picks it up within minutes. No deploy, no CMS subscription.
5 minutes to switch on
“How do I get those animated scenes on my own pages?”
Author a live tile
Tiles are JSON, not code: shapes, palette roles, motion, and a cost budget the engine enforces. Write a spec, mount it behind any heading or card.
30 minutes
“What is this Play tab, and can it actually get me customers?”
The arcade (and its signup funnel)
Turn the play-to-signup funnel on, brand it, or remove it in one config line. Saved scores become real member signups in your organization.
5 minutes
“How do I give my customers a logged-in home?”
The member portal
What is dashboard configuration versus framework code, stated honestly — plus how members arrive, what they can self-serve, and how to advertise it.
20 minutes
“How do I launch on my own domain without breaking SEO?”
Put it on your domain
DNS, the env var everyone forgets, the redeploy that must follow, and how to verify canonical URLs and share cards actually moved with you.
20 minutes
“Where do I put my GA4/GTM/Meta ID, and why is nothing showing up?”
Analytics, consent, and the CSP
The one precedence answer (dashboard beats config), how consent gating changes what you see, and why the CSP opens itself only for what you enable.
5 minutes
“My styles work locally but vanish when deployed.”
Custom CSS without breaking production
The strict CSP silently drops inline styles — the page deploys unstyled with no error. Here is the bundled-stylesheet way that always survives.
10 minutes
Prefer to read it as a repo?
Every recipe lives in the template at docs/prompts/, versioned with the release you are on — the repository is always the newest source.