What problem does it solve? When editing a legacy React + Vite codebase that is mid-migration to Next.js, developers risk breaking visual parity and violating established conventions. This Skill preserves the current stack's coding standards, color palette, and component patterns so hotfixes and ports stay consistent with the live site. ## Core Features & Use Cases - Stack Documentation: Captures the current setup — React 19, Vite 8 (rolldown), plain JavaScript, co-located vanilla CSS, DM Sans and JetBrains Mono fonts, no router, no Tailwind. - Coding Conventions: Defines PascalCase components with co-located .jsx and .css files, kebab-case classes, inline colors, @keyframes animations, clamp() typography, and SVG icons with currentColor. - Hacker-Mode Palette: Provides the full token table (#080808 background, #00ff88 neon green accent, #00ccff blue accent) needed to rebuild the geek mode in Tailwind v4 during Phase 6. - Use Case: When applying a hotfix to src/components/Hero.jsx before Phase 2 of the migration, use this Skill to reuse the global .btn-primary styles and preserve the interactive terminal easter eggs. ## Quick Start Ask the AI to update a component in src/ following the legacy React and Vite conventions and hacker-mode color palette before the Next.js migration completes.