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.

document - Prompt - OpenSmartRoute

Name: document
Author: RetrolariumLab

Prompt file imported from RetrolariumLab/alien_soldier_src (.claude/commands/document.md). Copyright stays with the author.

Document Procedures Skill

Documents a batch of assembly procedures by analyzing their code and creating rename mappings.

Trigger

Use /document or /document COUNT to document procedures.

Workflow

Read workflow/batch_procedures.txt (created by make prepare-batch)
Analyze each procedure's code and context
Create workflow/rename_batch.csv with new names

Instructions

When this skill is invoked:

Step 1: Check Prerequisites

Verify workflow/batch_procedures.txt exists. If not, tell user to run:

make prepare-batch COUNT=40

Step 2: Read Batch File

Read workflow/batch_procedures.txt which contains:

Procedure code listings
Scene and frame context
Memory change indicators (RAM, VDP, Z80, YM2612, PSG)
Visual diff paths

Step 3: Analyze Each Procedure

For each procedure, determine:

What it does - Read the assembly code
Category - Based on operations:
- Gfx_ - VDP registers, VRAM writes, DMA, palettes
- Sys_ - System init, main loop, memory clear
- Sound_ - Z80, audio, YM2612, PSG
- Input_ - Controller reading
- Physics_ - Movement, collision
- Sprite_ - Sprite table, OAM
- Anim_ - Animation frames
- Effect_ - Visual effects
- Player_ - Player logic
- Boss_ - Boss AI
- Enemy_ - Enemy AI
- UI_ - HUD, menus, text
- Math_ - Calculations, RNG
- Stage_ - Level logic
- Object_ - Game objects
- Data_ - Data processing, decompression
Descriptive name - Action-oriented: Category_VerbNoun
- Good: Gfx_LoadTilesToVRAM, Player_CheckDeath
- Bad: DoStuff, Process, Handler

Step 4: Create CSV

Create workflow/rename_batch.csv:

old_name,new_name,description
sub_1234,Gfx_LoadSegaTiles,Loads Sega logo tiles to VRAM via DMA
loc_5678,Sys_MainLoop,Main game loop that calls update routines

Rules:

First line must be header: old_name,new_name,description
Use double quotes around descriptions with commas
No duplicate new_name values
Names must be valid assembly labels (alphanumeric + underscore, start with letter)

Step 5: Summary

Report:

Total procedures documented
Categories breakdown (how many Gfx_, Sys_, etc.)
Any uncertain procedures that need human review

Naming Heuristics

Code Patterns → Categories

Pattern	Category
`move.* (VDP_CTRL)`	`Gfx_`
`move.* (VDP_DATA)`	`Gfx_`
`jsr.*DMA`	`Gfx_`
`move.* (Z80_*)`	`Sound_`
`move.* (YM2612_*)`	`Sound_`
`move.* (IO_DATA*)`	`Input_`
`move.* (word_FFF7*)`	`Input_` (controller state)
`jsr.*Random`	`Math_`
`clr/move (word_FF*)`	RAM variable access
`rts` only	Short helper or stub

Scene Context → Naming

Scene	Likely Content
`Sega screen`	Init, logo, system setup
`Title screen`	Menu, options, UI
`Stage *`	Gameplay, enemies, player
`Boss *`	Boss AI, attacks
`Results`	Score, UI

Example Analysis

Procedure: sub_4BA
Scene: Sega screen
Code:
    move.w  #$8F02,(VDP_CTRL).l
    move.l  #$40000003,(VDP_CTRL).l
    lea     (TilesData_Sega).l,a0
    move.w  #$2000,d0
    jsr     (Gfx_DMATransfer).l
    rts

Analysis:
- Sets VDP auto-increment ($8F02)
- Sets VRAM write address
- Loads Sega tiles address
- Transfers 8KB via DMA
- Category: Gfx_
- Name: Gfx_LoadSegaLogoTiles
- Description: Loads Sega logo tile graphics to VRAM via DMA

CSV entry:
sub_4BA,Gfx_LoadSegaLogoTiles,Loads Sega logo tile graphics to VRAM via DMA

After Completion

Tell the user to run:

make rename                   # Apply renames
make build && make compare    # Verify ROM unchanged
git add alien_soldier_j.s && git commit

Install document 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.

# Document Procedures Skill Documents a batch of assembly procedures by analyzing their code and creating rename mappings. ## Trigger Use `/document` or `/document COUNT` to document procedures. ## Workflow 1. Read `workflow/batch_procedures.txt` (created by `make prepare-batch`) 2. Analyze each procedure's code and context 3. Create `workflow/rename_batch.csv` with new names ## Instructions When this skill is invoked: ### Step 1: Check Prerequisites Verify `workflow/batch_procedures.txt` exists. If not, tell user to run: ```bash make prepare-batch COUNT=40 ``` ### Step 2: Read Batch File Read `workflow/batch_procedures.txt` which contains: - Procedure code listings - Scene and frame context - Memory change indicators (RAM, VDP, Z80, YM2612, PSG) - Visual diff paths ### Step 3: Analyze Each Procedure For each procedure, determine: 1. **What it does** - Read the assembly code 2. **Category** - Based on operations: - `Gfx_` - VDP registers, VRAM writes, DMA, palettes - `Sys_` - System init, main loop, memory clear - `Sound_` - Z80, audio, YM2612, PSG - `Input_` - Controller reading - `Physics_` - Movement, collision - `Sprite_` - Sprite table, OAM - `Anim_` - Animation frames - `Effect_` - Visual effects - `Player_` - Player logic - `Boss_` - Boss AI - `Enemy_` - Enemy AI - `UI_` - HUD, menus, text - `Math_` - Calculations, RNG - `Stage_` - Level logic - `Object_` - Game objects - `Data_` - Data processing, decompression 3. **Descriptive name** - Action-oriented: `Category_VerbNoun` - Good: `Gfx_LoadTilesToVRAM`, `Player_CheckDeath` - Bad: `DoStuff`, `Process`, `Handler` ### Step 4: Create CSV Create `workflow/rename_batch.csv`: ```csv old_name,new_name,description sub_1234,Gfx_LoadSegaTiles,Loads Sega logo tiles to VRAM via DMA loc_5678,Sys_MainLoop,Main game loop that calls update routines ``` Rules: - First line must be header: `old_name,new_name,description` - Use double quotes around descriptions with commas - No duplicate new_name values - Names must be valid assembly labels (alphanumeric + underscore, start with letter) ### Step 5: Summary Report: - Total procedures documented - Categories breakdown (how many Gfx_, Sys_, etc.) - Any uncertain procedures that need human review ## Naming Heuristics ### Code Patterns → Categories | Pattern | Category | |---------|----------| | `move.* (VDP_CTRL)` | `Gfx_` | | `move.* (VDP_DATA)` | `Gfx_` | | `jsr.*DMA` | `Gfx_` | | `move.* (Z80_*)` | `Sound_` | | `move.* (YM2612_*)` | `Sound_` | | `move.* (IO_DATA*)` | `Input_` | | `move.* (word_FFF7*)` | `Input_` (controller state) | | `jsr.*Random` | `Math_` | | `clr/move (word_FF*)` | RAM variable access | | `rts` only | Short helper or stub | ### Scene Context → Naming | Scene | Likely Content | |-------|----------------| | `Sega screen` | Init, logo, system setup | | `Title screen` | Menu, options, UI | | `Stage *` | Gameplay, enemies, player | | `Boss *` | Boss AI, attacks | | `Results` | Score, UI | ## Example Analysis ``` Procedure: sub_4BA Scene: Sega screen Code: move.w #$8F02,(VDP_CTRL).l move.l #$40000003,(VDP_CTRL).l lea (TilesData_Sega).l,a0 move.w #$2000,d0 jsr (Gfx_DMATransfer).l rts Analysis: - Sets VDP auto-increment ($8F02) - Sets VRAM write address - Loads Sega tiles address - Transfers 8KB via DMA - Category: Gfx_ - Name: Gfx_LoadSegaLogoTiles - Description: Loads Sega logo tile graphics to VRAM via DMA CSV entry: sub_4BA,Gfx_LoadSegaLogoTiles,Loads Sega logo tile graphics to VRAM via DMA ``` ## After Completion Tell the user to run: ```bash make rename # Apply renames make build && make compare # Verify ROM unchanged git add alien_soldier_j.s && git commit ```

{ "prompt": "# Document Procedures Skill\n\nDocuments a batch of assembly procedures by analyzing their code and creating rename mappings.\n\n## Trigger\n\nUse `/document` or `/document COUNT` to document procedures.\n\n## Workflow\n\n1. Read `workflow/batch_procedures.txt` (created by `make prepare-batch`)\n2. Analyze each procedure's code and context\n3. Create `workflow/rename_batch.csv` with new names\n\n## Instructions\n\nWhen this skill is invoked:\n\n### Step 1: Check Prerequisites\n\nVerify `workflow/batch_procedures.txt` exists. If not, tell user to run:\n```bash\nmake prepare-batch COUNT=40\n```\n\n### Step 2: Read Batch File\n\nRead `workflow/batch_procedures.txt` which contains:\n- Procedure code listings\n- Scene and frame context\n- Memory change indicators (RAM, VDP, Z80, YM2612, PSG)\n- Visual diff paths\n\n### Step 3: Analyze Each Procedure\n\nFor each procedure, determine:\n\n1. **What it does** - Read the assembly code\n2. **Category** - Based on operations:\n - `Gfx_` - VDP registers, VRAM writes, DMA, palettes\n - `Sys_` - System init, main loop, memory clear\n - `Sound_` - Z80, audio, YM2612, PSG\n - `Input_` - Controller reading\n - `Physics_` - Movement, collision\n - `Sprite_` - Sprite table, OAM\n - `Anim_` - Animation frames\n - `Effect_` - Visual effects\n - `Player_` - Player logic\n - `Boss_` - Boss AI\n - `Enemy_` - Enemy AI\n - `UI_` - HUD, menus, text\n - `Math_` - Calculations, RNG\n - `Stage_` - Level logic\n - `Object_` - Game objects\n - `Data_` - Data processing, decompression\n\n3. **Descriptive name** - Action-oriented: `Category_VerbNoun`\n - Good: `Gfx_LoadTilesToVRAM`, `Player_CheckDeath`\n - Bad: `DoStuff`, `Process`, `Handler`\n\n### Step 4: Create CSV\n\nCreate `workflow/rename_batch.csv`:\n\n```csv\nold_name,new_name,description\nsub_1234,Gfx_LoadSegaTiles,Loads Sega logo tiles to VRAM via DMA\nloc_5678,Sys_MainLoop,Main game loop that calls update routines\n```\n\nRules:\n- First line must be header: `old_name,new_name,description`\n- Use double quotes around descriptions with commas\n- No duplicate new_name values\n- Names must be valid assembly labels (alphanumeric + underscore, start with letter)\n\n### Step 5: Summary\n\nReport:\n- Total procedures documented\n- Categories breakdown (how many Gfx_, Sys_, etc.)\n- Any uncertain procedures that need human review\n\n## Naming Heuristics\n\n### Code Patterns → Categories\n\n| Pattern | Category |\n|---------|----------|\n| `move.* (VDP_CTRL)` | `Gfx_` |\n| `move.* (VDP_DATA)` | `Gfx_` |\n| `jsr.*DMA` | `Gfx_` |\n| `move.* (Z80_*)` | `Sound_` |\n| `move.* (YM2612_*)` | `Sound_` |\n| `move.* (IO_DATA*)` | `Input_` |\n| `move.* (word_FFF7*)` | `Input_` (controller state) |\n| `jsr.*Random` | `Math_` |\n| `clr/move (word_FF*)` | RAM variable access |\n| `rts` only | Short helper or stub |\n\n### Scene Context → Naming\n\n| Scene | Likely Content |\n|-------|----------------|\n| `Sega screen` | Init, logo, system setup |\n| `Title screen` | Menu, options, UI |\n| `Stage *` | Gameplay, enemies, player |\n| `Boss *` | Boss AI, attacks |\n| `Results` | Score, UI |\n\n## Example Analysis\n\n```\nProcedure: sub_4BA\nScene: Sega screen\nCode:\n move.w #$8F02,(VDP_CTRL).l\n move.l #$40000003,(VDP_CTRL).l\n lea (TilesData_Sega).l,a0\n move.w #$2000,d0\n jsr (Gfx_DMATransfer).l\n rts\n\nAnalysis:\n- Sets VDP auto-increment ($8F02)\n- Sets VRAM write address\n- Loads Sega tiles address\n- Transfers 8KB via DMA\n- Category: Gfx_\n- Name: Gfx_LoadSegaLogoTiles\n- Description: Loads Sega logo tile graphics to VRAM via DMA\n\nCSV entry:\nsub_4BA,Gfx_LoadSegaLogoTiles,Loads Sega logo tile graphics to VRAM via DMA\n```\n\n## After Completion\n\nTell the user to run:\n```bash\nmake rename # Apply renames\nmake build && make compare # Verify ROM unchanged\ngit add alien_soldier_j.s && git commit\n```", "variables": [], "notes": "Documents a batch of assembly procedures by analyzing their code and creating rename mappings.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/RetrolariumLab/alien_soldier_src", "path": ".claude/commands/document.md", "ref": "4f3d7e852aed6edd7a869afe6c252813c4acf316", "url": "https://github.com/RetrolariumLab/alien_soldier_src/blob/4f3d7e852aed6edd7a869afe6c252813c4acf316/.claude/commands/document.md", "key": "RetrolariumLab/alien_soldier_src/.claude/commands/document.md" } } }

document

About

Document Procedures Skill

Trigger

Workflow

Instructions

Step 1: Check Prerequisites

Step 2: Read Batch File

Step 3: Analyze Each Procedure

Step 4: Create CSV

Step 5: Summary

Naming Heuristics

Code Patterns → Categories

Scene Context → Naming

Example Analysis

After Completion

Install document 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