typescript-patterns

A set of coding rules for using TypeScript safely in Vue 3 applications. It covers shared data types, component properties and events, stores, and reusable composables.

In plain words
What is it for?
Use it when building Vue 3 components, stores, API response models, and reusable composables. It guides developers to find shared types, add missing ones, and apply TypeScript features such as generics and discriminated unions.
Why use it?
It helps prevent mismatched data and duplicated type definitions as an application grows. It also gives the codebase a consistent way to describe and reuse data shapes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/aliarghyani/vue-cursor-rules/typescript-patterns
Clone the repo
git clone --depth 1 https://github.com/aliarghyani/vue-cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01088
Opus 5 $0.00000 $0.00544
Sonnet 5 $0.00000 $0.00218
Haiku 4.5 $0.00000 $0.00109

Measured 2d ago against content hash 9cd9122009b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.cursor/rules/typescript-patterns.mdc · 175 lines

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 prefer import type for 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

  1. Search the types/ directory (root alias types/* and @/types) for existing definitions before declaring one inline.
  2. When a matching type exists, import it with import type { MyType } from '@/types' to avoid namespace or value imports.
  3. 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.
  4. Avoid declare namespace or 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

Read the full file on GitHub · 175 lines

Changes

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.

  1. 2d ago First seen · 175 lines · 0 tokens per session scan A 9cd9122009b0

Subscribe to this mod's changes

typescript-patterns is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo 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.