Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Naming

ASecurity

Use this whenever a new file/folder is created or renamed in this Vue project, when reviewing a module for consistency, or when the right path for a file is unclear. Also triggers on "what should I name this?", "is this file named correctly?", "audit module naming". Enforces kebab-case folders, dot-prefixed `{module}.{name}.{type}.vue|js` files, multi-entity rules, singular vs plural for views, and the layered structure UI → Store → API.

20 stars
0 votes
0 copies
0 views
Added 9/20/2026
developmentvueapi

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add pierreb-devkit/Vue --skill naming --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Naming?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Naming
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pierreb-devkit-naming/badge)](https://www.skillsdirectory.com/skills/pierreb-devkit-naming)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: naming
description: >
  Use this whenever a new file/folder is created or renamed in this Vue
  project, when reviewing a module for consistency, or when the right path
  for a file is unclear. Also triggers on "what should I name this?", "is
  this file named correctly?", "audit module naming". Enforces kebab-case
  folders, dot-prefixed `{module}.{name}.{type}.vue|js` files, multi-entity
  rules, singular vs plural for views, and the layered structure
  UI → Store → API.
---

# Naming Skill

Audit or apply the project's file and folder naming conventions.

## Conventions

### Folders

| Location           | Case                | Example                                                 |
| ------------------ | ------------------- | ------------------------------------------------------- |
| Top-level src dirs | kebab-case          | `src/lib/`, `src/modules/`                              |
| Module dirs        | kebab-case          | `modules/home/`, `modules/user-settings/`               |
| Module sub-dirs    | fixed names         | `components/`, `views/`, `stores/`, `router/`, `tests/` |
| Component utils    | `components/utils/` | `components/utils/`                                     |

### Files

| Type      | Pattern                         | Example                   |
| --------- | ------------------------------- | ------------------------- |
| Component | `{module}.{name}.component.vue` | `home.hero.component.vue` |
| View      | `{module}.{name}.view.vue`      | `auth.signin.view.vue`    |
| Store     | `{module}.store.js`             | `tasks.store.js`          |
| Router    | `{module}.router.js`            | `users.router.js`         |
| Unit Test | `{target}.unit.tests.js`        | `home.store.unit.tests.js`  |
| E2E Test  | `{target}.e2e.tests.js`         | `auth.signup.e2e.tests.js`  |
| Service   | `{name}.js`                     | `axios.js`                |
| Helper    | `{name}.js`                     | `tools.js`                |
| Plugin    | `{name}.js`                     | `vuetify.js`              |
| Config    | `{name}.js` or `index.js`       | `development.js`          |

### Multi-entity modules

When a module contains multiple entities (e.g., `billing` with `subscription`), components and views add an entity segment after the module prefix. Stores keep the simple `{module}.store.js` pattern (one store per module).

| Correct | Wrong |
| --- | --- |
| `billing.pricingCard.component.vue` | `PricingCard.component.vue` |
| `billing.plans.view.vue` | `plans.view.vue` |
| `billing.store.js` | `subscription.store.js` |

Pattern (components/views): `{module}.{entity}[.{name}].{type}.{ext}`

### Case conventions in code

| Context             | Convention         | Example                             |
| ------------------- | ------------------ | ----------------------------------- |
| Variable / function | lowerCamelCase     | `useHomeStore`, `paginationRequest` |
| Component name (JS) | PascalCase         | `HomeHeroComponent`                 |
| Store export        | `use{Module}Store` | `useTasksStore`                     |
| Constant / env key  | UPPER_SNAKE_CASE   | `MY_MODULE_KEY`                     |

---

## Rules

1. **Dot-notation prefix**: always prefix with the module name separated by dots
   - `home.hero.component.vue` not `hero.component.vue`
   - `tasks.store.js` not `store.js`

2. **Semantic suffix**: always add the type suffix
   - `.component.vue` for reusable components
   - `.view.vue` for page-level views
   - `.store.js` for Pinia stores
   - `.router.js` for route definitions
   - `.unit.tests.js` for unit tests, `.e2e.tests.js` for E2E tests

3. **Singular vs plural**: follow the module's data semantics
   - List of items → plural: `tasks.view.vue`, `users.view.vue`
   - Single item → singular: `task.view.vue`, `user.view.vue`

4. **Utility sub-components**: place in `components/utils/` and keep the module prefix
   - `components/utils/home.blur.background.component.vue`

5. **Shared code**: files in `src/lib/` use simple kebab-case, no module prefix
   - `src/lib/helpers/tools.js`, `src/lib/plugins/vuetify.js`

---

## Applying names

Derive name as: module prefix (kebab-case) + `.` + semantic name + `.` + type suffix. Place in the correct sub-directory (`components/`, `views/`, `stores/`, `router/`, `tests/`). When auditing, check each file against the tables above and report violations.

Attribution

pierreb-devkitpierreb-devkit
View sourceMore from pierreb-devkit →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

284722 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2192 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Tanstack Start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per ...

9881 votes

Pentest

PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

5491 votes
View all in development →