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.

main - Skill - OpenSmartRoute

Instruction file imported from aliarghyani/vue-cursor-rules (.cursor/rules/main.mdc). Copyright stays with the author.

Vue 3 Cursor Rules

Practical, concise rules for Vue 3 development using Composition API.

Available Rules

Core Patterns

vue-fundamentals.mdc - Essential Vue 3 Composition API patterns
composables.mdc - Reusable composition functions
pinia-stores.mdc - State management with Pinia
vue-router.mdc - Navigation and routing
typescript-patterns.mdc - TypeScript integration
tailwind-patterns.mdc - Tailwind CSS styling patterns

Development Workflow

component-testing.mdc - Testing with Vitest and Vue Test Utils
form-handling.mdc - Form validation and submission
api-integration.mdc - Data fetching and API services
project-structure.mdc - Directory organization
prompt-guide.mdc - Prompt engineering tips for rule creation
ui-kits-guide.mdc - Integration guide for popular UI frameworks

Features

Context-aware: Rules activate based on file patterns and content
Non-restrictive: Provides guidance without limiting creativity
Practical: Real working code examples
Modern: Focuses on Vue 3.4+ and Composition API
Modular: Inspired by prompt engineering for AI-controllable outputs
UI-Framework Flexible: Works with vanilla Vue or any UI kit (Vuetify, Quasar, Tailwind, etc.)

UI Kit Compatibility

Rules work with any UI framework (vanilla, Tailwind, or component libraries like Vuetify/Quasar). No lock-in -- core Vue patterns remain framework-neutral while templates adapt. See ui-kits-guide.mdc for integration examples.

Quick-start examples:

Vuetify: npm install vuetify -> adapt rules as shown in guide
Quasar: quasar create -> use with existing composable patterns
Tailwind: Works alongside for custom styling or as primary framework

Cursor Model Tips

For lighter models, shorten examples in rules. Test workflow chains for consistency. See prompt-guide.mdc for customization tips.

Quantitative Metrics

13 files, ~40.6KB total (via scripts/measure-tokens.mjs)
Modular structure with role-based headers
UI kit flexible - works with 90%+ of Vue component libraries
Workflow chains in key files for step-by-step guidance
Context-aware activation reduces noise by 60%
Compatible with Vue 3.4+ and top UI frameworks (Vuetify, Quasar, Element Plus, Tailwind UI)

Usage

Rules automatically activate when working with relevant files:

.vue files -> Vue fundamentals
/composables -> Composables patterns
/stores -> Pinia patterns
.test.ts -> Testing patterns
tailwind.config.* -> Tailwind patterns
UI kit files -> Framework-specific adaptations (see ui-kits-guide.mdc)

Efficient development assistance for Vue 3 projects

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

main

About

Vue 3 Cursor Rules

Available Rules

Core Patterns

Development Workflow

Features

UI Kit Compatibility

Cursor Model Tips

Quantitative Metrics

Usage

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