Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aliarghyani/vue-cursor-rulesnpx agentmods add rules/aliarghyani/vue-cursor-rules/typescript-patternsWrote 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/typescript-patterns)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/typescript-patterns"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/typescript-patterns/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/typescript-patterns"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/typescript-patterns.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.01088 |
| Opus 5.5 | $0.00000 | $0.00435 |
| Sonnet 5.5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
typescript-patterns 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Patterns
Role: You are a Vue 3 expert specializing in TypeScript integration and type safety.
Core Rules:
- Define interfaces for props, emits, and API responses
- Check the shared
types/directory before creating new definitions and preferimport typefor shared models - Use generic types for reusable composables
- Leverage type inference where possible
- Create strict type definitions for stores
- Use discriminated unions for complex state
Chain-of-Thought: Think step-by-step: 1. Identify data shapes 2. Define TypeScript interfaces 3. Apply generics for reusability 4. Ensure type safety
Shared Type Imports
- Search the
types/directory (root aliastypes/*and@/types) for existing definitions before declaring one inline. - When a matching type exists, import it with
import type { MyType } from '@/types'to avoid namespace or value imports. - If a type is missing, add it to
types/index.ts(or the appropriate shared file), export it, and reuse it across components, stores, and composables. - Avoid
declare namespaceor global augmentations unless the project already uses them; prefer explicit modules.
// Good: explicit shared type import
import { ref } from 'vue'
import type { User } from '@/types'
const users = ref<User[]>([])
// Avoid: implicitly referencing unresolved namespaces
const users = ref<UserNamespace.User[]>([]) // Lints as namespace usage
Component Props Typing
Import shared types from the project's types directory for consistency:
import { User } from '../../types'
<script setup lang="ts">
import { User } from '../../types'
interface Props {
user: User
showEmail?: boolean
size?: 'sm' | 'md' | 'lg'
}
const props = withDefaults(defineProps<Props>(), {
showEmail: true,
size: 'md'
})
interface Emits {
click: [user: User]
delete: [userId: number]
}
const emit = defineEmits<Emits>()
</script>
Reactive Refs with Types
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 · 175 lines · 0 tokens per session scan A 9cd9122009b0
typescript-patterns 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 1,088 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.
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.
project-overview
A project overview for a uni-app application built with Vue 3, TypeScript, Vite, and UnoCSS. It explains the supported platforms, main folders, configuration files, and development commands.
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
code
A set of coding rules for Vue 3 components written with TypeScript. It covers component structure, typed properties and events, reusable composables, and stylesheet conventions.
structure
A set of frontend project rules for organizing files, naming code, using TypeScript, and structuring Vue components. It specifies locations and conventions for components, styles, API code, utilities, types, imports, and exports.