click-path-auditBehavioral audit of UI event handlers. Maps each state action's side effects, then traces every handler call in order to find sequential undo, async races, stale closures, dead paths, and effects that reset what a handler just set. Use when a button or control does nothing or leaves the wrong state
javascriptJavaScript runtime semantics for ESM vs CommonJS, module side effects, promises and the event loop, async ownership and cleanup, browser vs Node/Bun/Deno/edge boundaries, measured performance, and focused JS tests. Use when writing, reviewing, or debugging *.js/*.mjs/*.cjs or runtime behavior of any
reactChange, review, or debug React components: \"this component is slow\", \"this list feels laggy when I type\", \"it re-renders too much\", \"make it faster\", stale state, effect loops, lost state, hydration mismatches. Covers component boundaries, props vs local state, derived values, effects, keys,
tanstackTanStack Query, Router, Form, Table, Virtual, and Start: state ownership, query keys, cache invalidation, loaders, search-param validation, server-driven tables, virtualization, and SSR/hydration boundaries. Use when code imports @tanstack/* or when debugging stale/duplicate data, lost form values,
typescriptTypeScript type-level and compiler work covering tsconfig strictness, narrowing, generics, discriminated unions, declarations and module resolution, public type APIs, runtime validation of unknown data, and type tests. Use when editing *.ts/*.tsx types or tsconfig.json, or fixing tsc errors. Not for
viteVite configuration and build behavior: env variables and what reaches the client bundle, dev vs build vs preview, chunking, library mode, SSR externals, dependency pre-bundling, dev-server proxy, Docker and monorepo access, and slow dev servers, for Vite 7 and 8. Use when editing vite.config.*, debu
vueVue 3 component and state work with the Composition API (script setup), Pinia stores, and Nuxt 4 data fetching and hydration: props, emits and defineModel, composables, ref vs reactive, watchers and cleanup, template refs, SSR safety, and focused component tests. Use when adding, changing, reviewing