How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

debug-and-fix - Prompt - OpenSmartRoute

Name: debug-and-fix
Author: bep713

Prompt file imported from bep713/madden-franchise-editor (.github/prompts/debug-and-fix.prompt.md). Fill in {{error}}, {{file}} before use. Copyright stays with the author.

Debug & Fix Plan

Input

Console Error: {{error}}
Target File: {{file}}

Instructions

Read the Error Carefully
- Identify the error type, message, and stack trace
- Note which process it occurred in (main, renderer, preload)
- Identify the exact line and function where it failed
Understand the Context
- Read the target file completely
- Understand what the code is trying to do
- Check related files (imports, handlers, services)
- For Electron apps, verify IPC patterns are correct:
  - Main process uses ipcMain.handle
  - Preload uses contextBridge + ipcRenderer.invoke
  - Renderer calls via window.franchiseAPI or window.electronAPI
Find Root Cause
- Trace the error back to its source
- Check for common pitfalls:
  - Missing error handling in IPC handlers
  - Incorrect file ID usage (should use FranchiseFileManager map)
  - SASS not compiled (run gulp sass:watch)
  - Main process needs restart (not just renderer refresh)
  - Schema version mismatches
- Check if the error is a symptom of a deeper issue
Create Fix Plan
- Describe the root cause clearly
- List specific files that need changes
- Provide the exact code changes needed
- Include any commands to run (e.g., rebuild, restart)
- Note any verification steps

Output Format

## Error Analysis

- **Error Type:** [e.g., TypeError, ReferenceError, IPC timeout]
- **Process:** [main | renderer | preload]
- **Location:** [file:line]
- **Trigger:** [what action caused this]

## Root Cause

[Clear explanation of why this error occurs]

## Fix Plan

### 1. [File to edit]

- **Change:** [what to change]
- **Reason:** [why this fixes the issue]

### 2. [Additional steps if needed]

- [e.g., restart app, rebuild native modules]

## Verification

- [ ] [Step to verify the fix works]
- [ ] [Step to ensure no regressions]

Example Usage

Error: TypeError: Cannot read properties of undefined (reading 'getTable')
File: renderer/js/index.js:245

This would analyze the error, trace it through the IPC layer, and provide a concrete fix plan.

Install debug-and-fix 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.

# Debug & Fix Plan ## Input - **Console Error:** {{error}} - **Target File:** {{file}} ## Instructions 1. **Read the Error Carefully** - Identify the error type, message, and stack trace - Note which process it occurred in (main, renderer, preload) - Identify the exact line and function where it failed 2. **Understand the Context** - Read the target file completely - Understand what the code is trying to do - Check related files (imports, handlers, services) - For Electron apps, verify IPC patterns are correct: - Main process uses `ipcMain.handle` - Preload uses `contextBridge` + `ipcRenderer.invoke` - Renderer calls via `window.franchiseAPI` or `window.electronAPI` 3. **Find Root Cause** - Trace the error back to its source - Check for common pitfalls: - Missing error handling in IPC handlers - Incorrect file ID usage (should use FranchiseFileManager map) - SASS not compiled (run `gulp sass:watch`) - Main process needs restart (not just renderer refresh) - Schema version mismatches - Check if the error is a symptom of a deeper issue 4. **Create Fix Plan** - Describe the root cause clearly - List specific files that need changes - Provide the exact code changes needed - Include any commands to run (e.g., rebuild, restart) - Note any verification steps ## Output Format ```markdown ## Error Analysis - **Error Type:** [e.g., TypeError, ReferenceError, IPC timeout] - **Process:** [main | renderer | preload] - **Location:** [file:line] - **Trigger:** [what action caused this] ## Root Cause [Clear explanation of why this error occurs] ## Fix Plan ### 1. [File to edit] - **Change:** [what to change] - **Reason:** [why this fixes the issue] ### 2. [Additional steps if needed] - [e.g., restart app, rebuild native modules] ## Verification - [ ] [Step to verify the fix works] - [ ] [Step to ensure no regressions] ``` ## Example Usage ``` Error: TypeError: Cannot read properties of undefined (reading 'getTable') File: renderer/js/index.js:245 ``` This would analyze the error, trace it through the IPC layer, and provide a concrete fix plan.

{ "prompt": "# Debug & Fix Plan\n\n## Input\n\n- **Console Error:** {{error}}\n- **Target File:** {{file}}\n\n## Instructions\n\n1. **Read the Error Carefully**\n - Identify the error type, message, and stack trace\n - Note which process it occurred in (main, renderer, preload)\n - Identify the exact line and function where it failed\n\n2. **Understand the Context**\n - Read the target file completely\n - Understand what the code is trying to do\n - Check related files (imports, handlers, services)\n - For Electron apps, verify IPC patterns are correct:\n - Main process uses `ipcMain.handle`\n - Preload uses `contextBridge` + `ipcRenderer.invoke`\n - Renderer calls via `window.franchiseAPI` or `window.electronAPI`\n\n3. **Find Root Cause**\n - Trace the error back to its source\n - Check for common pitfalls:\n - Missing error handling in IPC handlers\n - Incorrect file ID usage (should use FranchiseFileManager map)\n - SASS not compiled (run `gulp sass:watch`)\n - Main process needs restart (not just renderer refresh)\n - Schema version mismatches\n - Check if the error is a symptom of a deeper issue\n\n4. **Create Fix Plan**\n - Describe the root cause clearly\n - List specific files that need changes\n - Provide the exact code changes needed\n - Include any commands to run (e.g., rebuild, restart)\n - Note any verification steps\n\n## Output Format\n\n```markdown\n## Error Analysis\n\n- **Error Type:** [e.g., TypeError, ReferenceError, IPC timeout]\n- **Process:** [main | renderer | preload]\n- **Location:** [file:line]\n- **Trigger:** [what action caused this]\n\n## Root Cause\n\n[Clear explanation of why this error occurs]\n\n## Fix Plan\n\n### 1. [File to edit]\n\n- **Change:** [what to change]\n- **Reason:** [why this fixes the issue]\n\n### 2. [Additional steps if needed]\n\n- [e.g., restart app, rebuild native modules]\n\n## Verification\n\n- [ ] [Step to verify the fix works]\n- [ ] [Step to ensure no regressions]\n```\n\n## Example Usage\n\n```\nError: TypeError: Cannot read properties of undefined (reading 'getTable')\nFile: renderer/js/index.js:245\n```\n\nThis would analyze the error, trace it through the IPC layer, and provide a concrete fix plan.", "variables": [ "error", "file" ], "notes": "Analyze a console error in the target file, find root cause, and create a detailed fix plan", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/bep713/madden-franchise-editor", "path": ".github/prompts/debug-and-fix.prompt.md", "ref": "9987119a5485b045b6ddd4c548de4cd811de021c", "url": "https://github.com/bep713/madden-franchise-editor/blob/9987119a5485b045b6ddd4c548de4cd811de021c/.github/prompts/debug-and-fix.prompt.md", "key": "bep713/madden-franchise-editor/.github/prompts/debug-and-fix.prompt.md" } } }

debug-and-fix

About

Debug & Fix Plan

Input

Instructions

Output Format

Example Usage

Install debug-and-fix and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews