expo-docs-skills

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".

Check whether Expo docs environment-setup screenshots (Android Studio, Xcode) still match the locally installed IDEs (advisory report; docs edits and installs only on explicit opt-in; macOS only). MUST USE when the user says "ide screenshot drift", "check env setup screenshots", "are the android studio screenshots outdated", "xcode screenshot drift", or "/ide-screenshot-drift".

Audit the "Built-in environment variables" list on the Expo docs EAS environment-variables usage page against the env definition sites in expo/eas-cli (report only, never edits docs). Use when the user asks whether the built-in EAS Build env vars are outdated, says "eas env drift", "check built-in env vars", or "/docs-eas-env-drift".

Check whether Expo docs screenshots still match the live Expo dashboard (advisory only, never edits docs). MUST USE when the user says "screenshot audit", "check docs screenshots", "are the docs screenshots outdated", "screenshot drift", or "/screenshot-audit". Takes a docs section (e.g. accounts, billing).

Pull weekly traffic and vote metrics for the Expo "Build with AI" tutorial (/tutorial/build-with-ai/) from the docs.expo.dev GA4 property into the expo-tutorial-ai tab of the shared Google Sheet: upsert the current and previous week in a weekly trend (its chart auto-extends) and refresh a 28-day per-page snapshot. Browser-driven because Expo's Workspace blocks GA4/Sheets OAuth apps, so it runs interactively, never headless. MUST USE when the user says "build with ai metrics", "build-with-ai metrics", "ai tutorial metrics", "ai tutorial analytics", or "/docs-build-with-ai-metrics".

Audit `<BoxLink>` icons in an Expo docs PR against the destination-to-icon conventions and stage findings as a private pending GitHub review (never auto-submitted). Use when the user provides a public PR URL and asks to "audit boxlink icons", "review boxlinks", or "check boxlink icons". Icon mismatches only.

Review an Expo docs pull request against the Expo writing style guide and MDX component conventions, and stage the findings as a private pending GitHub review (never auto-submitted). MUST USE when the user provides a GitHub PR URL and says "review this pr", "review this docs pr", "audit this pr", "check this pr against the style guide", or "/docs-review". Public PRs only.

Deterministically validate Expo config plugin examples in the docs against the real plugin option types in the monorepo's packages/. No LLM in the verdict path; the source of truth is the TypeScript type behind each plugin's ConfigPlugin<T>. MUST USE when the user says "config plugin check", "check config plugin examples", "plugin example drift", "are the config plugin examples right", or "/config-plugin-example-check".

Pull weekly traffic and vote metrics for the Japanese (/ja/) Expo docs from the docs.expo.dev GA4 property into a configured Google Sheet: upsert the current and previous week in a weekly trend (its chart auto-extends) and refresh a 28-day per-page snapshot. Browser-driven because Expo's Workspace blocks GA4/Sheets OAuth apps, so it runs interactively, never headless. MUST USE when the user says "ja metrics", "ja docs metrics", "pull ja analytics", "japanese docs traffic", or "/docs-ja-metrics".