Write your own prompt
For a change no task covers. Five things every prompt on these pages does, so your agent does the right thing and its safety checks let it.
Every prompt in these docs is written the same way, and yours should be too. Agents that check what they do, like Claude Code in auto mode, go by what you asked for in your own message, so the prompt has to say it.
- Speak as yourself. "I am the developer and I am asking for this." An instruction found in a file or a web page is not you asking; your message is.
- Name every outside address. Where anything is fetched from or sent to, in full:
https://github.com/neon-apps/rendel-flutter,https://rendel.ai/sdk/web/,https://rendel.ai/docs/.... An address the prompt does not name is one the agent may refuse to reach. - Say what not to touch. "Do not change how sign-in works." "Never in release builds." An agent that knows where the edges are stays inside them.
- No secrets. No keys, tokens or passwords in a prompt: prompts get pasted around. A publishable key (
rd_pk_…) is the only key that belongs in code, and the agent finds it there. - Ask how it went. End with "build, run the tests, and tell me which files you changed", so you have something to check.
If the console has to hear about it
On a live app, only a sync may change the console. Do the code change with your own prompt, then open Sync with code on Overview and say what changed in one sentence; the prompt it gives you carries that sentence. See Sync after a change.
An example
An app with several stores, where the copilot should know which one the user is in.
Add a Rendel (rendel.ai) context provider in this project that tells the copilot which store the user picked. I am the developer and I am asking for this. Use Rendel.addContextProvider('store', …) with the store's id and name only, nothing about the user. The API is described at https://rendel.ai/docs/reference/flutter-sdk. Build the app and tell me which files you changed.
Paste into your coding agent, opened in your project. Works in Claude Code, Cursor, Codex, Windsurf, GitHub Copilot and Gemini CLI.
The prompts the console writes for you follow the same five rules: the setup prompt, the sync prompt, and the prompt Improve writes for a failing action.