What problem does it solve? Frontend work across this estate spans four very different codebases — two Next.js 16 / React 19 / Tailwind 4 apps, a legacy CRA + MUI app, and a static artboard generator — and generic React instincts are wrong in at least one of them. This Skill encodes the per-repo conventions, traps, and verified facts so changes match the file being edited instead of an assumed house style. ## Core Features & Use Cases - Per-repo stack maps: Framework, styling, and test setup for Survey-Forms, CleverClass, phd-monitoring, and Emerge-Design, including which repos have no tests at all. - Convention enforcement: Tailwind 4 CSS-first theming (no tailwind.config.ts), the tw- prefix in Tailwind 3, Radix primitives and cn() in CleverClass, colocated tests in Survey-Forms. - Trap documentation: The one-origin session rule, output: 'standalone' deploy requirement, stale .env.example files, cosmetic client-side auth checks, and generated artboards that must never be edited directly. - Use Case: When asked to add a form to CleverClass, follow its react-hook-form + zod + Radix conventions and run npm run build as the only available verification, rather than importing patterns from another repo. ## Quick Start Use the frontend skill to add a new validated form component to the CleverClass admin section following its existing conventions.