vue-options-api-best-practices
Skill1 starsChanged 3 months agoMITView on GitHub
Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.
5 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- vuejs-ai/skillsword for word, first seen Oct 25, 2026
- rockcookies/skillsedited, first seen Oct 13, 2026
- liangmiQwQ/skillsword for word, first seen Oct 11, 2026
- hyf0/vue-skillsword for word, first seen Oct 8, 2026
- filipefalcaofs/repo-padraoword for word, first seen Jul 8, 2026
Other versions5 projects use a version of this.
Word for word · 4
- hyf0/vue-skills★ 3.2k100% same
- vuejs-ai/skills★ 3.1k100% same
- liangmiQwQ/skills★ 1100% same
- filipefalcaofs/repo-padrao★ 0100% same
Edited · 1
- rockcookies/skills★ 1100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- brainstormSkill
- continual-learningSkill
- create-adaptable-composableSkill
- deep-researchSkill
- draw-mermaid-diagramsSkill
- electronSkill
- interpret-tech-notesSkill
- vue-best-practicesSkill
- vue-debug-guidesSkill
- vue-jsx-best-practicesSkill
- vue-pinia-best-practicesSkill
- vue-router-best-practicesSkill
- vue-testing-best-practicesSkill
- write-idea-docsSkill
The file
Files
Vue.js Options API best practices, TypeScript integration, and common gotchas.
TypeScript
- Need to enable TypeScript type inference for component properties → See ts-options-api-use-definecomponent
- Enabling type safety for Options API this context → See ts-strict-mode-options-api
- Using old TypeScript versions with prop validators → See ts-options-api-arrow-functions-validators
- Event handler parameters need proper type safety → See ts-options-api-type-event-handlers
- Need to type object or array props with interfaces → See ts-options-api-proptype-complex-types
- Injected properties missing TypeScript types completely → See ts-options-api-provide-inject-limitations
- Complex computed properties lack clear type documentation → See ts-options-api-computed-return-types
Methods & Lifecycle
- Methods aren't binding to component instance context → See no-arrow-functions-in-methods
- Lifecycle hooks losing access to component data → See no-arrow-functions-in-lifecycle-hooks
- Debounced functions sharing state across component instances → See stateful-methods-lifecycle
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
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.

