project-structure

project-structure is a cursor rule for Cursor from aliarghyani/vue-cursor-rules. It costs 7 tokens per session (565 once invoked), scanned A, original, MIT.

A set of rules for organizing Vue 3 projects, where Vue 3 is a framework for building web interfaces. It recommends grouping code by feature and separating reusable components, pages, state stores, API services, types, utilities, and static assets.

In plain words
What is it for?
Use it when designing or reviewing a Vue 3 codebase, deciding where components and views belong, organizing composables and Pinia stores, and defining folders for services, types, utilities, and assets.
Why use it?
It gives a consistent structure as a Vue project grows, making related files easier to find and reducing mixing between interface code, data handling, and shared logic. It also recommends consistent names and clean import paths.

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/project-structure
Clone the repo
git clone --depth 1 https://github.com/aliarghyani/vue-cursor-rules

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 project-structure

README.md
[![agentmods](https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/project-structure.svg)](https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/project-structure)
Your own site
<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/project-structure"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/project-structure.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 565 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.00007 $0.00565
Opus 5 $0.00003 $0.00282
Sonnet 5 $0.00001 $0.00113
Haiku 4.5 $0.00001 $0.00056

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

Security

Grade A, and why

project-structure 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 4d 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/project-structure.mdc · 76 lines

What it actually says

Project Structure

Role: You are a Vue 3 expert specializing in scalable project architecture and organization.

Core Rules:

  • Follow feature-based directory structure
  • Use barrel exports for clean imports
  • Maintain consistent naming conventions
  • Separate concerns (components, composables, stores)
  • Keep related files together

Chain-of-Thought: Think step-by-step: 1. Identify feature boundaries 2. Organize by domain 3. Setup clean import paths 4. Maintain consistency

src/
├── components/          # Reusable UI components
│   ├── ui/             # Base UI components (Button, Input, etc.)
│   └── features/       # Feature-specific components
├── views/              # Page components
├── composables/        # Reusable composition functions
├── stores/             # Pinia stores
├── router/             # Vue Router configuration
├── services/           # API services and external integrations
├── types/              # TypeScript type definitions
├── utils/              # Utility functions
├── assets/             # Static assets (images, styles)
└── main.ts             # Application entry point

Component Organization

components/
├── ui/
│   ├── Button.vue
│   ├── Input.vue
│   ├── Modal.vue
│   └── index.ts        # Export barrel
├── features/
│   ├── UserProfile/
│   │   ├── UserProfile.vue
│   │   ├── UserAvatar.vue
│   │   └── index.ts
│   └── ProductCard/
│       ├── ProductCard.vue
│       ├── ProductImage.vue
│       └── index.ts

Naming Conventions

  • Components: PascalCase (UserProfile.vue)
  • Views: PascalCase with View suffix (HomeView.vue)
  • Composables: camelCase with use prefix (useUserData.ts)
  • Stores: camelCase with Store suffix (userStore.ts)
  • Types: PascalCase for interfaces (User, ApiResponse)
  • Files: kebab-case for utilities (api-client.ts)

Import/Export Patterns

// components/ui/index.ts - Barrel exports
export { default as Button } from './Button.vue'
export { default as Input } from './Input.vue'
export { default as Modal } from './Modal.vue'

// In components
import { Button, Input } from '@/components/ui'
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. 4d ago First seen · 76 lines · 7 tokens per session scan A 93f0dba2fe94

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo ago), licensed MIT. It adds 7 tokens to every session and 565 once invoked, about $0.0000 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-08-30.