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.

adr - Prompt - OpenSmartRoute

Name: adr
Author: mgiovani

Prompt file imported from mgiovani/ai-cursor-init (.cursor/commands/cursor-init/adr.md). Copyright stays with the author.

Create Architecture Decision Record

Create a new Architecture Decision Record (ADR) documenting an architectural decision.

What This Does

Generates a structured ADR document following industry best practices:

Configuration Check: Verifies if documentation.core.adr is explicitly disabled in .cursor-init.yaml
Extract Title: Gets the decision title from your command (text after /adr)
Determine Number: Scans docs/adr/ directory for the highest existing ADR number and increments
Template Selection: Uses configured ADR template variant (nygard_style, full, lightweight, madr)
Context Gathering: Uses codebase search to find relevant information for the ADR topic
Generate ADR: Creates numbered ADR file in docs/adr/ with format 000X-sanitized-title.md
Populate Content: Fills template with title, number, date, and gathered context

Usage

Basic ADR creation:

/adr "Database Migration Strategy"

With template variant override:

/adr lightweight "Quick Technical Decision"

Additional examples:

/adr "API Authentication Approach"
/adr "Frontend Framework Selection"
/adr "Microservices Communication Pattern"

Template Variants

Configure default variant in .cursor-init.yaml:

templates:
  adr: "nygard_style"  # Options: nygard_style, full, lightweight, madr

Nygard Style (Default)

Michael Nygard's ADR format - concise and focused.

Sections:

Title
Status (Proposed, Accepted, Deprecated, Superseded)
Context
Decision
Consequences

Full Template

Comprehensive ADR with detailed sections.

Sections:

Title
Status
Context
Decision Drivers
Considered Options
Decision
Consequences (Positive, Negative, Neutral)
Pros and Cons
Related Decisions
References

Lightweight Template

Minimal ADR for quick decisions.

Sections:

Title
Status
Decision
Rationale

MADR Template

Markdown Architectural Decision Records format.

Sections:

Title
Status
Context and Problem Statement
Decision Drivers
Considered Options
Decision Outcome
Consequences

Parameter Override

Override default template for specific ADR:

/adr lightweight "Use Redis for Session Storage"
/adr full "Adopt Event-Driven Architecture"
/adr madr "Select Database Technology"

Example Output

File: docs/adr/0006-use-redis-for-session-storage.md

# ADR-0006: Use Redis for Session Storage

**Status:** Proposed

**Context:**
Our application needs to handle user sessions across multiple server instances in a distributed environment. Currently using in-memory sessions, which doesn't work with horizontal scaling.

**Decision:**
Adopt Redis as the session storage backend for distributed session management.

**Consequences:**

**Positive:**
- Enables horizontal scaling of application servers
- Fast session read/write performance (sub-millisecond)
- Built-in expiration for session cleanup
- Widely supported by frameworks

**Negative:**
- Additional infrastructure dependency
- Requires Redis monitoring and maintenance
- Network latency for session operations

**Neutral:**
- Need to implement Redis connection pooling
- Must handle Redis failover scenarios

ADR Numbering

First ADR: 0001-record-architecture-decisions.md (meta-ADR)
Subsequent ADRs: Auto-incremented (0002, 0003, etc.)
Format: XXXX-kebab-case-title.md

Configuration

Disable ADR creation:

documentation:
  core:
    adr: false  # Prevents ADR generation

If ADR documentation is disabled, I will inform you and skip creation.

Process

I will:

Check if ADR documentation is disabled in configuration
Extract the decision title from your command
Sanitize title to kebab-case for filename
Check docs/adr/ for highest number
Increment to get new ADR number
Load configured ADR template variant
Gather context from codebase related to the decision
Populate template with:
- ADR number
- Title
- Current date
- Status: "Proposed"
- Relevant context from codebase
Create file in docs/adr/000X-title.md
Report creation with ADR number

When to Create ADRs

Create an ADR when making:

Technology stack decisions
Architecture pattern choices
Database or storage decisions
API design choices
Security architecture decisions
Deployment strategy decisions
Major library/framework selections

Best Practices

Create ADRs early in decision process
Update status as decision progresses (Proposed → Accepted)
Link related ADRs together
Keep focused on one decision per ADR
Include context even if it seems obvious

Template Location: .cursor/cursor-init/templates/adr/ Configuration File: .cursor-init.yaml (optional) Output Directory: docs/adr/

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

# Create Architecture Decision Record Create a new Architecture Decision Record (ADR) documenting an architectural decision. ## What This Does Generates a structured ADR document following industry best practices: 1. **Configuration Check**: Verifies if `documentation.core.adr` is explicitly disabled in `.cursor-init.yaml` 2. **Extract Title**: Gets the decision title from your command (text after `/adr`) 3. **Determine Number**: Scans `docs/adr/` directory for the highest existing ADR number and increments 4. **Template Selection**: Uses configured ADR template variant (nygard_style, full, lightweight, madr) 5. **Context Gathering**: Uses codebase search to find relevant information for the ADR topic 6. **Generate ADR**: Creates numbered ADR file in `docs/adr/` with format `000X-sanitized-title.md` 7. **Populate Content**: Fills template with title, number, date, and gathered context ## Usage Basic ADR creation: ``` /adr "Database Migration Strategy" ``` With template variant override: ``` /adr lightweight "Quick Technical Decision" ``` Additional examples: ``` /adr "API Authentication Approach" /adr "Frontend Framework Selection" /adr "Microservices Communication Pattern" ``` ## Template Variants Configure default variant in `.cursor-init.yaml`: ```yaml templates: adr: "nygard_style" # Options: nygard_style, full, lightweight, madr ``` ### Nygard Style (Default) Michael Nygard's ADR format - concise and focused. **Sections:** - Title - Status (Proposed, Accepted, Deprecated, Superseded) - Context - Decision - Consequences ### Full Template Comprehensive ADR with detailed sections. **Sections:** - Title - Status - Context - Decision Drivers - Considered Options - Decision - Consequences (Positive, Negative, Neutral) - Pros and Cons - Related Decisions - References ### Lightweight Template Minimal ADR for quick decisions. **Sections:** - Title - Status - Decision - Rationale ### MADR Template Markdown Architectural Decision Records format. **Sections:** - Title - Status - Context and Problem Statement - Decision Drivers - Considered Options - Decision Outcome - Consequences ## Parameter Override Override default template for specific ADR: ``` /adr lightweight "Use Redis for Session Storage" /adr full "Adopt Event-Driven Architecture" /adr madr "Select Database Technology" ``` ## Example Output File: `docs/adr/0006-use-redis-for-session-storage.md` ```markdown # ADR-0006: Use Redis for Session Storage **Status:** Proposed **Context:** Our application needs to handle user sessions across multiple server instances in a distributed environment. Currently using in-memory sessions, which doesn't work with horizontal scaling. **Decision:** Adopt Redis as the session storage backend for distributed session management. **Consequences:** **Positive:** - Enables horizontal scaling of application servers - Fast session read/write performance (sub-millisecond) - Built-in expiration for session cleanup - Widely supported by frameworks **Negative:** - Additional infrastructure dependency - Requires Redis monitoring and maintenance - Network latency for session operations **Neutral:** - Need to implement Redis connection pooling - Must handle Redis failover scenarios ``` ## ADR Numbering - First ADR: `0001-record-architecture-decisions.md` (meta-ADR) - Subsequent ADRs: Auto-incremented (0002, 0003, etc.) - Format: `XXXX-kebab-case-title.md` ## Configuration Disable ADR creation: ```yaml documentation: core: adr: false # Prevents ADR generation ``` If ADR documentation is disabled, I will inform you and skip creation. ## Process I will: 1. Check if ADR documentation is disabled in configuration 2. Extract the decision title from your command 3. Sanitize title to kebab-case for filename 4. Check `docs/adr/` for highest number 5. Increment to get new ADR number 6. Load configured ADR template variant 7. Gather context from codebase related to the decision 8. Populate template with: - ADR number - Title - Current date - Status: "Proposed" - Relevant context from codebase 9. Create file in `docs/adr/000X-title.md` 10. Report creation with ADR number ## When to Create ADRs Create an ADR when making: - Technology stack decisions - Architecture pattern choices - Database or storage decisions - API design choices - Security architecture decisions - Deployment strategy decisions - Major library/framework selections ## Best Practices - Create ADRs early in decision process - Update status as decision progresses (Proposed → Accepted) - Link related ADRs together - Keep focused on one decision per ADR - Include context even if it seems obvious --- **Template Location**: `.cursor/cursor-init/templates/adr/` **Configuration File**: `.cursor-init.yaml` (optional) **Output Directory**: `docs/adr/`

{ "prompt": "# Create Architecture Decision Record\n\nCreate a new Architecture Decision Record (ADR) documenting an architectural decision.\n\n## What This Does\n\nGenerates a structured ADR document following industry best practices:\n\n1. **Configuration Check**: Verifies if `documentation.core.adr` is explicitly disabled in `.cursor-init.yaml`\n2. **Extract Title**: Gets the decision title from your command (text after `/adr`)\n3. **Determine Number**: Scans `docs/adr/` directory for the highest existing ADR number and increments\n4. **Template Selection**: Uses configured ADR template variant (nygard_style, full, lightweight, madr)\n5. **Context Gathering**: Uses codebase search to find relevant information for the ADR topic\n6. **Generate ADR**: Creates numbered ADR file in `docs/adr/` with format `000X-sanitized-title.md`\n7. **Populate Content**: Fills template with title, number, date, and gathered context\n\n## Usage\n\nBasic ADR creation:\n```\n/adr \"Database Migration Strategy\"\n```\n\nWith template variant override:\n```\n/adr lightweight \"Quick Technical Decision\"\n```\n\nAdditional examples:\n```\n/adr \"API Authentication Approach\"\n/adr \"Frontend Framework Selection\"\n/adr \"Microservices Communication Pattern\"\n```\n\n## Template Variants\n\nConfigure default variant in `.cursor-init.yaml`:\n\n```yaml\ntemplates:\n adr: \"nygard_style\" # Options: nygard_style, full, lightweight, madr\n```\n\n### Nygard Style (Default)\nMichael Nygard's ADR format - concise and focused.\n\n**Sections:**\n- Title\n- Status (Proposed, Accepted, Deprecated, Superseded)\n- Context\n- Decision\n- Consequences\n\n### Full Template\nComprehensive ADR with detailed sections.\n\n**Sections:**\n- Title\n- Status\n- Context\n- Decision Drivers\n- Considered Options\n- Decision\n- Consequences (Positive, Negative, Neutral)\n- Pros and Cons\n- Related Decisions\n- References\n\n### Lightweight Template\nMinimal ADR for quick decisions.\n\n**Sections:**\n- Title\n- Status\n- Decision\n- Rationale\n\n### MADR Template\nMarkdown Architectural Decision Records format.\n\n**Sections:**\n- Title\n- Status\n- Context and Problem Statement\n- Decision Drivers\n- Considered Options\n- Decision Outcome\n- Consequences\n\n## Parameter Override\n\nOverride default template for specific ADR:\n\n```\n/adr lightweight \"Use Redis for Session Storage\"\n/adr full \"Adopt Event-Driven Architecture\"\n/adr madr \"Select Database Technology\"\n```\n\n## Example Output\n\nFile: `docs/adr/0006-use-redis-for-session-storage.md`\n\n```markdown\n# ADR-0006: Use Redis for Session Storage\n\n**Status:** Proposed\n\n**Context:**\nOur application needs to handle user sessions across multiple server instances in a distributed environment. Currently using in-memory sessions, which doesn't work with horizontal scaling.\n\n**Decision:**\nAdopt Redis as the session storage backend for distributed session management.\n\n**Consequences:**\n\n**Positive:**\n- Enables horizontal scaling of application servers\n- Fast session read/write performance (sub-millisecond)\n- Built-in expiration for session cleanup\n- Widely supported by frameworks\n\n**Negative:**\n- Additional infrastructure dependency\n- Requires Redis monitoring and maintenance\n- Network latency for session operations\n\n**Neutral:**\n- Need to implement Redis connection pooling\n- Must handle Redis failover scenarios\n```\n\n## ADR Numbering\n\n- First ADR: `0001-record-architecture-decisions.md` (meta-ADR)\n- Subsequent ADRs: Auto-incremented (0002, 0003, etc.)\n- Format: `XXXX-kebab-case-title.md`\n\n## Configuration\n\nDisable ADR creation:\n```yaml\ndocumentation:\n core:\n adr: false # Prevents ADR generation\n```\n\nIf ADR documentation is disabled, I will inform you and skip creation.\n\n## Process\n\nI will:\n1. Check if ADR documentation is disabled in configuration\n2. Extract the decision title from your command\n3. Sanitize title to kebab-case for filename\n4. Check `docs/adr/` for highest number\n5. Increment to get new ADR number\n6. Load configured ADR template variant\n7. Gather context from codebase related to the decision\n8. Populate template with:\n - ADR number\n - Title\n - Current date\n - Status: \"Proposed\"\n - Relevant context from codebase\n9. Create file in `docs/adr/000X-title.md`\n10. Report creation with ADR number\n\n## When to Create ADRs\n\nCreate an ADR when making:\n- Technology stack decisions\n- Architecture pattern choices\n- Database or storage decisions\n- API design choices\n- Security architecture decisions\n- Deployment strategy decisions\n- Major library/framework selections\n\n## Best Practices\n\n- Create ADRs early in decision process\n- Update status as decision progresses (Proposed → Accepted)\n- Link related ADRs together\n- Keep focused on one decision per ADR\n- Include context even if it seems obvious\n\n---\n\n**Template Location**: `.cursor/cursor-init/templates/adr/`\n**Configuration File**: `.cursor-init.yaml` (optional)\n**Output Directory**: `docs/adr/`", "variables": [], "notes": "Create a new Architecture Decision Record (ADR) documenting an architectural decision.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/mgiovani/ai-cursor-init", "path": ".cursor/commands/cursor-init/adr.md", "ref": "fc15400e4baab4607f408f5b83fed19263e564e3", "url": "https://github.com/mgiovani/ai-cursor-init/blob/fc15400e4baab4607f408f5b83fed19263e564e3/.cursor/commands/cursor-init/adr.md", "key": "mgiovani/ai-cursor-init/.cursor/commands/cursor-init/adr.md" } } }

adr

About

Create Architecture Decision Record

What This Does

Usage

Template Variants

Nygard Style (Default)

Full Template

Lightweight Template

MADR Template

Parameter Override

Example Output

ADR Numbering

Configuration

Process

When to Create ADRs

Best Practices

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