expo-docs-terminal-auditlisted

# Expo Docs Terminal Audit Audit `<Terminal>` components in local Expo docs `.mdx` files for single-package-manager commands that should be multi-PM per established Expo conventions. The skill produces an in-session report; after the user reviews, it can apply the suggested conversions directly to the source files. **Single concern: single-PM-to-multi-PM conversions only.** This skill does not check Terminal title, `browserAction`, or any other prop. It does not flag inline prose mentions of package managers outside `<Terminal>` blocks. It does not invent new multi-PM shapes; it uses the patterns Expo already documents. **Local-first. No GitHub.** Operates on `.mdx` files on disk. Does not fetch PRs, write JSON reports, or stage PR comments. The output is an in-session markdown report; edits are applied directly to the file(s) only with explicit user approval. ## When to Use - Auditing a single `.mdx` file (yours or anyone's) for Terminal multi-PM compliance. - Sweeping a directory of `.mdx` files (e.g. `docs/pages/get-started/`) before opening a PR. - Cleaning up legacy single-PM Terminal blocks in a guide you are editing. Not the right tool for: PR-level reviews (use `expo-docs-review` or `expo-docs-boxlink-audit` for those), prose checks (use `expo-writing-style`), or any Terminal check beyond single-vs-multi PM. ## Input A local file path or a directory. - Single file: absolute or repo-relative path to an `.mdx` file. Example: `expo/docs/pages/get-started/create-