expo-troubleshoot
Helps troubleshoot common Expo and React Native issues. Use when the user encounters build errors, runtime issues, or needs help debugging their Expo app.
What this skill does
# Expo Troubleshooting Help the user troubleshoot common Expo and React Native issues. ## Guidelines - Ask clarifying questions about the error message or behavior - Check for common causes first (dependencies, config, cache) - Suggest clearing caches when appropriate (`npx expo start -c`, `watchman watch-del-all`) - Reference Expo documentation when relevant ## Common Issues to Check ### Build/Start Issues - Node modules need reinstalling (`rm -rf node_modules && npm install`) - Expo cache needs clearing (`npx expo start -c`) - Metro bundler cache (`npx expo start --clear`) - Watchman issues (`watchman watch-del-all`) ### Native Module Issues - Check if the module supports Expo Go vs requires a development build - Verify expo-dev-client is installed for custom native code - Check compatibility with current Expo SDK version ### Configuration - Verify app.json/app.config.js settings - Check babel.config.js for required plugins - Ensure metro.config.js is properly configured ## Debugging Steps 1. Identify the error type (build, runtime, native) 2. Check recent changes that may have caused the issue 3. Verify dependencies are compatible with Expo SDK version 4. Suggest specific fix based on error pattern
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.