best▌

Type-safe routing patterns, data loading strategies, and navigation best practices for TanStack Router in React. \n \n Covers 33 rules across 10 categories: type safety, route organization, data loading, search params, error handling, navigation, code splitting, preloading, and route context \n Emphasizes type inference through router registration, from parameters, and queryOptions integration to prevent runtime errors \n Includes data loading patterns with TanStack Query integration, deferred d

Guidelines for building high-quality Expo React Native applications with JavaScript, focusing on clean code, modularity, and performance.

Tamagui v1.x patterns beyond fundamentals: Config v4, compiler optimization, compound components, and gotchas.

React and Next.js performance optimization guidelines across 45 rules in 8 priority categories. \n \n Covers critical waterfalls elimination, bundle size optimization, and server-side performance with specific patterns like Promise.all, dynamic imports, and React.cache() \n Includes medium-priority rules for re-render optimization, rendering performance, and JavaScript efficiency with concrete code examples \n Organized by impact level with prefixed rule names (async-, bundle-, server-, client-,

Best Minds \n \n \"Don't think of LLMs as entities but as simulators.\"\n— Andrej Karpathy \n \n 核心 \n 不要问 AI \"你怎么看\"。 \n 要问： 这个问题，世界上谁最懂？TA 会怎么说？ \n 然后模拟那个人。 \n 原则 \n \n 问题决定人数 — 一个人够就一个，需要碰撞才多个 \n 找真正最懂的 — 不是找\"合适的\"，是找\"最强的\" \n 基于真实 — 模拟要基于 TA 公开的思想、著作、言论 \n 引用原话 — 尽可能用 TA 说过的话 \n \n vs ai-coaches \n \n \n \n ai-coaches \n best-minds \n \n \n \n \n 从 13 个预设智者选 \n 从全世界找 \n \n \n 基于关键词匹配 \n 基于问题本质 \n \n \n

Comprehensive performance optimization guide for Angular applications. Contains prioritized rules for eliminating performance bottlenecks, optimizing bundles, and improving rendering.

Expert guidelines for NumPy development, focusing on array programming, numerical computing, and performance optimization.

Vue 3 development with Composition API, <script setup> , and TypeScript as the standard approach. \n \n Enforces a structured workflow: confirm architecture, apply core foundations (reactivity, SFC structure, component focus, data flow, composables), then add optional features only when needed \n Requires reading and applying four core references before implementation: reactivity, SFC structure, component data flow, and composables \n Provides explicit component-splitting rules based on res

VueUse composable patterns, SSR compatibility, and TypeScript integration best practices. \n \n Covers SSR-specific gotchas and patterns for safely using VueUse composables in server-rendered environments \n Addresses common issues with element ref handling and type inference when working with VueUse APIs \n Provides efficiency rules to help debug and resolve VueUse integration problems consistently \n

33 React performance and composition rules across bundle optimization, re-rendering, rendering, hooks, and component patterns. \n \n Covers 6 rule categories: bundle size optimization (barrel imports, conditional loading, preloading), re-render prevention (functional setState, derived state, memoization), rendering performance (content-visibility, hydration, transitions), client patterns (passive listeners, localStorage versioning), hooks best practices (limiting useEffect, named functions), and