GiammeGiamme/linear-spanks/skills/extras/tech-vue/SKILL.md

tech-vue

Skill1 starsChanged 28 days agoMITView on GitHub

Technology skill loaded when working in a Vue.js ecosystem.

In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When building Vue applications, prioritize modern API usage and component composition:
line 11
Very specific:
Composition API: Use the Composition API (<script setup>) by default.
line 13
Very specific:
Template Logic: Keep templates clean. Move complex logic (e.g., nested ternaries) into computed properties.
line 16
Distinctive:
State Management: Use Pinia over Vuex for new global state management needs, leveraging its modular, type-safe stores.
line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Vue.js Best Practices

Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.

When building Vue applications, prioritize modern API usage and component composition:

Composition API: Use the Composition API (<script setup>) by default. Avoid the Options API in new components.
Reactivity: Differentiate between ref (for primitives) and reactive (for objects). Avoid destructuring reactive objects without toRefs.
Composables: Extract reusable stateful logic into Composables (use...) rather than relying on mixins.
Template Logic: Keep templates clean. Move complex logic (e.g., nested ternaries) into computed properties.
State Management: Use Pinia over Vuex for new global state management needs, leveraging its modular, type-safe stores.

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