stack-currency-check

Verify framework patterns against official docs and cache results in CURRENT_PATTERNS.md.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill stack-currency-check-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-currency-check
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/stack-currency-check
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill stack-currency-check-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI models often default to outdated framework patterns from training data, shipping deprecated APIs (like Supabase getSession instead of getUser) that require follow-up fix tasks. This Skill verifies that the patterns about to be used for a given framework and version match current official documentation before greenfield code is written. ## Core Features & Use Cases - Official-docs verification: Fetches current recommended patterns, deprecated patterns, and breaking changes per framework version from official docs, release notes, and migration guides. - Project-level caching: Persists verified guidance in CURRENT_PATTERNS.md so subsequent tasks reuse it instead of re-fetching, with a 30-day staleness threshold. - Completeness enforcement: Every requested framework is reported as verified or unverified with a reason, so nothing is silently dropped. - Use Case: When impact-analysis flags greenfield work on a Next.js and Supabase project, run this Skill to confirm current auth and data-fetching patterns, cache them, and unblock implementation planning. ## Quick Start Verify the current official patterns for the frameworks in my project and cache the results in CURRENT_PATTERNS.md.

Frequently Asked Questions about stack-currency-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my framework patterns are up to date before coding?▼

Run this Skill with your active task folder and framework list. It reads pinned versions from SOURCE_OF_TRUTH.md or package.json, fetches official docs for each framework, and writes current and deprecated patterns into CURRENT_PATTERNS.md.

What sources are used to check framework currency?▼

Only official framework documentation, official release notes and changelogs, official migration guides, and AAA company engineering blogs such as Vercel, Stripe, and Cloudflare. Stack Overflow, tutorials, and random blogs are explicitly excluded.

When should I run a stack currency check?▼

Run it when impact-analysis flags greenfield work in an established framework, when starting a project with frameworks released after the model's training cutoff, or when an existing CURRENT_PATTERNS.md cache is older than 30 days.

When should I not use this Skill?▼

Skip it when working incrementally on an established codebase with clear internal precedent, when choosing the stack itself (use stack-recommend instead), or when fetching an arbitrary URL (use capture-references instead).

What happens if a framework version cannot be verified?▼

The framework is reported as unverified with a specific reason, such as an unpinned version or unreachable docs. It is never silently omitted from the result, since silent omission is the exact gap this Skill exists to prevent.