Update to Roar AI

{
  "description": "Build an app with the person and put it online with Roar AI, change an app that is already online, give it AI, or limit what it spends. Use when the person asks to make, deploy, update or fix an app or website on Roar AI.",
  "included_files": [],
  "name": "build-and-change-apps",
  "skill_md_contents": "---\nname: build-and-change-apps\ndescription: Build an app with the person and put it online with Roar AI, change an app that is already online, give it AI, or limit what it spends. Use when the person asks to make, deploy, update or fix an app or website on Roar AI.\n---\n\n# Build and change apps on Roar AI\n\nRoar AI puts an app online from the files written in this chat and runs it. No GitHub account, server or ZIP file is needed.\n\n## Build a new app\n\n1. Ask only what the job needs. For a website: what the business is called and what it does. For a chatbot: what the business does and what people usually ask.\n2. Agree in a few lines what the app does, then write it. Keep a first app small.\n3. Put it online with `deploy_app_from_files`. The answer gives the app's `appId`: keep it for every later step.\n4. Call `get_deploy_status` with `waitSeconds` until it is live, then share the link. Pass on in one line what its `nextStep` says the app can have next.\n\n## Change an app that is already online\n\nNever ask the person to connect GitHub or upload a ZIP for an app that was deployed from files. Its files are on Roar AI.\n\n1. Find the app with `list_apps` if you do not have its `appId`.\n2. If its files are not in this chat, call `list_app_files`, then `read_app_file` for each file you will change.\n3. Send only the files that changed with `update_app_files`. Every other file stays as it is.\n4. Call `get_deploy_status` with `waitSeconds`, then share the link.\n\nUse `update_app_files` for a change. `deploy_app_from_files` always makes a new app with a new address.\n\nIf a change is refused because a deploy is already running, call `get_deploy_status` with `waitSeconds` until it finishes, then send the change again.\n\nAn app that deploys from a GitHub repository is changed by pushing to that repository.\n\n## Give an app AI\n\nEvery app on Roar AI already has its own key. The app reads it from `ROAR_API_KEY`, and the endpoint from `ROAR_BASE_URL`, which is OpenAI-compatible. `list_models` gives the model names.\n\n- Do not create a key for an app hosted on Roar AI.\n- Never put a key in the code or in the chat.\n- Call the models from the app's server code, not from the browser.\n\n## Limit what an app spends on AI\n\nUse `set_app_ai_budget` with the app's `appId` and a monthly amount in USD. The app's AI calls stop when the month's spend reaches it, and start again the next month. `get_app_ai_budget` shows the current limit.\n\nYou can set a first limit or lower one. Raising or removing a limit is done by a person in the Roar AI console, under API keys.\n\nDo not create a new key to carry a limit: the app would not use it.\n\n## When a deploy fails\n\n`get_deploy_status` says what went wrong. `get_build_logs` has the detail. Fix the files and send them with `update_app_files`.\n\n## Keep it simple\n\n- Short messages, plain words.\n- No prices, credit or offers.\n- Share the live link whenever the app changes.\n"
}