migrate-cra-to-vite SKILL.md skillB
migrate-cra-to-vite 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-cra-to-vite@git:20261030.ab8811aPins git:20261030.ab8811a 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-cra-to-vite/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261030.ab8811a, committed Oct 30, 2026
- Size
- 5,332 bytes
- Repository stars
- 4
- License
- MIT
Move a Create React App (react-scripts) project to Vite - install Vite and @vitejs/plugin-react, move index.html to the project root with a module script, rename REACT_APP_ env variables to VITE_ and process.env to import.meta.env, handle %PUBLIC_URL%, SVG imports, path aliases, proxy and port settings, switch Jest to Vitest (or keep Jest with its own config), update scripts and CI, and verify. Use when asked to migrate off CRA or when legacy/react-class-cra applies.
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 Create React App → Vite ## When to use - The project uses `react-scripts` (CRA, deprecated since 14 Feb 2025) and the user wants a supported build. - If the user wants a framework instead (Next.js, React Router framework mode), follow that framework's CRA guide; this skill covers a client-only SPA on Vite (see `frontend/react-vite-spa`). ## Before you start - Read `react-scripts`, React, TypeScript, CRACO/react-app-rewired config, `src/setupProxy.js`, `.env*` files, `public/index.html`, Jest config in `package.json`, and how SVGs, CSS modules and images are imported. - Working tree clean; new branch (`chore/vite`); record the current build output size and a list of pages to smoke-test. - Ask the user: - whether to switch tests to Vitest now or keep Jest for this change; - the deployment base path (`homepage` in `package.json`) and the hosting setup; - whether network installs are approved (`core/supply-chain` cooldown applies). ## Steps 1. **Baseline:** `npm test -- --watchAll=false`, `npm run build`, and a smoke test of key pages. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_26rksvqcngolxz64/d83567273f46e3bd86afc0b5bbe5252069f0a5aaf2dd7ba2d3c316fb4411dcf9.json
Then /plugin install migrate-cra-to-vite@markdownregistry-26rksvqcngolxz64 in Claude Code. It installs git:20261030.ab8811a, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add phaedra-solutions/cursor-rules/migrate-cra-to-vite@sha256:d83567273f46e3bdThe line at the top of this page pins the label git:20261030.ab8811a, 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_26rksvqcngolxz64)
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-cra-to-vite 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-cra-to-vite from somewhere else? Ask it: where did my migrate-cra-to-vite 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-cra-to-vite/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 (5332 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_26rksvqcngolxz64 GET https://markdownregistry.com/api/v1/resolve?ref=phaedra-solutions/cursor-rules/migrate-cra-to-vite GET https://markdownregistry.com/api/v1/blob/d83567273f46e3bd86afc0b5bbe5252069f0a5aaf2dd7ba2d3c316fb4411dcf9
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.