amandeepmittal

Apply Expo's documentation writing style. MUST USE when writing or editing .mdx files under expo/docs/pages/ or reviewing prose in docs PRs. Covers voice, tone, punctuation, headings, link text, capitalization, platform order, and the Expo glossary. For MDX component mechanics and props, use docs-components. Does NOT cover API/TSDoc reference style.

Reference for the MDX components and syntax used in expo/docs pages (Terminal, Tabs, Step, SnackInline, ContentSpotlight, callouts, code-block variables). Use when deciding which component fits, checking what props it takes, or diagnosing MDX markup that breaks or renders wrong.

Translate one Expo MDX docs page from English to Japanese, writing to `pages/ja/<same-path>` and wiring it into the docs i18n config. Use when the user asks to translate a docs page to Japanese ("translate to ja", "ja translate").

Check Expo's YouTube channel for new videos not yet listed in docs additional resources. Use when the user wants to find and add recent Expo videos.

Convert displayed PNG/JPG/JPEG screenshots referenced by Expo docs MDX pages to lossy WebP, update their references, verify the converted files, and trash original PNGs/JPGs/JPEGs only when no docs page still references them. Use when asked to convert or optimize PNG screenshots in a file or directory under `expo/docs/pages/`. Do not use for JPEG, SVG, or images outside Expo docs.

Write PR titles and descriptions for Expo docs repository pull requests. Use when the user asks to "write a PR description" or "create a PR" for expo/docs; supports a --short mode that outputs only the How section.

Detect and apply drift between the English Expo tutorial (source of truth) and its Japanese translation under pages/ja/tutorial, via a per-page git-SHA watermark. Edits the working tree for a native-reviewer PR. MUST USE when the user says "sync japanese tutorial", "ja drift", or "/docs-ja-sync".

Review a SKILL.md in this repo against the skill-quality rubric (frontmatter, naming, size, code ratio, house style, references, plus clarity, directiveness, scope) and print an advisory report. Never edits skills. Use when the user says "skill quality", "review this skill", "lint this skill", "is this skill any good", or "/skill-quality". Takes a skill name, path, "all", or "--changed".

Apply consistent React Native + Expo conventions for project structure, Expo Router navigation, theming primitives, icons, sqlite data patterns, safe area handling, and bun/bunx tooling. Use when adding or updating screens, components, navigation, data, or dependencies in Expo/React Native apps so work matches these practices.

Guidance for building, refactoring, and debugging Expo + React Native apps (including Expo Router). Use when wiring screens/layouts, navigation (tab/stack) scaffolding with `_layout.tsx` per group, avoiding unwanted redirects in `app/index.tsx`, theming, data fetching with React Query/fetch, Expo module usage, offline handling, and running local Expo tooling (install/start/lint).

Install and wire @tanstack/react-query in Expo/React Native apps (providers, query client, fetch patterns, and screen usage). Use when adding React Query to a project or extending data fetching patterns.

Create and use iOS simulator development builds with EAS for Expo/React Native apps. Use when setting up simulator-only profiles, building, installing, and running dev clients on iOS simulators.

Migrate editor setup from Cursor to VS Code. Cleans old VS Code data, copies settings/keybindings from Cursor, removes Cursor-specific config keys, and installs all extensions fresh. Use when switching from Cursor to VS Code.