Standardize web app sign-in and account flows with shared session rules, email and Google login adapters, and an optional auth panel. Use the guidance to simplify signup, recovery, and return navigation while keeping native and TV integrations clearly identified as pending validation.
This skill should be used when the user asks to "standardize app authentication", "share login across web, mobile and TV", "reuse the Google login flow", "simplify signup", "fix password recovery", or "fix popup-blocked login". Use shared account/session contracts, email and Google web adapters, and an optional auth panel. Native and TV flows are integration contracts awaiting device validation.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Provide a short returning-user path and a dependable same-tab path. Google and the browser decide whether account selection or reauthentication is required. Do not promise silent login or call a flow fastest without measurements.
error_callback. Do not invent popup-failure detection, retry timers or user-agent rules.The app owns script loading, public client configuration, remembering the successful Google account, sessions, error reporting and navigation. The component owns rendering, pending/error UI and cancelling its credential operation when the auth surface closes.
For architecture standardization, read backend standard. It is a proposed target, not an implemented Go dependency or completed migration.
For web/native/TV clients or another social provider, read platforms and providers. Use one identity store and revocation model per product across its clients. Keep browser cookies and native secure-storage transport distinct.
Read provenance before claiming production coverage. Distinguish a shipped reference, a tested extraction and a pending app integration. Add future components as focused skills with code, integration contracts and behavior tests when an actual app supplies the evidence. Do not add empty catalogs or treat a component PR as permission to deploy another app.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Format responses for readers who benefit from concise, visible steps and low-friction starts. It puts the answer first, breaks work into short numbered actions, tracks progress, and adds brief educational notes around code changes while keeping secondary details separate.
Plan and assess how AI assistants discover and recommend a product to buyers who have not heard of it. Organize buyer questions, review answers and cited sources, identify content or access gaps, and define a repeatable way to measure visibility and customer outcomes.
Use this skill to automate browser tasks such as opening websites, reading page content, clicking controls, filling forms, signing in, extracting data, and taking screenshots. It explains a snapshot-based workflow for interacting with pages and handling tabs and waits.
Build, debug, or review applications built with Cloudflare’s Agents SDK and the `agents` package. It covers agent state, routing, chat, scheduled and durable work, and integrations, while consulting current Cloudflare documentation for implementation details.
Use this skill to plan and build web interfaces with a visual direction tied to the project. It guides choices for color, typography, layout, motion, and interface text, then encourages a review against the brief so the result feels deliberate and specific.
Work with Azure resources through Azure MCP: list and inspect storage, Key Vault, Cosmos DB, and AKS resources, manage secrets, upload blobs, and query Log Analytics. It helps choose the operation that fits the task and requires Azure authentication.