Migrate to Static Config

Migrate React Navigation 7.x or 8.x navigators from JSX-based Dynamic API Navigator and Screen elements to Static API object configuration. Use when converting React Navigation screen trees, static navigation containers, nested navigators, groups, linking/deep-link config, render callbacks, getComponent screens, custom navigators, or static/dynamic API boundaries while preserving behavior and TypeScript types.

23 stars 1 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add react-navigation/skills --skill migrate-to-static-config
Manual install
git clone --depth 1 https://github.com/react-navigation/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/migrate-to-static-config ~/.claude/skills/migrate-to-static-config

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Migrating to Static Config

## Goal

Convert React Navigation navigators from JSX-based dynamic setup to static configuration while preserving behavior, typing, and deep links.

## When to use

You are migrating screens from Dynamic API to the Static API in React Navigation.

## Adaptation policy

Treat the patterns in this skill as canonical starting points, not an exhaustive list. The absence of an exact matching example is not a blocker.

- Map local code to the closest pattern here and adapt it; infer an equivalent when the structure differs.
- Prefer the simplest migration that preserves behavior.
- Keep changes minimal and local, matching the existing code style and React Navigation's intended static API.
- Avoid bespoke abstractions unless the simpler patterns clearly cannot preserve behavior.

## Decision rule

Use this order of preference:

1. Direct static config conversion.
2. Static config plus `.with()` for navigator-level wrappers or dynamic navigator props.
3. Static config plus context for extra screen data that was previously passed through render callbacks.
4. Keep the navigator dynamic only if static config cannot express the screen structure without changing behavior materially.

## When to ask for clarification

Inspect the local code first.
Read the full skill on GitHub

Details

Skill name
migrate-to-static-config
Path
skills/migrate-to-static-config/SKILL.md
Repo updated
26 June 2026

FAQ

What does the Migrate to Static Config skill do?

Migrate React Navigation 7.x or 8.x navigators from JSX-based Dynamic API Navigator and Screen elements to Static API object configuration. Use when converting React Navigation screen trees, static navigation containers, nested navigators, groups, linking/deep-link config, render callbacks, getComponent screens, custom navigators, or static/dynamic API boundaries while preserving behavior and TypeScript types.

How do I install the Migrate to Static Config skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add react-navigation/skills --skill migrate-to-static-config. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Migrate to Static Config popular?

It lives in react-navigation/skills, which has 23 GitHub stars and 1 forks.

Related skills

Upgrade React Navigation

23

react-navigation/skills

Upgrade React Navigation to a new major version (6.x to 7.x or 7.x to 8.x), applying the required breaking changes — peer-dependency and tooling bumps, and renamed or removed navigate, linking, theme, navigator, and screen-option APIs — while preserving navigation behavior.

Frontend & Design

Mne Python Guide

43

NeuroAIHub/awesome_cognitive_and_neuroscience_skills

Domain-validated pipeline guidance for EEG/MEG data analysis using MNE-Python: data loading, preprocessing (filtering, ICA, re-referencing), epoching, ERP/ERF computation, time-frequency decomposition, source localization, decoding/MVPA, statistical testing, simulation, and visualization. Use this skill whenever the user works with EEG/MEG/sEEG/ECoG/NIRS/eye-tracking data in Python, mentions MNE, or needs neurophysiological analysis guidance.

Software Development

ZigStrike

57

javimosch/supercli

Use this skill when the user wants to use ZigStrike for ZigStrike, a powerful Payload Delivery Pipeline developed in Zig, offering a var.

Software DevelopmentIn 1 list

Production Grade

23

a-tokyo/aiworkspace

Principle-engineering posture for production-grade code: reads the repo first, plans before code, matches conventions, pulls latest docs over training recall, and ships the simplest correct change that holds the bar — proper algorithms and data structures, idempotent writes, schema+queries+indexes as one artefact, typed errors, tests in the same diff. Substrate-agnostic; defers to peer skills on their lanes. Use for non-trivial planning, design, implementation, review, or refactoring; RCA and debugging; performance and optimization work; changes touching a database schema, security, infrastruc

Software Development

Xwayland

57

javimosch/supercli

Use this skill when the user wants to use Xwayland, cli tool: xwayland.

Software DevelopmentIn 1 list

Repo to Skill

43

NeuroAIHub/awesome_cognitive_and_neuroscience_skills

Convert a GitHub repository or local codebase into a well-structured Claude Code skill with progressive disclosure. Use this skill whenever the user provides a GitHub URL or local repo path and asks to turn it into a skill, create a skill from a repo, or convert a library/tool/framework into reusable skill documentation. Also trigger when users say things like 'make a skill from this repo', 'turn this codebase into a skill', or 'I want a skill for [library name]'.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.