prompt-apilisted

# Prompt API ## Procedures **Step 1: Identify the integration surface** 1. Inspect the workspace for browser entry points, UI handlers, and any existing AI abstraction layer. 2. Execute `node scripts/find-frontend-targets.mjs .` to inventory likely frontend files and existing Prompt API usage when a Node runtime is available. 3. If a Node runtime is unavailable, inspect the nearest `package.json`, HTML entry point, and framework entry files manually to identify the browser app boundary. 4. If the workspace contains multiple frontend apps, prefer the app that contains the active route, component, or user-requested feature surface. 5. If the inventory still leaves multiple plausible frontend targets, stop and ask the user which app should receive the Prompt API integration. 6. If the project is not a browser web app, stop and explain that this skill does not apply. **Step 2: Confirm Prompt API viability** 1. Read `references/prompt-api-reference.md` before writing code. 2. Read `references/examples.md` when the feature needs a spec-valid message shape for text, multimodal, prefix, or tool-enabled sessions. 3. Read `references/compatibility.md` when the feature must support multiple browser generations or decide between native support and polyfills. 4. Read `references/polyfills.md` when the feature needs concrete package installation or backend configuration examples for Prompt API or Task API polyfills. 5. Verify that the feature runs in a secure window context and that the