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/WangTingYeYe/llm-agent-studyWrote 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/wangtingyeye/llm-agent-study/vue)<a href="https://agentmods.dev/rules/wangtingyeye/llm-agent-study/vue"><img src="https://agentmods.dev/badge/rules/wangtingyeye/llm-agent-study/vue/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/wangtingyeye/llm-agent-study/vue"><img src="https://agentmods.dev/badge/rules/wangtingyeye/llm-agent-study/vue.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.00587 |
| Opus 5.5 | $0.00000 | $0.00235 |
| Sonnet 5.5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
vue 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.
What it actually says
Vue 开发规范
组件命名
- 组件名应该始终使用多词组合，避免与HTML元素冲突
- 使用PascalCase命名组件：
TodoItem.vue、UserProfile.vue - 基础组件应使用特定前缀，如
Base、App或V - 组件名应该是描述性的，不要过于简略
组件结构
- 使用
<script setup>语法糖 - 使用组合式API (Composition API)
- 组件选项/属性顺序：
- name
- components
- props
- emits
- setup()
- data()
- computed
- methods
- 生命周期钩子
- 使用单文件组件(SFC)格式
Props 规范
- Prop名使用camelCase
- Prop需要定义类型和默认值
- 避免使用数组或对象的默认值，应该使用工厂函数返回默认值
- Prop应该尽可能详细地定义，包括类型、是否必须和验证函数
事件命名
- 事件名应使用kebab-case，如
item-click、menu-select - 自定义事件应该有明确的含义，表示发生了什么
- 避免使用容易混淆的事件名称
样式指南
- 优先使用scoped CSS
- 避免使用!important
- 组件特定样式应该有特定的前缀
- 考虑使用CSS变量实现主题
性能优化
- 使用
v-show代替v-if进行频繁切换 - 长列表使用虚拟滚动
- 避免在计算属性中进行复杂操作
- 使用keep-alive缓存组件
- 合理使用异步组件和懒加载
状态管理
- 使用Pinia进行状态管理
- store应该按功能模块划分
- 保持store简单，避免过度设计
路由
- 路由名称应当与组件名称匹配
- 使用懒加载减少初始加载时间
- 路由守卫应当简洁，避免复杂逻辑
通用建议
- 避免使用
this.$parent或this.$refs直接操作DOM - 优先使用计算属性而不是复杂的模板表达式
- 使用v-for时必须提供key
- 不要在同一元素上同时使用v-if和v-for
- 复用组件时使用key确保完全重新渲染
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 · 68 lines · 587 tokens per session scan A d253bf569ba7
vue is a cursor rule published in the GitHub repository WangTingYeYe/llm-agent-study (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 587 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-31.
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.