Build & Fix

Skill Detail

sg-auth-debug

Debug a broken auth flow in a real browser before you start guessing from static code alone.

A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.

Browse skills on GitHub Back to the hub

Problem

What problem this solves

Authentication failures are often hard to diagnose from code review alone because the break only becomes obvious once the browser flow actually runs.

Outcome

What changes when it works

You get a concrete diagnosis of where the auth flow fails across redirects, cookies, callbacks, middleware, provider tokens, Convex session propagation, and post-login behavior.

Why It Matters

What this changes for a solo founder

This skill matters when login bugs are blocking real usage and static inspection keeps producing weak theories instead of evidence.

When to use it

When login, callback, or session behavior is broken in the browser
When an auth bug needs reproduction in a real flow instead of pure code reading
When redirects, cookies, or middleware behavior look suspicious
When Clerk, Google OAuth, YouTube OAuth, Convex auth, or Flutter web auth bridges are involved

What you give it

A failing auth flow, bug report, or repro description
Any environment, provider, URL, or expected behavior details you already know

What you get back

A browser-level diagnosis
Evidence around the exact auth failure point
Stack-specific checks against bundled Clerk, Google OAuth, Convex, Astro, Flutter, Python, and Playwright references
Reusable implementation notes from ContentFlow and TubeFlow auth patterns when relevant
A clearer next fix or verification step

Typical examples

/sg-auth-debug login with Google returns to sign-in page
/sg-auth-debug Clerk callback fails on staging
/sg-auth-debug users authenticate but land on a blank dashboard
/sg-auth-debug Flutter web cannot exchange Clerk session into Convex
/sg-auth-debug YouTube OAuth works in Next.js but fails in Flutter

Limits

Some human-gated steps such as MFA or captcha may limit full automation
Google login through Playwright may require a prepared test account, saved state, or manual handoff when anti-bot checks trigger
Generic public page, visual, console, or network checks belong in sg-browser instead
It diagnoses the failure path; it does not replace the later fix or verification step

Related Skills

See the rest of the loop around this move.

Build & Fix

sg-browser

Open a URL in a real browser and verify one observable non-auth objective.

A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.

Open skill page

Build & Fix

sg-fix

Triage a bug fast, decide whether it is safe to patch now, and route it correctly.

The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.

Open skill page

Plan & Decide

sg-spec

Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.

The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.

Open skill page

Build & Fix

sg-start

Start implementation when the task is ready, and force a stronger path when it is not.

The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.

Open skill page

Audit & Improve

sg-verify

Check whether the work really satisfies the user story, not just whether the code compiles.

A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.

Open skill page

Operate & Ship

sg-prod

Check whether production is actually healthy after a push instead of assuming the deploy tells the truth.

A production verification skill for deployment status, logs, and live health checks after release.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.

Documentation Overview Open skills on GitHub Return to the skills hub