agentleFS
Sign inStart free
luigi-dvluigi-dv/react-ts-vite/.claude/skills/dependency-upgrade/SKILL.md

dependency-upgrade

Skill1 starsChanged 27 days agoMITView on GitHub

Upgrade dependencies safely in this React + TypeScript + Vite + Tailwind + Vitest project — grouped bumps, changelog review, known breaking changes, verification with the full quality gate and documentation updates. Use when asked to update, bump or modernise dependencies or to fix a broken upgrade.

  • Installs packages

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident-response, code-review and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 6 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Engines: when a tool raises its Node floor, update engines.node in package.json, .nvmrc, Docker base images (node:XX-alpine) and the CI …

    line 22

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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

Dependency upgrade

Procedure

  1. Inventory: npm outdated and npm ls --depth=0. Note majors vs minors.
  2. Group the upgrade so failures are attributable:
    • Toolchain: vite, @vitejs/plugin-react, vitest, @vitest/coverage-v8, typescript, happy-dom.
    • UI: react, react-dom, @types/react*, @headlessui/react, @heroicons/react, tailwindcss, @tailwindcss/forms, postcss, autoprefixer.
    • Quality: eslint, @eslint/js, typescript-eslint, eslint-plugin-react-hooks, eslint-plugin-react-refresh, globals, prettier, prettier-plugin-tailwindcss.
    • Testing library: @testing-library/*.
  3. Read the changelog / migration guide of every major bump before installing (npm view <pkg> homepage).
  4. Install one group: npm install <pkg>@latest … (keep caret ranges), then npm run check && npm run build && npm run preview (smoke the app). Commit the group.
  5. Engines: when a tool raises its Node floor, update engines.node in package.json, .nvmrc, Docker base images (node:XX-alpine) and the CI matrix together.
  6. Docs: README stack badges/versions, CHANGELOG.md (Unreleased → "Updated"), and this skill if a new pitfall appears.

Known pitfalls

  • Tailwind CSS 4 is CSS-first: tailwind.config.cjs and @tailwind directives are replaced by @import "tailwindcss" and @theme. Staying on 3.x keeps the current structure; migrating is a deliberate project, not a bump (npx @tailwindcss/upgrade).
  • Headless UI 2: dot-notation components (Dialog.Panel) are replaced by named exports (DialogPanel); state classes become data attributes (data-[focus]).
  • React 19: @types/react 19 removed the global JSX namespace (use React.JSX / ComponentType), forwardRef is optional (ref is a prop), Testing Library ≥ 16 with @testing-library/dom peer.
  • Vite 7+: Node ≥ 20.19/22.12 and no CJS Node API; Vite 8 (Rolldown) warns about JSON imports without with { type: 'json' } and prefers import.meta.dirname/fileURLToPath over __dirname.
  • Vitest 4/5: Node ≥ 22.12; environmentOptions.happyDOM for the DOM URL; coverage provider must be installed explicitly.
  • TypeScript 7 (native compiler) is not yet supported by typescript-eslint (<6.1); stay on 5.x until it is. tsc -b requires referenced projects with noEmit to be reached through a solution-style root (tsconfig.json with files: []).
  • ESLint 10: flat config only (eslint.config.js), new preserve-caught-error rule (new Error(msg, { cause })).
  • react-hooks 7: ships React Compiler rules (set-state-in-effect, purity, refs); fix the code rather than disabling them.

After upgrading

npm run check, npm run build, open npm run preview in a browser (light + dark), run npm run arch -- apply <other-arch> --dry-run to make sure the tooling still parses configs, and update the lockfile in the same commit.

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free