What problem does it solve? It enforces consistent frontend development practices when building or modifying the LANES Progressive Web App, preventing common UI mistakes like broken mobile layouts, duplicated components, and leaked business logic in the client. ## Core Features & Use Cases - Component Standardization: Requires checking the shared UI library (src/shared/ui) before creating raw HTML elements, and mandates the central <Button> component with standard variant and size props. - Responsive PWA Design: Enforces dual mobile/desktop implementations for every UI change, using CSS variables like var(--bottom-nav-height) with env(safe-area-inset-bottom) to prevent fixed navigation bars from obscuring content. - Animation Standards: Directs use of framer-motion with <AnimatePresence> for page transitions, modals, and direction-aware sliding interfaces. - Use Case: When asked to add a new flood-report card to the map view, the agent builds it with shared components, framer-motion entry animations, and verifies both the mobile drawer and desktop sidebar variants. ## Quick Start Ask the agent to create a responsive React component for the LANES frontend, such as a flood alert card that works on both mobile and desktop layouts.