agentleFS
lirantallirantal/slides-toxicskills-agent-skills-malware/.cursor/skills/vue-best-practices/SKILL.md

vue-best-practices

Skill0 starsChanged 25 days agoNo licenceView on GitHub

MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.

31 other projects use a version of this, 8 of them edited; 5 of 8 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 0 the 4 before.

How people change it

5 of 8 edited versions changed its rules, and some changes recur.

Of the 8 edited versions we compared: 3 keep every rule, 5 made changes of their own.

Rules people drop

  1. Create a brief component map before implementation for any non-trivial feature.dropped by 5 of 5
  2. Keep entry/root and route-level view components as composition surfaces by default.dropped by 5 of 5
  3. Prefer a feature folder layout (components/<feature>/..., composables/use<Feature>.ts) when adding more than one component.dropped by 5 of 5
  4. Keep SFC responsibilities focused; split large components.dropped by 5 of 5
  5. Prefer smaller components + composables over one “mega component”dropped by 5 of 5
  6. Keep entry/root and route view components thin: app shell/layout, provider wiring, and feature composition.dropped by 5 of 5
  7. Do not place full feature implementations in entry/root/view components when those features contain independent parts.dropped by 5 of 5
  8. Use provide/inject only for deep-tree dependencies or shared context.dropped by 5 of 5

Rules people add

  1. Decompose by responsibility: keep each implementation focused and the contracts between implementations explicit.added by 5 of 5
  2. Follow the project's layout and scale the design to the affected behavior. A local fix does not require a project-wide component map or new architectural layers.added by 5 of 5
  3. Keep SFC responsibilities cohesive; use the boundary criteria below when splitting.added by 5 of 5
  4. Treat file length, UI section count, and API size as review signals, not extraction thresholds. Keep a small cohesive production feature in one SFC when extra boundaries would not hide meaningful complexity.added by 5 of 5
  5. Use typed, scoped provide/inject for shared descendant dependencies when intermediate components only relay them; reassess component boundaries first. See the data-flow reference for scope and ownership.added by 5 of 5
  6. Keep DOM interaction and cleanup with its owning UI or composable. Preserve the explicit coordination other features need, such as committing a pending draft before saving.added by 5 of 5

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use create-adaptable-composable, vue-debug-guides and 10 more.

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.
  • hyf0Skill

    create-adaptable-composable

    Create a library-grade Vue composable that accepts maybe-reactive inputs (MaybeRef / MaybeRefOrGetter) so callers can pass a plain value, ref, or getter. Normalize inputs with toValue()/toRef() inside reactive effects (watch/watchEffect) to keep behavior predictable and reactive. Use this skill when user asks for creating adaptable or reusable composables.

    Also in 5 projects that use this

  • hyf0Skill

    vue-debug-guides

    Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.

    Also in 6 projects that use this

  • SentrySkill

    nitro

    Build and deploy universal JavaScript servers with Nitro v3. Use when working with nitro.config.ts, defineNitroConfig, defineHandler, defineConfig, server.ts entry, filesystem routing, route rules, useStorage, defineCachedHandler, useDatabase, definePlugin, runtime hooks, Vercel/Cloudflare deployment, or migrating from Nitro v2/nitropack.

    Also in 3 projects that use this

  • OpenAISkill

    using-superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    Also in 3 projects that use this

  • OpenAISkill

    finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    Also in 3 projects that use this

  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • +3 more from hyf0
  • +3 more from openai

The file

Show its rules and text

We split this skill into the rules it gives an agent

32 rules. 12 are common, 7 are distinctive, and 13 are very specific to this project.

  • 12

    Common

    Most of the 9 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 13

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 9 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.

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.