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.

project-orient - Prompt - OpenSmartRoute

Name: project-orient
Author: Knpod65

Prompt file imported from Knpod65/s2ims (.claude/commands/project-orient.md). Copyright stays with the author.

/project-orient — S²IMS Session Orientation

Purpose: Orient a new Claude session to the current project state. Run this at the start of every session.

When to use: First command in any new Claude Code session on S²IMS.

Framework detection — run before choosing verification method:

# Detect repo type at session start
test -f artisan && echo "ARTISAN: FOUND" || echo "ARTISAN: NOT FOUND"
test -f composer.json && grep -q '"laravel/framework"' composer.json \
  && echo "LARAVEL: DETECTED" || echo "LARAVEL: NOT DETECTED"
test -f package.json && grep -q '"next"' package.json \
  && echo "NEXT.JS: DETECTED" || echo "NEXT.JS: NOT DETECTED"

S²IMS result: NEXT.JS DETECTED — use npm verification only. Never run php artisan in S²IMS. For unknown or mixed repos: see docs/architecture/S2IMS_CROSS_REPO_ROUTE_VERIFICATION_DECISION_TREE_MC84.md.

Files to read (in order):

docs/architecture/NEXT_RENOVATION_STEPS.md — last 60 lines only (current MC status)
Most recent docs/daily-reports/*.md — last 2 files by name (what was done recently)
git log --oneline -10 — recent commit history

Files NOT to touch: Any src/, tools/, scripts/*, package.json

Behavior:

Run git log --oneline -10 to see recent commits
Read last 60 lines of NEXT_RENOVATION_STEPS.md
Find the 2 most recent daily reports (sort by filename date descending)
Summarize: current MC status, last completed work, active branch if any, recommended next action

Output format:

## S²IMS Session Orientation

**Current Branch**: [branch name]
**Main HEAD**: [commit hash]
**Last MC Completed**: MC[N] — [description]
**MC[N+1] Status**: [ready / in-progress / blocked]

### Recent Work
- [commit hash]: [message]

### Recommended Next Action
[1-2 sentences on what to do next]

Resource discovery — include this table in orientation output:

| Resource | Available? | Will Use? | Reason |
|----------|-----------|-----------|--------|
| /commands | List found | [Y/N] | ... |
| Skills    | List found | [Y/N] | ... |
| Subagents | List available | [Y/N] | ... |
| Connectors| List relevant | [Y/N] | ... |

Run: find .claude -maxdepth 4 -type f 2>/dev/null | sort to discover available commands and skills.

Resource usage standard: See docs/architecture/S2IMS_CLAUDE_RESOURCE_USAGE_STANDARD_MC75.md for full connector decision table and session report format.

Token-saving rules:

Read ONLY the last 60 lines of NEXT_RENOVATION_STEPS.md (not the full 3000+ lines)
Read ONLY 2 most recent daily reports
Do NOT read all design docs
Do NOT run npm build during orientation

Safety boundaries:

Read-only — no file changes, no commits, no npm commands

Install project-orient 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.

# /project-orient — S²IMS Session Orientation **Purpose**: Orient a new Claude session to the current project state. Run this at the start of every session. **When to use**: First command in any new Claude Code session on S²IMS. **Framework detection** — run before choosing verification method: ```bash # Detect repo type at session start test -f artisan && echo "ARTISAN: FOUND" || echo "ARTISAN: NOT FOUND" test -f composer.json && grep -q '"laravel/framework"' composer.json \ && echo "LARAVEL: DETECTED" || echo "LARAVEL: NOT DETECTED" test -f package.json && grep -q '"next"' package.json \ && echo "NEXT.JS: DETECTED" || echo "NEXT.JS: NOT DETECTED" ``` S²IMS result: NEXT.JS DETECTED — use npm verification only. Never run `php artisan` in S²IMS. For unknown or mixed repos: see `docs/architecture/S2IMS_CROSS_REPO_ROUTE_VERIFICATION_DECISION_TREE_MC84.md`. **Files to read (in order)**: 1. `docs/architecture/NEXT_RENOVATION_STEPS.md` — last 60 lines only (current MC status) 2. Most recent `docs/daily-reports/*.md` — last 2 files by name (what was done recently) 3. `git log --oneline -10` — recent commit history **Files NOT to touch**: Any src/*, tools/*, scripts/*, package.json **Behavior**: 1. Run `git log --oneline -10` to see recent commits 2. Read last 60 lines of NEXT_RENOVATION_STEPS.md 3. Find the 2 most recent daily reports (sort by filename date descending) 4. Summarize: current MC status, last completed work, active branch if any, recommended next action **Output format**: ``` ## S²IMS Session Orientation **Current Branch**: [branch name] **Main HEAD**: [commit hash] **Last MC Completed**: MC[N] — [description] **MC[N+1] Status**: [ready / in-progress / blocked] ### Recent Work - [commit hash]: [message] ### Recommended Next Action [1-2 sentences on what to do next] ``` **Resource discovery** — include this table in orientation output: ``` | Resource | Available? | Will Use? | Reason | |----------|-----------|-----------|--------| | /commands | List found | [Y/N] | ... | | Skills | List found | [Y/N] | ... | | Subagents | List available | [Y/N] | ... | | Connectors| List relevant | [Y/N] | ... | ``` Run: `find .claude -maxdepth 4 -type f 2>/dev/null | sort` to discover available commands and skills. **Resource usage standard**: See `docs/architecture/S2IMS_CLAUDE_RESOURCE_USAGE_STANDARD_MC75.md` for full connector decision table and session report format. **Token-saving rules**: - Read ONLY the last 60 lines of NEXT_RENOVATION_STEPS.md (not the full 3000+ lines) - Read ONLY 2 most recent daily reports - Do NOT read all design docs - Do NOT run npm build during orientation **Safety boundaries**: - Read-only — no file changes, no commits, no npm commands

{ "prompt": "# /project-orient — S²IMS Session Orientation\n\n**Purpose**: Orient a new Claude session to the current project state. Run this at the start of every session.\n\n**When to use**: First command in any new Claude Code session on S²IMS.\n\n**Framework detection** — run before choosing verification method:\n```bash\n# Detect repo type at session start\ntest -f artisan && echo \"ARTISAN: FOUND\" || echo \"ARTISAN: NOT FOUND\"\ntest -f composer.json && grep -q '\"laravel/framework\"' composer.json \\\n && echo \"LARAVEL: DETECTED\" || echo \"LARAVEL: NOT DETECTED\"\ntest -f package.json && grep -q '\"next\"' package.json \\\n && echo \"NEXT.JS: DETECTED\" || echo \"NEXT.JS: NOT DETECTED\"\n```\nS²IMS result: NEXT.JS DETECTED — use npm verification only. Never run `php artisan` in S²IMS.\nFor unknown or mixed repos: see `docs/architecture/S2IMS_CROSS_REPO_ROUTE_VERIFICATION_DECISION_TREE_MC84.md`.\n\n**Files to read (in order)**:\n1. `docs/architecture/NEXT_RENOVATION_STEPS.md` — last 60 lines only (current MC status)\n2. Most recent `docs/daily-reports/*.md` — last 2 files by name (what was done recently)\n3. `git log --oneline -10` — recent commit history\n\n**Files NOT to touch**: Any src/*, tools/*, scripts/*, package.json\n\n**Behavior**:\n1. Run `git log --oneline -10` to see recent commits\n2. Read last 60 lines of NEXT_RENOVATION_STEPS.md\n3. Find the 2 most recent daily reports (sort by filename date descending)\n4. Summarize: current MC status, last completed work, active branch if any, recommended next action\n\n**Output format**:\n```\n## S²IMS Session Orientation\n\n**Current Branch**: [branch name]\n**Main HEAD**: [commit hash]\n**Last MC Completed**: MC[N] — [description]\n**MC[N+1] Status**: [ready / in-progress / blocked]\n\n### Recent Work\n- [commit hash]: [message]\n\n### Recommended Next Action\n[1-2 sentences on what to do next]\n```\n\n**Resource discovery** — include this table in orientation output:\n```\n| Resource | Available? | Will Use? | Reason |\n|----------|-----------|-----------|--------|\n| /commands | List found | [Y/N] | ... |\n| Skills | List found | [Y/N] | ... |\n| Subagents | List available | [Y/N] | ... |\n| Connectors| List relevant | [Y/N] | ... |\n```\nRun: `find .claude -maxdepth 4 -type f 2>/dev/null | sort` to discover available commands and skills.\n\n**Resource usage standard**: See `docs/architecture/S2IMS_CLAUDE_RESOURCE_USAGE_STANDARD_MC75.md` for full connector decision table and session report format.\n\n**Token-saving rules**:\n- Read ONLY the last 60 lines of NEXT_RENOVATION_STEPS.md (not the full 3000+ lines)\n- Read ONLY 2 most recent daily reports\n- Do NOT read all design docs\n- Do NOT run npm build during orientation\n\n**Safety boundaries**:\n- Read-only — no file changes, no commits, no npm commands", "variables": [], "notes": "/project-orient — S²IMS Session Orientation", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/Knpod65/s2ims", "path": ".claude/commands/project-orient.md", "ref": "422420c09cc3e10c1f3220e2b6fdc35b7b63c477", "url": "https://github.com/Knpod65/s2ims/blob/422420c09cc3e10c1f3220e2b6fdc35b7b63c477/.claude/commands/project-orient.md", "key": "Knpod65/s2ims/.claude/commands/project-orient.md" } } }

project-orient

About

/project-orient — S²IMS Session Orientation

Install project-orient 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