Index of every page on this site: llms.txt
All skills
Run it yourself

Diagnoses and fixes Expo/React Navigation status bar mismatches. Use when status bar text/icons are hard to read, not matching header/background, flickering between screens, or behaving unexpectedly with transparent headers and safe areas.

  • 1 file
  • 3.2 KB
  • Updated 9 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/david-evans03/skills/expo-status-bar

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈64 tokens for metadata: the name and description. ≈755 when used: this file.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈257 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Expo Status Bar

When To Use

Use this skill when:

  • StatusBar style="auto" looks wrong for a screen.
  • Transparent headers make the top area hard to read.
  • Status bar behavior differs between routes or during navigation.
  • A root StatusBar is not matching what appears on specific screens.

Core Rule

Treat status bar behavior as the result of three layers:

  1. Owner: who controls style (expo-status-bar component vs navigator statusBar* options).
  2. Top background: what color/content is actually behind the status bar.
  3. Safe area layout: whether the top inset is intentionally handled.

Do not assume auto reads your screen background. It follows platform/theme behavior and can still look visually incorrect when the top region is not what you expected.

Troubleshooting Workflow

1) Identify the single source of truth

Check if both of these are set:

  • <StatusBar ... /> in root or screens
  • navigator statusBarStyle, statusBarHidden, or related screen options

If both exist, pick one owner for that flow and remove conflicting overrides.

2) Check transparent header interactions

If headerTransparent: true, content can render behind header/status bar. Then verify:

  • a top-safe-area strategy exists (screen-level SafeAreaView or useSafeAreaInsets top padding),
  • the top region has a deliberate background color (not accidental transparency).

3) Verify background under the status bar

Inspect the top-most rendered container on each affected screen:

  • If top is light, prefer dark status bar content.
  • If top is dark, prefer light status bar content.
  • If dynamic or image-heavy, avoid auto; set explicit per-screen style.

4) Audit route-level differences

Compare affected and unaffected screens for:

  • different wrappers (SafeAreaView, themed containers),
  • different header options,
  • conditional rendering during transitions.

5) Lock a strategy per flow

Pick one:

  • Global strategy: root <StatusBar style="..."> only, no route overrides.
  • Per-route strategy: explicit screen styles based on known background.

Avoid mixing strategies unless there is a clear reason.

Fix Patterns

Pattern A: Global owner

  • Keep one root <StatusBar ... />.
  • Remove navigator statusBar* options.
  • Ensure every screen's top area has predictable contrast.

Pattern B: Per-screen owner

  • Set explicit style per route when backgrounds differ.
  • Keep top safe-area/background consistent with each explicit style.

Pattern C: Transparent header flow

  • Keep header transparent for visual design.
  • Ensure top inset handling in content.
  • Set status bar style intentionally for the onboarding/auth flow if needed.

Quick Checklist

  • Only one status bar owner per flow.
  • headerTransparent screens handle top inset intentionally.
  • Top region behind status bar has intentional background.
  • auto is only used where it consistently looks correct.
  • No hidden per-screen override conflicts.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 6465931. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 9 months ago

README badge

README badge for david-evans03/skills/expo-status-bar