agentleFS
Sign inStart free
Benjaming61001Benjaming61001/skills/frontend-conventions/SKILL.md

frontend-conventions

Skill1 starsChanged 3 months agoMITView on GitHub

Enforce file structure, naming, and code conventions when creating, renaming, or moving files in Vue 3 + Vite or Nuxt 4 projects. Auto-detects framework. Covers file structure, naming patterns, interface naming, provider classes, stores, and enums.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backend-conventions.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    backend-conventions

    Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system. Use when adding or editing Python in src/ that logs (logger.info/exception), records metrics (metrics.incr/timing with tags), instruments spans/transactions, calls sentry_sdk.set_tag/set_attribute or set_span_tag/set_span_data, or reads registered options with options.get(). Trigger on "add logging", "log an error", "add a metric", "add a span", "instrument tracing", "set an attribute", "add a tag", "read an option", "LOG005", "LOG011", or metrics tag cardinality questions.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the project root for framework config files:

    line 16
  2. Very specific:

    If nuxt.config.ts exists → Nuxt 4 project → load references/file-structure-nuxt.md

    line 18
  3. Very specific:

    If vite.config.ts exists → Vue 3 + Vite project → load references/file-structure-vue.md

    line 19
  4. Very specific:

    All conventions live in references/:

    line 40

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Frontend Conventions

Apply consistent naming, file structure, and code patterns across Vue 3 + Vite and Nuxt 4 projects.

Framework Detection

Check the project root for framework config files:

  • If nuxt.config.ts exists → Nuxt 4 project → load references/file-structure-nuxt.md
  • If vite.config.ts exists → Vue 3 + Vite project → load references/file-structure-vue.md

When Invoked

  1. Detect framework using the rule above
  2. Load relevant references based on the file being created/edited:
File typeReference files to load
Directory structure questionsfile-structure-vue.md or file-structure-nuxt.md
New file creationnaming-patterns.md + interface-naming.md
.provider.ts filesprovider-class.md + provider-methods.md
.model.ts (enum) filesenum-pattern.md
use*.ts or store filesstore-pattern.md
Interface/type filesinterface-naming.md
Access level questionsaccess-levels.md
  1. Apply conventions from the loaded reference files to the current task

Reference Files

All conventions live in references/:

  • file-structure-vue.md — Vue 3 + Vite directory layout
  • file-structure-nuxt.md — Nuxt 4 + SSG directory layout
  • naming-patterns.md — File naming table (dot vs camelCase)
  • access-levels.md — Auth level definitions (public/private)
  • interface-naming.md — I/T/E prefix rules, request/response naming
  • provider-class.md — Provider class structure template
  • provider-methods.md — Provider method rules (GOOD/BAD patterns)
  • enum-pattern.md — Enum + type alias + options array
  • store-pattern.md — Pinia store template with persistence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free