Set the auth architecture and choose the real persistence layer

Force the AI builder to define and implement a real authentication approach before generating UI.

If your app already uses a stack like Supabase, Firebase Auth, Auth0, Clerk, NextAuth, or a custom backend, tell the builder to use that existing stack instead of inventing a fake one.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Inspect this codebase and implement a real authentication foundation using the existing stack where possible. I need email/password signup, login, logout, session persistence across refresh, protected dashboard routes, duplicate email handling, password reset, loading states, error states, and mobile responsive UI. Do not build placeholder forms. Use a real auth provider or real backend persistence, define where user state lives, define how session restoration works on app load, and wire the routing strategy for protected pages.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

The app has a real auth strategy selected and wired into the project, with a clear user/session state source and route protection plan.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

A real auth provider or backend auth implementation is presentThere is a defined source of truth for current user and session stateThe implementation plan covers signup, login, logout, reset, and route protectionThe solution uses secure password handling rather than storing plaintext passwords

Do not continue if…

! Creating signup and login forms that do not connect to a real auth provider or backend
! Pretending session persistence exists while user state resets on refresh
! Allowing direct access to protected routes by URL when logged out
! Handling duplicate email or invalid credentials only in console logs instead of showing UI errors

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

You built forms without proving real auth integration. Replace any mock auth logic with a real provider or backend implementation for signup, login, logout, session restore, password reset, and protected routes. Show exactly where the real session comes from and remove all fake success redirects.