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

Which file? Server-only (DB/secrets): +page.server.ts | Universal (runs both): +page.ts | API: +server.ts

Apple TV is a living room device driven entirely by focus-based navigation and the Siri Remote. There is no pointer, no touch screen, and no mouse. Every design decision must account for the 10-foot viewing distance, the simplicity of the remote, and the lean-back nature of TV consumption.

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

41 performance optimization rules for React Hook Form across form configuration, field subscription, validation, and component integration. \n \n Organized into 8 priority-ranked categories (form configuration and field subscription marked CRITICAL) with prefixed rule identifiers for automated refactoring and code generation \n Covers useForm setup, watch/useWatch patterns, useController isolation, validation resolver caching, useFieldArray best practices, and formState subscriptions \n Includes

Comprehensive UI refactoring guide based on Refactoring UI by Adam Wathan & Steve Schoger, implemented with Tailwind CSS utility classes. Contains 52 rules across 9 categories, prioritized by design impact to guide automated refactoring and code generation. Uses Tailwind CSS v4 syntax (v3 notes provided where syntax differs).

High-level system architecture design, decision documentation, and technology trade-off evaluation for distributed systems. \n \n Guides full architecture workflows from requirements gathering through stakeholder review, with explicit trade-off analysis and failure mode planning \n Produces architecture diagrams (Mermaid format), Architecture Decision Records (ADRs), and technology recommendations with documented rationale \n Covers architectural patterns, microservices structuring, scalability

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.