// GETTING STARTED
Dev Prompt: Feed Your AI Coding Assistant Real Config
Generate a single prompt with your project's live DATABASE_URL, storage keys, and env vars — paste it into Claude, Cursor, or any AI coding tool.
Every project has a Dev Prompt page (sidebar, below Domains) with a Generate button. It produces a single block of text with everything an AI coding assistant needs to work on the repo correctly against your actual live resources — copy it and paste it as the first message into Claude, Cursor, Copilot Chat, or any other AI coding tool.
What it contains
- Project basics: repo URL, production branch, tech stack, build/start commands, port, platform subdomain, custom domains.
- The real
DATABASE_URL(if a database is provisioned) and the database name. - Object storage credentials — bucket name, region, endpoint, access key, secret key — if a Space is provisioned. See
Object Storage (Spaces). - Every environment variable currently set on the project, system and user-defined, with real values (not masked — this is meant to be pasted somewhere you trust, like your own AI coding session).
- The most recent deploy's status, and its error message if it failed.
- A stack-specific note on the Dockerfile requirement — Python/Go/Other get a matching Dockerfile example with your actual port baked in; Node gets a note that it's usually unnecessary.
- A closing task checklist telling the assistant to verify DATABASE_URL wiring, Dockerfile presence, and storage config against the actual repo — not just acknowledge the resource list.
Why it closes with a task list, not just a resource dump
A prompt that's only configuration reads as reference material — a fresh AI session has no way to know what to do with it and will often just ask "what would you like me to do?" instead of acting. The checklist at the end gives it something concrete to check and fix (or confirm is already correct), so pasting the prompt alone is enough to get useful work done, without you having to add your own instructions on top.
When to regenerate it
Click Generate again any time — it's not cached. Regenerate after adding an environment variable, provisioning a database or storage bucket, or after a deploy fails, so the assistant is working from current state instead of what was true the last time you copied it.