What happened
Task: Diagnose a Flutter Web/Supabase password sign-in and recovery failure in a deployed Alpha application.
Skill said: The workflow correctly required current documentation and log checks, but its general troubleshooting guidance did not enforce a strict evidence order before drawing conclusions. We successively attributed the failure to user confirmation, browser privacy/cache behaviour, password mismatch, recovery routing, and finally the compiled Supabase URL.
Expected: Before suggesting credential resets or user-side retries, the workflow should require verification of (1) the exact frontend runtime configuration compiled into the deployed bundle, (2) whether an Auth request reached Supabase logs, (3) the HTTP response from the project Auth endpoint, and (4) whether the browser is actually executing the current deployed asset.
Source
File: SKILL.md
Section: Core Principles > Verify your work and Recover from errors, don't loop
Fix suggestion
Add an Auth troubleshooting evidence ladder: deployed config → network request → Auth logs → user state → credential reset. Explicitly warn that catch-all frontend error handling and stale service workers can make a configuration or deployment fault look like invalid credentials.
What happened
Task: Diagnose a Flutter Web/Supabase password sign-in and recovery failure in a deployed Alpha application.
Skill said: The workflow correctly required current documentation and log checks, but its general troubleshooting guidance did not enforce a strict evidence order before drawing conclusions. We successively attributed the failure to user confirmation, browser privacy/cache behaviour, password mismatch, recovery routing, and finally the compiled Supabase URL.
Expected: Before suggesting credential resets or user-side retries, the workflow should require verification of (1) the exact frontend runtime configuration compiled into the deployed bundle, (2) whether an Auth request reached Supabase logs, (3) the HTTP response from the project Auth endpoint, and (4) whether the browser is actually executing the current deployed asset.
Source
File:
SKILL.mdSection:
Core Principles > Verify your workandRecover from errors, don't loopFix suggestion
Add an Auth troubleshooting evidence ladder: deployed config → network request → Auth logs → user state → credential reset. Explicitly warn that catch-all frontend error handling and stale service workers can make a configuration or deployment fault look like invalid credentials.