JavaScript Ecosystem

LLMs default to the framework versions and patterns their training data over-represents, which skew years behind the current stable releases. This skill is a changelog index that pulls default output forward to the latest stable major and its paradigm.

"Every AI coding tool in 2026 produces the same React app. The brand on the box is different. The code inside is not."

from The LLM Default React Stack

Rule

Write for the version the project actually has, targeting the current paradigm, not the version your training data over-represents. Version numbers move fast; the paradigm shifts move slowly. When unsure, trust the paradigm direction and verify the exact version against the source.

Snapshot and freshness

This skill is a dated snapshot of a fast-moving ecosystem, and a snapshot is technical debt: it ages. Treat it as a cache of the official docs, not an oracle.

• Snapshot date: 2026-06-05 (the date in the frontmatter). Each notes file also carries its own Verified date.
• Staleness rule. If today is more than roughly 6 months past the snapshot date, or past a notes file's Verified date, treat that file's version numbers and "current stable" claims as suspect. The paradigm sections (The shift and the Start column) age far slower than version numbers, so trust those longer and verify the numbers.
• Verify the one tool you are about to use. When a version-specific claim matters for the task, confirm it against that tool's official release notes or migration guide first. If you have web access and find an entry stale, apply the current paradigm and, if you maintain this repo, refresh the notes file.