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.

TS-review-staged-unstaged - Prompt

Name: TS-review-staged-unstaged
Author: mauricio-morales

Prompt file imported from mauricio-morales/trashmail-panda (.claude/commands/typescript/TS-review-staged-unstaged.md). Fill in {{arguments}} before use. Copyright stays with the author.

List and review any files in the staging area, both staged and unstaged. Ensure you look at both new files and modified files.

Check the diff of each file to see what has changed.

Previous review report: {{arguments}}

May or may not be added, ignore the previous review if not specified.

Review Focus Areas

TypeScript Code Quality
- Strict TypeScript usage with explicit types
- No any types - use unknown if type is truly unknown
- Proper type imports with import type { } syntax
- Component props interfaces defined
- Astro's built-in types used (HTMLAttributes, ComponentProps)
- Following TypeScript strict mode compliance
Astro-Specific Patterns
- Proper hydration directives usage (client:load, client:visible, client:idle)
- Static-first approach with selective hydration
- Astro components for static content, framework components only for interactivity
- Proper use of Astro.props and component interfaces
- Content collections with Zod schemas
- Server islands implementation where appropriate
Performance & Bundle Optimization
- No unnecessary client-side JavaScript
- Appropriate hydration strategy choices
- Image optimization with Astro's Image component
- Bundle size considerations
- No over-hydration of static content
Security & Validation
- Input validation with Zod schemas
- Environment variables properly typed with astro:env
- Content Security Policy implementation
- No hardcoded secrets in client-side code
- API route validation with proper error handling
Content Management
- Content collections properly configured
- Zod schemas for all content types
- Type-safe content queries
- Proper content rendering and data handling
Package Management
- Using pnpm (not npm or yarn)
- Proper dependency management
- No unused dependencies
- Correct dev vs runtime dependencies
Code Structure & Architecture
- Components under 200 lines (500 line hard limit)
- Functions under 50 lines with single responsibility
- Proper separation of concerns
- Feature-based organization
- Islands architecture principles followed
Testing & Quality Assurance
- Vitest configuration and tests
- 80%+ test coverage maintained
- Component tests using Astro Container API
- API route integration tests
- Proper mocking of external dependencies
Build & Development
- astro check passes with zero errors
- ESLint compliance with zero warnings
- Prettier formatting applied
- Production build succeeds
- No hydration mismatches
Documentation & Maintenance
- Clear component interfaces
- Proper prop descriptions
- CLAUDE.md updates for new patterns/dependencies
- README updates if needed

Review Output

Create a concise review report with:

# TypeScript/Astro Code Review #[number]

## Summary

[2-3 sentence overview focusing on Astro-specific patterns and TypeScript quality]

## Issues Found

### 🔴 Critical (Must Fix)

- [Issue with file:line and suggested fix - focus on type safety, hydration, security]

### 🟡 Important (Should Fix)

- [Issue with file:line and suggested fix - focus on performance, patterns]

### 🟢 Minor (Consider)

- [Improvement suggestions for optimization, maintainability]

## Good Practices

- [What was done well - highlight proper Astro patterns, TypeScript usage]

## Astro-Specific Findings

- [Hydration strategy assessment]
- [Bundle size impact]
- [Content collection usage]
- [Performance optimizations]

## TypeScript Quality

- [Type safety assessment]
- [Strict mode compliance]
- [Interface definitions]

## Test Coverage

Current: X% | Required: 80%
Missing tests: [list with focus on component and API tests]

## Build Validation

- [ ] `astro check` passes
- [ ] `pnpm run lint` passes
- [ ] `pnpm run build` succeeds
- [ ] `pnpm test` passes with 80%+ coverage

Save report to PRPs/code_reviews/review[#].md (check existing files first)

Install TS-review-staged-unstaged 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.

List and review any files in the staging area, both staged and unstaged. Ensure you look at both new files and modified files. Check the diff of each file to see what has changed. Previous review report: {{arguments}} May or may not be added, ignore the previous review if not specified. ## Review Focus Areas 1. **TypeScript Code Quality** - Strict TypeScript usage with explicit types - No `any` types - use `unknown` if type is truly unknown - Proper type imports with `import type { }` syntax - Component props interfaces defined - Astro's built-in types used (HTMLAttributes, ComponentProps) - Following TypeScript strict mode compliance 2. **Astro-Specific Patterns** - Proper hydration directives usage (client:load, client:visible, client:idle) - Static-first approach with selective hydration - Astro components for static content, framework components only for interactivity - Proper use of Astro.props and component interfaces - Content collections with Zod schemas - Server islands implementation where appropriate 3. **Performance & Bundle Optimization** - No unnecessary client-side JavaScript - Appropriate hydration strategy choices - Image optimization with Astro's Image component - Bundle size considerations - No over-hydration of static content 4. **Security & Validation** - Input validation with Zod schemas - Environment variables properly typed with astro:env - Content Security Policy implementation - No hardcoded secrets in client-side code - API route validation with proper error handling 5. **Content Management** - Content collections properly configured - Zod schemas for all content types - Type-safe content queries - Proper content rendering and data handling 6. **Package Management** - Using pnpm (not npm or yarn) - Proper dependency management - No unused dependencies - Correct dev vs runtime dependencies 7. **Code Structure & Architecture** - Components under 200 lines (500 line hard limit) - Functions under 50 lines with single responsibility - Proper separation of concerns - Feature-based organization - Islands architecture principles followed 8. **Testing & Quality Assurance** - Vitest configuration and tests - 80%+ test coverage maintained - Component tests using Astro Container API - API route integration tests - Proper mocking of external dependencies 9. **Build & Development** - `astro check` passes with zero errors - ESLint compliance with zero warnings - Prettier formatting applied - Production build succeeds - No hydration mismatches 10. **Documentation & Maintenance** - Clear component interfaces - Proper prop descriptions - CLAUDE.md updates for new patterns/dependencies - README updates if needed ## Review Output Create a concise review report with: ```markdown # TypeScript/Astro Code Review #[number] ## Summary [2-3 sentence overview focusing on Astro-specific patterns and TypeScript quality] ## Issues Found ### 🔴 Critical (Must Fix) - [Issue with file:line and suggested fix - focus on type safety, hydration, security] ### 🟡 Important (Should Fix) - [Issue with file:line and suggested fix - focus on performance, patterns] ### 🟢 Minor (Consider) - [Improvement suggestions for optimization, maintainability] ## Good Practices - [What was done well - highlight proper Astro patterns, TypeScript usage] ## Astro-Specific Findings - [Hydration strategy assessment] - [Bundle size impact] - [Content collection usage] - [Performance optimizations] ## TypeScript Quality - [Type safety assessment] - [Strict mode compliance] - [Interface definitions] ## Test Coverage Current: X% | Required: 80% Missing tests: [list with focus on component and API tests] ## Build Validation - [ ] `astro check` passes - [ ] `pnpm run lint` passes - [ ] `pnpm run build` succeeds - [ ] `pnpm test` passes with 80%+ coverage ``` Save report to PRPs/code_reviews/review[#].md (check existing files first)

{ "prompt": "List and review any files in the staging area, both staged and unstaged.\nEnsure you look at both new files and modified files.\n\nCheck the diff of each file to see what has changed.\n\nPrevious review report: {{arguments}}\n\nMay or may not be added, ignore the previous review if not specified.\n\n## Review Focus Areas\n\n1. **TypeScript Code Quality**\n - Strict TypeScript usage with explicit types\n - No `any` types - use `unknown` if type is truly unknown\n - Proper type imports with `import type { }` syntax\n - Component props interfaces defined\n - Astro's built-in types used (HTMLAttributes, ComponentProps)\n - Following TypeScript strict mode compliance\n\n2. **Astro-Specific Patterns**\n - Proper hydration directives usage (client:load, client:visible, client:idle)\n - Static-first approach with selective hydration\n - Astro components for static content, framework components only for interactivity\n - Proper use of Astro.props and component interfaces\n - Content collections with Zod schemas\n - Server islands implementation where appropriate\n\n3. **Performance & Bundle Optimization**\n - No unnecessary client-side JavaScript\n - Appropriate hydration strategy choices\n - Image optimization with Astro's Image component\n - Bundle size considerations\n - No over-hydration of static content\n\n4. **Security & Validation**\n - Input validation with Zod schemas\n - Environment variables properly typed with astro:env\n - Content Security Policy implementation\n - No hardcoded secrets in client-side code\n - API route validation with proper error handling\n\n5. **Content Management**\n - Content collections properly configured\n - Zod schemas for all content types\n - Type-safe content queries\n - Proper content rendering and data handling\n\n6. **Package Management**\n - Using pnpm (not npm or yarn)\n - Proper dependency management\n - No unused dependencies\n - Correct dev vs runtime dependencies\n\n7. **Code Structure & Architecture**\n - Components under 200 lines (500 line hard limit)\n - Functions under 50 lines with single responsibility\n - Proper separation of concerns\n - Feature-based organization\n - Islands architecture principles followed\n\n8. **Testing & Quality Assurance**\n - Vitest configuration and tests\n - 80%+ test coverage maintained\n - Component tests using Astro Container API\n - API route integration tests\n - Proper mocking of external dependencies\n\n9. **Build & Development**\n - `astro check` passes with zero errors\n - ESLint compliance with zero warnings\n - Prettier formatting applied\n - Production build succeeds\n - No hydration mismatches\n\n10. **Documentation & Maintenance**\n - Clear component interfaces\n - Proper prop descriptions\n - CLAUDE.md updates for new patterns/dependencies\n - README updates if needed\n\n## Review Output\n\nCreate a concise review report with:\n\n```markdown\n# TypeScript/Astro Code Review #[number]\n\n## Summary\n\n[2-3 sentence overview focusing on Astro-specific patterns and TypeScript quality]\n\n## Issues Found\n\n### 🔴 Critical (Must Fix)\n\n- [Issue with file:line and suggested fix - focus on type safety, hydration, security]\n\n### 🟡 Important (Should Fix)\n\n- [Issue with file:line and suggested fix - focus on performance, patterns]\n\n### 🟢 Minor (Consider)\n\n- [Improvement suggestions for optimization, maintainability]\n\n## Good Practices\n\n- [What was done well - highlight proper Astro patterns, TypeScript usage]\n\n## Astro-Specific Findings\n\n- [Hydration strategy assessment]\n- [Bundle size impact]\n- [Content collection usage]\n- [Performance optimizations]\n\n## TypeScript Quality\n\n- [Type safety assessment]\n- [Strict mode compliance]\n- [Interface definitions]\n\n## Test Coverage\n\nCurrent: X% | Required: 80%\nMissing tests: [list with focus on component and API tests]\n\n## Build Validation\n\n- [ ] `astro check` passes\n- [ ] `pnpm run lint` passes\n- [ ] `pnpm run build` succeeds\n- [ ] `pnpm test` passes with 80%+ coverage\n```\n\nSave report to PRPs/code_reviews/review[#].md (check existing files first)", "variables": [ "arguments" ], "notes": "List and review any files in the staging area, both staged and unstaged. Ensure you look at both new files and modified files.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/mauricio-morales/trashmail-panda", "path": ".claude/commands/typescript/TS-review-staged-unstaged.md", "ref": "fabfae6834937751ee0967882224b890893eaafb", "url": "https://github.com/mauricio-morales/trashmail-panda/blob/fabfae6834937751ee0967882224b890893eaafb/.claude/commands/typescript/TS-review-staged-unstaged.md", "key": "mauricio-morales/trashmail-panda/.claude/commands/typescript/TS-review-staged-unstaged.md" } } }

TS-review-staged-unstaged

About

Review Focus Areas

Review Output

Install TS-review-staged-unstaged 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