frontend▌

Server Components by default, client interactivity on demand, with structured data fetching and caching strategies. \n \n Server Components handle data fetching and static content; Client Components ('use client') manage forms, state, and event handlers. Split responsibilities when both are needed. \n Data fetching uses static caching by default, with ISR (time-based revalidation) and dynamic (no-store) options for different freshness requirements. \n Routing relies on file conventions (page.tsx

Adaptive Flutter layouts that respond to screen size, platform, and input device across mobile, tablet, desktop, and web. \n \n Three-step workflow: abstract common widgets, measure available space with MediaQuery or LayoutBuilder, and branch UI based on width breakpoints (compact <600, medium 600–840, expanded ≥840) \n Covers layout fundamentals including Flutter's constraint system, common patterns (Row, Column, Expanded, Container), and responsive grid/navigation examples \n Best practic

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category. \n \n Covers five state types: local component state, global state, server state, URL state, and form state, with recommended solutions for each \n Includes complete TypeScript patterns for Redux Toolkit slices, Zustand with scalable slice architecture, Jotai atomic state, and React Query with optimistic updates \n Demonstrates combining client state (Zustand) with server state (React Quer

Complete reference for migrating UWP apps to WinUI 3 with before/after code examples. \n \n Maps all namespace changes from Windows.UI.Xaml.* to Microsoft.UI.Xaml.* , plus threading, windowing, and dialog APIs \n Covers the three most common Copilot mistakes: ContentDialog without XamlRoot, MessageDialog usage, and CoreDispatcher patterns \n Includes migration tables for window management, pickers, background tasks, settings, and GetForCurrentView() replacements \n Provides a 15-item migration c

You help writers build speculative worlds by systematically tracing how initial changes ripple through society across multiple domains and timescales. Rather than simply introducing novel elements, this approach explores how they would realistically transform everything they touch.

CSS, JavaScript, and HTML standards for building Shopify Liquid themes with progressive enhancement and design tokens. \n \n BEM naming convention with single-level element nesting, CSS custom properties for all design values, and logical properties for RTL support \n Web Components pattern for component-scoped JavaScript using native browser APIs only; no external dependencies \n Progressive enhancement: semantic HTML first, then CSS, then optional JavaScript enhancements \n Defensive CSS pract

Which rune? Props: $props() | Bindable: $bindable() | Computed: $derived() | Side effect: $effect() | State: $state()

This skill provides a structured workflow for translating Figma designs into production-ready code with pixel-perfect accuracy. It ensures consistent integration with the Figma MCP server, proper use of design tokens, and 1:1 visual parity with designs.

Automated frontend code review against a multi-category checklist, supporting both pending-change and targeted file reviews. \n \n Triggers on user requests to review frontend files ( .tsx , .ts , .js ) and applies a canonical checklist across Code Quality, Performance, and Business Logic categories \n Supports two review modes: pending-change review for staged/working-tree files before commit, and file-targeted review for specific named files \n Flags violations with urgency metadata (Urgent vs

45 React and Next.js performance rules organized by impact, from eliminating waterfalls to advanced patterns. \n \n Covers 8 priority categories spanning async optimization, bundle size, server/client data fetching, re-renders, rendering, JavaScript performance, and advanced patterns \n Each rule includes explanation, before/after code examples, and context; rules prefixed by category (e.g., async- , bundle- , server- ) for easy reference \n Prioritizes critical issues like waterfall elimination