best▌

Comprehensive guidance for building modern ecommerce storefronts with patterns, component architecture, and backend integration. \n \n Covers all storefront components: navigation, product pages, cart, checkout, and account pages across any framework (Next.js, SvelteKit, React, Vue) \n Includes critical accessibility patterns (aria-live for cart updates), mobile optimization (safe-area-inset, 44px touch targets), and SEO requirements (Product schema, Core Web Vitals) \n Provides mandatory backen

Comprehensive guide to implementing structured, secure, and performant logging across applications. Covers log levels, structured logging formats, contextual information, PII protection, and centralized logging systems.

Next.js App Router development patterns covering server/client components, data fetching, and routing. \n \n Server Components are the default; use Client Components only for interactivity (useState, event handlers, forms) \n Data fetching belongs in Server Components with three caching strategies: static (build-time), ISR (time-based revalidation), and dynamic (no-store) \n File conventions organize routes: page.tsx for UI, layout.tsx for shared structure, loading.tsx and error.tsx for states,

Multi-tenant organization setup with member management, role-based access control, and team support via Better Auth. \n \n Configure organizations with customizable creation rules, membership limits, and ownership constraints; creators automatically receive the owner role \n Manage members and invitations with email delivery, expiration windows, and shareable invitation URLs; support multiple roles per member \n Define custom roles and permissions with dynamic access control; check permissions s

Structured logging pattern using wide events for comprehensive request-level debugging and analytics. \n \n Consolidates all request context into a single JSON event per service, emitted at completion, rather than scattering log lines throughout handlers \n Emphasizes high cardinality fields (user IDs, request IDs) and high dimensionality (many fields per event) to enable flexible querying and correlation across services \n Requires business context in every event: subscription tier, cart value,

Vue JSX syntax patterns and migration guidance from React JSX. \n \n Covers attribute naming differences between Vue and React JSX (e.g., class vs className ) \n Includes JSX plugin configuration for Vue projects \n Provides reference material for migrating existing React JSX code to Vue or resolving attribute type errors \n

Vue Router 4 patterns, navigation guards, and route-lifecycle best practices. \n \n Covers five navigation guard patterns including async/await handling, deprecated next() function migration, infinite redirect loops, and param-change detection \n Addresses route-lifecycle gotchas like stale data when navigating between same routes and event listener cleanup on component unmount \n Includes guidance on beforeRouteEnter guard limitations, component instance access, and param-triggered navigation b

120+ performance rules across 18 categories for optimizing Three.js applications. \n \n Organized by priority from fundamental setup (Import Maps, modern renderers) through critical concerns (memory disposal, render loops, draw calls) to specialized topics (WebGPU, TSL shaders, WebXR) \n Covers both WebGLRenderer and WebGPURenderer with guidance on choosing between them and leveraging TSL (Three.js Shading Language) for shader development \n Includes practical rules for geometry batching, materi

Performance optimization and code style patterns for JavaScript and TypeScript code. Contains 17 rules focused on reducing unnecessary computation, optimizing data structures, and maintaining consistent conventions.

Standard Vue 3 workflow with Composition API, <script setup> , and TypeScript as the default approach. \n \n Requires confirming project architecture upfront and reading core references on reactivity, SFCs, component data flow, and composables before implementation \n Enforces minimal source state with ref / reactive , deriving everything possible with computed , and keeping templates declarative \n Mandates component splitting when responsibilities exceed one clear purpose, with entry/root