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

migrate-to-rslib

Skill97 starsChanged 3 months agoMITView on GitHub

Migrate tsc or tsup library projects to Rslib.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 19
  2. Distinctive:

    Do not change business logic: avoid touching source or business logic unless user explicitly asks.

    line 21
  3. Distinctive:

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

    line 22
  4. Distinctive:

    Run build command to verify the project builds successfully.

    line 41
  5. Distinctive:

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

    line 42
  6. Distinctive:

    Remove obsolete dependencies/config only after validation passes.

    line 45

≈ “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 Rslib

Goal

Migrate tsc and tsup projects to Rslib with minimal behavior changes and clear verification.

Supported source frameworks

  • tsc
  • tsup

Migration principles (must follow)

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

Workflow

  1. Detect source tool
    • tsup
      • Config: tsup.config.*
      • Dependency: tsup
      • Build script: uses tsup to build projects
    • tsc
      • Config: tsconfig.json or tsconfig.*.json
      • Dependency: typescript
      • Build script: uses tsc to build projects. And it should be noted that tsc used only for type checking (e.g., tsc --noEmit) does not make it a tsc build project.
  2. Apply tool-specific migration deltas
    • tsc: references/tsc.md
    • tsup: references/tsup.md
  3. Validate behavior
    • 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, mapped options, 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