vue-rules

vue-rules is a cursor rule for Cursor from yu-iskw/llmops-demo-ts. It costs 2,071 tokens per session, scanned A, original, Apache-2.0.

A set of development rules for building Vue applications with JavaScript or TypeScript. Vue is a framework for creating interactive web interfaces, and the guidance covers structure, reactivity, performance, and naming.

In plain words
What is it for?
Use it when designing or reviewing Vue components, pages, stores, utilities, and larger feature-based application structures.
Why use it?
It provides consistent choices for organizing Vue code and helps avoid unclear component, page, utility, and state-management structures as an application grows.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when designing or reviewing Vue components, pages, stores, utilities, and larger feature-based application structures.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/yu-iskw/llmops-demo-ts/vue-rules
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.

Clone the repo
git clone --depth 1 https://github.com/yu-iskw/llmops-demo-ts

Made for: Cursor.

Wrote 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.

agentmods badge for vue-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/vue-rules.svg)](https://agentmods.dev/rules/yu-iskw/llmops-demo-ts/vue-rules)
Your own site
<a href="https://agentmods.dev/rules/yu-iskw/llmops-demo-ts/vue-rules"><img src="https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/vue-rules.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,071 This file is loaded in full into every session.
When invoked 2,071 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02071 $0.02071
Opus 5 $0.01035 $0.01035
Sonnet 5 $0.00414 $0.00414
Haiku 4.5 $0.00207 $0.00207

Measured 3d ago against content hash c431d18a7670, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

vue-rules 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 3d 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/vue-rules.mdc · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vue.js Development Guidelines

You are an expert in JavaScript, TypeScript, and the Vue.js framework for scalable web development.

Key Principles

  • Write concise, technical responses with accurate Vue.js examples.
  • Leverage Vue.js reactivity system effectively.
  • Prioritize performance optimization and minimal JavaScript for optimal user experience.
  • Use descriptive variable names and follow Vue.js naming conventions.
  • Organize files logically, typically by feature or component type.

Project Structure

  • Use the recommended Vue CLI or Vite project structure.
  • Organize components into components/ for reusable UI elements.
  • Organize views/pages into views/ or pages/ for route-specific components.
  • Organize utility files into utils/ or helpers/.
  • Organize state management related files into store/ or stores/.

Recommended Modular Project Structure

For larger and more complex Vue.js applications, a modular monolithic architecture is highly recommended. This approach encapsulates each feature or domain, enhancing maintainability and scalability.

src/
├── app.ts                 # Main application setup (Express, middleware, error handlers)
├── main.ts                # Main entry point for Vue application
├── router.ts              # Global Vue Router configuration
├── store.ts               # Global Pinia/Vuex store configuration
├── assets/                # Static assets like images, fonts, global styles
│   └── images/
│   └── styles/
├── core/                  # Common components, services, and utilities used across the application
│   ├── components/        # Base or common UI components (e.g., BaseButton.vue)
│   ├── models/            # Core TypeScript interfaces/types for global entities
│   ├── store/             # Global or shared Pinia/Vuex modules
│   ├── services/          # Common business logic services
│   ├── views/             # Common layout components (e.g., DefaultLayout.vue)
│   └── utils/             # Common utility functions
├── modules/               # Feature-specific modules, each self-contained
│   ├── checkout/          # Example feature module (e.g., for e-commerce checkout)
│   │   ├── components/    # Components specific to the checkout module
│   │   ├── models/        # TypeScript interfaces/types for checkout entities
│   │   ├── store/         # Pinia/Vuex store specific to checkout
│   │   ├── services/      # Business logic services for checkout
│   │   ├── views/         # Routed components (pages) for checkout
│   │   └── routes.ts      # Route definitions for the checkout module
│   ├── user/              # Example user management module
│   │   ├── components/
│   │   ├── models/
│   │   ├── store/
│   │   ├── services/
│   │   ├── views/
│   │   └── routes.ts
│   └── ...
├── plugins/               # Vue plugins
├── types/                 # Custom global type definitions
├── tests/                 # Unit and integration tests
└── scss/                  # Global SCSS files

Read the full file on GitHub · 177 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. 3d ago First seen · 177 lines · 2,071 tokens per session scan A c431d18a7670

Subscribe to this mod's changes

vue-rules is a cursor rule published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 6d ago), licensed Apache-2.0. It adds 2,071 tokens to every session, about $0.0104 per session on Opus 5. 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-09-04.