← ClaudeAtlas

tech-radarlisted

MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project to check if dependencies are current. Also trigger proactively at the start of major upgrade sessions.
lethilu4796/claude-code-blueprint · ★ 0 · AI & Automation · score 75
Install: claude install-skill lethilu4796/claude-code-blueprint
# Tech Radar — Stack Update Scanner Checks for latest versions, breaking changes, deprecations, and security advisories across the user's core stack. ## Core Stack to Monitor | Category | Packages | |----------|----------| | **Frontend** | nuxt, vue, next, react, tailwindcss, formkit, pinia | | **Backend** | @nestjs/core, express, fastify | | **Database** | prisma, @prisma/client, knex, better-auth | | **Testing** | vitest, @vue/test-utils, @testing-library/react | | **Mobile** | expo, react-native, nativewind | | **AI** | ai (vercel ai-sdk), @ai-sdk/openai, @ai-sdk/anthropic | | **CLI** | commander, chalk, ora, inquirer | | **Build** | typescript, tsup, turbo, vite | | **Cloud** | @aws-sdk/client-s3, @aws-sdk/client-ec2 | ## Execution Steps 1. **Parse arguments**: If user specified a package/framework, focus on that. Otherwise scan full stack. 2. **Check latest versions** using WebSearch: - Search: `"{package} latest version {current_year}"` - Compare against currently installed version (check `package.json` in active project) - Flag major version bumps (potential breaking changes) 3. **Check for breaking changes**: - For major version bumps: search `"{package} v{new_major} migration guide"` - Summarize key breaking changes that affect our patterns - Cross-reference against known patterns in MEMORY.md 4. **Check security advisories**: - Search: `"{package} CVE {current_year}"` or `"{package} security advisory"` - Flag any HIGH or CRITICAL seve