Do not assume the new cache behavior; audit every fetch and classify its freshness. Add `force-cache` or `next: { revalidate: N }` for data that should be cached, use `no-store` for request-specific data, and add `revalidateTag`/`revalidatePath` after mutations. Also check Router/Data/Full Route cache interactions, then verify the stale path with a production build and a mutation-to-refresh test.
Installs into .claude/skills of the current project.
Are you the author of Nextjs Upgrade?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-nextjs-upgrade-9d7e960b)
Do not assume the new cache behavior; audit every fetch and classify its freshness. Add `force-cache` or `next: { revalidate: N }` for data that should be cached, use `no-store` for request-specific data, and add `revalidateTag`/`revalidatePath` after mutations. Also check Router/Data/Full Route cache interactions, then verify the stale path with a production build and a mutation-to-refresh test.
