Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/aliarghyani/vue-cursor-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/ui-kits-guide)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/ui-kits-guide"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/ui-kits-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/ui-kits-guide"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/ui-kits-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00667 |
| Opus 5.5 | $0.00000 | $0.00267 |
| Sonnet 5.5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
ui-kits-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Kits Guide
Role: You are a Vue 3 expert specializing in UI framework integration and component adaptation.
Core Rules:
- Keep core Vue patterns UI-framework neutral
- Adapt templates while preserving composable logic
- Choose kits based on project needs and design system
- Maintain TypeScript support across all integrations
- Use native Vue reactivity regardless of UI kit
Chain-of-Thought: Think step-by-step: 1. Choose appropriate UI kit 2. Apply core Vue rule 3. Adapt template syntax 4. Preserve reactivity patterns
Popular UI Kit Compatibility
| Kit | Best For | Strengths | Integration Focus |
|---|---|---|---|
| Tailwind UI/Headless UI | Custom designs | Full control, accessibility | Utility classes + composables |
| Vuetify | Material Design | Complete ecosystem | Component replacement |
| Quasar | Cross-platform | Mobile-first, PWA | Universal components |
| Element Plus | Enterprise/Admin | Rich components | Form-heavy apps |
Integration Patterns
Generic Composable (Kit-Agnostic)
// composables/useFormValidation.ts - Works with any UI kit
export function useFormValidation<T>(initialValues: T) {
const values = ref(initialValues)
const errors = ref<Record<string, string>>({})
// Core logic stays the same regardless of UI kit
const validate = () => {
// Validation logic here
}
return { values, errors, validate }
}
Tailwind UI Adaptation
<script setup lang="ts">
import { useFormValidation } from '@/composables/useFormValidation'
const { values, errors, validate } = useFormValidation({ email: '' })
</script>
<template>
<input
v-model="values.email"
class="block w-full rounded-md border-gray-300 focus:border-blue-500"
:class="{ 'border-red-300': errors.email }"
/>
</template>
Vuetify Adaptation
<script setup lang="ts">
// Same composable logic
const { values, errors, validate } = useFormValidation({ email: '' })
</script>
<template>
<v-text-field
v-model="values.email"
label="Email"
:error-messages="errors.email"
/>
</template>
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 101 lines · 0 tokens per session scan A b51fa534f9f9
ui-kits-guide is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 667 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
frontend-rules
A frontend development rule that points to existing Vue pages and components as examples. It refers to chat, notebook, and button files in the project.
frontend
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Ant Design Vue, and UnoCSS, with a deep understanding of best practices and performance optimization techniques in these technologies.