stack-updatelisted

Refreshes the stack knowledge base — checks the latest versions of every technology in stack-reference (official llms.txt, release pages, endoflife.date, npm/packagist/pkg.go.dev), rewrites the reference files with dated facts and sources, compares with the project's lockfiles, and proposes an upgrade plan. Run when references are older than 60 days or before planning upgrades.
gonimar/claude-web-studio · ★ 0 · Web & Frontend · score 78

Install: claude install-skill gonimar/claude-web-studio

# Stack Update Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. Web technology moves fast; the reference is a dated snapshot. This skill refreshes it on request: facts only from official sources, with a date and a link. ## Phase 1: Scope and current state Argument: `all`, `project`, or one technology. **In a project** (a filled `technical-preferences.md` exists) the default is `project` — only the technologies the project uses (the stack section of `technical-preferences.md` and the lockfiles); `all` refreshes every reference file and is meant for the plugin repository — in a project say in one line that the copy will diverge from the plugin and be overwritten by the next `/update`. Print the list of files in scope before collecting. Read `stack-reference/index.md` and the target files; list current versions and `updated:`. Read the project lockfiles (`go.mod`, `composer.lock`, `pnpm-lock.yaml`/`package-lock.json`) — actual project versions. ## Phase 2: Collect current data (in parallel, independent sources) | Technology | Source | |---|---| | Angular / Material / Taiga | `https://angular.dev/llms.txt`, `https://angular.dev/roadmap`, npm `@angular/core`, `@angular/material`, `taiga-ui.dev/llms.txt` | | Vue / Nuxt / Vite / Vitest | `vuejs.org/llms.txt`, `nuxt.com/llms.txt`, `vite.dev/llms.txt`, `vitest.dev/llms.txt`, GitHub releases | | Go | `go.dev/doc/devel/release`, `go.dev/doc/go1.NN` | | P