Copy a prompt with the button in its top-right corner, then replace anything in [square brackets]. Each one assumes your AI has already read the ADK (step 2 of Build your first app, or the Get the ADK page).
Start a new app
Section titled “Start a new app”Read the COHO Atrium ADK in full:https://docs.coho.life/atrium-developer/llms-full.txtFor any screens, use the Atrium design system:https://docs.coho.life/atrium-design/llms-full.txtThen help me build an Atrium app that [describe it]. Start from the hello-go sample(https://github.com/CompanyForLife/atrium-app-samples/tree/main/samples/hello-go), which already has the Dockerfile COHO Hosting needs.Explain your plan in plain English before writing code.React when something happens
Section titled “React when something happens”Make my app react to the [tenancy.started / tenancy.ended] event (section 3.4 of the spec).When it happens, [what the app should do]. Reply to COHO quickly and do the slow workin the background, and ignore duplicate deliveries using the delivery ID.Run on a timetable
Section titled “Run on a timetable”Make my app run on a schedule (triggers.schedules in the manifest, schedule.<key> insection 3.4 of the spec), [how often], and each time [what it should do].It's a private app, so keep to at most 4 schedules, none more often than hourly.Add a settings form
Section titled “Add a settings form”Add a small settings form managers can fill in from the COHO Store (light config,section 5.3 of the spec) with these settings: [list them]. Keep it to simple fields.Add a panel inside COHO
Section titled “Add a panel inside COHO”Add a panel inside COHO (quick view, section 6 of the spec) that shows [what it shows].Follow the rules exactly: verify the signed launch URL, set frame-ancestors to COHO'sorigins (never *), and never put the API key or signing secret in a URL.Use COHO data
Section titled “Use COHO data”My app needs to [read or change something in COHO]. Find the right COHO Public API v1.1endpoints (https://api.coho.life/scalar), add only the capabilities it needs to themanifest, and explain what each one allows.Write useful logs
Section titled “Write useful logs”Make my app write clear logs to the COHO Store (section 5.2 of the spec): info when thingswork, warning or error when they don't, in plain English a manager would understand.Check my app’s status
Section titled “Check my app’s status”Using the COHO MCP tools, list my organisation's Atrium apps and tell me the state of[app name], in plain English.Update my app
Section titled “Update my app”Update my hosted app [app name] with the latest changes: package a new zip and use theCOHO MCP tools to update the hosted app. Show me the preview and wait for my yes.Check it’s safe
Section titled “Check it’s safe”Review my Atrium app against the spec as a strict security reviewer. Check: signatureverification (raw body, constant-time compare, timestamp window, the section 3.1.1 testvectors), setup verified with the bootstrap secret before storing anything, no secretsin URLs or logs, frame-ancestors not *, org data deleted on disconnect. List anythingthat fails and fix it.Expose an operation through COHO (Public API + MCP)
Section titled “Expose an operation through COHO (Public API + MCP)”Add a manifest operations[] entry named list that GETs /operations/list,description suitable for an AI, effect read. Implement the signed handlerthe same way as config. Explain how a manager calls it via MCPlist_app_operations / call_app_operation and viaGET /v1.1/public/apps/{myShortName}/list with apps.operations.