amandeepmittal

expo-docs-pr

This skill should be used when the user asks to "write a PR description", "create a PR", mentions "PR description", "pull request", or discusses writing PR descriptions for the Expo docs repository.

Web & Frontend Listed

Convert PNG screenshots referenced in local Expo docs `.mdx` pages to lossy WebP, rewrite their `src` references, and trash the original PNGs. PNG-only. MUST USE when the user points at a docs section, directory, glob, or `.mdx` file under `expo/docs/pages/` and asks to "convert images to webp", "optimize docs images", "png to webp", "shrink/compress docs screenshots", "make docs images lighter", or runs "/expo-docs-webp".

expo-writing-style

Apply Expo's documentation writing style and MDX component conventions. MUST USE when writing or editing .mdx files under expo/docs/pages/, reviewing prose or component usage in docs PRs. Covers voice, tone, punctuation, headings, link text, capitalization, platform order, the Expo glossary, AND the MDX component catalog (Terminal, Tabs, Step, BoxLink, SnackInline, APISection, ConfigPluginExample, ProgressTracker, etc.). Does NOT cover API/TSDoc reference style.

Code & Development Listed

expo-docs-boxlink-audit

Audit `<BoxLink>` components in an Expo docs PR and flag mismatches between the Icon prop and the destination URL, then stage findings as a private pending GitHub review (never auto-submitted). MUST USE when the user provides a GitHub PR URL and says "audit boxlink icons", "review boxlinks", "check boxlink icons", or "/expo-docs-boxlink-audit". Public PRs only. Narrow scope: icon mismatches only, not other BoxLink props.

Code & Development Listed

expo-docs-review

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 "/expo-docs-review". Public PRs only.

expo-docs-terminal-audit

Audit local Expo docs `.mdx` files for `<Terminal>` blocks that use a single package-manager command where Expo conventions call for multi-PM variants. MUST USE when the user provides a local `.mdx` file, directory, or glob and asks to "audit terminal commands", "audit multi-pm", "check terminal blocks", "review terminal", or run "/expo-docs-terminal-audit". Reports findings in-session and edits only after explicit user approval.

expo-docs-ja-translator

Translate Expo MDX docs pages from English to Japanese. Use when the user asks to translate a docs page to Japanese, says "translate to ja", "ja translate", "translate this page (to Japanese)", or "/expo-docs-ja-translator". Outputs to `pages/ja/<same-path>` mirroring the English source. Preserves frontmatter keys, JSX tags, code blocks, links, and import statements; translates prose, headings, link text, and string-valued JSX props (title, description, summary).