chrome-extension-authlisted
Install: claude install-skill thomaslimited/chrome-extension-skills
# Chrome Extension Auth
Add sign-in and sessions to a Manifest V3 extension backed by a server. Two proven paths, one
shared session contract.
## Scope
This skill covers: Google SSO (OAuth "Web application" client + `launchWebAuthFlow`), email/password
sign-in, session issuance and verification, extension-side storage and API calls, CORS, rate
limiting, and revocation.
This skill does **not** cover:
- Payments, subscriptions, entitlements → `chrome-extension-payments`
- Chrome Web Store listing content, screenshots, review policy → `chrome-web-store-listing`
- Extension scaffolding, build tooling, content scripts → `chrome-extension-dev`
- Packaging and publishing → `chrome-extension-deploy`
## Decision table
| Situation | Choose | Why |
|---|---|---|
| Want the fastest signup, no password support burden | Google SSO only | No password storage/reset flow to build or secure |
| Users without Google accounts, enterprise, or privacy-sensitive audience | Email/password (or passwordless OTP) | Not everyone has/wants a Google account |
| Want maximum reach, willing to build both | Both, with account linking | Same email can arrive via either path — link, don't duplicate |
| Want passwordless but no OAuth complexity | Email OTP (magic code) | Simpler than full password flow; still needs an email provider |
Both paths **must** converge on the same session contract: a server-issued session JWT, verified
the same way, stored the same way in the extension. Do not build two differ