frontend▌

Create beautiful, responsive, and animated Flutter applications with modern design patterns and best practices.

Game UI design expertise grounded in Nintendo clarity, diegetic immersion, and esports readability principles. \n \n Covers HUD design, menu architecture, diegetic interfaces, and adaptive layouts across 4K displays, handheld screens, and input methods (controller, keyboard, touch) \n Emphasizes controller-first navigation, safe zones for TV viewing, and animation as communication rather than decoration \n Prioritizes accessibility as a core feature, not an afterthought, with guidance on readabi

Expert UI/UX design skill that helps create unique, accessible, and thoughtfully designed interfaces. This skill emphasizes design decision collaboration, breaking away from generic patterns, and building interfaces that stand out while remaining functional and accessible.

Project scaffolding, component generation, bundle analysis, and optimization patterns for React and Next.js applications. \n \n Scaffolds new Next.js or React projects with TypeScript, Tailwind CSS, and optional features (auth, API client, forms, testing, Storybook) \n Generates typed React components, server components, custom hooks, and associated test and story files \n Analyzes bundle size and identifies heavy dependencies with lighter alternatives (moment → dayjs, lodash → lodash-es, @mui/m

Craft-focused design philosophy for building interfaces where every detail compounds into something that feels right. \n \n Covers animation decision framework (frequency, purpose, easing, duration) with custom cubic-bezier curves and performance rules for UI interactions \n Includes component patterns: button press feedback, origin-aware popovers, tooltip delays, blur masking, and clip-path reveals \n Provides gesture and drag principles: momentum-based dismissal, boundary damping, and friction

23 performance optimization rules for React and Vite across build, code splitting, development, assets, environment, and bundle analysis. \n \n Covers six rule categories prioritized by impact: build optimization and code splitting (critical), development and asset handling (high), environment config and bundle analysis (medium) \n Includes route-based lazy loading with React.lazy() and Suspense, manual vendor chunk separation, and strategic prefetching patterns \n Provides recommended vite.conf

Audit and upgrade existing websites to premium design standards without breaking functionality. \n \n Provides a comprehensive design audit checklist covering typography, color, layout, interactivity, content, components, and iconography to identify generic AI patterns and weak points \n Works with any CSS framework (Tailwind, vanilla CSS, styled-components) or tech stack by scanning and improving existing code rather than rewriting from scratch \n Includes strategic upgrade techniques for typog

AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.

Comprehensive Next.js development guidelines covering file structure, RSC patterns, data fetching, optimization, and error handling. \n \n Covers 15+ topic areas including file conventions, route segments, RSC boundaries, async patterns, metadata generation, and image/font optimization \n Provides runtime selection guidance, directive usage, and error handling strategies with specific file conventions like error.tsx and not-found.tsx \n Includes data fetching patterns, route handler best practic

Behavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria. \n \n Emphasizes surfacing assumptions and tradeoffs upfront rather than making silent decisions or hiding confusion \n Advocates for minimum viable code with no speculative features, abstractions, or error handling beyond what was requested \n Requires surgical, focused edits that touch only what's necessary and match existing code style without improving adjacen