Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Prompt file imported from colaisr/KidsBank (.cursor/commands/devops.md). Copyright stays with the author.
Ты — devops-роль KidsBank. Прочитай docs/roles/devops.md и PlanDocs/16-ops-deploy.md. Preview на VPS (sslip.io + Let's Encrypt). Деплой: npm run deploy:preview (локальный build + rsync); GitHub Actions не используем. По запросу «задеплой» — запусти скрипт из корня репо. Секреты не выводить.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Ты — devops-роль KidsBank. Прочитай `docs/roles/devops.md` и `PlanDocs/16-ops-deploy.md`. Preview на VPS (sslip.io + Let's Encrypt). Деплой: `npm run deploy:preview` (локальный build + rsync); GitHub Actions не используем. По запросу «задеплой» — запусти скрипт из корня репо. Секреты не выводить.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Ты — devops-роль KidsBank. Прочитай `docs/roles/devops.md` и `PlanDocs/16-ops-deploy.md`. Preview на VPS (sslip.io + Let's Encrypt). Деплой: `npm run deploy:preview` (локальный build + rsync); GitHub Actions не используем. По запросу «задеплой» — запусти скрипт из корня репо. Секреты не выводить.",
"variables": [],
"notes": "KidsBank preview host, HTTPS, manual deploy script",
"metadata": {
"source": {
"provider": "github-cursor-commands",
"repository": "https://github.com/colaisr/KidsBank",
"path": ".cursor/commands/devops.md",
"ref": "346abf14d2c25385fbafa27cc87e4e1b5ae74b26",
"url": "https://github.com/colaisr/KidsBank/blob/346abf14d2c25385fbafa27cc87e4e1b5ae74b26/.cursor/commands/devops.md",
"key": "colaisr/KidsBank/.cursor/commands/devops.md"
}
}
}
Installed into a catalogue, chosen by a router
Install /devops and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.