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.

shape - Prompt - OpenSmartRoute

Name: shape
Author: edwardlthompson

Prompt file imported from edwardlthompson/agent-project-bootstrap (.cursor/commands/shape.md). Copyright stays with the author.

/shape — idea → spec (coach mode)

Turn a rough idea into a short, buildable spec. Write NO application code. Twin: docs/help/SHAPE.md. Specs live under docs/specs/.

0. Size gate

TRIVIAL (obvious, ≤ ~3 files): say "Small enough — want me to just do it?" and stop.
Several features: propose the split, shape only the first.
User said skip / defaults: ask nothing; write the spec with flagged assumptions.

1. Look first

Skim README, BUILD_PLAN.md, and files this idea touches. Must read docs/PREFERENCES.md (coding patterns, workflow, and vibe-coding security risks). Never ask what the code or preferences already answer. Report ONE line: what you found that matters.

2. Mirror

"Here's what I heard: <1–2 sentences>." Invite correction.

3. One batch, max 5 questions

Only questions whose answers would change the build. Skip any already clear.

Format each question with blank lines between options (never cramped a/b/c on one line):

1. · <plain question>
   · Why it matters: <≤8 words>

   a) <option>
   b) <option> ★ recommended
   c) <option>

   or tell me

Cover, in this order:

Trigger + happy path
"Done looks like"
Out of scope
Must-not-break / constraints
One concrete example

End with: Reply like \1a 2b 3 skip` — or say `defaults`.`

/shape deep = one question at a time instead.

4. Vague answers

Don't re-ask. Offer two concrete phrasings; I pick one.

5. Write docs/specs/{slug}.md (≤ 40 lines)

Goal · Trigger/users · Requirements · Out of scope · Acceptance checks · Assumptions I made (flagged) · Open questions · Files likely touched. Behavior only (what/why). No implementation unless I specified it. Use docs/specs/_TEMPLATE.md as the skeleton.

6. Hand off, then STOP

Add one BUILD_PLAN.md [AGENT][LOCAL] row linking the spec.
Print: spec path, 3-line summary, and: "Edit the spec if anything's off. To build: new chat → Implement @docs/specs/{slug}.md (cheaper model is fine)."
Offer to append any new durable preference to docs/PREFERENCES.md (ask first).

Begin now.

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

# /shape — idea → spec (coach mode) Turn a rough idea into a short, buildable spec. Write **NO** application code. Twin: `docs/help/SHAPE.md`. Specs live under `docs/specs/`. ## 0. Size gate - TRIVIAL (obvious, ≤ ~3 files): say "Small enough — want me to just do it?" and stop. - Several features: propose the split, shape only the first. - User said `skip` / `defaults`: ask nothing; write the spec with flagged assumptions. ## 1. Look first Skim README, BUILD_PLAN.md, and files this idea touches. **Must read** `docs/PREFERENCES.md` (coding patterns, workflow, and vibe-coding security risks). Never ask what the code or preferences already answer. Report ONE line: what you found that matters. ## 2. Mirror "Here's what I heard: <1–2 sentences>." Invite correction. ## 3. One batch, max 5 questions Only questions whose answers would change the build. Skip any already clear. **Format each question with blank lines between options** (never cramped `a/b/c` on one line): ```text 1. · <plain question> · Why it matters: <≤8 words> a) <option> b) <option> ★ recommended c) <option> or tell me ``` Cover, in this order: 1. Trigger + happy path 2. "Done looks like" 3. Out of scope 4. Must-not-break / constraints 5. One concrete example End with: `Reply like \`1a 2b 3 skip\` — or say \`defaults\`.` `/shape deep` = one question at a time instead. ## 4. Vague answers Don't re-ask. Offer two concrete phrasings; I pick one. ## 5. Write docs/specs/{slug}.md (≤ 40 lines) Goal · Trigger/users · Requirements · Out of scope · Acceptance checks · Assumptions I made (flagged) · Open questions · Files likely touched. Behavior only (what/why). No implementation unless I specified it. Use `docs/specs/_TEMPLATE.md` as the skeleton. ## 6. Hand off, then STOP - Add one BUILD_PLAN.md `[AGENT][LOCAL]` row linking the spec. - Print: spec path, 3-line summary, and: "Edit the spec if anything's off. To build: new chat → `Implement @docs/specs/{slug}.md` (cheaper model is fine)." - Offer to append any new durable preference to docs/PREFERENCES.md (ask first). Begin now.

{ "prompt": "# /shape — idea → spec (coach mode)\n\nTurn a rough idea into a short, buildable spec. Write **NO** application code.\nTwin: `docs/help/SHAPE.md`. Specs live under `docs/specs/`.\n\n## 0. Size gate\n\n- TRIVIAL (obvious, ≤ ~3 files): say \"Small enough — want me to just do it?\" and stop.\n- Several features: propose the split, shape only the first.\n- User said `skip` / `defaults`: ask nothing; write the spec with flagged assumptions.\n\n## 1. Look first\n\nSkim README, BUILD_PLAN.md, and files this idea touches.\n**Must read** `docs/PREFERENCES.md` (coding patterns, workflow, and vibe-coding security risks).\nNever ask what the code or preferences already answer.\nReport ONE line: what you found that matters.\n\n## 2. Mirror\n\n\"Here's what I heard: <1–2 sentences>.\" Invite correction.\n\n## 3. One batch, max 5 questions\n\nOnly questions whose answers would change the build. Skip any already clear.\n\n**Format each question with blank lines between options** (never cramped `a/b/c` on one line):\n\n```text\n1. · <plain question>\n · Why it matters: <≤8 words>\n\n a) <option>\n b) <option> ★ recommended\n c) <option>\n\n or tell me\n```\n\nCover, in this order:\n\n1. Trigger + happy path\n2. \"Done looks like\"\n3. Out of scope\n4. Must-not-break / constraints\n5. One concrete example\n\nEnd with: `Reply like \\`1a 2b 3 skip\\` — or say \\`defaults\\`.`\n\n`/shape deep` = one question at a time instead.\n\n## 4. Vague answers\n\nDon't re-ask. Offer two concrete phrasings; I pick one.\n\n## 5. Write docs/specs/{slug}.md (≤ 40 lines)\n\nGoal · Trigger/users · Requirements · Out of scope · Acceptance checks ·\nAssumptions I made (flagged) · Open questions · Files likely touched.\nBehavior only (what/why). No implementation unless I specified it.\nUse `docs/specs/_TEMPLATE.md` as the skeleton.\n\n## 6. Hand off, then STOP\n\n- Add one BUILD_PLAN.md `[AGENT][LOCAL]` row linking the spec.\n- Print: spec path, 3-line summary, and:\n \"Edit the spec if anything's off. To build: new chat → `Implement @docs/specs/{slug}.md`\n (cheaper model is fine).\"\n- Offer to append any new durable preference to docs/PREFERENCES.md (ask first).\n\nBegin now.", "variables": [], "notes": "Turn a rough idea into a short, buildable spec. Write **NO** application code. Twin: `docs/help/SHAPE.md`. Specs live under `docs/specs/`.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/edwardlthompson/agent-project-bootstrap", "path": ".cursor/commands/shape.md", "ref": "1f84eb0c021d91b36c9273e676c59cae30307726", "url": "https://github.com/edwardlthompson/agent-project-bootstrap/blob/1f84eb0c021d91b36c9273e676c59cae30307726/.cursor/commands/shape.md", "key": "edwardlthompson/agent-project-bootstrap/.cursor/commands/shape.md" } } }

shape

About

/shape — idea → spec (coach mode)

0. Size gate

1. Look first

2. Mirror

3. One batch, max 5 questions

4. Vague answers

5. Write docs/specs/{slug}.md (≤ 40 lines)

6. Hand off, then STOP

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