Tech Trend Watch
Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.
Install
npx skills add mizchi/skills --skill tech-trend-watchgit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/tech-trend-watch ~/.claude/skills/tech-trend-watchPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Long-Term Technology Watch
## Data Sources
| Source | Cadence | URL | What it measures |
|---|---|---|---|
| State of JS | Annual (autumn) | https://stateofjs.com | JS libraries, frameworks, tools — usage + satisfaction |
| State of CSS | Annual (autumn) | https://stateofcss.com | CSS tools, frameworks, features — usage + satisfaction |
| Thoughtworks Tech Radar | Twice yearly | https://www.thoughtworks.com/radar | Broad tech (langs, platforms, tools, techniques) — ring assignments |
Fetch the latest published edition of each before reviewing. Discover the data
download or API from that edition's official site and validate its schema;
do not construct an unverified JSON URL from a year template. Record the survey
year, publication date and source URL. The Radar's [official FAQ](https://www.thoughtworks.com/radar/faq)
describes a twice-yearly publication cadence (checked 2026-11-16).
## Step 1 — Inventory current stack
List all significant dependencies from `package.json`:
```bash
jq -r '(.dependencies // {}) + (.devDependencies // {}) | keys[]' package.json | sort
```
Focus on: frameworks, bundlers, test runners, type checkers, linters, CSS tooling, state management, routing, data fetching, animation. Exclude low-level utilities and polyfills from the review.
## Step 2 — State of JS/CSS mapping
For each technology in the current stack, locate it in the State of JS/CSS results.
### Satisfaction × Usage matrixDetails
- Skill name
tech-trend-watch- Repository
- mizchi/skills
- Path
tech-trend-watch/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Tech Trend Watch skill do?
Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.
How do I install the Tech Trend Watch skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill tech-trend-watch. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tech Trend Watch popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Stryker Js
423mizchi/skills
Introduce StrykerJS mutation testing or assess JavaScript/TypeScript test quality. Use Git diff mutations in CI and surviving mutants locally to find missing cases and weak assertions, including tests generated by AI.
Multica Review Test
279it235/multica-best-practices
Test-artifact dedicated review framework. Called by TestReviewer to professionally analyze Tester's cases/report/coverage doc (coverage depth/acceptance mapping/coverage reasonableness/conclusion truth/contract consistency), output PASS/FAIL + fix list, report to Leader.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.