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.
diagnose-and-fix-bug - Prompt - OpenSmartRoute
Promptv1.0.0
diagnose-and-fix-bug
First: If needed, console log everything. Anything that interacts with whatever is causing the bug should be console logged.
Prompt file imported from ziidonato/electronics-ai (.windsurf/workflows/diagnose-and-fix-bug.md). Copyright stays with the author.
First: If needed, console log everything. Anything that interacts with whatever is causing the bug should be console logged.
Second: If needed, use Playwright to try doing the action that is causing the bug, and read the console logs to see what is happening.
Third: Diagnose the issue and fix it.
Fourth: Verify that the bug is fixed with the playwright MCP.
Fifth: Add/edit tests to verify the bug is fixed and prevent regressions.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
First: If needed, console log everything. Anything that interacts with whatever is causing the bug should be console logged.
Second: If needed, use Playwright to try doing the action that is causing the bug, and read the console logs to see what is happening.
Third: Diagnose the issue and fix it.
Fourth: Verify that the bug is fixed with the playwright MCP.
Fifth: Add/edit tests to verify the bug is fixed and prevent regressions.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
Installed into a catalogue, chosen by a router
Install diagnose-and-fix-bug 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.
{
"prompt": "First: If needed, console log everything. Anything that interacts with whatever is causing the bug should be console logged.\n\nSecond: If needed, use Playwright to try doing the action that is causing the bug, and read the console logs to see what is happening.\n\nThird: Diagnose the issue and fix it.\n\nFourth: Verify that the bug is fixed with the playwright MCP.\n\nFifth: Add/edit tests to verify the bug is fixed and prevent regressions.",
"variables": [],
"notes": "First: If needed, console log everything. Anything that interacts with whatever is causing the bug should be console logged.",
"metadata": {
"source": {
"provider": "github-windsurf-workflows",
"repository": "https://github.com/ziidonato/electronics-ai",
"path": ".windsurf/workflows/diagnose-and-fix-bug.md",
"ref": "df7e9b69a186c578d3c105d71af4785e2cfd5b74",
"url": "https://github.com/ziidonato/electronics-ai/blob/df7e9b69a186c578d3c105d71af4785e2cfd5b74/.windsurf/workflows/diagnose-and-fix-bug.md",
"key": "ziidonato/electronics-ai/.windsurf/workflows/diagnose-and-fix-bug.md"
}
}
}
Fetch it by URL: GET /api/v1/registry/ziidonato-electronics-ai-diagnose-and-fix-bug-workflow/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
