migrate-vue2 SKILL.md skillB
migrate-vue2 from phaedra-solutions/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phaedra-solutions/cursor-rules/migrate-vue2@git:20261030.9df887aPins git:20261030.9df887a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phaedra-solutions/cursor-rules
- Path
skills/migrate-vue2/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261030.9df887a, committed Oct 30, 2026
- Size
- 5,362 bytes
- Repository stars
- 4
- License
- MIT
Migrate a Vue 2 app to Vue 3 with the official @vue/compat migration build, step by step - move to Vue 2.7 and replace Vue 3-incompatible libraries first, switch the build to Vue 3 plus @vue/compat in MODE 2, fix compat warnings feature by feature (filters, v-model, $listeners, events API, async components, transitions), migrate Vuex to Pinia or Vuex 4 and Vue Router 3 to the current router, then remove the compat build. Use when asked to migrate or upgrade Vue 2, or when legacy/vue2-nuxt2…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Migrate Vue 2 → Vue 3 ## When to use - The app runs Vue 2 (EOL 31 Dec 2023) and the user wants to move to Vue 3. - For Nuxt 2 apps, use the Nuxt path in `legacy/vue2-nuxt2` instead (Nuxt Bridge or a rebuild); this skill covers Vue apps built with Vite, Vue CLI or webpack. ## Before you start - Read `vue`, `vue-template-compiler`, `vue-router`, `vuex`, `@vue/test-utils`, the build tool (Vue CLI, webpack, Vite) and every Vue plugin and UI library from the lockfile. - For each library, find a Vue 3 version or a replacement (for example Vuetify 2 → 3, BootstrapVue → a Vue 3 alternative, `vue-i18n` 8 → 9+). Libraries without a Vue 3 path are the main blockers; list them for the user. - Working tree clean; new branch (`chore/vue-3`); a test suite and E2E smoke tests for main flows (add them first if missing). - Ask the user: - whether to migrate the build tool (Vue CLI → Vite) in the same project, as a separate step before or after; - Vuex → Pinia now, or Vuex 4 first; - whether network installs are approved (`core/supply-chain` cooldown applies). ## Steps 1. **Baseline:** install, lint, unit tests, E2E and a production build. Record failures. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_koniktzg6ayvrnyr/ce5e5d6be4bc6e8af8cf364f20062aa8b5500fa05b7840b41f97a91b0ee2f524.json
Then /plugin install migrate-vue2@markdownregistry-koniktzg6ayvrnyr in Claude Code. It installs git:20261030.9df887a, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add phaedra-solutions/cursor-rules/migrate-vue2@sha256:ce5e5d6be4bc6e8aThe line at the top of this page pins the label git:20261030.9df887a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_koniktzg6ayvrnyr)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phaedra-solutions/cursor-rules/migrate-vue2 since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of migrate-vue2 from somewhere else? Ask it: where did my migrate-vue2 come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 30, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/migrate-vue2/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5362 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
phaedra-solutions/cursor-rules · 4 stars · license MIT · pushed 2026-11-02 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_koniktzg6ayvrnyr GET https://markdownregistry.com/api/v1/resolve?ref=phaedra-solutions/cursor-rules/migrate-vue2 GET https://markdownregistry.com/api/v1/blob/ce5e5d6be4bc6e8af8cf364f20062aa8b5500fa05b7840b41f97a91b0ee2f524
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.