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.
reflect - Prompt - OpenSmartRoute
Promptv1.0.0
reflect
Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently?
Prompt file imported from vsashyn/photo-contest (.cursor/commands/reflect.md). Copyright stays with the author.
Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?
Note, don't write a 'reflection' markdown doc.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?
Note, don't write a 'reflection' markdown doc.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?\n\nNote, don't write a 'reflection' markdown doc.",
"variables": [],
"notes": "Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?",
"metadata": {
"source": {
"provider": "github-cursor-commands",
"repository": "https://github.com/vsashyn/photo-contest",
"path": ".cursor/commands/reflect.md",
"ref": "a67c95597c30cc1db4c7821a8523ca08e05c3391",
"url": "https://github.com/vsashyn/photo-contest/blob/a67c95597c30cc1db4c7821a8523ca08e05c3391/.cursor/commands/reflect.md",
"key": "vsashyn/photo-contest/.cursor/commands/reflect.md"
}
}
}
Installed into a catalogue, chosen by a router
Install reflect 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.