agentleFS
Sign inStart free
rstackjsrstackjs/agent-skills/skills/migrate-to-rsbuild/SKILL.md

migrate-to-rsbuild

Skill97 starsChanged 3 months agoMITView on GitHub

Migrate webpack, Vite, create-react-app (CRA/CRACO), or Vue CLI projects to Rsbuild.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Official guide first: treat Rsbuild migration docs as source of truth.

    line 21
  2. Distinctive:

    Do not change business logic: avoid touching app runtime code unless user explicitly asks.

    line 23
  3. Distinctive:

    Validate before cleanup: keep old tool dependencies/config temporarily if needed.

    line 24
  4. Very specific:

    Check package.json dependencies/scripts and config files:

    line 29
  5. Distinctive:

    Run dev server to verify the project starts without errors.

    line 42
  6. Distinctive:

    Run build command to verify the project builds successfully.

    line 43
  7. Distinctive:

    If issues remain, compare the old project configuration with the migration guide and complete any missing mappings.

    line 44
  8. Distinctive:

    Remove obsolete dependencies/config only after validation passes.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Migrate to Rsbuild

Goal

Migrate webpack, Vite, create-react-app (CRA/CRACO), or Vue CLI projects to Rsbuild with minimal behavior changes and clear verification.

Supported source frameworks

  • webpack
  • Vite
  • CRA / CRACO
  • Vue CLI

Migration principles (must follow)

  1. Official guide first: treat Rsbuild migration docs as source of truth.
  2. Smallest-change-first: complete baseline migration first, then migrate custom behavior.
  3. Do not change business logic: avoid touching app runtime code unless user explicitly asks.
  4. Validate before cleanup: keep old tool dependencies/config temporarily if needed; remove only after Rsbuild is green.

Workflow

  1. Detect source framework
    • Check package.json dependencies/scripts and config files:
      • webpack: webpack.config.*
      • Vite: vite.config.*
      • CRA/CRACO: react-scripts, @craco/craco, craco.config.*
      • Vue CLI: @vue/cli-service, vue.config.*
  2. Apply framework-specific deltas
    • webpack: references/webpack.md
    • Vite: references/vite.md
    • CRA/CRACO: references/cra.md
    • Vue CLI: references/vue-cli.md
  3. Validate behavior
    • Run dev server to verify the project starts without errors.
    • Run build command to verify the project builds successfully.
    • If issues remain, compare the old project configuration with the migration guide and complete any missing mappings.
  4. Cleanup and summarize
    • Remove obsolete dependencies/config only after validation passes.
    • Summarize changed files and any remaining manual follow-ups.

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.

Reviews can't be read right now.

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