Setting Up Tauri Projects

Next.js 15 critical performance fixes. Use when writing React components, data fetching, Server Actions, or optimizing bundle size.

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

Tailwind CSS advanced component patterns with CVA (class-variance-authority) and variant management. PROACTIVELY activate for: (1) building reusable component variants with CVA, (2) compound variants for complex states, (3) tailwind-merge for safe class composition, (4) clsx/cn utility for conditional classes, (5) Headless UI / Radix UI primitives styled with Tailwind, (6) shadcn/ui patterns, (7) component slot patterns (asChild), (8) polymorphic components, (9) prop-driven design tokens. Provides: CVA setup recipes, cn utility implementation, compound-variant patterns, shadcn/ui-style component templates, and asChild slot examples.

Guides creation and modification of domain feature systems organized under a systems/ directory. Covers directory layout, API service layer patterns, TanStack Query hooks (queries, mutations, optimistic updates), React context and XState store conventions, hook organization, and public API barrel exports. Use when adding a new domain system, extending an existing one, or fixing bugs in a system-layer codebase. Don't use for generic React component work, backend API implementation, or codebases not organized around a systems/ domain pattern.

Brad Frost's Atomic Design methodology for UI component hierarchies: atoms (indivisible elements), molecules (small groups of atoms), organisms (complex sections of molecules), and templates (page layouts). Enforces bottom-up composition (never skip levels), presentational components (data via props, events via callbacks, no data fetching), design tokens for all visual properties, and composition over inheritance. Use when building user interfaces, creating component libraries, organizing frontend code, designing form systems, or structuring any UI. Triggers on: "build a component", "component hierarchy", "design tokens", "presentational components", "composition over inheritance", "React/Vue/SwiftUI components", "atomic design". Applies to any UI framework.

Generate dynamic social preview images using Next.js file conventions and the next/og library. Server-rendered JSX images cached at build time.