upgrade-react-navigation
Upgrade React Navigation from 6.x to 7.x or from 7.x to 8.x.
What this skill does
# Upgrade React Navigation ## Goal Upgrade React Navigation to the next major version and handle all required breaking changes while preserving existing navigation behavior. ## When to use You are upgrading React Navigation major version (6.x -> 7.x or 7.x -> 8.x). ## Adaptation policy Treat the patterns in this skill as canonical starting points, not an exhaustive list. The examples are meant to illustrate the core patterns. When applying this skill to a codebase: - Prefer the simplest migration pattern that preserves behavior. - First try to map the local code to an equivalent of the patterns in this skill. - Do not require an exact matching example in the skill before proceeding. - If the local code differs in structure, infer the closest equivalent pattern and adapt it. - Keep changes minimal and upgrade only the affected code. ## Scope rule Do not treat the absence of an explicit example in this skill as a blocker. Use the guidance here to derive the appropriate migration for the local code. ## When to ask for clarification Inspect the local code first. If, after reading the relevant navigator and the upgrade reference, you cannot determine with high confidence whether an API changed or how to update it, pause and ask the user before editing code. Ask for clarification when: - A navigator uses APIs that are not covered in the official documentation or the upgrade reference. - The upgrade would require assumptions about which behavior changes are acceptable. ## References Check `@react-navigation/native` in `package.json` first. - If `6.x`, read [`references/upgrade-6-to-7.md`](./references/upgrade-6-to-7.md) - If `7.x`, read [`references/upgrade-7-to-8.md`](./references/upgrade-7-to-8.md) Load exactly one reference file unless explicitly comparing versions.
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.