cache-components
sangrokjung/claude-forge / skills/cache-components
guides Next.js caching and PPR , which improves: faster pages, less server computation
Details
- judge’s score
- 9/10
- place
- extra · Website
- publisher
- sangrokjung
- status
- new
- pinned commit
- 34d881d on GitHub (new tab)
- skill’s last commit
- Feb 23, 2026
- repo stars
- 862
- main type
- Website
Judgement
Precise skill, well targeted at the recent Cache Components APIs, with examples and error messages. Score reduced: "proactive" application too broad, annexes truncated, unofficial third-party repo.
reservations
- Annexes PATTERNS.md, REFERENCE.md and TROUBLESHOOTING.md truncated at 5,000 characters: partial assessment.
- No Next.js version indicated; the APIs (cacheLife, updateTag, 'use cache: remote') need checking against the official docs.
- The "proactive" activation on all components may push Claude to add 'use cache' without being asked.
- Third-party repo (sangrokjung/claude-forge), not official.
- Triggering
- 2/2
- Added value
- 2/2
- Precision
- 2/2
- Scope
- 2/2
- Quality
- 1/2
Alerts
no alerts
Neither the static scan nor the judge flagged a risk for this skill.
Original description
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Compone…
added on Oct 19, 2026 · license MIT