Proofreader API

Procedures

Step 1: Identify the browser integration surface

1. Inspect the workspace for browser entry points, editor or form UI handlers, and any existing built-in AI abstraction layer.
2. Execute node scripts/find-proofreader-targets.mjs . to inventory likely frontend files and existing Proofreader API markers when a Node runtime is available.
3. If a Node runtime is unavailable, inspect the nearest package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary.
4. If the workspace contains multiple frontend apps, prefer the app that contains the active text-entry route, editor component, or user-requested proofreading surface.
5. If the inventory still leaves multiple plausible frontend targets, stop and ask which app should receive the Proofreader API integration.
6. If the project is not a browser web app, stop and explain that this skill does not apply.

Step 2: Confirm API viability and option shape

1. Read references/proofreader-reference.md before writing code.
2. Read references/examples.md when the feature needs session creation, download monitoring, result rendering, or quota-aware preflight.
3. Read references/compatibility.md when preview flags, browser channels, hardware requirements, iframe constraints, or browser-specific option gaps matter.
4. Read references/troubleshooting.md when feature detection, availability, creation, or proofreading fails.
5. Verify that the feature runs in a secure Window context and that the current frame is allowed to use the proofreader permissions-policy feature.
6. Match availability() and create() option shapes exactly, especially for expectedInputLanguages, includeCorrectionTypes, includeCorrectionExplanations, and correctionExplanationLanguage when the target browser supports them.